From sales08 at kingunionledlight.com Thu May 5 14:40:49 2022 From: sales08 at kingunionledlight.com (Julie Liao) Date: Thu, 05 May 2022 13:40:49 +0000 Subject: =?utf-8?q?Segmented_Multi-Color_Lighting-RGBIC_0817=C2=A0Neon_Fl?= =?utf-8?q?ex?= Message-ID: <20220505134049.c14e90876e012da9@mg.cool-bird.cn> An HTML attachment was scrubbed... URL: From admin at winreportinc.com Fri May 13 03:22:14 2022 From: admin at winreportinc.com (Fendi Zhang) Date: Fri, 13 May 2022 10:22:14 +0800 (GMT+08:00) Subject: =?UTF-8?B?SGlnaCBQdXJpdHkgQm9laG1pdGUgVHJlbmRzIGFuZCBPcHBvcnR1bml0aWVzIEZvciBZb3UgIA==?= Message-ID: Hi. We published A Global Market Outlook Report on High Purity Boehmite 2022 for You and Competitors. If you have further interest in this report or related reports, we would be happy to share the sample report for your reference. The following manufacturers are covered: Nabaltec Estone Chinalco Sasol SINOCERA TOR Minerals Kawai Lime Industry Dequenne Chimie Osang Group Silkem KC TAIMEI Chemicals ...... Segment by Type Purity (99.0%-99.9%) Purity (above 99.9%) Segment by Application Lithium Battery Diaphragm Flame Retardant Ceramic Others Maybe it will be helpful to the marketing department or the person in charge of your company. We would be grateful if you could forward it. ---------------------- Best Regards Fendi Zhang | Sales Manager QYResearch INC. Phone: +86 137 6333 8542(7*24H), +1-626 2952 442(US) E-mail: fendi at qyresearch.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomas.bayon at heilbronn.dhbw.de Sat May 14 09:04:02 2022 From: tomas.bayon at heilbronn.dhbw.de (=?iso-8859-1?Q?Bay=F3n=2C_Tom=E1s_Prof=2E_Dr=2E?=) Date: Sat, 14 May 2022 08:04:02 +0000 Subject: Spende: 2 Million Euros Message-ID: <87EFD1C14C49794FB0F7727B6A7B8B850136619B@hn-ex2.heilbronn.dhbw.de> Sehr geehrter Beg?nstigter, Herzlichen Gl?ckwunsch, Ihre E-Mail hat 2 Millionen Euro gewonnen. Wenden Sie sich an die untenstehende E-Mail-Adresse, um einen Anspruch geltend zu machen E-Mail: vickysafrafoundation at yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From cso at utamaglobalindocargo.com Sat May 14 14:23:55 2022 From: cso at utamaglobalindocargo.com (=?UTF-8?B?44CQSVQg5LyY5YyW44CR?=) Date: Sat, 14 May 2022 21:23:55 +0800 Subject: =?UTF-8?B?cGtnLXB5dGhvbi1kZWJpYW4tbWFpbnTlhbPkuo466L2s56e7LeS8mOWMli3p?= =?UTF-8?B?gJrnn6XvvIE=?= Message-ID: <202205142123506978979@utamaglobalindocargo.com>

pkg-python-debian-maint at lists.alioth.debian.org

?????????????????????????????????????????????????????????????????????????5?17??????????????????????????????????????????????????????????????????????????

-----------------------------------------------------------------------------------

???????????????????

 1.??????????

 2.?????????????????????4??????3??

 3.?????????????

 4.???????????????

-----------------------------------------------------------------------------------

???? mail.??-?????

-----------------------------------------------------------------------------------

Dear :The superior informed the personnel of all departments that the login passwords of all users of the enterprise mailbox of Changhong company may be leaked. In order to avoid the loss of data, please re record and register in time. At that time, delete the mailbox that has not been logged in for a long time. All departments are required to operate according to the guidelines. If it is not recorded, it will be regarded as an unused account and the service will be suspended. Thank you for your cooperation!

 -----------------------------------------------------------------------------------

 Before filing, please carefully read the following account password rules: 1. Please fill in the current correct password;; 2. The password must meet the complexity requirements. 3. The password cannot include your full account name; 4. After filing, the filing password shall not be changed at will.

-----------------------------------------------------------------------------------

