Bug#985825: virtual rms considered mostly harmless
control: severity -1 important thanks So my plan is to replace src:vrms with src:check-dfsg-status and to provide a nice upgrade path and I might try to get this done for bullseye (caugh), (if) with the support of the release team, or maybe not. Then this would be my plan for bookworm. In any case this will be staged in experimental soon. However the outcome of this plan, I do think a virtual rms package in bullseye (after having that for the last X years) is ok, it's virtual after all - and having such a tool is also very worthwhile and enjoyed by many. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C ⠈⠳⣄ Society: Be Yourself! Society: No, not like that. signature.asc Description: PGP signature
Processed: virtual rms considered mostly harmless
Processing control commands: > severity -1 important Bug #985825 [vrms] vrms should not be part of bullseye Severity set to 'important' from 'serious' -- 985825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 984463, found 985743 in 20210322-1~exp1, found 985740 in 20210322-1~exp1 ...
Processing commands for cont...@bugs.debian.org:
> affects 984463 + recoll
Bug #984463 {Done: Kartik Mistry } [recollgui] recollgui:
missing Breaks+Replaces: recollcmd (<< 1.28)
Added indication that 984463 affects recoll
> found 985743 20210322-1~exp1
Bug #985743 {Done: maximilian attems } [firmware-qcom-soc]
firmware-qcom-soc: broken symlink: /lib/firmware/qcom/sdm845/wlanmdsp.mbn ->
../../ath10k/WCN3990/hw1.0/wlanmdsp.mbn
Marked as found in versions firmware-nonfree/20210322-1~exp1 and reopened.
> found 985740 20210322-1~exp1
Bug #985740 {Done: maximilian attems } [firmware-brcm80211]
firmware-brcm80211: broken symlink:
/lib/firmware/brcm/brcmfmac43362-sdio.lemaker,bananapro.txt ->
brcmfmac43362-sdio.cubietech,cubietruck.txt
Marked as found in versions firmware-nonfree/20210322-1~exp1 and reopened.
> found 986071 1:2.2.0-1
Bug #986071 [libmrpt-vision-lgpl-dev] libmrpt-vision-lgpl-dev: broken symlink
/usr/lib/x86_64-linux-gnu/libmrpt-vision-lgpl.so -> libmrpt-vision-lgpl.so.2.1
Marked as found in versions mrpt/1:2.2.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984463
985740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985740
985743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985743
986071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#986389: bfh-server: please add Breaks: exim4-config
Package: bfh-server Version: 20210101-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a similar issue like #985658 in progress-linux-server exists in bfh-server, too. I'd assume the same solution will work here, too, but I haven't tried it. [partially quoting from #985658] during a test with piuparts I noticed your package failed to install with --install-recommends enabled. (It installed fine with --install-recommends disabled.) Apt does not find a proper dependency solution due to exim vs. postfix, but adding a Breaks: exim4-config to progress-linux-server makes the install succeed because possible solutions that include installing exim (because some dependency of progress-linux-server (transitively) recommends some MTA) are discarded early and postfix wins. >From the attached log (scroll to the bottom...): 0m12.5s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmp9dNz5P', 'apt-get', '-y', 'install', 'bfh-server=20210101-1'] 0m13.1s DUMP: Reading package lists... Building dependency tree... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: exim4-config : Conflicts: postfix but 3.5.6-1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. 0m13.1s ERROR: Command failed (status=100): ['chroot', '/srv/piuparts/tmp/tmp9dNz5P', 'apt-get', '-y', 'install', 'bfh-server=20210101-1'] cheers, Andreas bfh-server_20210101-1.log.gz Description: application/gzip
Processed: Re: php-finder-facade: FTBFS: Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage()
Processing control commands: > tags -1 patch Bug #978334 [phpdox] php-finder-facade: FTBFS: Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage() Added tag(s) patch. -- 978334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978334: php-finder-facade: FTBFS: Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage()
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/0009-Compatibility-with-php-timer-4.0.patch: Cherrypick upstream
commit to fix compatibility with php-timer >= 4.0.
Thanks for considering the patch.
Logan
diff -Nru
phpdox-0.12.0/debian/patches/0009-Compatibility-with-php-timer-4.0.patch
phpdox-0.12.0/debian/patches/0009-Compatibility-with-php-timer-4.0.patch
--- phpdox-0.12.0/debian/patches/0009-Compatibility-with-php-timer-4.0.patch
1969-12-31 19:00:00.0 -0500
+++ phpdox-0.12.0/debian/patches/0009-Compatibility-with-php-timer-4.0.patch
2021-04-04 18:35:45.0 -0400
@@ -0,0 +1,54 @@
+From a71dfe4ffce072eb8402e5fd5303e6b3076ee0e7 Mon Sep 17 00:00:00 2001
+From: homerjsimpson000
+Date: Mon, 14 Dec 2020 09:13:14 +0100
+Subject: [PATCH] Update ShellProgressLogger.php
+
+Use ResourceUsageFormatter instead of Timer::resourceUsage to enable updating
to use both Timer ^2.0 and Timer 5.0.*
+---
+ src/logger/ShellProgressLogger.php | 26 +-
+ 1 file changed, 25 insertions(+), 1 deletion(-)
+
+diff --git a/src/logger/ShellProgressLogger.php
b/src/logger/ShellProgressLogger.php
+index 1017dda1..d76fdfd4 100644
+--- a/src/logger/ShellProgressLogger.php
b/src/logger/ShellProgressLogger.php
+@@ -1,6 +1,7 @@
+ resourceUsage();
+ print "\n\n";
+ }
++
++/**
++ * @return string
++ */
++private function resourceUsage(): string {
++$result = '';
++
++if(
++class_exists(ResourceUsageFormatter::class) &&
++method_exists(ResourceUsageFormatter::class,
'resourceUsageSinceStartOfRequest')
++) {
++/** @var ResourceUsageFormatter $resource */
++$resource = new ResourceUsageFormatter();
++$result = $resource->resourceUsageSinceStartOfRequest();
++} else if(
++class_exists(Timer::class) &&
++method_exists(Timer::class, 'resourceUsage')
++) {
++$result = Timer::resourceUsage();
++}
++
++return $result;
++}
+ }
diff -Nru phpdox-0.12.0/debian/patches/series
phpdox-0.12.0/debian/patches/series
--- phpdox-0.12.0/debian/patches/series 2020-12-21 07:03:11.0 -0500
+++ phpdox-0.12.0/debian/patches/series 2021-04-04 18:35:45.0 -0400
@@ -6,3 +6,4 @@
0006-Compatibility-with-recent-PHPUnit-8.patch
0007-Drop-versioned-dependency-that-can-t-be-satisfied.patch
0008-Adapt-to-recent-version-of-PHPUnit-9.patch
+0009-Compatibility-with-php-timer-4.0.patch
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 978334 phpdox 0.12.0-4 Bug #978334 [src:php-finder-facade] php-finder-facade: FTBFS: Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage() Bug reassigned from package 'src:php-finder-facade' to 'phpdox'. No longer marked as found in versions php-finder-facade/1.2.3-1 and php-finder-facade/2.0.0-1. Ignoring request to alter fixed versions of bug #978334 to the same values previously set Bug #978334 [phpdox] php-finder-facade: FTBFS: Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage() Marked as found in versions phpdox/0.12.0-4. > affects 978334 src:php-finder-facade Bug #978334 [phpdox] php-finder-facade: FTBFS: Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage() Added indication that 978334 affects src:php-finder-facade > thanks Stopping processing here. Please contact me if you need assistance. -- 978334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983389: closed by Debian FTP Masters (reply to Yangfl ) (Bug#983389: fixed in finit 4.0~rc3-1)
On Sat, Mar 20, 2021 at 08:27:07PM +, Debian Bug Tracking System wrote: >... > finit (4.0~rc3-1) unstable; urgency=medium > . >* New upstream release >* Enable some services by default (Closes: #983389) >... If finit should be in bullseye, this bug needs a more targeted fix that fixes only the bug and does not include a new upstream version. cu Adrian
Bug#986384: [Courier-imap] courier and maildrop it seems does not work as xpected
Source: courier Severity: grave Justification: causes non-serious data loss I setup both : real system users and virtual ones, both servers have mixed users nature (system ones and virtuals) The specific build removal of the courier-maildrop package breaks the courier MTA utilizing the virtual accounts tools, noted that some variables are imported that normal build of maildrop does not! (I compared the rules files of both), those are HOME, SHELL, LOGNAME and MAILDIRQUOTA while the standalone version won't. MArkus.. i revised and checked related bugs in debian and it seems that standar "maildrop" package is a piece of crap respect of this.. for working i must get back the older courier-maildrop and builds my own package from courier sources, can you get back the build of courier-maildrop i remember that i previously send a request about this! SAM: but,i cannot understand pretty well .. we need to clarify this cos i try to reproduce and i dont know if this was the problem, i do not set any sticky bit in home users.. but my home users are under a subdirectory.. maybe this can be misinterpreted? i found this problem randomly in newer versions of debian packages (i try to compile from sources and i do not have such problem) and in one particular scenery ALWAYS are reproducible: a) server are in a migration of ip and upgrading of programs b) there's some dynamic deliveries pending c) mail queue has almost 200 thousands of pending mails When I changed the DNS to the new server with exact configuration, but another ip, mails are delivered in log and courier system, but if you use lasted maildrop debian shit it does not work! all the new mails are delivered and dissapears (are in queue only but log as delivered) El dom, 4 de abr. de 2021 a la(s) 12:04, Sam Varshavchik ( mr...@courier-mta.com) escribió: > PICCORO McKAY Lenz writes: > > > I have installed maildrop (no longer courier-maildrop) and I am > surprised to > > find that the mails are not arriving at Maildir user place, even > > at /var/mail/spool/$USER file! . that's i ask here to you guys cos i > dont > > know if the problem is dropmail debian package (build separately puff) > or > > courier.. > > It's a long-standing problem with the debian package. > > > I define correctly the maildellivery in imap etc etc but I notice that > the > > mail is in /var/spool/mail instead of in the user's home... and I > already > > defined in /etc/maildroprc the DEFAULT > > Except that the standalone maildrop build is not going to know what the > DEFAULT is, without the appropriate -d option. > > I do not remember any more details, this problem comes up every once in a > while. > > ___ > Courier-imap mailing list > courier-i...@lists.sourceforge.net > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap >
Bug#974616: nomacs: "charset=Ascii" appears before the comment of the image
On 2020-12-14 23:45:06, Vincent Lefevre wrote: > Control: retitle -1 nomacs uses internal libexiv2 functions to get the user > comment > Control: severity -1 serious > Control: tags -1 - patch > > On 2020-12-12 21:59:38 +0100, Vincent Lefevre wrote: >> I'm attaching the patch I've written. There was already a function >> that removes substrings of the form 'charset="ASCII"' case >> insensitively. So I do the same thing with 'charset=ASCII' >> (i.e. without the double-quotes) and 'charset=Unicode', which >> appears when the string has non-ASCII characters. >> >> Note that this function is a hack: it will remove real occurrences >> of such strings, not just those added by libexiv2. However, there >> is very little probability that such strings really appear in the >> comment. And one cannot do much better to fix the issue. > > This is just a workaround that seems to work with the current > libexiv2 version, but according to the upstream libexiv2 maintainer, > nomacs uses some internal libexiv2 function, which means that an > update of libexiv2 can break it at any time, potentially introducing > security issues. > > Note that a change of behavior could have already been seen with the > upgrade of libexiv2-27 to 0.27.3 with the appearance of spurious data > before the comment. > > The correct way to get the comment with the public API is > > std::string comment = Exiv2::CommentValue(value().toString()).comment()); > > Note: The upstream nomacs version comes with a bundled libexiv2, > meaning that this may not be an issue to use internal libexiv2 > features. Debian chose to use the shared library, thus it needs > to replace these internals by calls to the public API. Is this fixed upstream, in the latest 3.16 release? I mean I understand that it *still* bundles exiv2 and friends: https://github.com/nomacs/nomacs/tree/master/3rd-party ... but maybe their usage of the library improved? There is #974617 for upgrading to 3.16... a. -- By now the computer has moved out of the den and into the rest of your life. It will consume all of your spare time, and even your vacation, if you let it. It will empty your wallet and tie up your thoughts. It will drive away your family. Your friends will start to think of you as a bore. And what for? - The True Computerist by Tom Pittman
Bug#985509: marked as done (libeinfo-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libeinfo.so -> libeinfo.so.1)
Your message dated Sun, 04 Apr 2021 16:54:56 + with message-id and subject line Bug#985509: fixed in openrc 0.42-2.1 has caused the Debian Bug report #985509, regarding libeinfo-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libeinfo.so -> libeinfo.so.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.) -- 985509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libeinfo-dev Version: 0.42-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m23.7s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libeinfo.so -> libeinfo.so.1 (libeinfo-dev:amd64) libeinfo1 ships /lib/x86_64-linux-gnu/libeinfo.so.1 cheers, Andreas libeinfo-dev_0.42-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: openrc Source-Version: 0.42-2.1 Done: Mark Hindley We believe that the bug you reported is fixed in the latest version of openrc, 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 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Hindley (supplier of updated openrc 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: Fri, 02 Apr 2021 11:16:00 +0100 Source: openrc Architecture: source Version: 0.42-2.1 Distribution: unstable Urgency: medium Maintainer: OpenRC Debian Maintainers Changed-By: Mark Hindley Closes: 985509 Changes: openrc (0.42-2.1) unstable; urgency=medium . * Non-maintainer upload. * Make -dev package symlinks in /usr/lib target shared libraries in /lib. (Closes: #985509). Checksums-Sha1: d28af760f2af398aa4346ef47567ce8351b7 2209 openrc_0.42-2.1.dsc aede5ca936b5bf2b0b73c3ca87d15daf8ee59a15 26552 openrc_0.42-2.1.debian.tar.xz 3275ded0cfe38756746ed58bef0119b75fd179ce 7811 openrc_0.42-2.1_amd64.buildinfo Checksums-Sha256: 7f34bd3e6a29bf0153fba18ab6c4d0f16e6345fa1e7a6d14fb678e13920f269f 2209 openrc_0.42-2.1.dsc e80f62af6c9a8432189aeb4c6956b14676dd7659ea757a44514457b89d8bed1c 26552 openrc_0.42-2.1.debian.tar.xz 3e1305f5177cb7c542d4f71f46b499d4a504232a0b053b844a5bdaee39f335e8 7811 openrc_0.42-2.1_amd64.buildinfo Files: 5e55b01dacb117ac6d390438d4be02e8 2209 admin optional openrc_0.42-2.1.dsc 01ff941385cfc9266cc59eaa9bdb36bb 26552 admin optional openrc_0.42-2.1.debian.tar.xz ffd7f0a0e323e0d3d98c5eb2882dafb8 7811 admin optional openrc_0.42-2.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEUGwVpCsK9aCoVCPu0opFvzKH1kkFAmBnQ7IACgkQ0opFvzKH 1knCkxAApzDrB0NK3tYmgVwUnstJqfnvHSlMQI/RLoWERxidw5vqur1QCQ+zuEmZ 4C9/gcAVYnBZaNHcVcpHK7+rtHOYUYBKUHedVfuaRIy03hV/XMJ4gScrJg+lfhvM dS4TnxdSWKmjxMfzI1L8lZO4nEl/7jqD5IHEMcFeumUDA9TXmw2oFpy0sq0MZYRD dX+A17uJw2oBuTY3CcdDa9eCXkZE00Os7Gy5j1Ai74+bUoKC4O5zrDCASunlYjqv gzVK4O6m6/tg7uRyz8BXes3fqUmhzXOrxetCnVqumosT8PNaZqtCyxms73e/QhA3 c4cFV5YJ1jzZ62qWmX0MHVTn4r61tvreT9nmzgUWNr6wJ0t4Q1ugHnwslGDosA+W k5OqBLPBwK57eBztzpp3AZy/OkssV/LH8doY3Yvk3cU41E5unam8SdXhsmpsGOCP pUc9WOICqgZMgjqDzSJGRg434a7AR9lON/+6SYwXj20UMbeQAArcGNNYIOj5hF8b Dn+3VnjwsNiHoptWiP6/aEfVstI9sOzbKMKB0H1joOtQ4ALMe6T4y/9871rP/WIJ d8wKks2xIcqz2h+45CtObGEh1dcJ1ZmU6qwNnowC0IzdP5D1iwifKOi0Be8wpNey aj5N/Dfj9VO+2cIdnlaleM5L0qQHLYIjmtX39w6ZwP0N/XAZAlA= =us94 -END PGP SIGNATURE End Message ---
Bug#984439: marked as done (netgen: FTBFS on armhf (unaligned access on arm64 kernel))
Your message dated Sun, 04 Apr 2021 12:33:28 + with message-id and subject line Bug#984439: fixed in netgen 6.2.2006+really6.2.1905+dfsg-2.1 has caused the Debian Bug report #984439, regarding netgen: FTBFS on armhf (unaligned access on arm64 kernel) 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.) -- 984439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netgen Version: 6.2.2006+really6.2.1905+dfsg-2 Severity: serious Hello, looks like the package FTBFS on armhf with an arm64 kernel. See e.g. builds from reproducible-builds.org https://tests.reproducible-builds.org/debian/logs/unstable/armhf/netgen_6.2.2006+really6.2.1905+dfsg-2.build2.log.gz Can you please have a look? thanks Gianfranco --- End Message --- --- Begin Message --- Source: netgen Source-Version: 6.2.2006+really6.2.1905+dfsg-2.1 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of netgen, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated netgen 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: Fri, 02 Apr 2021 14:05:03 +0200 Source: netgen Architecture: source Version: 6.2.2006+really6.2.1905+dfsg-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Gianfranco Costamagna Closes: 984439 Changes: netgen (6.2.2006+really6.2.1905+dfsg-2.1) unstable; urgency=medium . * Non-maintainer upload. * debian/patches/4fad6e0631718a4bb574d67505e0ebfef1f171ce.patch: - upstream fix for armhf build failure (Closes: #984439) Checksums-Sha1: 790c8c8378644cd4743500e4fdefb038d3040093 2805 netgen_6.2.2006+really6.2.1905+dfsg-2.1.dsc f94262fdd206d297492b57383b0d4996b7dc9d55 16700 netgen_6.2.2006+really6.2.1905+dfsg-2.1.debian.tar.xz f34dd569040070d1d0598e6962cce51517a09d8f 13483 netgen_6.2.2006+really6.2.1905+dfsg-2.1_source.buildinfo Checksums-Sha256: 31c5359939a901240e654b7e9245a1348ed34bfc513fbb03e41e31c6fa0ec322 2805 netgen_6.2.2006+really6.2.1905+dfsg-2.1.dsc 4968c715dcd89940b7c96c0d8e12408af71294065343d750f55217c5f6feca16 16700 netgen_6.2.2006+really6.2.1905+dfsg-2.1.debian.tar.xz 9ee5f615f1cbd526475a0bf4d0b1234f78c26b3c29b2b2c35e778e70569bd5b6 13483 netgen_6.2.2006+really6.2.1905+dfsg-2.1_source.buildinfo Files: aec7c8ab8d16a92883e2ea1a65c99b58 2805 math optional netgen_6.2.2006+really6.2.1905+dfsg-2.1.dsc 3dd7229886b1447325a2e74a14333929 16700 math optional netgen_6.2.2006+really6.2.1905+dfsg-2.1.debian.tar.xz ca5603a63728b98780545d5cd6bb85ad 13483 math optional netgen_6.2.2006+really6.2.1905+dfsg-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmBnCHgACgkQ808JdE6f XdnkExAAwPD7aIDFOr98CxqjrQ8/L1bz6KKtoaMeAzIsobVz5HVrGDzSjq7QknC0 jTUX2ua7nnkrTZ5NXtGZDR/Re6btmzzwsnJ2CBWn/xQW9Pb7jksiZJGAuL+7f6ID SGKAhO5h2QP5ylvE+4gRWzOVIdkJ79cUkOpJ03HvWGwhz6TkHAyBKMCmuP/Ww2m6 iyBznWAd1EhurqKshyHO+M9Qwes6zL4Yt4Q72WXX9Kv2ilFRkCpt/9/rrVTPynyq HreljdyV2tJRi7QYPKzCVJyw8Wc/hUbOG5a0hFdWWx6JwurZsKho6+0z7So1db4y iPj3ESgmwQXlo8woNxREs2MmckVX/ildHLxx46qMsXOpEsziF34nrWEhIyYt8AT1 3KlKUSyfggusFFBa6dYHSCmxg/tMJqQV16lettRaBN0ityqYagbuNuHFFLaf50E6 l4aBd6bFwy1T3kp8/GXDOR0YtFYZ6qY2JgnzCA2VaMD2nJof0Xcfe7iQeas+GHMI Di18sfmV4abSJFrk6/gUyp5ClwjdAIobeYbeB84xoqpaiDzu5zJ7D1GokQ97HZ7k ATSUEdkmh/sGY3t9fcPX+RrkrVakMlRhj3+GjgvWYzr4HYPHPFshlRIf1j/H1h5V aa+l/1a9Y1UNMX9ugyA4XzbtzLlqOd8E3YxX8dDuVuWMwDJ9feU= =DfYR -END PGP SIGNATURE End Message ---
Processed: Bug#983853 marked as pending in horizon
Processing control commands: > tag -1 pending Bug #983853 [openstack-dashboard] openstack-dashboard: fails to upgrade from 'buster': Couldn't find anything to import: /horizon/lib/font_awesome/scss/font-awesome.scss Added tag(s) pending. -- 983853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983853: marked as pending in horizon
Control: tag -1 pending Hello, Bug #983853 in horizon 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/openstack-team/services/horizon/-/commit/17117aafea05398ebf02c390a7dfa3a56f6bdb41 * Revert previous fix, which is in fact a problem in the fonts-font-awesome package and should be handled there: see bug #986220. (Closes: #983853). (this message was generated automatically) -- Greetings https://bugs.debian.org/983853
Bug#986351: hplip: Printing Places All Jobs On Hold
severity 986351 important thanks On Sat 03 Apr 2021 at 21:17:00 -0400, Roger wrote: [...] > This issue happens often. The system is Debian 10, with Xfce 4.12 and > an HP Photosmart C3100 Series All-in-One printer running on USB > connection. All updates have been applied as notified by the OS > system. > > In trying to install it: > hplip is already the newest version (3.18.12+dfsg0-2). > > > cups runs fine, but it cannot release the files, even when attempting > to do so directly. Thank you for your report, Roger. Please give the output of lpinfo -v Do you mean "often" or "always"? Regards, Brian.
Processed: Re: Bug#986351: hplip: Printing Places All Jobs On Hold
Processing commands for cont...@bugs.debian.org: > severity 986351 important Bug #986351 [hplip] hplip: Printing Places All Jobs On Hold Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 986351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986238: marked as done (gubbins: broken symlink: /usr/bin/gubbins_drawer -> ../share/gubbins/gubbins_drawer.py)
Your message dated Sun, 04 Apr 2021 11:18:22 + with message-id and subject line Bug#986238: fixed in gubbins 2.4.1-4 has caused the Debian Bug report #986238, regarding gubbins: broken symlink: /usr/bin/gubbins_drawer -> ../share/gubbins/gubbins_drawer.py 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.) -- 986238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gubbins Version: 2.4.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m42.3s ERROR: FAIL: Broken symlinks: /usr/bin/gubbins_drawer -> ../share/gubbins/gubbins_drawer.py (gubbins) cheers, Andreas gubbins_2.4.1-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gubbins Source-Version: 2.4.1-4 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of gubbins, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated gubbins package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Apr 2021 16:11:03 +0530 Source: gubbins Architecture: source Version: 2.4.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 986238 Changes: gubbins (2.4.1-4) unstable; urgency=medium . * Team upload. * Fix symlink to right place (Closes: #986238) Checksums-Sha1: 0fc7a97c0b3bb3308c566bfee866b40681610efc 2193 gubbins_2.4.1-4.dsc a444135f3956bef243fd7ce195b1af24c52eb069 6988 gubbins_2.4.1-4.debian.tar.xz c4fc793fbfcf71cd25c3e1e92da3c57be1e5baf1 8128 gubbins_2.4.1-4_amd64.buildinfo Checksums-Sha256: cd60e5a604dae8dfed02006e80750a18de380073f81cb6922cc87487073884a4 2193 gubbins_2.4.1-4.dsc 32ec94912079a05c0f3fdfc2e56f3807b21f16a75d2081dc2ae6422a8adc0a17 6988 gubbins_2.4.1-4.debian.tar.xz 7d8733ec0f127bb2007866ad054f1e904d4eadce6cef2ada24ed756f3fc48be7 8128 gubbins_2.4.1-4_amd64.buildinfo Files: 7a86021b3176d8c938b2c77acac2f382 2193 science optional gubbins_2.4.1-4.dsc 436dc6a3cbd3c71225f28cb3843d1df8 6988 science optional gubbins_2.4.1-4.debian.tar.xz f93109fc9daddb3ba899289dd847d869 8128 science optional gubbins_2.4.1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmBpmrAUHG5wYXRyYTk3 NEBnbWFpbC5jb20ACgkQALrnSzQzafFpXw//RB28Xj4cJ3pxr5U6BDyv4ttHHCNq SX6c2AdWPBrzEx8/Lta5AOrza3tEl/yLfHu5x6qozrqPNUEI9pCZ+vEXAcZxHVdg eD3TYkyaSVH6Q2cjISkhNCUQb9CLqXzosoBd/sXkYFTUu0675D70Cgq8CPffj6QG pZhYB7Ytxs4OhSe3IgVzMfA5mDUjP6e6IAt5sOQBJhEWSQQScD6/ZtyAdP22AziU 9jD9WKnaqHwLMnVv4Fk1CcFMObk7mYTm+UYKfgOyRubiD7E07ab1IDg5glOLwjsp cBUChB0dDx5IfOTqbA/k0S7zieQtdNUPMBs7AhwV8U7mBsiH8mFLTwLnUEtakYaN EkFMzA+H51zDeIctWU4k4kMSsD/DnAgzc+K/nuTRG7s0J5nrWg52Qf8TNKSfYYyw KjEkuAoUQGu0QwgISGJfTyUGWpkaQKQPSVBLQ77UCh2opqt0gYIqHyeVV9+oohn5 kIv5CbQ4aKKnVdq1VYW2ZwPdm1NoA1m9GlTX3wgiBLJ9RDGlJB878C9kgORK/NwS pVjSk0yK9QIpXSV/L4+CV1zxOd6v7j+QZL1YYVqJaYwwLoC84teWr7s/YFGeG4Wy hYDm9j8cBKYpV/kRclj450nA+V09931126INHt2pYhg0Pl5VJC2NY5fAGk3wsJe9 jhSo95ArabFLFxU= =H2B2 -END PGP SIGNATURE End Message ---
Processed: Mark as fixed
Processing commands for cont...@bugs.debian.org:
> fixed 986307 1.4.2-7
Bug #986307 {Done: Nilesh Patra } [src:scrappie] scrappie:
flaky armhf autopkgtest: Invalid control character at: line 1 column 91 (char
90)
Marked as fixed in versions scrappie/1.4.2-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
986307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#986307: marked as done (scrappie: flaky armhf autopkgtest: Invalid control character at: line 1 column 91 (char 90))
Your message dated Sun, 4 Apr 2021 15:24:03 +0530
with message-id
and subject line Re: [Debian-med-packaging] Bug#986307: marked as done
(scrappie: flaky armhf autopkgtest: Invalid control character at: line 1 column
91 (char 90))
has caused the Debian Bug report #986307,
regarding scrappie: flaky armhf autopkgtest: Invalid control character at: line
1 column 91 (char 90)
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.)
--
986307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scrappie
Version: 1.4.2-4
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
Your package has an autopkgtest, great. However, I looked into
the history of your autopkgtest [1] and I noticed the it fails regularly
on armhf, while sporadically a rerun passes. I copied some of the output
at the bottom of this report. It seems there's regularly a non-printable
character at the end of the UUID of the first two tests too, including
in this case.
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.
Paul
[1] https://ci.debian.net/packages/s/scrappie/testing/armhf/
https://ci.debian.net/data/autopkgtest/testing/armhf/s/scrappie/11240539/log.gz
autopkgtest [22:23:14]: test run-unit-test: [---
Test functionality
Test 1
>read_ch228_file118.fast5 { "filename" : "read_ch228_file118.fast5",
"uuid" : "e47468bf-12e3-4208-a866-babdd780e9c0 ", "normalised_score" :
0.479833, "nblock" : 5778, "sequence_length" : 2448,
"blocks_per_base" : 2.360294, "nsample" : 29150, "trim" : [ 200, 29090 ] }
PASS
Test 2
>read_ch228_file118.fast5 { "filename" : "read_ch228_file118.fast5",
"uuid" : "e47468bf-12e3-4208-a866-babdd780e9c0%", "normalised_score" :
0.459902, "nevent" : 5787, "sequence_length" : 1695,
"events_per_base" : 3.414159 }
PASS
Test 3
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.5zv20404/downtmp/autopkgtest_tmp/misc/json_to_tsv.py",
line 5, in
first_entry = json.loads(stdin.readline())
File "/usr/lib/python3.9/json/__init__.py", line 346, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.9/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.9/json/decoder.py", line 353, in raw_decode
obj, end = self.scan_once(s, idx)
json.decoder.JSONDecodeError: Invalid control character at: line 1
column 91 (char 90)
autopkgtest [22:24:01]: test run-unit-test: ---]
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Control: fixed -1 1.4.2-7
Hi,
On Sat, 3 Apr 2021 11:39:55 +0200 Graham Inggs wrote:
> Control: reopen -1
>
> The autopkgtest now fails with:
>
> dpkg-architecture: warning: cannot determine CC system type, falling
> back to default (native compilation)
> Skip Test 3 on armhf (see bug #986307)
> autopkgtest [08:53:06]: test run-unit-test: ---]
> autopkgtest [08:53:06]: test run-unit-test: - - - - - - - - - -
> results - - - - - - - - - -
> run-unit-testFAIL stderr: dpkg-architecture: warning: cannot
> determine CC system type, falling back to default (native compilation)
> autopkgtest [08:53:06]: test run-unit-test: - - - - - - - - - -
> stderr - - - - - - - - - -
> dpkg-architecture: warning: cannot determine CC system type, falling
> back to default (native compilation)
> autopkgtest [08:53:06]: summary
> run-unit-testFAIL stderr: dpkg-architecture: warning: cannot
> determine CC system type, falling back to default (native compilation)
Fixed this in 1.4.2-7
signature.asc
Description: PGP signature
--- End Message ---
