Bug#1010244: does not work with PHP 8.1
Package: phpsysinfo Version: 3.2.5-3 Severity: grave Tags: upstream phpsysinfo fails with: Fatal error: __autoload() is no longer supported, use spl_autoload_register() instead in /usr/share/phpsysinfo/includes/autoloader.inc.php on line 25 This has been fixed in a more recent upstream release. -- ciao, Marco signature.asc Description: PGP signature
Bug#1008445: golang-v2ray-core: FTBFS: src/github.com/lucas-clemente/quic-go/internal/qtls/go118.go:13:2: cannot find package "github.com/marten-seemann/qtls-go1-18" in any of
Hi Lucas, I cannot reproduce this bug. Is this test be re-tested or will it be tested periodically? I've tried to build it by pbuilder using sid chroot. It builds well. Build log is as attachment. Yours, Paul golang-v2ray-core_4.34.0-5_amd64.build.xz Description: application/xz OpenPGP_signature Description: OpenPGP digital signature
Bug#1009432: marked as done (unburden-home-dir: FTBFS: Config value: 'pages'. Error: The configuration option 'pages' was removed from MkDocs. Use 'nav' instead.)
Your message dated Tue, 26 Apr 2022 22:22:56 + with message-id and subject line Bug#1009432: fixed in unburden-home-dir 0.4.2 has caused the Debian Bug report #1009432, regarding unburden-home-dir: FTBFS: Config value: 'pages'. Error: The configuration option 'pages' was removed from MkDocs. Use 'nav' instead. 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.) -- 1009432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: unburden-home-dir Version: 0.4.1.3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure >dh_auto_build > make -j8 "INSTALL=install --strip-program=true" > make[1]: Entering directory '/<>' > env LC_ALL=C.UTF-8 mkdocs build --clean > ronn --manual="Unburden Your Home Directory" -r --pipe > docs/unburden-home-dir.1.md > unburden-home-dir.1 > [31mERROR- [0mConfig value: 'pages'. Error: The configuration option > 'pages' was removed from MkDocs. Use 'nav' instead. > Aborted with 1 Configuration Errors! > make[1]: *** [Makefile:10: html/index.html] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/04/12/unburden-home-dir_0.4.1.3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: unburden-home-dir Source-Version: 0.4.2 Done: Axel Beckert We believe that the bug you reported is fixed in the latest version of unburden-home-dir, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated unburden-home-dir package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Apr 2022 23:47:06 +0200 Source: unburden-home-dir Architecture: source Version: 0.4.2 Distribution: unstable Urgency: medium Maintainer: Axel Beckert Changed-By: Axel Beckert Closes: 1009432 Changes: unburden-home-dir (0.4.2) unstable; urgency=medium . * Support %i in the FILELAYOUT configuration variable to insert the current numerical user id to allow one using /run/user// as TARGETDIR. * Make documentation of the configuration file easier to grok. * Update "reburden" script link to point to the Wayback Machine. *sigh* * Fix a superfluous whitespace in output (and in the according tests). * Fix wrong file name order in output when creating symlinks after replacing files or directories. * Fix mkdocs deprecation warning by replacing "pages" by "nav". (Closes: #1009432) * Rephrase a comment in Makefile to be more precise. * Drop no more working Travis CI in favour of GitHub Actions. + Switch to using "cover -report codecovbash" instead of "… codecov". * Fix issues under test environments which have set $XDG_CONFIG_HOME. Checksums-Sha1: 4276d573006a5dafff55a4c0c638179317af9ea5 2311 unburden-home-dir_0.4.2.dsc f4302f5a708019cfba479e69f05e5adab9cd3d00 101564 unburden-home-dir_0.4.2.tar.xz 0cbd3b7a4543da3a96f6480fdd6d846ea16663d3 16478 unburden-home-dir_0.4.2_source.buildinfo Checksums-Sha256: b58222469976e3720c96d7282006edfaa769dd31468b2325edb21d37b959f34b 2311 unburden-home-dir_0.4.2.dsc
Bug#1004093: marked as done (haskell-text-icu: FTBFS with ICU 70.1)
Your message dated Tue, 26 Apr 2022 21:19:04 +
with message-id
and subject line Bug#1004093: fixed in haskell-text-icu 0.7.0.1-14.1
has caused the Debian Bug report #1004093,
regarding haskell-text-icu: FTBFS with ICU 70.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1004093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-text-icu
Version: 0.7.0.1-14
Severity: normal
Tags: ftbfs patch
Usertags: ICU70.1
Hi,
Soon I would like to start the ICU 70.1 transition. Your package FTBFS
with this release.
One reason is that since ICU 68.1 it doesn't define TRUE and FALSE
constants. You need to use the C99 / C++ ones which are lowercase
ones.
Another reason is the update to Unicode 14 for which the newer-icu
patch needs to be updated.
Patch is attached to make these easy for you.
Regards,
Laszlo/GCS
diff -Nru a/debian/patches/lowercase_true.patch b/debian/patches/lowercase_true.patch
--- a/debian/patches/lowercase_true.patch 1970-01-01 01:00:00.0 +0100
+++ b/debian/patches/lowercase_true.patch 2022-01-20 18:54:16.0 +0100
@@ -0,0 +1,19 @@
+Description: since ICU 68.1 TRUE and FALSE are no longer defined
+ Use their C99 / C++ analogues, ie use them in lowercase.
+Author: Laszlo Boszormenyi (GCS)
+Forwarded: no
+Last-Update: 2022-01-20
+
+---
+
+--- haskell-text-icu-0.7.0.1.orig/cbits/text_icu.c
haskell-text-icu-0.7.0.1/cbits/text_icu.c
+@@ -305,7 +305,7 @@ int32_t __hs_u_strFoldCase(UChar *dest,
+
+ int32_t __hs_u_strCompareIter(UCharIterator *iter1, UCharIterator *iter2)
+ {
+-return u_strCompareIter(iter1, iter2, TRUE);
++return u_strCompareIter(iter1, iter2, true);
+ }
+
+ UBlockCode __hs_ublock_getCode(UChar32 c)
diff -Nru a/debian/patches/newer-icu b/debian/patches/newer-icu
--- a/debian/patches/newer-icu 2020-08-19 12:06:30.0 +0200
+++ b/debian/patches/newer-icu 2022-01-20 18:54:13.0 +0100
@@ -1,17 +1,22 @@
--- a/Data/Text/ICU/Char.hsc
+++ b/Data/Text/ICU/Char.hsc
-@@ -129,6 +129,10 @@
- | PopDirectionalFormat
- | DirNonSpacingMark
- | BoundaryNeutral
-+ | FirstStrongIsolate
-+ | LeftToRightIsolate
-+ | RightToLeftIsolate
-+ | PopDirectionalIsolate
- deriving (Eq, Enum, Show, Typeable)
-
- instance NFData Direction where
-@@ -357,6 +361,94 @@
+@@ -51,6 +51,7 @@ module Data.Text.ICU.Char
+ , LineBreak_(..)
+ , SentenceBreak_(..)
+ , WordBreak_(..)
++, BidiPairedBracketType_(..)
+ -- * Property value types
+ , BlockCode(..)
+ , Direction(..)
+@@ -66,6 +67,7 @@ module Data.Text.ICU.Char
+ , LineBreak(..)
+ , SentenceBreak(..)
+ , WordBreak(..)
++, BidiPairedBracketType(..)
+ -- * Functions
+ , blockCode
+ , charFullName
+@@ -357,6 +359,48 @@ data BlockCode =
| SoraSompeng
| SundaneseSupplement
| Takri
@@ -57,52 +62,108 @@
+ | OldHungarian
+ | SupplementalSymbolsAndPictographs
+ | SuttonSignwriting
-+ | Adlam
-+ | Bhaiksuki
-+ | CyrillicExtendedC
-+ | GlagoliticSupplement
-+ | IdeographicSymbolsAndPunctuation
-+ | Marchen
-+ | MongolianSupplement
-+ | Newa
-+ | Osage
-+ | Tangut
-+ | TangutComponents
-+ | CJKUnifiedIdeographsExtensionF
-+ | KanaExtendedA
-+ | MasaramGondi
-+ | Nushu
-+ | Soyombo
-+ | SyriacSupplement
-+ | ZanabazarSquare
-+ | ChessSymbols
-+ | Dogra
-+ | GeorgianExtended
-+ | GunjalaGondi
-+ | HanifiRohingya
-+ | IndicSiyaqNumbers
-+ | Makasar
-+ | MayanNumerals
-+ | Medefaidrin
-+ | OldSogdian
-+ | Sogdian
-+ | EgyptianHieroglyphFormatControls
-+ | Elymaic
-+ | Nandinagari
-+ | NyiakengPuachueHmong
-+ | OttomanSiyaqNumbers
-+ | SmallKanaExtension
-+ | SymbolsAndPictographsExtendedA
-+ | TamilSupplement
-+ | Wancho
-+ | Chorasmian
-+ | CjkUnifiedIdeographsExtensionG
-+ | DivesAkuru
-+ | KhitanSmallScript
-+ | LisuSupplement
-+ | SymbolsForLegacyComputing
-+ | TangutSupplement
-+ | Yezidi
deriving (Eq, Enum, Bounded, Show, Typeable)
instance NFData BlockCode where
+@@ -475,6 +519,16 @@ data Bool_ =
+ -- ^ Printable character class.
+ | POSIXXDigit
+ -- ^ Hex digit character class.
++ | Cased
++ -- ^ Cased character class. For lowercase, uppercase and titlecase characters.
++ | CaseIgnorable
++ -- ^ Used in context-sensitive case mappings.
++ | ChangesWhenLowercased
++ | ChangesWhenUppercased
++ | ChangesWhenTitlecased
++ | ChangesWhenCasefolded
++ | ChangesWhenCasemapped
++ | ChangesWhenNFKCCasefolded
+ deriving (Eq, Enum, Show, Typeable)
+
+ instance NFData Bool_ where
+@@ -678,6
Bug#1004093: haskell-text-icu: diff for NMU version 0.7.0.1-14.1
Dear maintainer,
since this package is currently involved in the icu transition, I've
prepared an NMU for haskell-text-icu (versioned as 0.7.0.1-14.1). The
diff is attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru haskell-text-icu-0.7.0.1/debian/changelog haskell-text-icu-0.7.0.1/debian/changelog
--- haskell-text-icu-0.7.0.1/debian/changelog 2020-08-19 12:06:30.0 +0200
+++ haskell-text-icu-0.7.0.1/debian/changelog 2022-04-26 23:04:25.0 +0200
@@ -1,3 +1,11 @@
+haskell-text-icu (0.7.0.1-14.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Apply patch from László Böszörményi to build with icu 70.1 (Closes:
+#1004093)
+
+ -- Sebastian Ramacher Tue, 26 Apr 2022 23:04:25 +0200
+
haskell-text-icu (0.7.0.1-14) unstable; urgency=medium
* Patch for Unicode 11.0, 12.0, and 13.0 (Closes: #962402)
diff -Nru haskell-text-icu-0.7.0.1/debian/patches/lowercase_true.patch haskell-text-icu-0.7.0.1/debian/patches/lowercase_true.patch
--- haskell-text-icu-0.7.0.1/debian/patches/lowercase_true.patch 1970-01-01 01:00:00.0 +0100
+++ haskell-text-icu-0.7.0.1/debian/patches/lowercase_true.patch 2022-04-26 23:04:13.0 +0200
@@ -0,0 +1,19 @@
+Description: since ICU 68.1 TRUE and FALSE are no longer defined
+ Use their C99 / C++ analogues, ie use them in lowercase.
+Author: Laszlo Boszormenyi (GCS)
+Forwarded: no
+Last-Update: 2022-01-20
+
+---
+
+--- haskell-text-icu-0.7.0.1.orig/cbits/text_icu.c
haskell-text-icu-0.7.0.1/cbits/text_icu.c
+@@ -305,7 +305,7 @@ int32_t __hs_u_strFoldCase(UChar *dest,
+
+ int32_t __hs_u_strCompareIter(UCharIterator *iter1, UCharIterator *iter2)
+ {
+-return u_strCompareIter(iter1, iter2, TRUE);
++return u_strCompareIter(iter1, iter2, true);
+ }
+
+ UBlockCode __hs_ublock_getCode(UChar32 c)
diff -Nru haskell-text-icu-0.7.0.1/debian/patches/newer-icu haskell-text-icu-0.7.0.1/debian/patches/newer-icu
--- haskell-text-icu-0.7.0.1/debian/patches/newer-icu 2020-08-19 12:06:30.0 +0200
+++ haskell-text-icu-0.7.0.1/debian/patches/newer-icu 2022-04-26 23:04:13.0 +0200
@@ -1,17 +1,22 @@
--- a/Data/Text/ICU/Char.hsc
+++ b/Data/Text/ICU/Char.hsc
-@@ -129,6 +129,10 @@
- | PopDirectionalFormat
- | DirNonSpacingMark
- | BoundaryNeutral
-+ | FirstStrongIsolate
-+ | LeftToRightIsolate
-+ | RightToLeftIsolate
-+ | PopDirectionalIsolate
- deriving (Eq, Enum, Show, Typeable)
-
- instance NFData Direction where
-@@ -357,6 +361,94 @@
+@@ -51,6 +51,7 @@ module Data.Text.ICU.Char
+ , LineBreak_(..)
+ , SentenceBreak_(..)
+ , WordBreak_(..)
++, BidiPairedBracketType_(..)
+ -- * Property value types
+ , BlockCode(..)
+ , Direction(..)
+@@ -66,6 +67,7 @@ module Data.Text.ICU.Char
+ , LineBreak(..)
+ , SentenceBreak(..)
+ , WordBreak(..)
++, BidiPairedBracketType(..)
+ -- * Functions
+ , blockCode
+ , charFullName
+@@ -357,6 +359,48 @@ data BlockCode =
| SoraSompeng
| SundaneseSupplement
| Takri
@@ -57,52 +62,108 @@
+ | OldHungarian
+ | SupplementalSymbolsAndPictographs
+ | SuttonSignwriting
-+ | Adlam
-+ | Bhaiksuki
-+ | CyrillicExtendedC
-+ | GlagoliticSupplement
-+ | IdeographicSymbolsAndPunctuation
-+ | Marchen
-+ | MongolianSupplement
-+ | Newa
-+ | Osage
-+ | Tangut
-+ | TangutComponents
-+ | CJKUnifiedIdeographsExtensionF
-+ | KanaExtendedA
-+ | MasaramGondi
-+ | Nushu
-+ | Soyombo
-+ | SyriacSupplement
-+ | ZanabazarSquare
-+ | ChessSymbols
-+ | Dogra
-+ | GeorgianExtended
-+ | GunjalaGondi
-+ | HanifiRohingya
-+ | IndicSiyaqNumbers
-+ | Makasar
-+ | MayanNumerals
-+ | Medefaidrin
-+ | OldSogdian
-+ | Sogdian
-+ | EgyptianHieroglyphFormatControls
-+ | Elymaic
-+ | Nandinagari
-+ | NyiakengPuachueHmong
-+ | OttomanSiyaqNumbers
-+ | SmallKanaExtension
-+ | SymbolsAndPictographsExtendedA
-+ | TamilSupplement
-+ | Wancho
-+ | Chorasmian
-+ | CjkUnifiedIdeographsExtensionG
-+ | DivesAkuru
-+ | KhitanSmallScript
-+ | LisuSupplement
-+ | SymbolsForLegacyComputing
-+ | TangutSupplement
-+ | Yezidi
deriving (Eq, Enum, Bounded, Show, Typeable)
instance NFData BlockCode where
+@@ -475,6 +519,16 @@ data Bool_ =
+ -- ^ Printable character class.
+ | POSIXXDigit
+ -- ^ Hex digit character class.
++ | Cased
++ -- ^ Cased character class. For lowercase, uppercase and titlecase characters.
++ | CaseIgnorable
++ -- ^ Used in context-sensitive case mappings.
++ | ChangesWhenLowercased
++ | ChangesWhenUppercased
++ | ChangesWhenTitlecased
++ | ChangesWhenCasefolded
++ | ChangesWhenCasemapped
++ | ChangesWhenNFKCCasefolded
+ deriving (Eq, Enum, Show, Typeable)
+
+ instance NFData Bool_ where
+@@ -678,6 +732,37 @@ data JoiningGroup =
+ | Khaph
+ | Zhain
+ | BurushaskiYehBarree
++ | FarsiYeh
++ | Nya
++ | RohingyaYeh
++ | ManichaeanAleph
++ | ManichaeanAyin
++ | ManichaeanBeth
++ | ManichaeanDaleth
++ | ManichaeanDhamedh
++ | ManichaeanFive
++ | ManichaeanGimel
++
Bug#965756: marked as done (oneliner-el: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 26 Apr 2022 21:03:56 + with message-id and subject line Bug#965756: fixed in oneliner-el 0.3.6-9.2 has caused the Debian Bug report #965756, regarding oneliner-el: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: oneliner-el Version: 0.3.6-8 Severity: normal Usertags: compat-5-6-removal Hi, The package oneliner-el uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: oneliner-el Source-Version: 0.3.6-9.2 Done: Guilherme de Paula Xavier Segundo We believe that the bug you reported is fixed in the latest version of oneliner-el, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilherme de Paula Xavier Segundo (supplier of updated oneliner-el 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: Thu, 21 Apr 2022 11:01:29 -0300 Source: oneliner-el Architecture: source Version: 0.3.6-9.2 Distribution: unstable Urgency: medium Maintainer: OHURA Makoto Changed-By: Guilherme de Paula Xavier Segundo Closes: 965756 Changes: oneliner-el (0.3.6-9.2) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the '-k' option is not supported since compat 12. - Closes: #965756 Checksums-Sha1: 0220591b211525c953fdbc7396270248872a6819 1742 oneliner-el_0.3.6-9.2.dsc 95b5a57fa16b7eb2345487ef59928b61e6c24422 35440 oneliner-el_0.3.6-9.2.diff.gz 1f8cc420d72c22aac9ee43bbce764d6788d300cd 5709 oneliner-el_0.3.6-9.2_source.buildinfo Checksums-Sha256: 8977afa58516798bcff84e8ed5ba9e44be593169b25bb9dc59101959e5d19ff1 1742 oneliner-el_0.3.6-9.2.dsc f1a2f49eb59f43423b64c7dff5e8dd6d1f0cfd9fc562d7f5aad51590eeb7b310 35440 oneliner-el_0.3.6-9.2.diff.gz eb4cdd9642dca48fb235be8f713b360aa772428bf0bc3024755968484ab135bf 5709 oneliner-el_0.3.6-9.2_source.buildinfo Files: 2fe4eb97f2fbce70d9a311a618b1d8a3 1742 editors optional oneliner-el_0.3.6-9.2.dsc a682764fc62e04fefff5712cc90d6027 35440 editors optional oneliner-el_0.3.6-9.2.diff.gz 8240e5f2b8c136562762f9e5343d432a 5709 editors optional oneliner-el_0.3.6-9.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJhvfYACgkQ3mO5xwTr 6e9IwA/+J+Uymvv3YYGz5TnsSMvhkLydexEC+QWimeKQXRDkKk0tCGg7ZNXrTYrJ u+NN5Nnw+A+GdUB4yPWOwjnW6qk6xzCaMtpt25Yy722VLrygEca9aot99NN3mKgR CVHJ/rXNYGlCwzfY+mMUCwUpW8fNiDrGRZ9e+k1GzR8Gk7XQXAMQHDawByEPGUOT Xx7eg5fNUyBlCfSPbF3AkK7KeivZXVpGCjSK/zSY6mD8x075QTsT6VxX7j3wTj6U D2fairYeOxTgtLZ0WSVjFe1FvJLB0zGqCdoxX0JJNlSGxzaHpNMBhZYqDfBcamUJ geVjNxsBxm+gCr/SwCcJ6uy7ssxB4MtIgVsH5eQ/nmyBag9Y5ahUQlz8hY3tnZtT
Bug#965738: marked as done (mylvmbackup: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 26 Apr 2022 20:50:44 + with message-id and subject line Bug#965738: fixed in mylvmbackup 0.15-1.2 has caused the Debian Bug report #965738, regarding mylvmbackup: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mylvmbackup Version: 0.15-1.1 Severity: normal Usertags: compat-5-6-removal Hi, The package mylvmbackup uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: mylvmbackup Source-Version: 0.15-1.2 Done: Guilherme de Paula Xavier Segundo We believe that the bug you reported is fixed in the latest version of mylvmbackup, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilherme de Paula Xavier Segundo (supplier of updated mylvmbackup 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: Thu, 21 Apr 2022 10:42:15 -0300 Source: mylvmbackup Architecture: source Version: 0.15-1.2 Distribution: unstable Urgency: medium Maintainer: Debian MySQL Maintainers Changed-By: Guilherme de Paula Xavier Segundo Closes: 965738 Changes: mylvmbackup (0.15-1.2) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965738 Checksums-Sha1: d22c602f546a3b1384bd3ffadff0c1816ae068bd 1981 mylvmbackup_0.15-1.2.dsc df1fe81742fe51940f36b6ffbd3f4b9f7a0a629c 4704 mylvmbackup_0.15-1.2.debian.tar.xz 8f44dc625d55c1552ef2955947f6f6d8e83223b6 6338 mylvmbackup_0.15-1.2_source.buildinfo Checksums-Sha256: b91b981aae7e08aa040a148c31222e5ae820ecfe237afb04876a9b1147b171ec 1981 mylvmbackup_0.15-1.2.dsc 422f13ecb11b30eb70e57f7563a085ccc1b36e91f093f59a6720cd97da5efbdd 4704 mylvmbackup_0.15-1.2.debian.tar.xz efcc838848191e517548c9af1d50447c992dbbcf81a9c100088b11ffcd590e3d 6338 mylvmbackup_0.15-1.2_source.buildinfo Files: d6c8d14231d6055d1b8364907942c3e6 1981 misc extra mylvmbackup_0.15-1.2.dsc 40f769f3039ac6f0d219dd8091384bea 4704 misc extra mylvmbackup_0.15-1.2.debian.tar.xz a826560d32bb72f6fc5879aa5cf2d4a7 6338 misc extra mylvmbackup_0.15-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJhuesACgkQ3mO5xwTr 6e+NBg//btkCCrgH/55+fiEdTdzfd9bYFHLauS3R50Su9uXqxa9NNbZF08d1M+XF UBGV0SKC91rJNNL8nJBEVEOLdyQ6szjV49lubtEZisJucGdAcUgFl0B38KgZ8BBi 75GDf6N6/DHBWz8MYvNxxUUyVw8TqdjmgfqKZqii8+LAQsbWSJJx6lFvgG5iEksr BV21QUcfD6h1M1qyeHzx3RhV8RAY2urUd3HIGVdlSxNp+RZv6q8ZshlJsifJRvmX xrUoxz7zuLKWUtoHVKZHn4phi7WeF25sXluSOs3R1TC4q/M0z6NmFg00KnwORlk2 kLY2Lfs5/xGkSQqOV8DtQueHSbCKc0unCYjK7I4O3ICqCCFbUrBdR/h2aqgE+80c 9MzJM9NLC9jhvBqAzi35AEmaU9PQYT/P3qaAfYdv3fvlw+qLAxJjq8GNrk5OaEzT FoF02d3cUwdtGg8rCkPjMpK5ceN+vH+gUYxEGYT/5L4wZ/toP7syf2my8ABpM/nu
Bug#965608: marked as done (jpegpixi: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 26 Apr 2022 20:48:52 + with message-id and subject line Bug#965608: fixed in jpegpixi 1.1.1-5 has caused the Debian Bug report #965608, regarding jpegpixi: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jpegpixi Version: 1.1.1-4.1 Severity: normal Usertags: compat-5-6-removal Hi, The package jpegpixi uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: jpegpixi Source-Version: 1.1.1-5 Done: Guilherme de Paula Xavier Segundo We believe that the bug you reported is fixed in the latest version of jpegpixi, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilherme de Paula Xavier Segundo (supplier of updated jpegpixi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 Apr 2022 09:32:15 -0300 Source: jpegpixi Architecture: source Version: 1.1.1-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Guilherme de Paula Xavier Segundo Closes: 965608 Changes: jpegpixi (1.1.1-5) unstable; urgency=medium . * QA upload. * Migrations: - CDBS to DH. - Copyright to 1.0 format. - DebSrc to 3.0. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in - debian/docs: added 'AUTHORS' to install documentation. Build-Depends field and bumped level to 13. - Closes: #965608 * debian/clean: created to remove files generated from the build process. * debian/control: - Added Vcs-* field. - Added 'Rules-Requires-Root: no' to source stanza. - Bumped Standards-Version to 4.6.0. - Set Debian QA Group as maintainer. (see: #929538) * debian/patches/010_fix-groff-wrong-macro.patch: created to fix a macro error in a translation file. * debian/rules: added DEB_BUILD_MAINT_OPTIONS variable to improve GCC hardening. * debian/salsa-ci.yml: added to provide CI tests for Salsa. * debian/source/include-binaries: added to allow binarie in CI tests. * debian/source/options: created to ignore changes in po/. * debian/tests/control: added new tests. * debian/watch: updated using a fake site to explain about the current status of the original upstream homepage. Checksums-Sha1: 17c611b69dbeef5e6f095ee470131e3eac198ded 1878 jpegpixi_1.1.1-5.dsc 44257ad683e29b84c22660ca53622bdd084e59c7 4804 jpegpixi_1.1.1-5.debian.tar.xz b92ffa83bf1664aa33cb45dc6041e030edad179d 5752 jpegpixi_1.1.1-5_source.buildinfo Checksums-Sha256: e77715f8cacb2aac06271e43fd5bfe79eb3d009bfb54b153813d003d54b0454b 1878 jpegpixi_1.1.1-5.dsc ba943ea9f1264c55a92d517987935645530f857dcdc87fb2cadff5569fe5df19 4804 jpegpixi_1.1.1-5.debian.tar.xz 725de97b6d4ef3c6910017de1237750ada57f6afa51dff453afac37d0499a59f 5752
Bug#1008907: marked as done (pipewire: Pipewire.service dump at start, status=11/SEGV after upgrade 0.3.49-1)
Your message dated Tue, 26 Apr 2022 20:34:36 + with message-id and subject line Bug#1008907: fixed in pipewire 0.3.50-2 has caused the Debian Bug report #1008907, regarding pipewire: Pipewire.service dump at start, status=11/SEGV after upgrade 0.3.49-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1008907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pipewire Version: 0.3.49-1 Severity: grave Justification: renders package unusable Dear Maintainer, 2022-04-03 13:26:47 upgrade pipewire:i386 0.3.48-1 0.3.49-1 No sound and no speaker symbol visible. Apr 3 14:02:25 debian wireplumber[755]: Failed to set scheduler settings: Operation not permitted Apr 3 14:02:27 debian dbus-daemon[763]: [session uid=117 pid=763] Successfully activated service 'org.gtk.vfs.Daemon' Apr 3 14:02:27 debian systemd[672]: Started Virtual filesystem service. Apr 3 14:02:27 debian bluetoothd[531]: Player registered: sender=:1.33 path=/media_player0 Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/ldac Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptx_hd Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_hd Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptx Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/sbc Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/sbc Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/sbc_xq Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/sbc_xq Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_1 Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_0 Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream_duplex Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 5 threads of 3 processes of 1 users. Apr 3 14:02:30 debian rtkit-daemon[785]: Successfully made thread 1070 of process 753 owned by '117' RT at priority 5. Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 6 threads of 3 processes of 1 users. Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 6 threads of 3 processes of 1 users. Apr 3 14:02:30 debian rtkit-daemon[785]: Successfully made thread 1071 of process 753 owned by '117' RT at priority 5. Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 7 threads of 3 processes of 1 users. Apr 3 14:02:31 debian systemd[672]: Started Sound Service. Apr 3 14:02:32 debian gnome-session[1046]: gnome-session-binary[1046]: GLib- GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 3 14:02:32 debian gnome-session[1046]: gnome-session-binary[1046]: GLib- GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 3 14:02:32 debian gnome-session-binary[1046]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 3 14:02:32 debian gnome-session-binary[1046]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 3 14:02:35 debian bluetoothd[531]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down Apr 3 14:02:38 debian kernel: [ 92.842352] pipewire[752]: segfault at 1 ip b5aaf5da sp bfdedb30 error 4 in libspa-alsa.so[b5a7d000+7d000] Apr 3 14:02:38 debian kernel: [ 92.842386] Code: 47 0c 83 c0 08 89 47 0c 8b 47 14 85 c0 74 0b 90 83 00 08 8b 40 08 85 c0 75 f6 89 f3 8b 03 89 44 24 08 85 c0 0f 84 34 23 00 00 <0f> b6 00 88 44 24 1b 3c 3f 0f 84 87 16 00 00 83 c3 04 31 d2 89 54 Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33
Bug#1005505: marked as done (accountsservice: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpvj3vxj0b/testfile.c:17: undefined reference to `setutxdb')
Your message dated Tue, 26 Apr 2022 16:35:58 -0400 with message-id and subject line Re: accountsservice: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpvj3vxj0b/testfile.c:17: undefined reference to `setutxdb' has caused the Debian Bug report #1005505, regarding accountsservice: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpvj3vxj0b/testfile.c:17: undefined reference to `setutxdb' 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.) -- 1005505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: accountsservice Version: 0.6.55-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /tmp/ccAdzkTL.o: in function `main': > ./obj-x86_64-linux-gnu/meson-private/tmpvj3vxj0b/testfile.c:17: undefined > reference to `setutxdb' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2022/02/12/accountsservice_0.6.55-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 22.07.5-1--- End Message ---
Bug#965460: marked as done (cli-common: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 26 Apr 2022 20:33:55 + with message-id and subject line Bug#965460: fixed in cli-common 0.10+nmu1 has caused the Debian Bug report #965460, regarding cli-common: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cli-common Version: 0.10 Severity: normal Usertags: compat-5-6-removal Hi, The package cli-common uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: cli-common Source-Version: 0.10+nmu1 Done: Guilherme de Paula Xavier Segundo We believe that the bug you reported is fixed in the latest version of cli-common, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilherme de Paula Xavier Segundo (supplier of updated cli-common 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: Thu, 21 Apr 2022 09:30:10 -0300 Source: cli-common Architecture: source Version: 0.10+nmu1 Distribution: unstable Urgency: medium Maintainer: Debian Mono Group Changed-By: Guilherme de Paula Xavier Segundo Closes: 965460 Changes: cli-common (0.10+nmu1) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965460 Checksums-Sha1: 3fc885639c6d6716f9fc419b483597a2379c2b0f 1909 cli-common_0.10+nmu1.dsc ce1c09fb71fc8670e7dcd0886a36e55469d4eabc 42282 cli-common_0.10+nmu1.tar.gz 8dfdbf97a59b483699df32e33face8a469ac0344 5677 cli-common_0.10+nmu1_source.buildinfo Checksums-Sha256: 6e51e8b01410beae3f228e74d4c74940e21badc24391846a20485623e8dccae1 1909 cli-common_0.10+nmu1.dsc 046edafe8caf0ddedb990c97eace303bcc3f6e2299f75a282e0de1a49fcef178 42282 cli-common_0.10+nmu1.tar.gz 778ab17df9f45ba126a0383e30511a0e1c5063564f51f01136ae0c624f5ae08c 5677 cli-common_0.10+nmu1_source.buildinfo Files: 18fa80e5788869ea86c753dce4880d94 1909 cli-mono optional cli-common_0.10+nmu1.dsc d09576bc91955c7b217a88b059119662 42282 cli-mono optional cli-common_0.10+nmu1.tar.gz 1e9b085623a20549f0eccc8979ec4e12 5677 cli-mono optional cli-common_0.10+nmu1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJhtOgACgkQ3mO5xwTr 6e+EaA//YXA7+Yw0KN3A3I0G21BOyfOulDSLvWnI0ooGC1/RP8z10kR2PkN9croq KBLhbZV3OWj6tvk105GMtF+TtLpRzoa3bsb7sMNzxpOa3YNXkFVfmXxaPsLrnjaU B3i0W0rQRXPLVxZwpYXY2wQojHM7Aa8OhcvqfvEmHd2TYBhCBHLznBUmVIPB+1mY tywes5rJkT74skMGCmrL8B7H8iSeTZU8X6SZDjFU65pxn2nRq8PqlpTa1MaOmmnY Fb0GmmofwiEvL+OpjSIcg8Dlx+ksYzy3VNtM0Cps7jJ/Ye4mewS9QNtoLMhK1QFS jJQ5LtR8aiBD03atAECfNgw9sKYr8gwYLKF08m6AImoVV0sbfvXr04pptLX1SIq7 iz6XsFYCYMifEGIgif/Y0u/u6IeKJYCNMnSUeiPX2RPcRYCXcSqHvKOfKpCoqAa3 IW2vnjwtJkyxI5WNnKtVgYVyYhUzLDB+VuegYrQ5WfjSDUIDtsmasE/7wBL1vfxc
Bug#1010236: xye: Xye is stuck in an infinite loop on arm
Package: xye Version: 0.12.2+dfsg-9 Severity: grave Justification: renders package unusable X-Debbugs-Cc: krzpyrk...@gmail.com Dear Maintainer, Xye relies heavily on x86 specific feature which is signedness of char type. It builds without errors on armhf and arm64 (and possibly other architectures that are affected) but hangs in an infinite loop as soon as "Play" button is pressed. The reason for that is internally all xy coordinates are represented not by int, but a char. On x86, subtracting 1 from 0 results in -1, on arm 255. This is a root of the problem. Some examples: src/xye.cpp:1234 for (j=XYE_VERT-1;j>=0;j--) // j reaches 255 on arm src/xye:1874 dx= (dx>=XYE_HORZ)?0:(dx<0)?XYE_HORZ-1:dx; // dx is never going to be less that 0, we can't walk through map's edges I've spent a while trying to replace chars with ints here and there but I gave up after seeing how this platform-specific oddity is deeply embedded in the code. Initially I managed to get "Play" button to work, but the minions did not move. Levels containing teleporters were getting stuck in an infinite loop. I've tried building the program with clang, enabling it's magnificent -fsanitize=integer feature, that detects (among other things) char overflows. The log was all red. The proposed solution is to enforce -fsigned-char in CFLAGS and CXXFLAGS. The program worked out of the box, all the issues I've encountered so far are gone. Tested on armhf and arm64.
Processed: Bug#1008907 marked as pending in pipewire
Processing control commands: > tag -1 pending Bug #1008907 [pipewire] pipewire: Pipewire.service dump at start, status=11/SEGV after upgrade 0.3.49-1 Added tag(s) pending. -- 1008907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008907: marked as pending in pipewire
Control: tag -1 pending Hello, Bug #1008907 in pipewire 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/utopia-team/pipewire/-/commit/3c1703098cca37b633981d0bbd8f6ca96345373b Add an upstream patch to fix argument type (Closes: #1008907) (this message was generated automatically) -- Greetings https://bugs.debian.org/1008907
Bug#1009418: marked as done (autokey: FTBFS: dh_missing: warning: usr/lib/python3.10/dist-packages/autokey/__pycache__/__init__.cpython-310.pyc exists in debian/tmp but is not installed to anywhere)
Your message dated Tue, 26 Apr 2022 19:18:47 + with message-id and subject line Bug#1009418: fixed in autokey 0.95.10-2.1 has caused the Debian Bug report #1009418, regarding autokey: FTBFS: dh_missing: warning: usr/lib/python3.10/dist-packages/autokey/__pycache__/__init__.cpython-310.pyc exists in debian/tmp but is not installed to anywhere 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.) -- 1009418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: autokey Version: 0.95.10-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > chmod a-x debian/autokey-common/usr/share/icons/*/*/*/*.svg > make[1]: Leaving directory '/<>' >dh_missing -O--buildsystem=pybuild > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/__init__.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/common.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/configmanager.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/configmanager_constants.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/gtkapp.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/interface.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/macro.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/model.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/monitor.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/qtapp.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/scripting.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/scripting_Store.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/scripting_highlevel.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/__pycache__/service.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/iomediator/__pycache__/__init__.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/iomediator/__pycache__/_iomediator.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/iomediator/__pycache__/_keygrabber.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/iomediator/__pycache__/_waiter.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/iomediator/__pycache__/_windowgrabber.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/iomediator/__pycache__/constants.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3.10/dist-packages/autokey/iomediator/__pycache__/key.cpython-310.pyc > exists in debian/tmp but is not installed to anywhere > dh_missing: error: missing files, aborting > The following debhelper tools have
Bug#1010231: android-platform-tools dropped symbols (at least causes autopkgtest regression inandroid-platform-art)
Source: android-platform-tools Control: found -1 android-platform-tools/29.0.6-9 Control: affects -1 src:android-platform-art Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks Dear maintainer(s), With a recent upload of android-platform-tools the autopkgtest of android-platform-art fails in testing when that autopkgtest is run with the binary packages of android-platform-tools from unstable. It passes when run with only packages from testing. In tabular form: passfail android-platform-tools from testing29.0.6-9 android-platform-art from testing10.0.0+r36-5 all others from testingfrom testing I copied some of the output at the bottom of this report. Looking at the error, it seems the library dropped a symbol. That needs to be handled by bumping SONAME and going through a library transition. I might be wrong reading the signs thought. Currently this regression is blocking the migration of android-platform-tools to testing [1]. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=android-platform-tools https://ci.debian.net/data/autopkgtest/testing/amd64/a/android-platform-art/21177056/log.gz all.dex /usr/bin/dexdump2: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/all.xml which is empty failed: /usr/bin/dexdump2 -e -l xml all.dex /usr/bin/dexlist: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/all.lst which is empty failed: /usr/bin/dexlist all.dex /usr/bin/dexdump2: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/all.txt which is empty failed: /usr/bin/dexdump2 -adfh all.dex bytecodes.dex /usr/bin/dexdump2: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/bytecodes.xml which is empty failed: /usr/bin/dexdump2 -e -l xml bytecodes.dex /usr/bin/dexlist: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/bytecodes.lst which is empty failed: /usr/bin/dexlist bytecodes.dex /usr/bin/dexdump2: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/bytecodes.txt which is empty failed: /usr/bin/dexdump2 -adfh bytecodes.dex checkers.dex /usr/bin/dexdump2: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/checkers.xml which is empty failed: /usr/bin/dexdump2 -e -l xml checkers.dex /usr/bin/dexlist: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/checkers.lst which is empty failed: /usr/bin/dexlist checkers.dex /usr/bin/dexdump2: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/checkers.txt which is empty failed: /usr/bin/dexdump2 -adfh checkers.dex const-method-handle.dex /usr/bin/dexdump2: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/const-method-handle.xml which is empty failed: /usr/bin/dexdump2 -e -l xml const-method-handle.dex /usr/bin/dexlist: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/const-method-handle.lst which is empty failed: /usr/bin/dexlist const-method-handle.dex /usr/bin/dexdump2: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/const-method-handle.txt which is empty failed: /usr/bin/dexdump2 -adfh const-method-handle.dex invoke-custom.dex /usr/bin/dexdump2: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/invoke-custom.xml which is empty failed: /usr/bin/dexdump2 -e -l xml invoke-custom.dex /usr/bin/dexlist: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/invoke-custom.lst which is empty failed: /usr/bin/dexlist invoke-custom.dex /usr/bin/dexdump2: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: Crc64GenerateTable cmp: EOF on /tmp/test-1496/invoke-custom.txt which is empty failed: /usr/bin/dexdump2 -adfh invoke-custom.dex
Processed: android-platform-tools dropped symbols (at least causes autopkgtest regression inandroid-platform-art)
Processing control commands: > found -1 android-platform-tools/29.0.6-9 Bug #1010231 [src:android-platform-tools] android-platform-tools dropped symbols (at least causes autopkgtest regression inandroid-platform-art) Marked as found in versions android-platform-tools/29.0.6-9. > affects -1 src:android-platform-art Bug #1010231 [src:android-platform-tools] android-platform-tools dropped symbols (at least causes autopkgtest regression inandroid-platform-art) Added indication that 1010231 affects src:android-platform-art -- 1010231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010230: nvidia-graphics-drivers-legacy-390xx: autopkgtest needs update for new version of dkms: includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch
Source: nvidia-graphics-drivers-legacy-390xx
Version: 390.147-4
Severity: serious
X-Debbugs-CC: d...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:dkms
Dear maintainer(s),
With a recent upload of dkms the autopkgtest of
nvidia-graphics-drivers-legacy-390xx fails in testing when that
autopkgtest is run with the binary packages of dkms from unstable on
armhf. It passes when run with only packages from testing. In tabular form:
passfail
dkms from testing3.0.3-1
nvidia-graphics-drivers-legacy-390xx from testing390.147-4
all others from testingfrom testing
I copied some of the output at the bottom of this report. As I
understand it, the dkms changes extend the testing drastically and show
a real issue.
Currently this regression is blocking the migration of dkms to testing
[1]. Of course, dkms shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in dkms was
intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from dkms should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=dkms
https://ci.debian.net/data/autopkgtest/testing/armhf/n/nvidia-graphics-drivers-legacy-390xx/21184047/log.gz
At top level:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:999:5:
error: unknown type name ‘NV_WORKQUEUE_DATA_T’; did you mean
‘NV_WORKQUEUE_FLUSH’?
999 | NV_WORKQUEUE_DATA_T *data
| ^~~
| NV_WORKQUEUE_FLUSH
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.c: In
function ‘nv_flush_caches’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.c:225:5:
error: implicit declaration of function ‘NV_ON_EACH_CPU’
[-Werror=implicit-function-declaration]
225 | NV_ON_EACH_CPU(nv_flush_cache, NULL);
| ^~
cc1: some warnings being treated as errors
make[3]: ***
[/usr/src/linux-headers-5.17.0-1-common/scripts/Makefile.build:293:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.o] Error 1
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:
In function ‘os_queue_work_item’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1031:5:
error: implicit declaration of function ‘NV_WORKQUEUE_INIT’; did you
mean ‘NV_WORKQUEUE_FLUSH’? [-Werror=implicit-function-declaration]
1031 | NV_WORKQUEUE_INIT(>task, os_execute_work_item,
| ^
| NV_WORKQUEUE_FLUSH
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1031:36:
error: ‘os_execute_work_item’ undeclared (first use in this function);
did you mean ‘rm_execute_work_item’?
1031 | NV_WORKQUEUE_INIT(>task, os_execute_work_item,
|^~~~
|rm_execute_work_item
In file included from
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:15:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:
In function ‘os_is_efi_enabled’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/common/inc/nv-linux.h:224:26:
warning: returning ‘bool (*)(int)’ {aka ‘_Bool (*)(int)’} from a
function with return type ‘NvS32’ {aka ‘int’} makes integer from pointer
without a cast [-Wint-conversion]
224 | #define NV_EFI_ENABLED() efi_enabled
| ^~~
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1110:12:
note: in expansion of macro ‘NV_EFI_ENABLED’
1110 | return NV_EFI_ENABLED();
|^~
In file included from
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:15:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:
In function ‘os_get_euid’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/common/inc/nv-linux.h:154:46:
error: ‘struct task_struct’ has no member named ‘euid’
154 | #define NV_CURRENT_EUID() (__kuid_val(current->euid))
| ^~
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1338:18:
note: in expansion of macro ‘NV_CURRENT_EUID’
1338 | *pSecToken = NV_CURRENT_EUID();
| ^~~
cc1: some warnings being treated as errors
make[3]: ***
Processed: nvidia-graphics-drivers-legacy-390xx: autopkgtest needs update for new version of dkms: includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch
Processing control commands: > affects -1 src:dkms Bug #1010230 [src:nvidia-graphics-drivers-legacy-390xx] nvidia-graphics-drivers-legacy-390xx: autopkgtest needs update for new version of dkms: includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch Added indication that 1010230 affects src:dkms -- 1010230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: msp430mcu: diff for NMU version 20120406-2.2
Processing control commands: > tags 965736 + patch Bug #965736 [src:msp430mcu] msp430mcu: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965736 + pending Bug #965736 [src:msp430mcu] msp430mcu: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965736: msp430mcu: diff for NMU version 20120406-2.2
Control: tags 965736 + patch Control: tags 965736 + pending Dear maintainer, I've prepared an NMU for msp430mcu (versioned as 20120406-2.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru msp430mcu-20120406/debian/changelog msp430mcu-20120406/debian/changelog --- msp430mcu-20120406/debian/changelog 2021-01-03 11:45:50.0 -0300 +++ msp430mcu-20120406/debian/changelog 2022-04-22 14:18:57.0 -0300 @@ -1,3 +1,14 @@ +msp430mcu (20120406-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965736 + + -- Guilherme de Paula Xavier Segundo Fri, 22 Apr 2022 14:18:57 -0300 + msp430mcu (20120406-2.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -Nru msp430mcu-20120406/debian/compat msp430mcu-20120406/debian/compat --- msp430mcu-20120406/debian/compat 2012-05-10 12:16:44.0 -0300 +++ msp430mcu-20120406/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru msp430mcu-20120406/debian/control msp430mcu-20120406/debian/control --- msp430mcu-20120406/debian/control 2012-05-10 12:16:44.0 -0300 +++ msp430mcu-20120406/debian/control 2022-04-22 14:18:57.0 -0300 @@ -3,7 +3,7 @@ Priority: extra Maintainer: Luca Bruno Standards-Version: 3.9.3 -Build-Depends: debhelper (>= 7) +Build-Depends: debhelper-compat (= 13) Package: msp430mcu Architecture: all
Processed: sympy breaks einsteinpy autopkgtest: name 'numpy' is not defined
Processing control commands: > found -1 sympy/1.10.1-1 Bug #1010215 [src:sympy, src:einsteinpy] sympy breaks einsteinpy autopkgtest: name 'numpy' is not defined Marked as found in versions sympy/1.10.1-1. > found -1 einsteinpy/0.3.0-2 Bug #1010215 [src:sympy, src:einsteinpy] sympy breaks einsteinpy autopkgtest: name 'numpy' is not defined Marked as found in versions einsteinpy/0.3.0-2. -- 1010215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010215: sympy breaks einsteinpy autopkgtest: name 'numpy' is not defined
Source: sympy, einsteinpy
Control: found -1 sympy/1.10.1-1
Control: found -1 einsteinpy/0.3.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of sympy the autopkgtest of einsteinpy fails in
testing when that autopkgtest is run with the binary packages of sympy
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
sympy from testing1.10.1-1
einsteinpy from testing0.3.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of sympy to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=sympy
https://ci.debian.net/data/autopkgtest/testing/amd64/e/einsteinpy/21184013/log.gz
=== FAILURES
===
___ test_lambdify_with_args
def test_lambdify_with_args():
x, y = symbols("x y")
T = BaseRelativityTensor([x + y, x], (x, y), config="l")
args, f = T.tensor_lambdify(y, x)
arr = np.array(f(2, 1))
/usr/lib/python3/dist-packages/einsteinpy/tests/test_symbolic/test_tensor.py:251:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
y = 2, x = 1
def _lambdifygenerated(y, x):
return numpy.array((x + y, x))
E NameError: name 'numpy' is not defined
:2: NameError
=== warnings summary
===
../../../../usr/lib/python3/dist-packages/einsteinpy/ijit.py:30
../../../../usr/lib/python3/dist-packages/einsteinpy/ijit.py:30
/usr/lib/python3/dist-packages/einsteinpy/ijit.py:30: UserWarning:
Could not import numba package. All einsteinpy functions will work
properly but the CPU intensive algorithms will be slow. Consider
installing numba to boost performance.
tests/test_plotting/test_fractal.py: 64 warnings
/usr/lib/python3/dist-packages/einsteinpy/plotting/fractal.py:20:
DeprecationWarning:
`np.complex` is a deprecated alias for the builtin `complex`. To
silence this warning, use `complex` by itself. Doing this will not
modify any behavior and is safe. If you specifically wanted the numpy
scalar type, use `np.complex128` here.
Deprecated in NumPy 1.20; for more details and guidance:
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info
FAILED tests/test_symbolic/test_tensor.py::test_lambdify_with_args -
NameErro...
1 failed, 230 passed, 8 xfailed, 640002 warnings in 322.36s
(0:05:22) =
autopkgtest [12:16:46]: test command1
OpenPGP_signature
Description: OpenPGP digital signature
Processed: paramiko breaks libcloud autopkgtest: SSHException not raised by connect
Processing control commands: > found -1 paramiko/2.10.3-1 Bug #1010214 [src:paramiko, src:libcloud] paramiko breaks libcloud autopkgtest: SSHException not raised by connect Marked as found in versions paramiko/2.10.3-1. > found -1 libcloud/3.4.1-2 Bug #1010214 [src:paramiko, src:libcloud] paramiko breaks libcloud autopkgtest: SSHException not raised by connect Marked as found in versions libcloud/3.4.1-2. -- 1010214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010094: marked as done (liblttoolbox3 must be linked with libicu)
Your message dated Tue, 26 Apr 2022 15:03:47 + with message-id and subject line Bug#1010094: fixed in lttoolbox 3.6.4-1 has caused the Debian Bug report #1010094, regarding liblttoolbox3 must be linked with libicu 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.) -- 1010094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: liblttoolbox3-3.6-1 Severity: serious Tags: ftbfs patch Forwarded: https://github.com/apertium/lttoolbox/pull/141 https://buildd.debian.org/status/fetch.php?pkg=lttoolbox=amd64=3.6.1-2%2Bb2=1650723091=0 ... dh_shlibdeps -a dpkg-shlibdeps: warning: symbol u_strCaseCompare_71 used by debian/liblttoolbox3-3.6-1/usr/lib/x86_64-linux-gnu/liblttoolbox3-3.6.so.1.0.0 found in none of the libraries dpkg-shlibdeps: warning: symbol u_tolower_71 used by debian/liblttoolbox3-3.6-1/usr/lib/x86_64-linux-gnu/liblttoolbox3-3.6.so.1.0.0 found in none of the libraries dpkg-shlibdeps: warning: symbol u_isdigit_71 used by debian/liblttoolbox3-3.6-1/usr/lib/x86_64-linux-gnu/liblttoolbox3-3.6.so.1.0.0 found in none of the libraries dpkg-shlibdeps: warning: symbol u_errorName_71 used by debian/liblttoolbox3-3.6-1/usr/lib/x86_64-linux-gnu/liblttoolbox3-3.6.so.1.0.0 found in none of the libraries dpkg-shlibdeps: warning: symbol u_sscanf_71 used by debian/liblttoolbox3-3.6-1/usr/lib/x86_64-linux-gnu/liblttoolbox3-3.6.so.1.0.0 found in none of the libraries dpkg-shlibdeps: warning: symbol u_strHasMoreChar32Than_71 used by debian/liblttoolbox3-3.6-1/usr/lib/x86_64-linux-gnu/liblttoolbox3-3.6.so.1.0.0 found in none of the libraries dpkg-shlibdeps: warning: symbol u_fclose_71 used by debian/liblttoolbox3-3.6-1/usr/lib/x86_64-linux-gnu/liblttoolbox3-3.6.so.1.0.0 found in none of the libraries dpkg-shlibdeps: warning: symbol uloc_setDefault_71 used by debian/liblttoolbox3-3.6-1/usr/lib/x86_64-linux-gnu/liblttoolbox3-3.6.so.1.0.0 found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN6icu_7122UCharCharacterIterator7hasNextEv used by debian/liblttoolbox3-3.6-1/usr/lib/x86_64-linux-gnu/liblttoolbox3-3.6.so.1.0.0 found in none of the libraries dpkg-shlibdeps: warning: symbol u_isspace_71 used by debian/liblttoolbox3-3.6-1/usr/lib/x86_64-linux-gnu/liblttoolbox3-3.6.so.1.0.0 found in none of the libraries dpkg-shlibdeps: warning: 20 other similar warnings have been skipped (use -v to see them all) ... It works when all users also happen to link with (the right version of) libicu, if they don't linking or running code using liblttoolbox3 fails like: https://buildd.debian.org/status/fetch.php?pkg=apertium=ppc64=3.8.1-2%2Bb2=1650794468=0 ... /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `u_isalnum_67' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `u_strHasMoreChar32Than_67' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `u_isspace_67' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `u_feof_67' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `u_finit_67' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `u_toupper_67' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `icu_67::UCharCharacterIterator::UCharCharacterIterator(icu_67::ConstChar16Ptr, int)' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `u_errorName_67' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `u_fopen_67' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `u_sprintf_67' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `icu_67::UCharCharacterIterator::hasNext()' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to `u_fflush_67' /usr/bin/ld: /usr/lib/gcc/powerpc64-linux-gnu/11/../../../powerpc64-linux-gnu/liblttoolbox3.so: undefined reference to
Bug#1010214: paramiko breaks libcloud autopkgtest: SSHException not raised by connect
Source: paramiko, libcloud
Control: found -1 paramiko/2.10.3-1
Control: found -1 libcloud/3.4.1-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of paramiko the autopkgtest of libcloud fails in
testing when that autopkgtest is run with the binary packages of
paramiko from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
paramiko from testing2.10.3-1
libcloud from testing3.4.1-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of paramiko to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=paramiko
https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libcloud/21182944/log.gz
=== FAILURES
===
__ ParamikoSSHClientTests.test_key_file_non_pem_format_error
___
self = testMethod=test_key_file_non_pem_format_error>
@patch('paramiko.SSHClient', Mock)
@unittest.skipIf(paramiko_version >= '2.7.0',
'New versions of paramiko support OPENSSH key format')
def test_key_file_non_pem_format_error(self):
path = os.path.join(os.path.dirname(__file__),
'fixtures', 'misc',
'test_rsa_non_pem_format.key')
# Supplied as key_material
with open(path, 'r') as fp:
private_key = fp.read()
conn_params = {'hostname': 'dummy.host.org',
'username': 'ubuntu',
'key_material': private_key}
mock = ParamikoSSHClient(**conn_params)
expected_msg = 'Invalid or unsupported key type'
assertRaisesRegex(self, paramiko.ssh_exception.SSHException,
expected_msg, mock.connect)
test/compute/test_ssh_client.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/libcloud/utils/py3.py:145: in
assertRaisesRegex
return getattr(self, 'assertRaisesRegex')(*args, **kwargs)
E AssertionError: SSHException not raised by connect
-- Captured log call
---
DEBUGlibcloud.compute.ssh:ssh.py:365 Connecting to server
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1004018: nat: Removal of obsolete debhelper compat 5 and 6 in bookworm
Hi all,
I've fixed this bug. I'll do an NMU very soon. The debdiff is as attachment.
The major changes are:
1. Use debhelper 13.
2. Use DebSrc3.0. So we split diff.gz to debian/patches
If no one object this after 10 days. I'll upload this to delay/10 queue.
Yours,
Paul
diff -Nru nat-1.0/client.c nat-1.0/client.c
--- nat-1.0/client.c 2022-04-26 22:51:30.0 +0800
+++ nat-1.0/client.c 1997-02-17 11:18:04.0 +0800
@@ -2711,7 +2711,7 @@
(CVAL (inbuf, smb_rcls), SVAL (inbuf, smb_err));
/* this "can't happen" but does against misconfigured samba, fer example */
if ((cur_serr == 2) && (sec_mode & 1))
- DEBUG (1,("Wanted TCon passwd in USER-mode sec!!!\n"));
+ DEBUG (1,("Wanted TCon passwd in USER-mode sec?!??!\n"));
return(False);
} /* if smb_rcls err */
@@ -3521,7 +3521,7 @@
natprintf("[*]--- CONNECTED with name: %s\n", p);
#endif
-DEBUG(1,("session to %s (0x%x) open\n", desthost, name_type));
+DEBUG(0,("session to %s (0x%x) open\n", desthost, name_type));
phase = 2;
goto phase_2;
} else {
@@ -3613,7 +3613,7 @@
username[0] = '\0';
while (!done) {
if (!userfd || !passfd)
- done = !uppair();
+ uppair();
else {
if (fgets(password, sizeof(password), passfd) == NULL) {
rewind(passfd);
@@ -3636,11 +3636,8 @@
}
if ((! *username) && (! *password))
- done = !uppair();/* sleaze for NT */
+ uppair();/* sleaze for NT */
-if (done)
-break; /* Stop when uppair is done */
-
#ifdef VERBOSE
natprintf("[*]--- Attempting to connect with Username: `%s' Password: `%s'\n",
username, password);
diff -Nru nat-1.0/debian/changelog nat-1.0/debian/changelog
--- nat-1.0/debian/changelog 2022-04-26 22:51:30.0 +0800
+++ nat-1.0/debian/changelog 2022-04-26 22:48:16.0 +0800
@@ -1,3 +1,15 @@
+nat (1:1.0-6.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Migrate to debhelper-compat version 13 (Closes: #965744, #1004018)
+- Delete debian/compat
+- Build-Depends on debhelper-compat (= 13)
+ * Use DebSrc3.0 (quilt)
+- Split diff.gz to debian/patches
+ * debian/control: Change Priority from extra to optional
+
+ -- Ying-Chun Liu (PaulLiu) Tue, 26 Apr 2022 22:48:16 +0800
+
nat (1:1.0-6) unstable; urgency=medium
* include.h: Apply patch provided by Cyril Roelandt to fix
diff -Nru nat-1.0/debian/compat nat-1.0/debian/compat
--- nat-1.0/debian/compat 2022-04-26 22:51:30.0 +0800
+++ nat-1.0/debian/compat 1970-01-01 08:00:00.0 +0800
@@ -1 +0,0 @@
-5
diff -Nru nat-1.0/debian/control nat-1.0/debian/control
--- nat-1.0/debian/control 2022-04-26 22:51:30.0 +0800
+++ nat-1.0/debian/control 2022-04-26 22:26:59.0 +0800
@@ -1,8 +1,8 @@
Source: nat
Section: admin
-Priority: extra
+Priority: optional
Maintainer: Javier Fernandez-Sanguino Peña
-Build-Depends: debhelper (>> 3.0.0)
+Build-Depends: debhelper-compat (= 13)
Standards-Version: 3.9.6
Homepage: http://www.tux.org/pub/security/secnet/tools/nat10/
diff -Nru nat-1.0/debian/patches/0001_add_samples.patch nat-1.0/debian/patches/0001_add_samples.patch
--- nat-1.0/debian/patches/0001_add_samples.patch 1970-01-01 08:00:00.0 +0800
+++ nat-1.0/debian/patches/0001_add_samples.patch 2022-04-26 22:21:34.0 +0800
@@ -0,0 +1,99 @@
+Index: nat-1.0/samples/localhost-samba.log
+===
+--- /dev/null
nat-1.0/samples/localhost-samba.log
+@@ -0,0 +1,38 @@
++
++[*]--- Checking host: 127.0.0.1
++[*]--- Obtaining list of remote NetBIOS names
++[*]--- Remote systems name tables:
++
++ LINUX
++ LINUX
++ LINUX
++ __MSBROWSE__
++ SAMBA
++ SAMBA
++ SAMBA
++ SAMBA
++
++[*]--- Attempting to connect with name: *
++[*]--- CONNECTED with name: *
++[*]--- Attempting to connect with protocol: MICROSOFT NETWORKS 1.03
++[*]--- Remote server wants us to encrypt, telling it not to
++[*]--- Attempting to connect with protocol: PC NETWORK PROGRAM 1.0
++[*]--- Attempting to establish session
++
++[*]--- Attempting to access share: \\*\
++[*]--- Unable to access
++
++[*]--- Attempting to access share: \\*\ADMIN$
++[*]--- Unable to access
++
++[*]--- Attempting to access share: \\*\C$
++[*]--- Unable to access
++
++[*]--- Attempting to access share: \\*\D$
++[*]--- Unable to access
++
++[*]--- Attempting to access share: \\*\ROOT
++[*]--- Unable to access
++
++[*]--- Attempting to access share: \\*\WINNT$
++[*]--- Unable to access
+Index: nat-1.0/samples/w2000as.log
+===
+--- /dev/null
nat-1.0/samples/w2000as.log
+@@ -0,0 +1,51 @@
++
++[*]--- Checking host: 192.168.0.159
++[*]--- Obtaining list of remote NetBIOS names
++[*]--- Remote systems name tables:
++
++ INet~Services
++ IS~W2000AS
++ W2000AS
++ W2000AS
++ WORKGROUP
++ ADMINISTRATOR
++ W2000AS
++ WORKGROUP
++
Bug#1004018: Is smb-nat still useful?
Hi Adrian, I just went into this package and found it might be still useful. The purpose of this package is different than the samba tools. This package is trying to test some simple security holes that a samba server might expose. It will try to iterate all public shares. And tries to login into it by common user names and passwords. So it seems to me that this package is still useful. I'll prepare a NMU soon. I'll send a debdiff, waiting for 10 days. And then I'll upload to delay/10 queue. Migrate to debhelper 13 and debsrc3.0 seems not very hard to me. Yours, Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#965443: marked as done (cadaver: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 26 Apr 2022 13:49:08 + with message-id and subject line Bug#965443: fixed in cadaver 0.23.3-2.2 has caused the Debian Bug report #965443, regarding cadaver: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cadaver Version: 0.23.3-2.1 Severity: normal Usertags: compat-5-6-removal Hi, The package cadaver uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: cadaver Source-Version: 0.23.3-2.2 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of cadaver, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated cadaver 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: Fri, 15 Apr 2022 21:27:34 -0300 Source: cadaver Architecture: source Version: 0.23.3-2.2 Distribution: unstable Urgency: medium Maintainer: Sebastian Harl Changed-By: Joao Eriberto Mota Filho Closes: 668477 965443 Changes: cadaver (0.23.3-2.2) unstable; urgency=medium . * Non-maintainer upload. * Migrated to DebSrc 3.0. Consequently: - debian/README.source: removed because the content of this file is a disclaimer about dpatch. - debian/source/options: created to ignore changes in config.guess and config.sub. - Migrated the current patch from dpatch to quilt. - Closes: #668477 * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the '-k' option is not supported since compat 12. - Closes: #965443 Checksums-Sha1: 4b13eb79a4c698620da4fd60c30444c292fc9849 2009 cadaver_0.23.3-2.2.dsc 2b2df09e2c8b08dc89e61740b090da96afe7c403 7112 cadaver_0.23.3-2.2.debian.tar.xz c44398c859ed1d0256f4f1a8a4be34e7e5a0ce9a 6870 cadaver_0.23.3-2.2_source.buildinfo Checksums-Sha256: a513609ba95b69dd3583cfdb22e6fe6c598eef438c2fe057cc3f6abc6d80bb27 2009 cadaver_0.23.3-2.2.dsc ea652598f7267e9a82258fa4056f34d1e797b725be27781a5ea4ba9d539d1185 7112 cadaver_0.23.3-2.2.debian.tar.xz afb5489bfe34a5185e5beb0af352d1f2e823db11158174ab3eef23680e6e83b1 6870 cadaver_0.23.3-2.2_source.buildinfo Files: 86d710c9173e98acf83dd50bf6bf753e 2009 web optional cadaver_0.23.3-2.2.dsc 624319a07dd7cd21fee05b4a5f15fa8a 7112 web optional cadaver_0.23.3-2.2.debian.tar.xz c16652a4c7864eb99c991dc0cba72bb8 6870 web optional cadaver_0.23.3-2.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJavhYACgkQ3mO5xwTr 6e9SAQ/9G9RWHwGlZ7FMa9PqbN5g9TipgGAY8h5fSFWGQ3aflw400uBVTmKvvj7b AiKO7WT6GxNsWuWjXgrpgxTeqUoqUpzrp1d4ZxMon+GqF9HaqVYTuAtQyX4xt5mC
Bug#668477: marked as done ([PATCH] cadaver: Helping to update to packaging format 3.0)
Your message dated Tue, 26 Apr 2022 13:49:08 +
with message-id
and subject line Bug#668477: fixed in cadaver 0.23.3-2.2
has caused the Debian Bug report #668477,
regarding [PATCH] cadaver: Helping to update to packaging format 3.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.)
--
668477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cadaver
Severity: wishlist
Tags: patch
Hi,
The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:
http://wiki.debian.org/Projects/DebSrc3.0
I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.
Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.
Thanks,
Jari
>From 4efd030c73e549d91d2e36bbc79819040901f933 Mon Sep 17 00:00:00 2001
From: Jari Aalto
Date: Thu, 12 Apr 2012 09:13:38 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Signed-off-by: Jari Aalto
---
debian/README.source |4
debian/changelog | 10 ++
debian/compat |2 +-
debian/control |6 +++---
debian/copyright |4 ++--
debian/patches/00list |2 --
...{manpage_hyphen.dpatch => manpage_hyphen.patch} |7 ++-
debian/patches/series |2 ++
debian/rules | 11 +++
debian/source/format |1 +
10 files changed, 28 insertions(+), 21 deletions(-)
delete mode 100644 debian/README.source
delete mode 100644 debian/patches/00list
rename debian/patches/{manpage_hyphen.dpatch => manpage_hyphen.patch} (84%)
create mode 100644 debian/patches/series
create mode 100644 debian/source/format
diff --git a/debian/README.source b/debian/README.source
deleted file mode 100644
index a7decf0..000
--- a/debian/README.source
+++ /dev/null
@@ -1,4 +0,0 @@
-This package uses dpatch to manage all modifications to the upstream source.
-See /usr/share/doc/dpatch/README.source.gz for instructions how to generate
-the patched source, add a new modification, and remove an existing one.
-
diff --git a/debian/changelog b/debian/changelog
index 03fc20a..7e19d3d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+cadaver (0.23.3-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+ * Update to Standards-Version to 3.9.3 and debhelper to 9.
+ * Add build-arch and build-indep targets; use dh_prep in rules file.
+ * Fix copyright-refers-to-symlink-license (Lintian).
+
+ -- Jari Aalto Thu, 12 Apr 2012 09:08:23 +0300
+
cadaver (0.23.3-1) unstable; urgency=low
* New upstream version:
diff --git a/debian/compat b/debian/compat
index 7ed6ff8..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-5
+9
diff --git a/debian/control b/debian/control
index fa61358..23e24c5 100644
--- a/debian/control
+++ b/debian/control
@@ -2,15 +2,15 @@ Source: cadaver
Section: web
Priority: optional
Maintainer: Sebastian Harl
-Build-Depends: debhelper (>= 5), dpkg-dev (>= 1.14.6), dpatch, autotools-dev, libncurses5-dev, libxml2-dev, libreadline-dev | libreadline5-dev, zlib1g-dev (>= 1:1.1.3), libneon27-gnutls-dev (>= 0.28)
-Standards-Version: 3.8.3
+Build-Depends: debhelper (>= 9), autotools-dev, libncurses5-dev, libxml2-dev, libreadline-dev | libreadline5-dev, zlib1g-dev (>= 1:1.1.3), libneon27-gnutls-dev (>= 0.28)
+Standards-Version: 3.9.3
Homepage: http://www.webdav.org/cadaver/
Vcs-Git: git://git.tokkee.org/pkg-cadaver.git
Vcs-Browser: http://git.tokkee.org/?p=pkg-cadaver.git
Package: cadaver
Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
Description: command-line WebDAV client
cadaver supports file upload, download, on-screen display, in-place editing,
namespace operations (move/copy), collection creation and deletion, property
diff --git
Bug#1009385: marked as done (libldns3 1.7.1-2.1 changes output of ldns-key2ds, causing FTBFS on dns-root-data)
Your message dated Tue, 26 Apr 2022 13:33:51 + with message-id and subject line Bug#1009385: fixed in ldns 1.8.1-1 has caused the Debian Bug report #1009385, regarding libldns3 1.7.1-2.1 changes output of ldns-key2ds, causing FTBFS on dns-root-data 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.) -- 1009385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dns-root-data Version: 2021011101 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # Verify root-anchors.xml using OpenSSL > openssl smime -verify -noverify -inform DER -in root-anchors.p7s -content > root-anchors.xml > Verification successful > > source="http://data.iana.org/root-anchors/root-anchors.xml;> > . > validUntil="2019-01-11T00:00:00+00:00"> > 19036 > 8 > 2 > 49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5 > > > 20326 > 8 > 2 > E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D > > > # Verify root.hints > gpgv --keyring /<>/registry-admin.key > /<>/root.hints.sig /<>/root.hints > gpgv: Signature made Mon Jan 11 15:55:50 2021 UTC > gpgv:using DSA key 937BB869E3A238C5 > gpgv: Good signature from "Registry Administrator " > # Create key from validated root-anchors.xml > ./parse-root-anchors.sh < root-anchors.xml | sort -k 4 -n > root-anchors.ds > Digest 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 > expired on 2019-01-11T00:00:00+00:00 > # Create key from downloaded root.key > /usr/bin/ldns-key2ds -n -2 root.key | cut --fields=1,3- --output-delimiter=' > ' | sort -k 4 -n > root.ds > # Compare the DS from root.key and from root-anchors.xml > diff -u root-anchors.ds root.ds > --- root-anchors.ds 2022-04-12 16:59:11.126351522 + > +++ root.ds 2022-04-12 16:59:11.130351536 + > @@ -1 +1 @@ > -. IN DS 20326 8 2 > e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d > +. IN DS 20326 8 2 > 0ae721f59a19244008217c3d2a646183acef2f17cf4c30929a3f29d09311c05e > make[1]: *** [debian/rules:23: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/04/12/dns-root-data_2021011101_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ldns Source-Version: 1.8.1-1 Done: Michael Tokarev We believe that the bug you reported is fixed in the latest version of ldns, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated ldns package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Apr 2022 16:05:17 +0300 Source: ldns Architecture: source Version: 1.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian DNS Team Changed-By: Michael Tokarev Closes: 1005646 1008638 1009385 Changes: ldns (1.8.1-1) unstable; urgency=medium . * New upstream version 1.8.1 Closes: #1008638 (FTBFS with python 3.10 due to distutils check) Closes: #1005646 (FTBFS with OpenSSL 3.0) Closes: #1009385 (output of ldns-key2ds changes after compiler changes) Closes: CVE-2020-19860 (heap buffer overflow in while verifying zone file)
Bug#1008638: marked as done (ldns: FTBFS: checking for the distutils Python package... no)
Your message dated Tue, 26 Apr 2022 13:33:51 +
with message-id
and subject line Bug#1008638: fixed in ldns 1.8.1-1
has caused the Debian Bug report #1008638,
regarding ldns: FTBFS: checking for the distutils Python package... no
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.)
--
1008638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ldns
Version: 1.7.1-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
ldns FTBFS:
checking for the distutils Python package... no
configure: error: cannot import Python module "distutils".
Please check your Python installation. The error was:
:1: DeprecationWarning: The distutils package is deprecated and slated
for removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
See
https://buildd.debian.org/status/fetch.php?pkg=ldns=amd64=1.7.1-2%2Bb2=1648456911=0
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ldns
Source-Version: 1.8.1-1
Done: Michael Tokarev
We believe that the bug you reported is fixed in the latest version of
ldns, 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 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Tokarev (supplier of updated ldns package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 26 Apr 2022 16:05:17 +0300
Source: ldns
Architecture: source
Version: 1.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Team
Changed-By: Michael Tokarev
Closes: 1005646 1008638 1009385
Changes:
ldns (1.8.1-1) unstable; urgency=medium
.
* New upstream version 1.8.1
Closes: #1008638 (FTBFS with python 3.10 due to distutils check)
Closes: #1005646 (FTBFS with OpenSSL 3.0)
Closes: #1009385 (output of ldns-key2ds changes after compiler changes)
Closes: CVE-2020-19860 (heap buffer overflow in while verifying zone file)
Closes: CVE-2020-19861 (heap overflow/leakage when reading a zone file)
* rework the build system, fixing numerous issues:
- stop overwriting files at install time from different builds
and ending up using the build with wrong configure options
- stop running install twice
- stop removing system-installed files if any on clean
- stop doing (re)build of everything just for the python build
- build python bits in the main build and perform extra steps
only if there's more than one python version to build for
(this effectively eliminates miltiple builds completely)
- clarify build with multiple pyversions and why it still fails
- remove old, now irrelevant, stuff (like overriding options
which are being in effect anyway, or which has no effect)
- move variable-based custom install rule for libldns.pc
into .install file once dh now allows variables in there
- reduce startup time by eliminating dpkg's default.mk which is slow
- remove the wrongly-generated staic lib for the python bindings
(_ldns.{a,la}) in the install rules instead of ignoring them
in dh_install -X
- fix add --with-trust-anchor= so it actually works
- replace dh --with python with Build-Depend: dh-sequence-python3
- run dh only for supported targets/sequences
* update symbols file for 1.8 version, adding 6 new symbols
* remove Makefile-remove-install-libldns-pc.patch
* update short descriptions of all packages to mention what is
actually in there instead of being the same for all packages
* remove Build-Dependes: chrpath & pkg-config (not used)
* add fix-pyldns-include.patch to fix building pyldns outside source dir
* d/control: update Stdandards-Version to 4.6.0.1 (no changes)
* d/watch: rework, simplify, use https, enable pgp signature verification
* add upstream/signing-key.asc with the followig key:
E5F8F8212F77A498 "Willem Toorop "
* remove trailing whitespace from d/changelog
* add myself to uploaders
Checksums-Sha1:
0d89d28421f4ed0966b020de73a37a5383c9a7c2 1900
Processed: bug 1010166 is forwarded to https://bugs.webkit.org/show_bug.cgi?id=239767
Processing commands for cont...@bugs.debian.org: > forwarded 1010166 https://bugs.webkit.org/show_bug.cgi?id=239767 Bug #1010166 [src:webkit2gtk] webkit2gtk: 2.36.1-1 apparent regression seen in devhelp autopkgtest Set Bug forwarded-to-address to 'https://bugs.webkit.org/show_bug.cgi?id=239767'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008349: marked as done (python-securesystemslib: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Tue, 26 Apr 2022 12:05:51 +
with message-id
and subject line Bug#1008349: fixed in python-securesystemslib 0.23.0-1
has caused the Debian Bug report #1008349,
regarding python-securesystemslib: FTBFS: dh_auto_test: error: pybuild --test
-i python{version} -p "3.10 3.9" returned exit code 13
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.)
--
1008349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-securesystemslib
Version: 0.22.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py config
> running config
> I: pybuild base:237: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/__init__.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/signer.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/settings.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/util.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/interface.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/exceptions.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/schema.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/rsa_keys.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/ecdsa_keys.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/formats.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/unittest_toolbox.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/storage.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/keys.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/process.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/ed25519_keys.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> copying securesystemslib/hash.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib
> creating
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/gpg
> copying securesystemslib/gpg/__init__.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/gpg
> copying securesystemslib/gpg/util.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/gpg
> copying securesystemslib/gpg/exceptions.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/gpg
> copying securesystemslib/gpg/dsa.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/gpg
> copying securesystemslib/gpg/rsa.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/gpg
> copying securesystemslib/gpg/eddsa.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/gpg
> copying securesystemslib/gpg/common.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/gpg
> copying securesystemslib/gpg/handlers.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/gpg
> copying securesystemslib/gpg/functions.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/gpg
> copying securesystemslib/gpg/constants.py ->
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/gpg
> creating
> /<>/.pybuild/cpython3_3.10_securesystemslib/build/securesystemslib/_vendor
> copying securesystemslib/_vendor/__init__.py ->
>
Bug#1009822: marked as done (gnss-sdr: autopkgtest regression)
Your message dated Tue, 26 Apr 2022 08:48:50 + with message-id and subject line Bug#1009822: fixed in gnss-sdr 0.0.17-1 has caused the Debian Bug report #1009822, regarding gnss-sdr: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1009822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnss-sdr Version: 0.0.16-1 Severity: serious Tags: sid bookworm gnss-sdr's autopkgtest fail with gr-osmosdr 0.2.3-6 autopkgtest [14:10:33]: test testgnsssdr: [--- terminate called after throwing an instance of 'std::runtime_error' what(): rpcmanager: Aggregator not in use, and a rpc booter is already registered Aborted autopkgtest [14:10:33]: test testgnsssdr: ---] autopkgtest [14:10:33]: test testgnsssdr: - - - - - - - - - - results - - - - - - - - - - testgnsssdr FAIL non-zero exit status 134 autopkgtest [14:10:34]: test testgnsssdr: - - - - - - - - - - stderr - - - - - - - - - - terminate called after throwing an instance of 'std::runtime_error' what(): rpcmanager: Aggregator not in use, and a rpc booter is already registered Aborted autopkgtest [14:10:34]: summary testgnsssdr FAIL non-zero exit status 134 See https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnss-sdr/20968987/log.gz Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: gnss-sdr Source-Version: 0.0.17-1 Done: Carles Fernandez We believe that the bug you reported is fixed in the latest version of gnss-sdr, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carles Fernandez (supplier of updated gnss-sdr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 25 Apr 2022 15:30:30 + Source: gnss-sdr Architecture: source Version: 0.0.17-1 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: Carles Fernandez Closes: 1008901 1009822 Changes: gnss-sdr (0.0.17-1) unstable; urgency=medium . * First release of upstream version 0.0.17 * Updated URL in debian/control * Added libcpu-features-dev dependency * Updated debian/copyright file * Fixed building against gnuradio 3.10.2.0 (Closes: #1008901) which includes: - Fixed building against gr-osmosdr 0.2.3-6 (Closes: #1009822) Checksums-Sha1: a3d9a11708cc90567972d840d383ede2b56bc048 2656 gnss-sdr_0.0.17-1.dsc 3da011a62b322a6bf2dbb772e6ae27cebca520f0 4460661 gnss-sdr_0.0.17.orig.tar.gz 5cbe4090a93a34bf812cf81641a921c096375bbd 833 gnss-sdr_0.0.17.orig.tar.gz.asc ee63d4f3c221140dabfede925065250ef37d45e1 13804 gnss-sdr_0.0.17-1.debian.tar.xz 67455c87ef771b04769ff6fd0a0c2a5e993d72f1 6810 gnss-sdr_0.0.17-1_source.buildinfo Checksums-Sha256: 90d5516f7f6c55fd4fb03d67ad02c38c4a5a10307252f302b2eaf1c034e1890e 2656 gnss-sdr_0.0.17-1.dsc 94fbfd2b8ab453f32f84ac82f8c4885a96d1c020ac979ceeaedae0ce2e6bf7cc 4460661 gnss-sdr_0.0.17.orig.tar.gz c5291c41ba587acf6f6c24761bb94f82e5110fd93c15607a06197755fdf24289 833 gnss-sdr_0.0.17.orig.tar.gz.asc 473fd7ea2e1a86c22337cdc5712a15f3a9be7dda2cbbf9b595ece12c9f205dd7 13804 gnss-sdr_0.0.17-1.debian.tar.xz 2cc0fec85c6a8861e4c196ff91e8d258655d9cd745c3304546b40362bba998c0 6810 gnss-sdr_0.0.17-1_source.buildinfo Files: 8c5b428f29cfe75a22efcc55dd400f11 2656 hamradio optional gnss-sdr_0.0.17-1.dsc 26ed549c12e4c01f606645f8b80677f6 4460661 hamradio optional gnss-sdr_0.0.17.orig.tar.gz 91a731a0a94af7dfca0273cfc6da4f9c 833 hamradio optional gnss-sdr_0.0.17.orig.tar.gz.asc 58ae9d2d114a8898da9b6d424b27ca65 13804 hamradio optional gnss-sdr_0.0.17-1.debian.tar.xz 55379338861ea2490a72c3e9612e84e2 6810 hamradio optional gnss-sdr_0.0.17-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmJnrekQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFNJ5C/9Fppcajh6Eub86q1d29I8daMAz2gOWvDOI a6LDyDQc+P7UlRb8ZHJQHA6L6U3rujz4UJ7WGn6BGV8w9GPC4OxUfiiTZnmsb+vh ZZdURVKhm7kJvriw6rxxcJmQEnjo71WIQj+a1oZYFLAlQQ7zDhU7LXhuBw9kZB7V
Bug#1008901: marked as done (gnss-sdr FTBFS: Missing #include )
Your message dated Tue, 26 Apr 2022 08:48:50 + with message-id and subject line Bug#1008901: fixed in gnss-sdr 0.0.17-1 has caused the Debian Bug report #1008901, regarding gnss-sdr FTBFS: Missing #include 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.) -- 1008901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnss-sdr Version: 0.0.16-1 Severity: serious Tags: ftbfs patch Forwarded: https://github.com/gnss-sdr/gnss-sdr/pull/593 https://buildd.debian.org/status/logs.php?pkg=gnss-sdr=0.0.16-1%2Bb2 ... /<>/src/algorithms/signal_source/adapters/limesdr_signal_source.cc: In constructor ‘LimesdrSignalSource::LimesdrSignalSource(const ConfigurationInterface*, const string&, unsigned int, unsigned int, Concurrent_Queue >*)’: /<>/src/algorithms/signal_source/adapters/limesdr_signal_source.cc:100:67: error: ‘diagnostic_information’ is not a member of ‘boost’ 100 | LOG(WARNING) << "Boost exception: " << boost::diagnostic_information(e); | ^~ ... --- End Message --- --- Begin Message --- Source: gnss-sdr Source-Version: 0.0.17-1 Done: Carles Fernandez We believe that the bug you reported is fixed in the latest version of gnss-sdr, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carles Fernandez (supplier of updated gnss-sdr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 25 Apr 2022 15:30:30 + Source: gnss-sdr Architecture: source Version: 0.0.17-1 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: Carles Fernandez Closes: 1008901 1009822 Changes: gnss-sdr (0.0.17-1) unstable; urgency=medium . * First release of upstream version 0.0.17 * Updated URL in debian/control * Added libcpu-features-dev dependency * Updated debian/copyright file * Fixed building against gnuradio 3.10.2.0 (Closes: #1008901) which includes: - Fixed building against gr-osmosdr 0.2.3-6 (Closes: #1009822) Checksums-Sha1: a3d9a11708cc90567972d840d383ede2b56bc048 2656 gnss-sdr_0.0.17-1.dsc 3da011a62b322a6bf2dbb772e6ae27cebca520f0 4460661 gnss-sdr_0.0.17.orig.tar.gz 5cbe4090a93a34bf812cf81641a921c096375bbd 833 gnss-sdr_0.0.17.orig.tar.gz.asc ee63d4f3c221140dabfede925065250ef37d45e1 13804 gnss-sdr_0.0.17-1.debian.tar.xz 67455c87ef771b04769ff6fd0a0c2a5e993d72f1 6810 gnss-sdr_0.0.17-1_source.buildinfo Checksums-Sha256: 90d5516f7f6c55fd4fb03d67ad02c38c4a5a10307252f302b2eaf1c034e1890e 2656 gnss-sdr_0.0.17-1.dsc 94fbfd2b8ab453f32f84ac82f8c4885a96d1c020ac979ceeaedae0ce2e6bf7cc 4460661 gnss-sdr_0.0.17.orig.tar.gz c5291c41ba587acf6f6c24761bb94f82e5110fd93c15607a06197755fdf24289 833 gnss-sdr_0.0.17.orig.tar.gz.asc 473fd7ea2e1a86c22337cdc5712a15f3a9be7dda2cbbf9b595ece12c9f205dd7 13804 gnss-sdr_0.0.17-1.debian.tar.xz 2cc0fec85c6a8861e4c196ff91e8d258655d9cd745c3304546b40362bba998c0 6810 gnss-sdr_0.0.17-1_source.buildinfo Files: 8c5b428f29cfe75a22efcc55dd400f11 2656 hamradio optional gnss-sdr_0.0.17-1.dsc 26ed549c12e4c01f606645f8b80677f6 4460661 hamradio optional gnss-sdr_0.0.17.orig.tar.gz 91a731a0a94af7dfca0273cfc6da4f9c 833 hamradio optional gnss-sdr_0.0.17.orig.tar.gz.asc 58ae9d2d114a8898da9b6d424b27ca65 13804 hamradio optional gnss-sdr_0.0.17-1.debian.tar.xz 55379338861ea2490a72c3e9612e84e2 6810 hamradio optional gnss-sdr_0.0.17-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmJnrekQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFNJ5C/9Fppcajh6Eub86q1d29I8daMAz2gOWvDOI a6LDyDQc+P7UlRb8ZHJQHA6L6U3rujz4UJ7WGn6BGV8w9GPC4OxUfiiTZnmsb+vh ZZdURVKhm7kJvriw6rxxcJmQEnjo71WIQj+a1oZYFLAlQQ7zDhU7LXhuBw9kZB7V s21fbO/FgnQwfJEppBAskgYoZTrNTFm2yUC14/fb26ElnxSn3D6EZLPQtdXqKqAR VS2XElXntWEd1fneT3RGnyEntRlZWegPwh8niuHGryNdiRR3ppg8FpZGS96Nwo3H HMfhZXDbj+oACRduJJlgNRK9KnksuK1UoI7fDfimyyAPPJuHTpEJWQ0nK0cwCCXd E385Eg76uoolzc8aukR9jcGSO7RNjMrwdvMA0IvhKOW6oi3sFAXXwrUYO2Hgz7i2
Bug#997265: Removing opensurgsim from Debian (Was: [simquest/opensurgsim] Build failures with libeigen3-3.4.0 (Issue #5))
Hi, as far as I can see the Debian Med team is not able to take over upstream work on opensurgsim. Thus I'd suggest to remove this package from Debian if nobody might step in. Kind regards Andreas. - Weitergeleitete Nachricht von Harald Scheirich - Date: Mon, 25 Apr 2022 13:38:05 -0700 From: Harald Scheirich To: simquest/opensurgsim Cc: Andreas Tille , Comment Subject: Re: [simquest/opensurgsim] Build failures with libeigen3-3.4.0 (Issue #5) Sorry there really isn't any work being done using OSS at the moment on our side, any change will have to come from the community -- Reply to this email directly or view it on GitHub: https://github.com/simquest/opensurgsim/issues/5#issuecomment-1109017448 You are receiving this because you commented. Message ID: - Ende weitergeleitete Nachricht - -- http://fam-tille.de
Bug#1010053: marked as done (php-pecl-http FTBFS: PHP_DEFAULT_VERSION cannot be empty)
Your message dated Tue, 26 Apr 2022 07:19:20 + with message-id and subject line Bug#1010053: fixed in php-pecl-http 4.2.2-1 has caused the Debian Bug report #1010053, regarding php-pecl-http FTBFS: PHP_DEFAULT_VERSION cannot be empty 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.) -- 1010053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-pecl-http Version: 4.2.1+php8-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=php-pecl-http=4.2.1%2Bphp8-2%2Bb1 ... fakeroot debian/rules clean PHP_DEFAULT_VERSION_DEFAULT := "8.1" PHP_DEFAULT_VERSION_OVERRIDE := "7.4" AVAILABLE_PHP_VERSIONS := "8.1" /usr/share/dh-php/pkg-pecl.mk:39: *** PHP_DEFAULT_VERSION cannot be empty. Stop. dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: php-pecl-http Source-Version: 4.2.2-1 Done: Ondřej Surý We believe that the bug you reported is fixed in the latest version of php-pecl-http, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý (supplier of updated php-pecl-http package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 Apr 2022 09:01:15 +0200 Source: php-pecl-http Architecture: source Version: 4.2.2-1 Distribution: unstable Urgency: medium Maintainer: Debian PHP PECL Maintainers Changed-By: Ondřej Surý Closes: 1005198 1006742 1010053 Changes: php-pecl-http (4.2.2-1) unstable; urgency=medium . * New upstream version 4.2.2 * Strip the PHP default version (Closes: #1010053, #1006742, #1005198) Checksums-Sha1: fa56dcd834358fdd9b4a57580613052b1fb00e64 2407 php-pecl-http_4.2.2-1.dsc fed59506124ce448edd845de8cb1aa1ff122f780 224436 php-pecl-http_4.2.2.orig.tar.gz 9e420d6801f4f62bc6619a31e551b170a4ff942e 5300 php-pecl-http_4.2.2-1.debian.tar.xz 7cbc54e78c9e3f902044c8b2be4abc0766d92c88 8953 php-pecl-http_4.2.2-1_amd64.buildinfo Checksums-Sha256: dc0bbb6514e90ceedfd87e99ea51de98838213b4f8f9ccb26b473da814f9e697 2407 php-pecl-http_4.2.2-1.dsc c338afd29259f0093f07f4e99b80705a2d5bb046c7ab32e5938eef29bbb63a6e 224436 php-pecl-http_4.2.2.orig.tar.gz bb00399dfe8363cf5b52a0cb49fdc21e233119288271584ab8494117017baff1 5300 php-pecl-http_4.2.2-1.debian.tar.xz ea7c6f8bff5eef220d350a41ec6db2e975e1b751d8f11a5a587064d9c63acf99 8953 php-pecl-http_4.2.2-1_amd64.buildinfo Files: 6a966331dd1a1ced7cde0f1ef5f9c581 2407 web optional php-pecl-http_4.2.2-1.dsc 20404ddf2ef73b70b171d75bafa410d8 224436 web optional php-pecl-http_4.2.2.orig.tar.gz c8b59c2f21ef481fdb946554068a3932 5300 web optional php-pecl-http_4.2.2-1.debian.tar.xz 99dfa3a2d3dafbbdeb79a037af83c157 8953 web optional php-pecl-http_4.2.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmJnmadfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u WcKRVQ//bvYYQaAxUxhs2XKdo3Gy6R6a9O0m8YKv1rH00AlVljcSohGXvSQAe1ft qWxZ5KVYjrg8GjA1plLljkTtTU/TrgUh7meQWuyhBJl11miHNu+vAMdUYoNeG64Z Fe6K9eBBcUoxXty9i4qHfr5rRrjZS5WlkV+pLWUhFxWxbW21sVJJqgKsElY9CpF2 rcFAVJnTvuFF1+/1s34EfOtCQCUUqcDCnvTdCekNl71j73aeOT/51hi92WdRsYVy BqK5BFlAO7QV+s83NI5zOQrDbry1MitZbwSBMVajgCRGQDjk3kjGdYvvwvDYsoLF N7OaJh1JddIgx+FcgdcizZ6IHkWyRUmha0HiO7ClCZzVJMXn74WotJKwwMW4TWc4 ZdF/MAZeqsmqPNnAad85VE7zwU/T+drTHkeGsqpEWWE60hXHVgDum6JbhOW4+CvK 57xSpqA2IgHMa83W9KMwvY+GIa7FLTe1wIsJobr29CjTGp12z3Lmctk4nXHDwgCc IC8YFY6z6GAkQtRHuBS9DaQJY6g5vr6Glqe0Vl7VMadpmte/mxBXZTNkaZj8WD6F cUo9dv4lLtmVfl1EQcQUFgOZW7W32L1DvD4i/bsaCARaTWm/mMDPjByPLR2WTjkE nuh3ZXmYcA43aqdnUPaV0DjSNByxGPmQ3NsUngjvTnAM27fWvk8= =mtTR -END PGP SIGNATURE End Message ---
Bug#1010198: prompt-toolkit breaks xonsh autopkgtest: '_GeneratorContextManager' object has no attribute 'send_text'
Source: prompt-toolkit, xonsh
Control: found -1 prompt-toolkit/3.0.29-1
Control: found -1 xonsh/0.11.0+dfsg-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of prompt-toolkit the autopkgtest of xonsh fails in
testing when that autopkgtest is run with the binary packages of
prompt-toolkit from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
prompt-toolkit from testing3.0.29-1
xonsh from testing0.11.0+dfsg-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of prompt-toolkit to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=prompt-toolkit
https://ci.debian.net/data/autopkgtest/testing/amd64/x/xonsh/21156238/log.gz
__ ERROR at teardown of test_ptk_prompt['hello'-None]
__
xonsh_execer =
@pytest.fixture
def ptk_shell(xonsh_execer):
from prompt_toolkit.input import create_pipe_input
from prompt_toolkit.output import DummyOutput
from xonsh.ptk_shell.shell import PromptToolkitShell
inp = create_pipe_input()
out = DummyOutput()
shell = PromptToolkitShell(
execer=xonsh_execer, ctx={}, ptk_args={"input": inp,
"output": out}
)
yield inp, out, shell
inp.close()
E AttributeError: '_GeneratorContextManager' object has no
attribute 'close'
tests/conftest.py:194: AttributeError
ERROR at teardown of test_ptk_prompt[2 * 3-6]
_
xonsh_execer =
@pytest.fixture
def ptk_shell(xonsh_execer):
from prompt_toolkit.input import create_pipe_input
from prompt_toolkit.output import DummyOutput
from xonsh.ptk_shell.shell import PromptToolkitShell
inp = create_pipe_input()
out = DummyOutput()
shell = PromptToolkitShell(
execer=xonsh_execer, ctx={}, ptk_args={"input": inp,
"output": out}
)
yield inp, out, shell
inp.close()
E AttributeError: '_GeneratorContextManager' object has no
attribute 'close'
tests/conftest.py:194: AttributeError
=== FAILURES
===
test_ptk_prompt['hello'-None]
_
line = "'hello'", exp = None
ptk_shell = (0x7fcdeb517940>, 0x7fcdeacb2e90>, 0x7fcdeadac3a0>)
capsys = <_pytest.capture.CaptureFixture object at 0x7fcdeae03190>
@pytest.mark.parametrize(
"line, exp",
[
[repr("hello"), None],
["2 * 3", "6"],
],
)
def test_ptk_prompt(line, exp, ptk_shell, capsys):
inp, out, shell = ptk_shell
inp.send_text(f"{line}\nexit\n") # note: terminate with '\n'
E AttributeError: '_GeneratorContextManager' object has no
attribute 'send_text'
tests/test_ptk_shell.py:139: AttributeError
___ test_ptk_prompt[2 * 3-6]
___
line = '2 * 3', exp = '6'
ptk_shell = (0x7fcdeb2f1480>, 0x7fcdeacd6b00>, 0x7fcdeb588e20>)
capsys = <_pytest.capture.CaptureFixture object at 0x7fcdeb749c90>
@pytest.mark.parametrize(
"line, exp",
[
[repr("hello"), None],
["2 * 3", "6"],
],
)
def test_ptk_prompt(line, exp, ptk_shell, capsys):
inp, out, shell = ptk_shell
inp.send_text(f"{line}\nexit\n") # note: terminate with '\n'
E AttributeError: '_GeneratorContextManager' object has no
attribute 'send_text'
tests/test_ptk_shell.py:139: AttributeError
OpenPGP_signature
Description: OpenPGP digital signature
Processed: prompt-toolkit breaks xonsh autopkgtest: '_GeneratorContextManager' object has no attribute 'send_text'
Processing control commands: > found -1 prompt-toolkit/3.0.29-1 Bug #1010198 [src:prompt-toolkit, src:xonsh] prompt-toolkit breaks xonsh autopkgtest: '_GeneratorContextManager' object has no attribute 'send_text' Marked as found in versions prompt-toolkit/3.0.29-1. > found -1 xonsh/0.11.0+dfsg-1 Bug #1010198 [src:prompt-toolkit, src:xonsh] prompt-toolkit breaks xonsh autopkgtest: '_GeneratorContextManager' object has no attribute 'send_text' Marked as found in versions xonsh/0.11.0+dfsg-1. -- 1010198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010195: astroquery: autopkgtest regression: No module named 'PIL'
Source: astroquery Version: 0.4.6+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of astroquery the autopkgtest of astroquery fails in testing when that autopkgtest is run with the binary packages of astroquery from unstable. It passes when run with only packages from testing. In tabular form: passfail astroquery from testing0.4.6+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. To the bystander it looks like a new dependency was missed. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=astroquery https://ci.debian.net/data/autopkgtest/testing/amd64/a/astroquery/21157298/log.gz __ ERROR collecting hips2fits/tests/test_hips2fits.py __ ImportError while importing test module '/usr/lib/python3/dist-packages/astroquery/hips2fits/tests/test_hips2fits.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.10/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) /usr/lib/python3/dist-packages/astroquery/hips2fits/__init__.py:39: in from .core import hips2fits, hips2fitsClass /usr/lib/python3/dist-packages/astroquery/hips2fits/core.py:28: in from PIL import Image E ModuleNotFoundError: No module named 'PIL' __ ERROR collecting hips2fits/tests/test_hips2fits_remote.py ___ ImportError while importing test module '/usr/lib/python3/dist-packages/astroquery/hips2fits/tests/test_hips2fits_remote.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.10/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) /usr/lib/python3/dist-packages/astroquery/hips2fits/__init__.py:39: in from .core import hips2fits, hips2fitsClass /usr/lib/python3/dist-packages/astroquery/hips2fits/core.py:28: in from PIL import Image E ModuleNotFoundError: No module named 'PIL' OpenPGP_signature Description: OpenPGP digital signature
Bug#1005981: marked as done (Please migrate away from dpatch)
Your message dated Tue, 26 Apr 2022 06:19:54 + with message-id and subject line Bug#1005981: fixed in redet 8.26-1.5 has caused the Debian Bug report #1005981, regarding Please migrate away from dpatch 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.) -- 1005981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: redet Version: 8.26-1.4 Severity: serious dpatch is deprecated and will be removed before the bookworm release. Please migrate to source format 3.0 (quilt) instead. --- End Message --- --- Begin Message --- Source: redet Source-Version: 8.26-1.5 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of redet, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated redet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Apr 2022 02:26:50 -0300 Source: redet Architecture: source Version: 8.26-1.5 Distribution: unstable Urgency: medium Maintainer: Bartosz Fenski Changed-By: Joao Eriberto Mota Filho Closes: 1005981 Changes: redet (8.26-1.5) unstable; urgency=medium . * Non-maintainer upload. * Migrated to DebSrc 3.0. Consequently: - Migrated the current patch from dpatch to quilt. - Closes: #1005981 Checksums-Sha1: 88626ff1261d8568c4a4344bea5453535f445d39 1758 redet_8.26-1.5.dsc 7e112983e96063e329c77bcf34f2b4fc73d4d7ce 4028 redet_8.26-1.5.debian.tar.xz 0fec7b5ab44cb2163e272f636409b8ec5a675c39 5685 redet_8.26-1.5_source.buildinfo Checksums-Sha256: 755f007fe903fb9d8eb85462af5d4a00f23b5c1ef798ec0dcaec03b16e1b4677 1758 redet_8.26-1.5.dsc c9e85b97bd2a23d9e9f54051eb5ca8e08d685f339e646320ce25e640bef28acc 4028 redet_8.26-1.5.debian.tar.xz 2ce25b4d6cb25d6f494aea2b64ceedaa7f34446175e773e2cd87f59db5ea8edc 5685 redet_8.26-1.5_source.buildinfo Files: 65938e6ac644b30022c17c757c7e1b32 1758 x11 optional redet_8.26-1.5.dsc 7f4a47dc39b15c783aaded9498d0aec2 4028 x11 optional redet_8.26-1.5.debian.tar.xz 063d4d3b9c059677b291944d1c476613 5685 x11 optional redet_8.26-1.5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJaVLUACgkQ3mO5xwTr 6e9fbhAAiAD4ykRsWxiBujHE/Yzq4E3ANNSKjhD1PQw6Ux3VW8EAmel3tOOwGtS+ 6xmjzQuw81+7+vQsTawVStw3bj81siop/7fB/9NeudU5WGoFPEq6xTns5umhf+vK 2LxjUo+0QTIg/Wp7NzYzY0uD1F0QFEp5szaUN8mO+3FCxhWyXwVgIdI5yP3PCGq/ 1eVjuUMDhCRybg6ZGAKJMeG3EDIJJ1lqqKIVRfxfdE0EyK4mVeXBNmG9NGlVsf73 SVwrg1Ig6emfZXTmTmevGP3gezLIN456Jwau1oYQ9lSr2Ujn0rfVdqn+wMDcr8Q5 n4fwskT4a09FNIjP3RzIdabmmW5CdFGZ5kEZa0UGdZ6E2c18iJWabRqO6YtT8I5H sx9kRGvoZBD15cFb/SKP+h2N32H/dXO2BVnY9VuKo2dcZY3nwce+UQ1y4iw9+hra d6BmFCQuIkt18EB1yaJ4vq4Ukje3s2b8C/qG5THoYFAd8wvBaqdNRU7tfQjKQ6PL DHmAz9R28e145tYb88rImvMrxDjxnGJ118h+UAF4tBPhYKqMcTugQsgb5x9xrWHl NWxLR3w0pT/gB7PU8iaFKEJLdwGm3XZN3kvurfKT95ZaA/6/cEUG/cu6Xbecx0GD lbyUslQhTKP2XvhqcIhmkaIYlTYcyiP9+JyRf50jV/QPvbE/mV8= =53VA -END PGP SIGNATURE End Message ---