Visit ????.com Filing Center

 -----------------------------------------------------------------------------------

-------------- next part -------------- An HTML attachment was scrubbed... URL: From aglaw at nulau.edu.ua Tue May 17 23:05:15 2022 From: aglaw at nulau.edu.ua (aglaw at nulau.edu.ua) Date: Tue, 17 May 2022 22:05:15 -0000 Subject: CHARITY!!!! Message-ID: It is a great previledge to be in a position to help others and for that reason i will be making a donation of $1,000,000(Million) to you from Thomas Yi,winner of $235.4 million Powerball Jackpot 2021,for more information please contact via email: thomasyi.org at gmail.com Thanks. -- This email has been checked for viruses by AVG. https://www.avg.com From sales08 at kingunionledlight.com Tue May 24 11:30:28 2022 From: sales08 at kingunionledlight.com (Julie Liao) Date: Tue, 24 May 2022 10:30:28 +0000 Subject: New Arrival Dot-Free SMD2025 LED Strip Anti Broken Holder design Message-ID: <20220524103028.c022ac0fd38b65b8@mg.cool-bird.cn> An HTML attachment was scrubbed... URL: From noreply at release.debian.org Thu May 26 06:39:22 2022 From: noreply at release.debian.org (Debian testing autoremoval watch) Date: Thu, 26 May 2022 05:39:22 +0000 Subject: python-debian is marked for autoremoval from testing Message-ID: python-debian 0.1.43 is marked for autoremoval from testing on 2022-06-30 It (build-)depends on packages with these RC bugs: 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 https://bugs.debian.org/1011146 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl From stephanlachnit at debian.org Fri May 27 09:05:47 2022 From: stephanlachnit at debian.org (Stephan Lachnit) Date: Fri, 27 May 2022 10:05:47 +0200 Subject: Bug#1011937: python-debian: Please consider moving deb822 to a standalone distro-independent Python package Message-ID: <165363874790.57092.1598103857686408427.reportbug@sldesktop> Source: python-debian Version: 0.1.43 Severity: wishlist X-Debbugs-Cc: stephanlachnit at debian.org, max.mehl at fsfe.org I'm working on a project that aims to use REUSE [1] to automate the process of creating and maintaing the d/copyright file. tl;dr: REUSE is a specification to annote license and copyright holder in a machine-readable way in the source files itself. Since Debian has a similar per-file copyright concept, using information from source packages that follow this specification can in principle be automated to reduce the work maintainers have to do. For several reasons it would be nice to have a d/copyright parser at hand, and since python-debian provides this with the deb822 module, it would be unneccessary work to write this again. REUSE already uses python-debian for this, but wants to get rit of it because there are some issue with this module on non-Debian OSes [2]. To come to the topic of this wishlist-bugreport: would it be possible to factor the deb822 parser out in a completetly separate Python package (on PyPi), e.g. python3-deb822, that explicitly does not depend on a Debian environment? Cheers, Stephan [1]: https://reuse.software/ [2]: https://github.com/fsfe/reuse-tool/issues/466 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled From jelmer at jelmer.uk Fri May 27 10:15:00 2022 From: jelmer at jelmer.uk (Jelmer =?UTF-8?Q?Vernoo=C4=B3?=) Date: Fri, 27 May 2022 09:15:00 +0000 Subject: Bug#1011937: python-debian: Please consider moving deb822 to a standalone distro-independent Python package In-Reply-To: <165363874790.57092.1598103857686408427.reportbug@sldesktop> References: <165363874790.57092.1598103857686408427.reportbug@sldesktop> <165363874790.57092.1598103857686408427.reportbug@sldesktop> Message-ID: Hi Stephan, On Fri, May 27, 2022 at 10:05:47AM +0200, Stephan Lachnit wrote: > I'm working on a project that aims to use REUSE [1] to automate the > process of creating and maintaing the d/copyright file. > > tl;dr: REUSE is a specification to annote license and copyright holder > in a machine-readable way in the source files itself. Since Debian has a > similar per-file copyright concept, using information from source > packages that follow this specification can in principle be automated to > reduce the work maintainers have to do. > > > For several reasons it would be nice to have a d/copyright parser at > hand, and since python-debian provides this with the deb822 module, it > would be unneccessary work to write this again. REUSE already uses > python-debian for this, but wants to get rit of it because there are > some issue with this module on non-Debian OSes [2]. > > > To come to the topic of this wishlist-bugreport: would it be possible to > factor the deb822 parser out in a completetly separate Python package > (on PyPi), e.g. python3-deb822, that explicitly does not depend on a > Debian environment? What are the portability issues that exist in non-Debian environments? I'd prefer to address those if possible rather than factoring out the deb822 module, since that complicates on an ongoing basis in the future. FWIW python-debian is packaged in other Linux distributions, so my guess is that the issue is non-Linux rather than non-Debian environments? https://repology.org/project/python:debian/versions Jelmer From jelmer at jelmer.uk Fri May 27 10:15:00 2022 From: jelmer at jelmer.uk (Jelmer =?UTF-8?Q?Vernoo=C4=B3?=) Date: Fri, 27 May 2022 09:15:00 +0000 Subject: Bug#1011937: python-debian: Please consider moving deb822 to a standalone distro-independent Python package In-Reply-To: <165363874790.57092.1598103857686408427.reportbug@sldesktop> References: <165363874790.57092.1598103857686408427.reportbug@sldesktop> <165363874790.57092.1598103857686408427.reportbug@sldesktop> Message-ID: Hi Stephan, On Fri, May 27, 2022 at 10:05:47AM +0200, Stephan Lachnit wrote: > I'm working on a project that aims to use REUSE [1] to automate the > process of creating and maintaing the d/copyright file. > > tl;dr: REUSE is a specification to annote license and copyright holder > in a machine-readable way in the source files itself. Since Debian has a > similar per-file copyright concept, using information from source > packages that follow this specification can in principle be automated to > reduce the work maintainers have to do. > > > For several reasons it would be nice to have a d/copyright parser at > hand, and since python-debian provides this with the deb822 module, it > would be unneccessary work to write this again. REUSE already uses > python-debian for this, but wants to get rit of it because there are > some issue with this module on non-Debian OSes [2]. > > > To come to the topic of this wishlist-bugreport: would it be possible to > factor the deb822 parser out in a completetly separate Python package > (on PyPi), e.g. python3-deb822, that explicitly does not depend on a > Debian environment? What are the portability issues that exist in non-Debian environments? I'd prefer to address those if possible rather than factoring out the deb822 module, since that complicates on an ongoing basis in the future. FWIW python-debian is packaged in other Linux distributions, so my guess is that the issue is non-Linux rather than non-Debian environments? https://repology.org/project/python:debian/versions Jelmer From stephanlachnit at debian.org Fri May 27 11:01:17 2022 From: stephanlachnit at debian.org (Stephan Lachnit) Date: Fri, 27 May 2022 12:01:17 +0200 Subject: Bug#1011937: python-debian: Please consider moving deb822 to a standalone distro-independent Python package In-Reply-To: References: <165363874790.57092.1598103857686408427.reportbug@sldesktop> <165363874790.57092.1598103857686408427.reportbug@sldesktop> Message-ID: Hi Jelmer, Thanks for the quick response! I'm not an expert on python-debian and I don't use other distros than Debian, so I can only forward you some bug reports from https://github.com/fsfe/reuse-tool/issues/466: - https://github.com/fsfe/reuse-tool/issues/311 (fixed now) - https://github.com/fsfe/reuse-tool/issues/425: `apt_pkg.Error: W:Unable to read /etc/apt/apt.conf.d/ - DirectoryExists (2: No such file or directory), E:Unable to determine a suitable packaging system type` This one is probably tricky to solve, maybe python-debian can check if it is in a Debian env by checking /etc/os-release? Ofc if python-debian would ensure cross-platform operability, that would be great, then there would be no need for a package split. I guess it depends a bit on the policy: is it tested on non-Debian platforms or just an afterthought where bugs get fixed when reported in version? If it is the latter, REUSE will probably still try to replace it. If it is the former, I think there is little reason to move away from python-debian. cc/ Max Mehl? Looking quickly at the CI though, it does not seem that this is currently the case. Maybe you could add a `unit-tests-alpine` and `unit-tests-windows` job based on the official Python Docker images [1] (w/ dependencies pulled via pip)? IMHO this should give enough confidence in the cross-platform operability of this package (again cc/ Max Mehl, I'm not a developer of REUSE). Best, Stephan [1]: https://hub.docker.com/_/python On Fri, May 27, 2022 at 11:15 AM Jelmer Vernoo? wrote: > > Hi Stephan, > > On Fri, May 27, 2022 at 10:05:47AM +0200, Stephan Lachnit wrote: > > I'm working on a project that aims to use REUSE [1] to automate the > > process of creating and maintaing the d/copyright file. > > > > tl;dr: REUSE is a specification to annote license and copyright holder > > in a machine-readable way in the source files itself. Since Debian has a > > similar per-file copyright concept, using information from source > > packages that follow this specification can in principle be automated to > > reduce the work maintainers have to do. > > > > > > For several reasons it would be nice to have a d/copyright parser at > > hand, and since python-debian provides this with the deb822 module, it > > would be unneccessary work to write this again. REUSE already uses > > python-debian for this, but wants to get rit of it because there are > > some issue with this module on non-Debian OSes [2]. > > > > > > To come to the topic of this wishlist-bugreport: would it be possible to > > factor the deb822 parser out in a completetly separate Python package > > (on PyPi), e.g. python3-deb822, that explicitly does not depend on a > > Debian environment? > > What are the portability issues that exist in non-Debian environments? I'd > prefer to address those if possible rather than factoring out the deb822 > module, since that complicates on an ongoing basis in the future. > > FWIW python-debian is packaged in other Linux distributions, so my guess > is that the issue is non-Linux rather than non-Debian environments? > https://repology.org/project/python:debian/versions > > Jelmer From jelmer at debian.org Fri May 27 11:09:29 2022 From: jelmer at debian.org (Jelmer =?UTF-8?Q?Vernoo=C4=B3?=) Date: Fri, 27 May 2022 11:09:29 +0100 Subject: Bug#1011937: python-debian: Please consider moving deb822 to a standalone distro-independent Python package In-Reply-To: References: <165363874790.57092.1598103857686408427.reportbug@sldesktop> <165363874790.57092.1598103857686408427.reportbug@sldesktop> <165363874790.57092.1598103857686408427.reportbug@sldesktop> Message-ID: On Fri, May 27, 2022 at 12:01:17PM +0200, Stephan Lachnit wrote: > I'm not an expert on python-debian and I don't use other distros than > Debian, so I can only forward you some bug reports from > https://github.com/fsfe/reuse-tool/issues/466: > - https://github.com/fsfe/reuse-tool/issues/311 (fixed now) > - https://github.com/fsfe/reuse-tool/issues/425: `apt_pkg.Error: > W:Unable to read /etc/apt/apt.conf.d/ - DirectoryExists (2: No such > file or directory), E:Unable to determine a suitable packaging system > type` > This one is probably tricky to solve, maybe python-debian can check > if it is in a Debian env by checking /etc/os-release? > > Ofc if python-debian would ensure cross-platform operability, that > would be great, then there would be no need for a package split. I > guess it depends a bit on the policy: is it tested on non-Debian > platforms or just an afterthought where bugs get fixed when reported > in version? If it is the latter, REUSE will probably still try to > replace it. If it is the former, I think there is little reason to > move away from python-debian. cc/ Max Mehl? It looks like reuse doesn't juse use deb822, but the copyright module as well - so just extracting deb822 would not be sufficient: https://github.com/fsfe/reuse-tool/issues/454 > Looking quickly at the CI though, it does not seem that this is > currently the case. Maybe you could add a `unit-tests-alpine` and > `unit-tests-windows` job based on the official Python Docker images > [1] (w/ dependencies pulled via pip)? IMHO this should give enough > confidence in the cross-platform operability of this package (again > cc/ Max Mehl, I'm not a developer of REUSE). I'd prefer that avenue; we could potentially disable some of the functionality on windows (e.g. stuff that relies on python3-apt, which AFAIK is already optional). >From what I can tell, the testsuite runs fine on other Linux platforms - we haven't had many bugreports from packagers on those platforms. I wouldn't be surprised if people came along in the future that e.g. needed watch file parsing on Windows or copyright file parsing, and I wouldn't want to have to split out all of those as separate modules as well. Cheers, Jelmer > On Fri, May 27, 2022 at 11:15 AM Jelmer Vernoo? wrote: > > > > Hi Stephan, > > > > On Fri, May 27, 2022 at 10:05:47AM +0200, Stephan Lachnit wrote: > > > I'm working on a project that aims to use REUSE [1] to automate the > > > process of creating and maintaing the d/copyright file. > > > > > > tl;dr: REUSE is a specification to annote license and copyright holder > > > in a machine-readable way in the source files itself. Since Debian has a > > > similar per-file copyright concept, using information from source > > > packages that follow this specification can in principle be automated to > > > reduce the work maintainers have to do. > > > > > > > > > For several reasons it would be nice to have a d/copyright parser at > > > hand, and since python-debian provides this with the deb822 module, it > > > would be unneccessary work to write this again. REUSE already uses > > > python-debian for this, but wants to get rit of it because there are > > > some issue with this module on non-Debian OSes [2]. > > > > > > > > > To come to the topic of this wishlist-bugreport: would it be possible to > > > factor the deb822 parser out in a completetly separate Python package > > > (on PyPi), e.g. python3-deb822, that explicitly does not depend on a > > > Debian environment? > > > > What are the portability issues that exist in non-Debian environments? I'd > > prefer to address those if possible rather than factoring out the deb822 > > module, since that complicates on an ongoing basis in the future. > > > > FWIW python-debian is packaged in other Linux distributions, so my guess > > is that the issue is non-Linux rather than non-Debian environments? > > https://repology.org/project/python:debian/versions > > > > Jelmer > > -- > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-python-debian-maint From owner at bugs.debian.org Sat May 28 08:12:03 2022 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 28 May 2022 07:12:03 +0000 Subject: Processed: Bug#875305 marked as pending in python-debian References: <6291ca9c7e56f_3b2fb4367c@godard.mail> <59b549e7.5be0620a.e018c.78b2@mx.google.com> Message-ID: Processing control commands: > tag -1 pending Bug #875305 [python3-debian] Support for finding changelog.Debian.gz in perl-base Added tag(s) pending. -- 875305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875305 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From niels at thykier.net Sat May 28 08:16:35 2022 From: niels at thykier.net (Niels Thykier) Date: Sat, 28 May 2022 09:16:35 +0200 Subject: Bug#994911: error modifying deb822 object while iterating In-Reply-To: References: <858fe96c-e213-2d72-8b33-e335bc798e96@thykier.net> Message-ID: Control: tags -1 moreinfo unreproducible On Thu, 14 Oct 2021 19:17:47 +0000 Jelmer Vernooij wrote: > [...] > Yep, this is standard behaviour with a dict - so I wouldn't be surprised if > this was happening generally, but the default deb822 doesn't exhibit > this so it makes migrating a bit harder. > > Unfortunately I've lost track of the run in the janitor that > showed this issue so we'll just have to re-enable and see > if it's fixed now. > > Jelmer > > > Hi Jelmer, Can you still reproduce this bug? I suspect it might have been fixed as a side-effect of another change already. Alternative, if you can reproduce it, please attach the code + file that triggers the bug so I can investigate it in detail. Thanks, ~Niels From owner at bugs.debian.org Sat May 28 08:36:03 2022 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 28 May 2022 07:36:03 +0000 Subject: Processed: Re: error modifying deb822 object while iterating References: Message-ID: Processing control commands: > tags -1 moreinfo unreproducible Bug #994911 [python3-debian] error modifying deb822 object while iterating Added tag(s) moreinfo and unreproducible. -- 994911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994911 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From stuart at debian.org Sat May 28 15:51:10 2022 From: stuart at debian.org (Stuart Prescott) Date: Sun, 29 May 2022 00:51:10 +1000 Subject: Bug#1011937: python-debian: Please consider moving deb822 to a standalone distro-independent Python package In-Reply-To: References: <165363874790.57092.1598103857686408427.reportbug@sldesktop> <165363874790.57092.1598103857686408427.reportbug@sldesktop> Message-ID: <2535405.UMHQ6L3ysD@simurgh> Hi Stephan, On Friday, 27 May 2022 20:09:29 AEST Jelmer Vernoo? wrote: > On Fri, May 27, 2022 at 12:01:17PM +0200, Stephan Lachnit wrote: > > I'm not an expert on python-debian and I don't use other distros than > > Debian, so I can only forward you some bug reports from Thanks! I'd spotted one of these in the past but not others. > > https://github.com/fsfe/reuse-tool/issues/466: I'd definitely rather make python-debian more portable than have projects forking bits of it into local vendored versions. Vendoring code creates technical debt and is somewhat antithetical to the idea of making code more reusable. > > - https://github.com/fsfe/reuse-tool/issues/425: `apt_pkg.Error: > > W:Unable to read /etc/apt/apt.conf.d/ - DirectoryExists (2: No such > > file or directory), E:Unable to determine a suitable packaging system > > type` As already noted, python-debian works fine without python-apt installed; the unexpected situation here is that python-apt is installed but non-functional in some way. I'm not sure whether the bug is really that a non-functional python-apt is installed, but if we can work around it, then even better. I have a feeling that we can change the way we use apt_pkg these days and that we can avoid generating that error. I need to talk to the python-apt people about that, but also I also need a way of reproducing an environment where a non-functional python-apt is installed so that I can test this out. From https://salsa.debian.org/python-debian-team/python-debian/-/ merge_requests/85 > > Since Alpine really doesn't offer anything, a lot of fail because of > > missing `bin/ar`, which is an excellent test for a non-Debian-standard > > environment. Not sure how this should be handled best though: maybe > > something similar to the `have_apt_pkg` variable? This is only the tests and in particular, it's making the test data -- ArFile and DebFile are actually much more portable (except for the zstd compressed .debs where there remain portability problems because of the requirement for a zstd binary). It's only the tests that need the 'ar' binary and nothing in the module code itself. There's a few options here: * require that ar be installed for the purposes of testing just as we do in Debian; this is an explicit dependency in Debian, not something that happens to be there because more batteries are included. The binutils package gives us ar and is listed in debian/control, it's just that Python hasn't come up with a way of expressing such dependencies in setup.py or similar. For alpine, ar is in the binutils package and there are a few different versions available for windows, such as via a gcc package from choco. * use something else to make the .deb files for the test suite. I could imagine a fallback for missing ar(1) that uses a pure python ar implementation that can be installed via pip on these other platforms. The arpy module can't make ar files at present which is a shame; the `unix_ar` or `ar` modules look promising for that, there might be others. https://github.com/getninjas/unix_ar https://github.com/vidstige/ar * skip the tests that need ar; in practice, that's probably all the tests from debian/tests/test_debfile.py, and so a module level skip might be appropriate, with something like ``` pytestmark = pytest.mark.skipif(not shutil.which("ar"), reason="...") ``` I'm cautious about automatically skipping tests because that's a route to non- determinism, accidentally skipping tests, and therefore missing problems. However, we do that for python-apt already, so there's precedent already in the code; I'd be fine with that as a short term solution in advance of something better. Thanks in advance for your contribution to python-debian :) cheers Stuart -- Stuart Prescott http://www.nanonanonano.net/ stuart at nanonanonano.net Debian Developer http://www.debian.org/ stuart at debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 From ftpmaster at ftp-master.debian.org Sun May 29 15:39:56 2022 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Sun, 29 May 2022 14:39:56 +0000 Subject: Processing of python-debian_0.1.44_source.changes Message-ID: python-debian_0.1.44_source.changes uploaded successfully to localhost along with the files: python-debian_0.1.44.dsc python-debian_0.1.44.tar.xz python-debian_0.1.44_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) From ftpmaster at ftp-master.debian.org Sun May 29 16:08:28 2022 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Sun, 29 May 2022 15:08:28 +0000 Subject: python-debian_0.1.44_source.changes ACCEPTED into unstable Message-ID: Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sun, 29 May 2022 12:06:57 +1000 Source: python-debian Architecture: source Version: 0.1.44 Distribution: unstable Urgency: medium Maintainer: Debian python-debian Maintainers Changed-By: Stuart Prescott Closes: 875305 Changes: python-debian (0.1.44) unstable; urgency=medium . [ Simon Chopin ] * Add support for zstd compression in .deb files (LP: #1923845) with thanks also to Athos Ribeiro and Quirin Pamp for contributions to this feature. . [ Jelmer Vernoo? ] * Use logging.warning rather than warnings for data problems. . [ Stuart Prescott ] * Support for finding files (including changelog.Debian.gz) that are beyond a symlink within the package (Closes: #875305). * Update packaging for zstd compressed .deb code. * Annotate binutils build-dep with . * Update Standards-Version to 4.6.1 (no changes required). . [ Niels Thykier ] * Various improvements to the round-trip-safe deb822 parser. Checksums-Sha1: d07f3fbcac502baf59cc116af51e6eb5871fd890 2246 python-debian_0.1.44.dsc 078545d834703d1cfc8a638e358676cb66996ddc 179372 python-debian_0.1.44.tar.xz 2ae014e6a34ccf1f31033f60748b9db8888226d8 7150 python-debian_0.1.44_amd64.buildinfo Checksums-Sha256: e7316a837285321e18967473b2f9a12eab73d23f8512486064a74912b79bdb2d 2246 python-debian_0.1.44.dsc cc71205d3ebedbce97ef81e8da0c7c31cca62589683623b54497561d7b34430d 179372 python-debian_0.1.44.tar.xz 5e76db62293281c9c0cd3e528ba369f7cc1d0c1617871c967f3800d1feee63f2 7150 python-debian_0.1.44_amd64.buildinfo Files: 3cea58b57e59eadded0c6326f9f021f6 2246 python optional python-debian_0.1.44.dsc fcff9b3aebaa7b2ce48802225d9f8db2 179372 python optional python-debian_0.1.44.tar.xz 46697afbabd39150859bc65c8ded1471 7150 python optional python-debian_0.1.44_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAmKS1ekACgkQu8F+uxOW 8ve3FQ//fTkybDE63DWMN3rOPpsBP4a0IGyu+84+QKqa1BAMNcsrNRV9XTK9a6TH laMbciySyGVelKMjKS/BbqHX4Z1T8tGXJhgX0fIE0u9QOoR5GKsp7g2fKHawgOUH IAz3UQ6Og28W0CyaPHMN/S8t6B53G1T2bda0j5y/lce8756b4W9yshGREK1RKLKX xTjysYmI1xCK5TbBfvLTswd8RZLVGSwx4CEoYcve9TUulOI+xKR4LhudBT1AuPd2 SPQpH0lA8qh6U9xNwAWeo4kUTSZyFZAo/bMcj0PG3Kxo/vUHhtNDjHxkZ3g63Qpr Nudo+JvbNZNR4VD/WnmbID2I6w7j1GIqb2f2bteNaFc6gtfl0dYBPyIUVYEjI91g 1adAHSVBbagv4eQvHV6OnVnyl3a7ol+PqfepnlOlo8OcK7WDJvp0R0cwZ7zHyxRF PcThHLk7Cz+mmy9TSkrHOlfT8dwZwAtsiZ3sXGsH0dxCerN3A8hqsF9EhCJMVps9 Sv45Pty8y5HTvtZ7+H/AifDh5iX/qPzCV8+gp0QGce3cvGt1H429hem3uP51wEl+ AMLpJuBekaju2CLM1VB5Hc+eKZsB1ZTO4LeCT+N9gxpWMzGeKQBOzyT//bGCabDg 6z1C3LBYh4KjcH9kXbjJKwMOkKJ/sis2gRfilVpmXeae65APBZo= =gDSN -----END PGP SIGNATURE----- Thank you for your contribution to Debian. From owner at bugs.debian.org Sun May 29 16:12:02 2022 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sun, 29 May 2022 15:12:02 +0000 Subject: Bug#875305: marked as done (Support for finding changelog.Debian.gz in perl-base) References: <59b549e7.5be0620a.e018c.78b2@mx.google.com> Message-ID: Your message dated Sun, 29 May 2022 15:08:29 +0000 with message-id and subject line Bug#875305: fixed in python-debian 0.1.44 has caused the Debian Bug report #875305, regarding Support for finding changelog.Debian.gz in perl-base 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 owner at bugs.debian.org immediately.) -- 875305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875305 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Stuart Prescott Subject: Support for finding changelog.Debian.gz in perl-base Date: Mon, 11 Sep 2017 00:19:15 +1000 Size: 9765 URL: -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters Subject: Bug#875305: fixed in python-debian 0.1.44 Date: Sun, 29 May 2022 15:08:29 +0000 Size: 6686 URL: