Bug#963444: marked as done (epubcheck: FTBFS: [ERROR] /<>/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java:[267,7]

[Debian Bug Tracking System]

Your message dated Fri, 11 Sep 2020 06:48:25 +
with message-id 
and subject line Bug#963444: fixed in epubcheck 4.2.4-1
has caused the Debian Bug report #963444,
regarding epubcheck: FTBFS: [ERROR] 
/<>/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java:[267,7]
  is not 
abstract and does not override abstract method 
test(com.adobe.epubcheck.opf.ValidationContext) in java.util.function.Predicate
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.)


-- 
963444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: epubcheck
Version: 4.2.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>   mh_patchpoms -pepubcheck --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [WARNING] The project org.w3c:epubcheck:jar:4.2.2 uses prerequisites which is 
> only intended for maven-plugin projects but not for non maven-plugin 
> projects. For such purposes you should use the maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> [INFO] -< org.w3c:epubcheck 
> >--
> [INFO] Building EPUBCheck :: Validation Tool for EPUB 4.2.2
> [INFO] [ jar 
> ]-
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> epubcheck ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 5 resources to /<>/target
> [INFO] Copying 332 resources
> [INFO] Copying 1 resource
> [INFO] 
> [INFO] --- xml-maven-plugin:1.0.1:transform (default) @ epubcheck ---
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/collection-manifest-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/epub-xhtml-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/epub-svg-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/ocf-encryption-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/media-overlay-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/collection-do-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/ocf-metadata-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/package-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/epub-nav-30.sch
> [INFO] Transformed 9 file(s).
> [INFO] Transforming file: 
> /<>/target/generated-resources/intermediate-schema/collection-manifest-30.sch
> [INFO] Transforming file: 
> /<>/ta

Bug#969261: cyrus-common: bumping to debhelper 13 needs usind dh_installtmpfiles

[Jean Charles Delépine]

Package: cyrus-common
Version: 3.2.3-1
Followup-For: Bug #969261

Hello,

The file /usr/lib/tmpfile.d/cyrus-imapd.conf isn't installed anymore.
Cyrus can't start without the dirs /run/cyrus and /run/cyrus/socket
created by systemd tmpfile mechanism.

https://manpages.debian.org/testing/debhelper/dh_installsystemd.1.en.html

debian/package.tmpfile
Only used in compat 12 or earlier. In compat 13+, this file is handled by 
dh_installtmpfiles(1) instead.

If this exists, it is installed into usr/lib/tmpfiles.d/ in the package 
build directory. Note that the "tmpfiles.d" mechanism is currently only used by 
systemd.

Without this file cyrus can't start on a fresh install and can't reboot on an 
old one.

Sincerly,
Jean Charles Delépine


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (901, 'testing'), (500, 'stable'), (90, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-1-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cyrus-common depends on:
ii  adduser 3.118
ii  db-upgrade-util 5.3.1+nmu1
ii  db-util 5.3.1+nmu1
ii  debconf [debconf-2.0]   1.5.74
ii  e2fsprogs   1.45.6-1
ii  gawk1:5.0.1+dfsg-1
ii  init-system-helpers 1.58
ii  libc6   2.31-3
ii  libclamav9  0.102.4+dfsg-1+b1
ii  libcom-err2 1.45.6-1
ii  libgcc-s1   10.2.0-6
ii  libical33.0.8-2
ii  libicu6767.1-4
ii  libjansson4 2.13.1-1
ii  libkrb5-3   1.17-10
ii  libldap-2.4-2   2.4.51+dfsg-1
ii  libpcre32:8.39-13
ii  libpq5  12.4-1
ii  libsasl2-2  2.1.27+dfsg-2
ii  libsasl2-modules2.1.27+dfsg-2
ii  libsnmp35   5.8+dfsg-5
ii  libsqlite3-03.33.0-1
ii  libssl1.1   1.1.1g-1
ii  libstdc++6  10.2.0-6
ii  libwrap07.6.q-30
ii  libxapian30 1.4.17-1
ii  libxml2 2.9.10+dfsg-6
ii  libzephyr4  3.1.2-1+b3
ii  lsb-base11.1.0
ii  netbase 6.1
ii  perl5.30.3-4
ii  postfix [mail-transport-agent]  3.5.6-1
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages cyrus-common recommends:
ii  cyrus-admin  3.2.3-1

Versions of packages cyrus-common suggests:
pn  apt-listchanges
ii  cyrus-admin3.2.3-1
pn  cyrus-caldav   
ii  cyrus-clients  3.2.3-1
pn  cyrus-doc  
pn  cyrus-imapd
pn  cyrus-murder   
pn  cyrus-nntpd
pn  cyrus-pop3d
pn  cyrus-replication  
ii  sasl2-bin  2.1.27+dfsg-2

-- Configuration Files:
/etc/imapd.conf changed [not included]

-- debconf-show failed

Bug#970067: lxc-templates: bullseye: /updates -> -security

[Paul Wise]

Package: lxc-templates
Version: 3.0.4-3
Severity: serious
File: /usr/share/lxc/templates/lxc-debian
User: debian-de...@lists.debian.org
Usertags: bullseye-security

With the release of Debian bullseye and later, security updates are
provided in the bullseye-security suite instead of bullseye/updates.

The lxc-debian script appears to write an apt sources.list that will
not provide security updates for sources.list scripts created in order
to cater to Debian bullseye images. I suggest that this script check
the version of the Debian release in question using distro-info and
then if the release is 11 or higher, then use $release-security
otherwise use $release/updates as before. It is much better to use
distro-info than to hard-code the release version numbers. It might
even be a good idea to include the security suite information in
distro-info itself and look it up from there.

   $ grep -A3 -B23 /updates /usr/share/lxc/templates/lxc-debian
   write_sourceslist()
   {
   local rootfs="$1";  shift
   local release="$1"; shift
   local arch="$1";shift

   local prefix="deb"
   if [ -n "${arch}" ]; then
   prefix="deb [arch=${arch}]"
   fi

   if [ "$mainonly" = 1 ]; then
 non_main=''
   else
 non_main=' contrib non-free'
   fi

   cat >> "${rootfs}/etc/apt/sources.list" << EOF
   ${prefix} $MIRROR  ${release} main${non_main}
   EOF

   if [ "$release" != "unstable" -a "$release" != "sid" ]; then
 cat >> "${rootfs}/etc/apt/sources.list" << EOF
   ${prefix} $SECURITY_MIRROR ${release}/updates main${non_main}
   EOF
   fi
   }

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Processed: #933116 : Update ownership

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> owner 933116 Richard Hansen 
Bug #933116 [libcgi-application-plugin-viewcode-perl] 
libcgi-application-plugin-viewcode-perl: build-depends on pkg-components that 
won't be in Bullseye unless it finds a new upstream maintainer
Owner changed from Nick Morrott  to Richard Hansen 
.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
933116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#969863: marked as done (rifiuti2: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 21:22:13 +
with message-id 
and subject line Bug#969863: fixed in rifiuti2 0.7.0-2
has caused the Debian Bug report #969863,
regarding rifiuti2: autopkgtest should be marked superficial
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.)


-- 
969863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rifiuti2
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'rifiuti2' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'rifiuti2'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: rifiuti2
Source-Version: 0.7.0-2
Done: Giovani Augusto Ferreira 

We believe that the bug you reported is fixed in the latest version of
rifiuti2, 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 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated rifiuti2 
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, 10 Sep 2020 17:51:29 -0300
Source: rifiuti2
Architecture: source
Version: 0.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Giovani Augusto Ferreira 
Closes: 969863
Changes:
 rifiuti2 (0.7.0-2) unstable; urgency=medium
 .
   [ Samuel Henrique ]
   * Add salsa-ci.yml
   * Configure git-buildpackage for Debian
 .
   [ Giovani Augusto Ferreira ]
   * Bumped DH level to 13.
   * Bumped standards version to 4.5.0, no changes needed.
   * debian/control:
   - Added 'Rules-Requires-Root: no' to source stanza.
   * debian/copyright: updated packaging years.
   * debian/tests/control: add superficial restriction. (closes: #969863)
   * Set upstream metadata fields:
   - Bug-Database, Bug-Submit, Repository, Repository-Browse.
   * Run wrap-and-sort.
Checksums-Sha1:
 4d31e02891684bff2ae85848c9f9408d2a8e7183 1967 rifiuti2_0.7.0-2.dsc
 a67fb47626287ad2894b963b8994099d451ee620 4996 rifiuti2_0.7.0-2.debian.tar.xz
 fed73741eb24fc15f4112fffbf9e338598364d59 6380 rifiuti2_0.7.0-2_source.buildinfo
Checksums-Sha256:
 2e1544fbad90e72c0dd323767b93286f30899cd3e784559c8b0d607690479a3b 1967 
rifiuti2_0.7.0-2.dsc
 7f717fe6e6a8916bd5bc03c3533ce736549146c8108ee3164595a727f9a7 4996 
rifiuti2_0.7.0-2.debian.tar.xz
 bd8f1f9679320734f97fa1e70ea23984a2753f24a1f11db534a617c70e23d75e 6380 
rifiuti2_0.7.0-2_source.buildinfo
Files:
 2543aab7ee58c652a57701f3b632 1967 utils optional rifiuti2_0.7.0-2.dsc
 ef2b0025ccda32249218984dac6177e0 4996 utils optional 
rifiuti2_0.7.0-2.debian.tar.xz
 32d48a3c17d7999c686ddd83d8129f40 6380 utils optional 
rifiuti2_0.7.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEs/UaJxJhnD7NdLjheElO9yN1pmwFAl9akzIACgkQeElO9yN1
pmyeqA/8CrbV69vsXjJGvdAe67zQtPNHNxHBlGtDcNtTLIBGp0Od7LRQjUryp10v
A/j/FzvWbQrzVpk4BqzXiQMkKbgTClq/86SDPuY6SMXrImrQEQV1K+WxGQm9PXQs
2zhE8khr9HjranwDbCQXVhGcS4jncIOM+ZhJskWXPyOu8XJ8uzqvyOoLjCnkGhx+
wpdRdw4D/BAwpehf4gw88piG9NOsVlKd7mVhAIexrn5sPjrsuie7ah8gsklLeh+/
/vO0i6VKicoeUqOG/7KVJcX2aX3iKkEytYngBr7gB20oexmMvvw4mPAojeGBp2lS
lQckL5D6sfpdIgbc2Vi2YRRGCiPXk+kKmH4KW4Rgm4LfWhQpLo8ZnKN3x0w5JsH9
MQT6jnZMw9lnpn6rHzAmi2Xeteetbq5fNg4nk8YdEvPcQcixq2jgr9EgLIbkEX7U
HjUoX/v5/qxmFv/ZIagNvoheLxmToJWOdEyLdz6yJLZQ6piJTbZ3tYDXc4nsSFe0
DOIPbSKb13SI3C/O/LX/CzE4OV+xRctgIHZl70kMvDp01bS8Pn94LNUtwEtCjfPs
2JTU3d0sPQmT9UtynOXZf5FTaT83+

Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

forwarded 969592 https://gitlab.com/sane-project/backends/-/issues/352
thanks


Hello Sebastian,

the version 1.0.31-1~experimental1 was build successful on armel and armhf.But
qcam wasn't build. So I forward this bug to upstream.


CU
Jörg 


- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl9alPAACgkQCfifPIyh
0l01Qw/8DTpeg9WfVZDd2fS7Sd1rccGNfM4fJ2+nbRNzfEOHQrfvD0SO+Oiv6T2d
swDqw/gKYuoSDeZh/hO1bkWXn/rsEQPj1jsU5bAF2k22UqZD733EugmzKk1a+kWC
qyglt/sN4AUIX50K+WsFrGfDSYcJ/Yy/uGrWbiuHy4w/rRya+qzIiXm/MjchGvRJ
ORNkoVC66lXHAUR3elLsttRALOo9E5r7HUgPtBthvwasdjL7g3qQC8IbhWjb5OL8
QjJ361X150hbxFWa/HcBUNFkgihtSak/AFeElfkUaEjwjliDjz6Kl+aEdasUDIfc
9fluf1EoBzOFA2zXWo100F9b888TbCNq6cEpH345ZYoCKcoe5gGJvfbrtMO5IkCN
PBi4mRmIieHS+03EKkgTitD84jzEr19N+as4dkB8yc+GfOJVKAFPFwhcZMxivZLM
ITg2xESSlUt5CQgF5UArCkFW7MuuQsnfuGsO+S2rL8XIVeWwgxGCD7lMYfT39Crw
KgGF9bc+nVXSqf0PTtkoLSOM9LzSNZsvj3Hl2TNLGkW9o9xJb6Z1m9Py/yPd/tlu
KfzByorTKLy4dc40RxZKBylmVrQiFoA7EGDfSyQ3JJx3r/gVuedgIzoZetTMI6qp
QyC34Vy5B9i2hEZHoaAzF39qzqKahR0GAls8kHumJb6260Rxi8Y=
=wQwI
-END PGP SIGNATURE-

Processed: Re: Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 969592 https://gitlab.com/sane-project/backends/-/issues/352
Bug #969592 [src:sane-backends] sane-backends: FTBFS: +#MISSING: 1.0.27# 
sanei_pp_outb_epp@Base 1.0.25
Set Bug forwarded-to-address to 
'https://gitlab.com/sane-project/backends/-/issues/352'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
969592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#969863: marked as pending in rifiuti2

[Giovani Augusto Ferreira]

Control: tag -1 pending

Hello,

Bug #969863 in rifiuti2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/pkg-security-team/rifiuti2/-/commit/c31447af31acc09fbab1bd14178e44abf3316222


d/t/control: Add superficial restriction (closes: #969863)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/969863

Processed: Bug#969863 marked as pending in rifiuti2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #969863 [src:rifiuti2] rifiuti2: autopkgtest should be marked superficial
Added tag(s) pending.

-- 
969863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#970051: gr-gsm: FTBFS on mips64el

[Sebastian Ramacher]

Source: gr-gsm
Version: 0.42.2.20200214-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

The rebuild of gr-gsm for the gnuradio transition failed to build on
mips64el:
| 14/19 Test #14: qa_tch_f_chans_demapper ***Failed1.31 sec
| .F
| ==
| FAIL: test_sacch_tf (__main__.qa_tch_f_chans_demapper)
| SACCH/TF tests
| --
| Traceback (most recent call last):
|   File "/<>/python/qa_tch_f_chans_demapper.py", line 147, in 
test_sacch_tf
| self.assertEqual(odd,  self.sacch_fr_test(ts=3, frames=[38, 51, 64, 77, 
90, 103, 116, 129], bursts=bursts))
| AssertionError: Lists differ: ['010[445 chars]', 
'000100[107 chars]000'] != ['010[445 
chars]']
|
| First list contains 1 additional elements.
| First extra element 3:
| 
'0001'
|
| Diff is 1087 characters long. Set self.maxDiff to None to see it.
|
| --
| Ran 2 tests in 0.085s
|
| FAILED (failures=1)
|
|   Start 15: qa_tch_h_chans_demapper
| 15/19 Test #15: qa_tch_h_chans_demapper    Passed1.42 sec
|   Start 16: qa_gsm_bcch_ccch_demapper
| 16/19 Test #16: qa_gsm_bcch_ccch_demapper ..   Passed1.85 sec
|   Start 17: qa_gsm_bcch_ccch_sdcch4_demapper
| 17/19 Test #17: qa_gsm_bcch_ccch_sdcch4_demapper ...   Passed1.85 sec
|   Start 18: qa_gsm_sdcch8_demapper
| 18/19 Test #18: qa_gsm_sdcch8_demapper .   Passed1.85 sec
|   Start 19: qa_txtime_setter
| 19/19 Test #19: qa_txtime_setter ...   Passed1.21 sec
|
| 95% tests passed, 1 tests failed out of 19
|
| Total Test time (real) =  25.60 sec
|
| The following tests FAILED:
|14 - qa_tch_f_chans_demapper (Failed)
| Errors while running CTest
| make[2]: *** [Makefile:152: test] Error 8

See
https://buildd.debian.org/status/fetch.php?pkg=gr-gsm&arch=mips64el&ver=0.42.2.20200214-1%2Bb3&stamp=1599727226&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#957948: marked as done (wmmatrix: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 20:39:04 +
with message-id 
and subject line Bug#957948: fixed in wmmatrix 0.2-12.1
has caused the Debian Bug report #957948,
regarding wmmatrix: ftbfs with GCC-10
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.)


-- 
957948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wmmatrix
Version: 0.2-12
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/wmmatrix_0.2-12_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
dpkg-buildpackage: info: source package wmmatrix
dpkg-buildpackage: info: source version 0.2-12
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Torsten Werner 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
test -x debian/rules
rm -f debian/stamp-makefile-build debian/stamp-makefile-install
/usr/bin/make -C . CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro" -k clean
make[1]: Entering directory '/<>'
for i in wmMatrix.o matrix.o xutils.o yarandom.o ; do \
rm -f $i; \
done
rm -f wmMatrix
make[1]: Leaving directory '/<>'
dh_clean 
dh_clean: warning: Compatibility levels before 9 are deprecated (level 5 in use)
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory '/<>'
make[1]: 'reverse-config' is up to date.
make[1]: Leaving directory '/<>'
if [ -d "." ]; then \
  cd . && QUILT_PATCHES=/<>/debian/patches quilt --quiltrc 
/dev/null pop -a -R || test $? = 2 ; \
fi
No patch removed
rm -rf ./.pc
rm -f debian/stamp-patch*
 debian/rules build
test -x debian/rules
mkdir -p "."
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory '/<>'
make[1]: 'reverse-config' is up to date.
make[1]: Leaving directory '/<>'
cd . && QUILT_PATCHES=/<>/debian/patches quilt --quiltrc /dev/null 
push -a || test $? = 2
Applying patch Makefile.diff
patching file Makefile

Applying patch wmMatrix.c.diff
patching file wmMatrix.c

Now at patch wmMatrix.c.diff
touch debian/stamp-patched
/usr/bin/make -f debian/rules update-config
make[1]: Entering directory '/<>'
make[1]: 'update-config' is up to date.
make[1]: Leaving directory '/<>'
/usr/bin/make -C . CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro" 
make[1]: Entering directory '/<>'
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -DLinux -c wmMatrix.c -o wmMatrix.o 
-I/usr/X11R6/include/X11 -I/usr/X11R6/include
wmMatrix.c: In function ‘main’:
wmMatrix.c:248:2: warning: implicit declaration of function ‘short_uusleep’ 
[-Wimplicit-function-declaration]
  248 |  short_uusleep(DELAY);
  |  ^
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -DLinux -c matrix.c -o matrix.o 
-I/usr/X11R6/include/X11 -I/usr/X11R6/include
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -DLinux -c xutils.c -o xutils.o 
-I/usr/X11R6/inc

Bug#970050: haskell-gi-gtk: FTBFS: ghc: out of memory (requested 1048576 bytes)

[Sebastian Ramacher]

Source: haskell-gi-gtk
Version: 3.0.36-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

haskell-gi-gtk failed to build on armhf:
| [472 of 504] Compiling GI.Gtk.Objects.TextTagTable ( 
GI/Gtk/Objects/TextTagTable.hs, dist-ghc/build/GI/Gtk/Objects/TextTagTable.o )
| [473 of 504] Compiling GI.Gtk.Objects.TextBuffer ( 
GI/Gtk/Objects/TextBuffer.hs, dist-ghc/build/GI/Gtk/Objects/TextBuffer.o )
| ghc: out of memory (requested 1048576 bytes)
| make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 251
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

See 
https://buildd.debian.org/status/fetch.php?pkg=haskell-gi-gtk&arch=armhf&ver=3.0.36-1&stamp=1599676696&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

[Sebastian Ramacher]

Control: tags -1 - moreinfo

On 2020-09-10 18:37:24 +0200, Jörg Frings-Fürst wrote:
> tags 969592 +moreinfo
> thanks
> 
> Hello Sebastian,
> 
> from the log I see 
> 
> *** qcam backend requires (ioperm, inb and outb) or portaccess functions -
> disabling
> 
> which comes through  
> 
> checking for ioperm... no
> checking for i386_set_ioperm... no
> 
> I don't have a arm* machine for checking this. But I think that the kernel
> dosn't support ioperm() at buildtime. 

glibc removed support for ioperm on arm in 2.30:
https://github.com/bminor/glibc/commit/6b33f373c7b9199e00ba5fbafd94ac9bfb4337b1

Cheers

> 
> 
> CU 
> Jörg
> 
> 
> Am Samstag, den 05.09.2020, 18:11 +0200 schrieb Sebastian Ramacher
> > Source: sane-backends
> > Version: 1.0.27-3.2
> > Severity: serious
> > Tags: ftbfs sid bullseye
> > Justification: fails to build from source (but built successfully in the 
> > past)
> > 
> > sane-backends FTBFS on armel and armhf:
> > > @@ -7204,7 +7151,7 @@
> > >   sanei_pp_outb_addr@Base 1.0.25
> > >   sanei_pp_outb_ctrl@Base 1.0.25
> > >   sanei_pp_outb_data@Base 1.0.25
> > > - sanei_pp_outb_epp@Base 1.0.25
> > > +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25
> > >   sanei_pp_release@Base 1.0.25
> > >   sanei_pp_set_datadir@Base 1.0.25
> > >   sanei_pp_setmode@Base 1.0.25
> > > dh_makeshlibs: error: failing due to earlier errors
> > > make[1]: *** [debian/rules:139: override_dh_makeshlibs-arch] Error 25
> > > make[1]: Leaving directory '/<>'
> > > make: *** [debian/rules:25: binary-arch] Error 2
> > 
> > See
> > https://buildd.debian.org/status/fetch.php?pkg=sane-backends&arch=armel&ver=1.0.27-3.2%2Bb2&stamp=1599315993&raw=0
> > 
> > Cheers
> -- 
> New:
> GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
> GPG key (long) : 09F89F3C8CA1D25D
> GPG Key: 8CA1D25D
> CAcert Key S/N : 0E:D4:56
> 
> Old pgp Key: BE581B6E (revoked since 2014-12-31).
> 
> Jörg Frings-Fürst
> D-54470 Lieser
> 
> 
> git:  https://jff.email/cgit/
> 
> Threema:  SYR8SJXB
> Wire: @joergfringsfuerst
> Skype:joergpenguin
> Ring: jff
> Telegram: @joergfringsfuerst
> 
> 
> My wish list: 
>  - Please send me a picture from the nature at your home.
> 
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #969592 [src:sane-backends] sane-backends: FTBFS: +#MISSING: 1.0.27# 
sanei_pp_outb_epp@Base 1.0.25
Removed tag(s) moreinfo.

-- 
969592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#961841: fontforge FTBFS on 64bit big endian: test failures

[John Paul Adrian Glaubitz]

Hello!

This bug blocks a couple of packages from being built on big-endian targets
in Debian Ports and also causes the package to be still affected by an
RC for too long.

Any chance this can be fixed the next days? Apparently the necessary changes
have already been merged in Salsa.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#969812: marked as done (cldump: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 19:18:34 +
with message-id 
and subject line Bug#969812: fixed in cldump 0.11~dfsg-4
has caused the Debian Bug report #969812,
regarding cldump: autopkgtest should be marked superficial
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.)


-- 
969812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cldump
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'cldump' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'cldump'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: cldump
Source-Version: 0.11~dfsg-4
Done: Sudip Mukherjee 

We believe that the bug you reported is fixed in the latest version of
cldump, 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 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated cldump 
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, 10 Sep 2020 19:54:56 +0100
Source: cldump
Architecture: source
Version: 0.11~dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Sudip Mukherjee 
Closes: 969812
Changes:
 cldump (0.11~dfsg-4) unstable; urgency=medium
 .
   * QA upload.
   * Mark autopkgtest as superficial. (Closes: #969812)
Checksums-Sha1:
 677dc1d0b34d4d4b837e53020ce751cb32e9eb32 1705 cldump_0.11~dfsg-4.dsc
 6bbe93c1aff1742397bbd5d66f00a45db312da00 2688 cldump_0.11~dfsg-4.debian.tar.xz
 a181ca9da29c0bf532c94aa93ba15886ff65f1ab 5685 
cldump_0.11~dfsg-4_amd64.buildinfo
Checksums-Sha256:
 c255754e8d6be886e47fdd1dd43bd4a980930d41fde519cc5bbddc0e79b8f04b 1705 
cldump_0.11~dfsg-4.dsc
 66d332a59ae4c9a945b75048421da5710d9d6e46c0a6311f2cb99e977d7599ea 2688 
cldump_0.11~dfsg-4.debian.tar.xz
 a4981d0c0efd20f43e4af1dc192d36c130e682224b0f608a4149b2749482526a 5685 
cldump_0.11~dfsg-4_amd64.buildinfo
Files:
 ce1dd85457eede591ac5443c5c069c8d 1705 misc optional cldump_0.11~dfsg-4.dsc
 1dd7f54b8cfb5eb39e3731b43fff55f1 2688 misc optional 
cldump_0.11~dfsg-4.debian.tar.xz
 02b283d8484729b10d3c598bb5fd67fc 5685 misc optional 
cldump_0.11~dfsg-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAl9ad6EACgkQR5mjUUbR
KzW6Ig//dkYrNr1YZ0rS+bZRNG7Q2FRFY9uf/31FUhjZT6K6zqXVfYP7OZdHYbWV
2oBr6JwdLgbeBLEjTKctNGM9Ld+i4OZ0oNzkxjDR33vIYakS9HCCqeKhhH65WoAa
STy5kwroy7xc2xA6XEfGZzYSa+H1F+8TLWtcVPknY06L4lPPbCkrS7fEUFZRM0+Y
2brCsMF0MHXoiO55dGHX+1vADzXRg4kTB8sOU/HAtpHQPGPjgJi1lsWOljKtP0uZ
JIsqdC2/bHE6O4ImJ8oZlvrqn9p582ub52wSW+VkR5ZURX210fIl8EwY/NV3NYLH
gXROHsy3UIHZ1mz172cCm+NRBoqeoxqPLnUv4SPquTgM4p1FqJbJonq3V2DcHJ2q
oSKuP6ssOPEGfIQS6fFK5OUVRNeUlg7PP9iHwxRHF4a0C1zXn1YHmB8n3XLW8qOH
ZIAHlrJxKcm7ZHHfF+jdvlVLwzoLieLum0qINeYRiNBBG2D50iRe9XhN9IpVVecQ
QXcMMaEM8KDcbWQ5csL3mJOsIBpsyM935HgjdQSS5WFiRTUauTBDsARJYS/TIqHt
vcE/hZSMsK5N4UzZRhoctVb00RCIPGm5GeZq0xGtCaSqPr1h0tPoiBz7zXfXMxs+
rC5Tp89WX52Akl8Vog451bKUCaESiMMcLB2WnDb31Z2Idp6LM5k=
=SEF5
-END PGP SIGNATURE End Message ---

Bug#969788: nextcloud-desktop: Upgrade removed part of configuration

[Tobias Frost]

On Thu, 10 Sep 2020 19:27:37 +0200 Tobias Frost  wrote:
> I'll see if I can find some logs…

Ok, it seems so that my instance deletes its configuration itself…

But I think that needs a word on my configuration:
~/Documents is synced with my Nextcloud intance
I have setup XDG_DATA and XDG_CONFIG to be on
~/Documents/XDG/$hostname/{XDG_DATA XDG_CONFIG}
(to be able to share XDG configurations files on complicant apps more easy
between PCs)

~/Documents/XDG/isildor/XDG_CONFIG/Nextcloud is a symlink to ~/.config/Nextcloud
 (so it is not on the share)

It seems that nextcloud app is deleting that file, (following the symlink)

Of course this could be a read herring, as I naively tried to reconfigure 
the nextcloud without deleting Documents and I just got conflict everywhere now.

It is possible the the app is following the symlink and thinks, hey , file not
on the nextcloud server, delete it… Could be another bug though; (I guess it
should not follow symlinks, at least it used to ignore symlinks when syncing to
servers)

Next step I'll try a fresh resync…

-- 
tobi

Bug#970036: libopenmpi-dev fails to install

[Gianfranco Costamagna]

control: tags -1 patch

On Thu, 10 Sep 2020 21:05:09 +0300 Adrian Bunk  wrote:
> Package: libopenmpi-dev
> Version: 4.0.5-2
> Severity: grave
> Tags: ftbfs
> Control: affects -1 src:scotch src:starpu
> 
> ...
> Setting up libopenmpi-dev:amd64 (4.0.5-2) ...
> update-alternatives: error: alternative path 
> /usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/include doesn't exist
> dpkg: error processing package libopenmpi-dev:amd64 (--configure):
> 
> 

grep DEB_HOST_MULTIARCH . -R |grep "\["
./debian/libopenmpi-dev.postinst:   --install 
/usr/include/$[DEB_HOST_MULTIARCH}/mpi mpi-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/include 50 \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/libmpi.so libmpi.so-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/lib/libmpi.so \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/libmpi++.so libmpi++.so-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/lib/libmpi_cxx.so \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi.pc mpi.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi.pc \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi-fort.pc 
mpi-fort.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi-fort.pc \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi-c.pc 
mpi-c.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi-c.pc \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi-cxx.pc 
mpi-cxx.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi-cxx.pc


sed "s/\$\[DEB_HOST_MULTIARCH}/\${DEB_HOST_MULTIARCH}/g" -i 
./debian/libopenmpi-dev.postinst
*might* do the trick here :)

G.

Processed: Re: libopenmpi-dev fails to install

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #970036 [libopenmpi-dev] libopenmpi-dev fails to install
Added tag(s) patch.

-- 
970036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#966653: Any progress?

[GCS]

Hi Thomas,

On Wed, Sep 9, 2020 at 8:42 AM Thomas Goirand  wrote:
> On 9/8/20 5:20 PM, László Böszörményi (GCS) wrote:
> > I even suspect the real bug is in GitLab itself, it
> > may not (correctly) handle the new gRPC version.
>
> If so, can we lower the severity of the bug to important?
 It's about GitLab so Pirate should be in charge here. On the other
hand, as I see he can't provide a small reproduction case and as
GitLab is a Sid only package (due to other reasons) I would say go
ahead and lower the severity.

Cheers,
Laszlo/GCS

Bug#970036: libopenmpi-dev fails to install

[Adrian Bunk]

Package: libopenmpi-dev
Version: 4.0.5-2
Severity: grave
Tags: ftbfs
Control: affects -1 src:scotch src:starpu

...
Setting up libopenmpi-dev:amd64 (4.0.5-2) ...
update-alternatives: error: alternative path 
/usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/include doesn't exist
dpkg: error processing package libopenmpi-dev:amd64 (--configure):

Processed: libopenmpi-dev fails to install

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:scotch src:starpu
Bug #970036 [libopenmpi-dev] libopenmpi-dev fails to install
Added indication that 970036 affects src:scotch and src:starpu

-- 
970036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#969788: nextcloud-desktop: Upgrade removed part of configuration

[Tobias Frost]

> 
> Can anyone confirm the problems of Erwan?

\o

I had 3 server configuration; after upgrade and reboot 
all those configurations were gone. I was prompted with an 
"first run" wizard.

apt.log says I was updating nextcloud-desktop:amd64 (2.6.4-1 -> 3.0.1-1)

Obersvations:
- I did not instantly reboot after instantly.
- Today, before the reboot, I had the nextcloud app hanging and needed to kill
it. 

I'll see if I can find some logs…

--
tobi

Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

tags 969592 +moreinfo
thanks

Hello Sebastian,

from the log I see 

*** qcam backend requires (ioperm, inb and outb) or portaccess functions -
disabling

which comes through  

checking for ioperm... no
checking for i386_set_ioperm... no

I don't have a arm* machine for checking this. But I think that the kernel
dosn't support ioperm() at buildtime. 


CU 
Jörg


Am Samstag, den 05.09.2020, 18:11 +0200 schrieb Sebastian Ramacher
> Source: sane-backends
> Version: 1.0.27-3.2
> Severity: serious
> Tags: ftbfs sid bullseye
> Justification: fails to build from source (but built successfully in the past)
> 
> sane-backends FTBFS on armel and armhf:
> > @@ -7204,7 +7151,7 @@
> >   sanei_pp_outb_addr@Base 1.0.25
> >   sanei_pp_outb_ctrl@Base 1.0.25
> >   sanei_pp_outb_data@Base 1.0.25
> > - sanei_pp_outb_epp@Base 1.0.25
> > +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25
> >   sanei_pp_release@Base 1.0.25
> >   sanei_pp_set_datadir@Base 1.0.25
> >   sanei_pp_setmode@Base 1.0.25
> > dh_makeshlibs: error: failing due to earlier errors
> > make[1]: *** [debian/rules:139: override_dh_makeshlibs-arch] Error 25
> > make[1]: Leaving directory '/<>'
> > make: *** [debian/rules:25: binary-arch] Error 2
> 
> See
> https://buildd.debian.org/status/fetch.php?pkg=sane-backends&arch=armel&ver=1.0.27-3.2%2Bb2&stamp=1599315993&raw=0
> 
> Cheers
- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl9aVkQACgkQCfifPIyh
0l1QXw//ec5SAyJBzhMcetEKS9ZzSIuVayVz7uBNp5+y24lkYQWHP65RSJfzZGZ4
nx4BLAS/8sYjvHSAAMt5uPQ0SkcyzJVkDpzfi6iqckKYinvYIrZUgFU/NIOgamo3
9REatQltfVMh93MqVUFkQjt78aJfvoGgYoNtbCCmxYpwNcLmYxc6rbBRarKTDvYW
JQ/rMYBM4UuziRhSxpwqd3XFA0NAl4PpyfHW7T2sDXUINLJTc862amxKaiILLM/J
1ED1HDrj29thTQN0KNkkhCyQfAkOzZLbrk+TNMc/2WzPUXJ8HAyJTdN3L4JgPOYm
UySUQ+Xv/2hATUKQgNOr/HFkXlXIi4Ov7mwWT5Qo/jyu6tIRxorI0AD+WWKYzQC/
seAjEKYyQMtPDnZ6eNWcf8xkkIDLXdzksDlYBYt0lx87ydh6x+jfiJh/xFVb/BZk
clL0CniYx7QUnCA3x0wEYSZNtzFlQPiTbJnERBMH5r1R9654JAb8zCvRjc2pvQYi
CBCYO2I4az7A+ABn5TTH4y5cANXjLc6P0bQO/zLi968VXD4yfm7d8mVVA7zAO7f+
z+TCAww5iUbLfzwJ6Wf8+ygdERSTQpswMQwfygQal9xF88v9bp+gcCNaYFqG0B5T
b0qOZMx2ZM15yctIaLB54MkvvuAxxeuIZvlWRCmJ3fQT432/MGI=
=BswM
-END PGP SIGNATURE-

Processed: Re: Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 969592 +moreinfo
Bug #969592 [src:sane-backends] sane-backends: FTBFS: +#MISSING: 1.0.27# 
sanei_pp_outb_epp@Base 1.0.25
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
969592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#962936: marked as done (sane-backends: please still keep libsane transitional package around)

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 16:19:04 +
with message-id 
and subject line Bug#962936: fixed in sane-backends 1.0.31-1~experimental1
has caused the Debian Bug report #962936,
regarding sane-backends: please still keep libsane transitional package around
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.)


-- 
962936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sane-backends
Version: 1.0.30-1~experimental2
Severity: serious

Hello, I tried to upgrade from the old sane-backends to the new one, and 
libsane in some condition
was not removed, and sane-utils were removed as result.

I don't know how and why, but adding back libsane as transitional package 
helped in doing the upgrade in a smooth
way.

The trivial patch uploaded in Ubuntu is here:

diff -Nru sane-backends-1.0.30/debian/changelog 
sane-backends-1.0.30/debian/changelog
--- sane-backends-1.0.30/debian/changelog   2020-05-31 07:23:01.0 
+
+++ sane-backends-1.0.30/debian/changelog   2020-06-14 11:36:40.0 
+
@@ -1,3 +1,11 @@
+sane-backends (1.0.30-1~experimental2ubuntu1) groovy; urgency=medium
+
+  * Sync from debian experimental, Remaining changes:
+- add back libsane transitional package, to ease upgrades.
+  (this can be dropped after 22.04)
+
+ -- Gianfranco Costamagna   Sun, 14 Jun 2020 
13:36:40 +0200
+
 sane-backends (1.0.30-1~experimental2) experimental; urgency=medium
 
   * debian/not-installed:
diff -Nru sane-backends-1.0.30/debian/control 
sane-backends-1.0.30/debian/control
--- sane-backends-1.0.30/debian/control 2020-05-26 10:15:40.0 +
+++ sane-backends-1.0.30/debian/control 2020-06-14 11:36:38.0 +
@@ -131,3 +131,24 @@
  .
  This package contains the files needed to build your applications
  using SANE.
+
+Package: libsane
+Architecture: any
+Multi-Arch: same
+Section: oldlibs
+Depends:
+ libsane1 (>= ${source:Version}),
+ ${misc:Depends}
+Description: API library for scanners [transitional package]
+ SANE stands for "Scanner Access Now Easy" and is an application
+ programming interface (API) that provides standardized access to any
+ raster image scanner hardware (flatbed scanner, hand-held scanner,
+ video- and still-cameras, frame-grabbers, etc.). The SANE standard is
+ free and its discussion and development are open to everybody. The
+ current source code is written to support several operating systems,
+ including GNU/Linux, OS/2, Win32 and various Unices and is available
+ under the GNU General Public License (commercial applications and
+ backends are welcome, too, however).
+ .
+ This package is here to ensure smooth upgrades. It can be removed when
+ you see fit.

thanks for considering it!

Gianfranco
--- End Message ---
--- Begin Message ---
Source: sane-backends
Source-Version: 1.0.31-1~experimental1
Done: =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?= 

We believe that the bug you reported is fixed in the latest version of
sane-backends, 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 962...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jörg Frings-Fürst  (supplier of updated sane-backends 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: Sat, 05 Sep 2020 17:48:20 +0200
Source: sane-backends
Binary: libsane libsane-common libsane-dev libsane1 libsane1-dbgsym sane-utils 
sane-utils-dbgsym
Architecture: source
Version: 1.0.31-1~experimental1
Distribution: experimental
Urgency: medium
Maintainer: Jörg Frings-Fürst 
Changed-By: Jörg Frings-Fürst 
Description:
 libsane- API library for scanners [transitional package]
 libsane-common - API library for scanners -- documentation and support files
 libsane-dev - API development library for scanners [development files]
 libsane1   - API library for scanners
 sane-utils - API library for scanners -- utilities
Closes: 931297 948711 962539 962936 968949 968953
Changes:
 sane-backends (1.0.31-1~experimental1) experimental; urgency=medium
 .
   * New upstream release (Closes: #968949, #962539).
   * Add back libsane transitional package, to ease

Bug#955440: marked as done (passenger: FTBFS on armel and armhf)

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 15:51:24 +
with message-id 
and subject line Bug#955440: fixed in passenger 5.0.30-1.2
has caused the Debian Bug report #955440,
regarding passenger: FTBFS on armel and armhf
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.)


-- 
955440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: passenger
Version: 5.0.30-1.1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

binNMUs of passenger failed on armel and armhf:
https://buildd.debian.org/status/fetch.php?pkg=passenger&arch=armel&ver=5.0.30-1.1%2Bb2&stamp=1584710127&raw=0
https://buildd.debian.org/status/fetch.php?pkg=passenger&arch=armhf&ver=5.0.30-1.1%2Bb2&stamp=1585045168&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: passenger
Source-Version: 5.0.30-1.2
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
passenger, 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 955...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated passenger 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: Thu, 10 Sep 2020 12:16:03 +0200
Source: passenger
Architecture: source
Version: 5.0.30-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Matthias Klose 
Closes: 955440 967033
Changes:
 passenger (5.0.30-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix alignment issues in the main CMSG codepath and switch arm Linux systems
 from the workaround codepath to the main codepath (Peter Green).
 Closes: 955440.
   * Drop usage of python2, use python3 by default. Closes: #967033.
Checksums-Sha1:
 60854fb809a49eb00984e7468b0cf2dc20b1e557 2598 passenger_5.0.30-1.2.dsc
 17db099bdf2fbcec4057fc4438d2bf04ce7fde96 18692 
passenger_5.0.30-1.2.debian.tar.xz
 d00e8615a1c2973a0c9030e62eb9d614918fb0d7 11603 
passenger_5.0.30-1.2_source.buildinfo
Checksums-Sha256:
 70ef70234efdefdc927bdc2a37ef8843c07da2e1107522af8650c8dc721a5969 2598 
passenger_5.0.30-1.2.dsc
 9f2a9b47f84f43f53d9a54633b395b750dd800f03a208c642f66a130f13fe402 18692 
passenger_5.0.30-1.2.debian.tar.xz
 3b3cfce2b04b802dd6b6eb67c62cfdbe54269b99c467949b22dffccee987d8e5 11603 
passenger_5.0.30-1.2_source.buildinfo
Files:
 c003c860bdd0825e13be4e33c94409d3 2598 ruby optional passenger_5.0.30-1.2.dsc
 e39d03a40663ae9353a95b3072caf2ec 18692 ruby optional 
passenger_5.0.30-1.2.debian.tar.xz
 029af10dc383d8b8300be2e6d4c25e05 11603 ruby optional 
passenger_5.0.30-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl9aRMwQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9dLuD/9e+X+Q7H9d4VTZ+ddzCTGEYzYbV0zZkZYB
/XDXTmYe9W+Id8sofoaq2lHtpaHPq3nVyWKVLmGPtpiLCii1JoC9lVnY50SpbF3x
oPFmEoCalUsNXXhYFNFc+IMLC+XEx3y8ZusaihXf3wTlc1wWTGipdW1WPgjhdwUU
7JYG1rGOKMaZ7nvNQauvdzCAETw6ZHvM2Qko54AgFYdUIXas1gcXIsd01IvJBy65
WkRzbGNxdoqMJ2q0gvhmyvK2xnXz0i61aEQ6tmEquLCRnHwyD15F/Gr4eOET4Usa
Vwdkz1W+LLpX2j7GY5nh/iL6igh5UoFS/FGRKJH1kMJX3nbl+rY8WGi57QX6MRdF
Zc4yGNLQnLECrq5qV0r78EYlPO8XJ1TG41PLfptQ3alzZLRMCnd0ww5Lv9FbSPLN
you+rE5fGJ8nrkRFEQPbQu8nRHn05+3WhsCXHVK2rC1h1LG3svYhw7e9rzF+YuIx
LU0wwdXv+k2XboMrqwqIw97M5++mmy1nYfHcHMVre3kl5x3dEp1widKoCISxnYg3
XnDY89AlI+7QeM4DPjDxDNl0jETlE8l0erSlZkXqicT3CQz9VkiQmn1oaFsgoVgl
RdKA40WJM0HZoCEoT5ZpPXUsj6thvcoLadXp4BKk3faAyUGmTik1jm0QiAPIllpL
XR5IcqSz5g==
=Kplb
-END PGP SIGNATURE End Message ---

Bug#954954: marked as done (libstdc++6: symbols file on armel incomplete)

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 15:50:52 +
with message-id 
and subject line Bug#954954: fixed in gcc-10 10.2.0-7
has caused the Debian Bug report #954954,
regarding libstdc++6: symbols file on armel incomplete
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.)


-- 
954954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: libstdc++6
severity: serious

Hi,

It seems the symbols file for libstdc++6 is missing some symbols on armel. The
build adds these with the latest version. This causes new builds that use
these symbols to pick up an (unnecessary) versioned dependency on the latest
gcc in unstable.

As this bug sometimes causes testing migrations to block on the migration of
gcc, and thus interferes with transitions, I'm filing this as serious. This
currently is the case with the opencv binNMU on armel, which is blocked behind
gcc-10, blocking the python3-defauls transition.

Maybe the build should we configured to fail when new symbols are discovered,
to avoid similar issues in the future.

Thanks!

Ivo
--- End Message ---
--- Begin Message ---
Source: gcc-10
Source-Version: 10.2.0-7
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
gcc-10, 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 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-10 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: Thu, 10 Sep 2020 17:24:36 +0200
Source: gcc-10
Architecture: source
Version: 10.2.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 954954
Changes:
 gcc-10 (10.2.0-7) unstable; urgency=medium
 .
   * Update to git 20200910 from the gcc-10 branch.
 - Fix PR c++/95164, PR target/85830 (PPC), PR tree-optimization/96820,
   PR target/96808 (PPC), PR tree-optimization/96597,
   PR tree-optimization/88240, PR tree-optimization/96854,
   PR target/96551 (x86), PR d/96924, PR fortran/95398, PR fortran/94672,
   PR libstdc++/92978, PR libstdc++/96851, PR target/96357 (AArch64),
   PR fortran/95109, PR fortran/94690.
   * Update libasan and libgfortran symbols files.
   * Replace the libstdc++ symbols file on armel with one based on
 symbol versions (versions different than for other architectures).
 Closes: #954954.
Checksums-Sha1:
 aed9c07c01f2703e761ead474c83e2f99574ec17 27590 gcc-10_10.2.0-7.dsc
 396c75ad6c8a2d766af30be12eb31364a141455e 2102376 gcc-10_10.2.0-7.debian.tar.xz
 e8c19e2da2daef4c5289966fa39a983e32e525d7 6223 gcc-10_10.2.0-7_source.buildinfo
Checksums-Sha256:
 56dbe135af209665ba6faa3430c81af7115c147c24713d0053db496294c92c98 27590 
gcc-10_10.2.0-7.dsc
 a48a509952f2704d106fee86c9f50a4d55d13c24146b2aad5f1bc5635a3ccae7 2102376 
gcc-10_10.2.0-7.debian.tar.xz
 862352bd25dcdda7feb74295faed885ec2d3b2dc76bc37508cf247802ce4f1be 6223 
gcc-10_10.2.0-7_source.buildinfo
Files:
 697f1ed184ad38c3ca8245e664669682 27590 devel optional gcc-10_10.2.0-7.dsc
 53e7ca96f3e444bef89dd19fa88ae4d8 2102376 devel optional 
gcc-10_10.2.0-7.debian.tar.xz
 60e267a0db83dfdfaa7da7fcd0b0a579 6223 devel optional 
gcc-10_10.2.0-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl9aRXYQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9XACD/4lKZ9Jo3rh8Lum+pOQHyFuA3b/dXGJ3Z9s
yYGhYEfxQeHX8vYgBm2HKzSuSdCfiQfhBwK9ouw1tm4bFopwtDRxQRfkUM/ii67L
HIuMSk/gjJC2zB2mI4OWcOCi/sRdEAo5GjO+Zo/FxaIxgC0eLNPuYD+GyGZJ1zOB
cqgxfFw6tPy0cL37RoyWd33OKU2HPyPEJDKkRriHUs65XyE8KNOOUM3KzPiibP/N
ciFvtORqa4v2yoskyMqJzsJyeY4Veib8QZeYv7ScQTbWRIIfN88SucN/okYfPohR
u1YY1DyCCsPv1Qje1EldUi4c/zZj7+SFfyAv9Jxqyd+2B4Hwqdk5mgiUQgqfSYHt
DCfArxztUjCX8WqeAuroDBRowaKsg03M4hK3wIj1jQKTdZUDNUtRJeb9hhO0315X
amUtIC5ZQ3ko2Q4FT9Nl0eP8bAdcWCLWEVPRMxJ1hJbXsGEf97rm9AydEq1bbQe/
gLF+2l856tJU48fnXEX+Mj96KJwkf1oZ8FdQDdQOJx6nint7VBhlfhRhtP2hSa8+
zbmP4RoYscFIp2U1ocvy9Ht0h6M3oDrm9mutwo5t/xu4/yYBzIaDsE4NtOXtB8DH
SxN7AeNS3yEbsr232dIhfV56JtUHevrpG5GOEt7UUdkHYbMZ03xAZy1UHA7jMURJ
X167J8yIKw==
=3OGD
-END PGP SIGN

Bug#967033: marked as done (passenger: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 15:51:24 +
with message-id 
and subject line Bug#967033: fixed in passenger 5.0.30-1.2
has caused the Debian Bug report #967033,
regarding passenger: Unversioned Python removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
967033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:passenger
Version: 5.0.30-1.1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

see 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/passenger/6517580/log.gz

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: passenger
Source-Version: 5.0.30-1.2
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
passenger, 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 967...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated passenger 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: Thu, 10 Sep 2020 12:16:03 +0200
Source: passenger
Architecture: source
Version: 5.0.30-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Matthias Klose 
Closes: 955440 967033
Changes:
 passenger (5.0.30-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix alignment issues in the main CMSG codepath and switch arm Linux systems
 from the workaround codepath to the main codepath (Peter Green).
 Closes: 955440.
   * Drop usage of python2, use python3 by default. Closes: #967033.
Checksums-Sha1:
 60854fb809a49eb00984e7468b0cf2dc20b1e557 2598 passenger_5.0.30-1.2.dsc
 17db099bdf2fbcec4057fc4438d2bf04ce7fde96 18692 
passenger_5.0.30-1.2.debian.tar.xz
 d00e8615a1c2973a0c9030e62eb9d614918fb0d7 11603 
passenger_5.0.30-1.2_source.buildinfo
Checksums-Sha256:
 70ef70234efdefdc927bdc2a37ef8843c07da2e1107522af8650c8dc721a5969 2598 
passenger_5.0.30-1.2.dsc
 9f2a9b47f84f43f53d9a54633b395b750dd800f03a208c642f66a130f13fe402 18692 
passenger_5.0.30-1.2.debian.tar.xz
 3b3cfce2b04b802dd6b6eb67c62cfdbe54269b99c467949b22dffccee987d8e5 11603 
passenger_5.0.30-1.2_source.buildinfo
Files:
 c003c860bdd0825e13be4e33c94409d3 2598 ruby optional passenger_5.0.30-1.2.dsc
 e39d03a40663ae9353a95b3072caf2ec 18692 ruby optional 
passenger_5.0.30-1.2.debian.tar.xz
 029af10dc383d8b8300be2e6d4c25e05 11603 ruby optional 
passenger_5.0.30-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl9aRMwQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9dLuD/9e+X+Q7H9d4VTZ+ddzCTGEYzYbV0zZkZYB
/XDXTmYe9W+Id8sofoaq2lHtpaHPq3nVyWKVLmGPtpiLCii1JoC9lVnY50SpbF3x
oPFmEoCalUsNXXhYFNFc+IMLC+XEx3y8ZusaihXf3wTlc1wWTGipdW1WPgjhdwUU
7JYG1rGOKMaZ7nvNQauvdzCAETw6ZHvM2Qko54AgFYdUIXas1gcXIsd01IvJBy65
WkRzbGNxdoqMJ2q0gvhmyvK2xnXz0i61aEQ6tmEquLCRnHwyD15F/Gr4eOET4Usa
Vwdkz1W+LLpX2j7GY5nh/iL6igh5UoFS/FGRKJH1kMJX3nbl+rY8WGi57QX6MRdF
Zc4yGNLQnLECrq5qV0r78EYlPO8XJ1TG41PLfptQ3alzZLRMCnd0ww5Lv9FbSPLN
you+rE5fGJ8nrkRFEQPbQu8nRHn05+3WhsCXHVK2rC1h1LG3svYhw7e9rzF+YuIx
LU0wwdXv+k2XboMrqwqIw97M5++mmy1nYfHcHMVre3kl5x3dEp1widKoCISxnYg

Bug#965352: libopenmpi3: breaks tests in client programs

[Drew Parsons]

Source: openmpi
Followup-For: Bug #965352

As far as the client programs go (dolfin mpi4py petsc4py scalapack),
they are all building now (with mpi4py now patched to ignore the
bug).

Please close this bug if we don't need to monitor the problem any more.

Bug#969852: marked as done (pompem: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 14:48:49 +
with message-id 
and subject line Bug#969852: fixed in pompem 0.2.0-6
has caused the Debian Bug report #969852,
regarding pompem: autopkgtest should be marked superficial
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.)


-- 
969852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pompem
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'pompem' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'pompem'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: pompem
Source-Version: 0.2.0-6
Done: Giovani Augusto Ferreira 

We believe that the bug you reported is fixed in the latest version of
pompem, 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 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated pompem 
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, 10 Sep 2020 11:15:25 -0300
Source: pompem
Architecture: source
Version: 0.2.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Giovani Augusto Ferreira 
Closes: 969852
Changes:
 pompem (0.2.0-6) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields:
   - Bug-Database, Bug-Submit, Repository, Repository-Browse.
 .
   [ Giovani Augusto Ferreira ]
   * Bumped DH level to 13.
   * Bumped standards version to 4.5.0, no changes needed.
   * debian/copyright: updated packaging years.
   * debian/tests/control: added superficial restriction. (closes: #969852)
   * debian/upstream/metadata: removed deprecated field.
 .
   [ Samuel Henrique ]
   * Configure git-buildpackage for Debian
Checksums-Sha1:
 558f4ca96e001abf3810ccd9be9f72475e8861e0 1922 pompem_0.2.0-6.dsc
 d77c57add3bf0ec901738cbce52cd85b29631df1 4116 pompem_0.2.0-6.debian.tar.xz
 8d01189b57982442e92779afda9a1abf6b375fec 5390 pompem_0.2.0-6_source.buildinfo
Checksums-Sha256:
 de9690ac3af442070f8e9f62f37d767e8ce44c7c1bc2de2ecf528cb1ee16d87c 1922 
pompem_0.2.0-6.dsc
 cc3d9bfb2958ce8b5d0a584fe5f3d37eacc60cc98a9b9c1b5cbb3c2c29467aa0 4116 
pompem_0.2.0-6.debian.tar.xz
 3c1395b96542e1b94adb231f4abbac54ffd2addd2bec23c198a6258cc49301c5 5390 
pompem_0.2.0-6_source.buildinfo
Files:
 8eef6ac96693914594dd94ec2465b4d2 1922 utils optional pompem_0.2.0-6.dsc
 da63583a89430ce5b83af2135b1790fa 4116 utils optional 
pompem_0.2.0-6.debian.tar.xz
 f2e25d8f51ec2ec16bf4c9e77f1be6fa 5390 utils optional 
pompem_0.2.0-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEs/UaJxJhnD7NdLjheElO9yN1pmwFAl9aNtsACgkQeElO9yN1
pmyuExAAtyZCSPLUC8BlfOo/gKp273T2T9AcPGCysGz6sVVVOZhUQFaeAg9sqBsf
wj6A7gYX53eTS4+IjHXVwK06K3Avv9iyGl8W3Wh/8ErH6Bls73lz2T1zKz2ypdqm
MjebnFdjoRTnUz/E0s0/2ZKdZ33Gbop91uq2or/sz+vBdFEA7SYH+gWpbD1mABbu
DV/a4gjPjdVeCBss6K1XtCAPRNNJZB1QAO+Yd2CEvETVO9gpCVAVlkyX1NgXkOGu
2UkCS5eVfPgevD1BQKj7hKDSgrqgIxN7995Go0gMLUhP+CmpO+uN1jcGTiCjAonH
EqJeJKp9FUqeXOA8Gu2NQwcvWbbGWQpeVfRjsmueDSobnKKecAEljXBD1vAX0RHd
doNWO6+Vl3GyJmASOvXI21Lca6ckYvOfJ3DST6zEkCK1rjBTTjYeu57R7c574DTn
if5/CB9lc09zgf0+5sc9r3ymnwfYyvAsLWTZgkUqsVe0Cr0nrGuf+U/sgMs8RYeT
hK1mDbcMlrPO3HVb/M9no+jCd9apDSUzhO9Id1NiZcoLqfrkwnnrMx8mHQC3pYkR
vceyxSrHZuqArDNGwZhR98hrJujyHroHYotO5cRIN5K5x0f6+4RCQdXwPkTaVo2O
N0xT3DkH7MIG1tpg+QjeSK+nwnRHvHdNJFV7+E6CwafA

Bug#962596: ca-certificates: Removal of GeoTrust Global CA requires investigation

[Michael Holloway]

Happy three-month bug birthday!  Any news?

Thanks,
Michael

Processed: Bug#969852 marked as pending in pompem

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #969852 [src:pompem] pompem: autopkgtest should be marked superficial
Added tag(s) pending.

-- 
969852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#969852: marked as pending in pompem

[Giovani Augusto Ferreira]

Control: tag -1 pending

Hello,

Bug #969852 in pompem reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/pkg-security-team/pompem/-/commit/39680021ea71e0068d713de607c84ddb048727bf


d/t/control: Add superficial restriction (closes: #969852)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/969852

Bug#970029: llvm-toolchain-8: should not be part of bullseye

[Sylvestre Ledru]

Le 10/09/2020 à 15:25, Sebastian Ramacher a écrit :

Source: llvm-toolchain-8
Version: 1:8.0.1-10
Severity: serious
Tags: sid bullseye

So I think it's time to get llvm-toolchain-8 removed from testing (and
from sid in the long run).



Agreed, many thanks for filling this bug. It was on my todo list for a while :)

Cheers,
Sylvestre

Bug#941685: marked as pending in libspring-java

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #941685 in libspring-java reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/java-team/libspring-java/-/commit/fc4d5693031df4dd2e0f76c4e1f75ec5f88a0edc


Depend on libhibernate-validator4-java instead of libhibernate-validator-java 
(Closes: #941685)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941685

Processed: Bug#941685 marked as pending in libspring-java

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941685 [src:libspring-java] libspring-java: FTBFS package 
org.hibernate.validator.method does not exist
Added tag(s) pending.

-- 
941685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#970029: llvm-toolchain-8: should not be part of bullseye

[Sebastian Ramacher]

Source: llvm-toolchain-8
Version: 1:8.0.1-10
Severity: serious
Tags: sid bullseye

$ dak rm -Rn llvm-toolchain-8 -s testin
Will remove the following packages from testing:

   clang-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
clang-8-doc | 1:8.0.1-10 | all
clang-8-examples | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
clang-format-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
clang-tidy-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
clang-tools-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
  clangd-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
libc++-8-dev | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
 libc++1-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
libc++abi-8-dev | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
libc++abi1-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
libclang-8-dev | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
libclang-common-8-dev | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x
libclang1-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
libfuzzer-8-dev | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
  liblld-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el
liblld-8-dev | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el
 liblldb-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el
liblldb-8-dev | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el
libllvm-8-ocaml-dev | 1:8.0.1-10 | amd64, arm64, armhf, i386, ppc64el, s390x
  libllvm8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
libomp-8-dev | 1:8.0.1-10 | amd64, arm64, armhf, i386, mips64el, ppc64el
libomp-8-doc | 1:8.0.1-10 | all
 libomp5-8 | 1:8.0.1-10 | amd64, arm64, armhf, i386, mips64el, ppc64el
 lld-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el
lldb-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el
llvm-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
llvm-8-dev | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
llvm-8-doc | 1:8.0.1-10 | all
llvm-8-examples | 1:8.0.1-10 | all
llvm-8-runtime | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
llvm-8-tools | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
llvm-toolchain-8 | 1:8.0.1-10 | source
python-clang-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
python-lldb-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el
python3-clang-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
python3-lldb-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el

Maintainer: LLVM Packaging Team 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


So I think it's time to get llvm-toolchain-8 removed from testing (and
from sid in the long run).

Cheers
-- 
Sebastian Ramacher

Bug#963979: marked as done (libhibernate-validator{,4}-java: both ship /usr/share/java/hibernate-validator.jar)

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 12:48:56 +
with message-id 
and subject line Bug#963979: fixed in libhibernate-validator4-java 4.3.4-3
has caused the Debian Bug report #963979,
regarding libhibernate-validator{,4}-java: both ship 
/usr/share/java/hibernate-validator.jar
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.)


-- 
963979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhibernate-validator-java,libhibernate-validator4-java
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 4.3.4-2
Control: found -1 5.3.6-1

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libhibernate-validator4-java.
  Preparing to unpack .../libhibernate-validator4-java_4.3.4-2_all.deb ...
  Unpacking libhibernate-validator4-java (4.3.4-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libhibernate-validator4-java_4.3.4-2_all.deb (--unpack):
   trying to overwrite '/usr/share/java/hibernate-validator.jar', which is also 
in package libhibernate-validator-java 5.3.6-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libhibernate-validator4-java_4.3.4-2_all.deb

Did you intend that the two packages are co-installable?


cheers,

Andreas


libhibernate-validator-java=5.3.6-1_libhibernate-validator4-java=4.3.4-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libhibernate-validator4-java
Source-Version: 4.3.4-3
Done: Emmanuel Bourg 

We believe that the bug you reported is fixed in the latest version of
libhibernate-validator4-java, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated 
libhibernate-validator4-java 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, 10 Sep 2020 14:36:33 +0200
Source: libhibernate-validator4-java
Architecture: source
Version: 4.3.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 963979
Changes:
 libhibernate-validator4-java (4.3.4-3) unstable; urgency=medium
 .
   * Team upload.
   * Renamed the /usr/share/java jar (Closes: #963979)
Checksums-Sha1:
 2fcbf8004cd114ce1bf548d84baae64a9b91a0f2 2641 
libhibernate-validator4-java_4.3.4-3.dsc
 e5ec848a713debd6e935077fd6edca3bd0a22191 6968 
libhibernate-validator4-java_4.3.4-3.debian.tar.xz
 d762485412103e3f270d4b88ff96943dcd159386 15168 
libhibernate-validator4-java_4.3.4-3_source.buildinfo
Checksums-Sha256:
 461f381f8b1d51edf545ecb8a31ab1f6e1874db7a2ce9d78fd041c1f2ae709be 2641 
libhibernate-validator4-java_4.3.4-3.dsc
 ad16fe85f727b898b0836468fa9cd89969efe7fc4b3f9536e3a1e97abcea3069 6968 
libhibernate-validator4-java_4.3.4-3.debian.tar.xz
 ce006782e88b439118ac1dfb88fdb31c34d91f51a79d903262c37b46f40cd6cd 15168 
libhibernate-validator4-java_4.3.4-3_source.buildinfo
Files:
 2273680423dc514d4a8111f468f70060 2641 java optional 
libhibernate-validator4-java_4.3.4-3.dsc
 917e4f0d434c28671527af11c5370758 6968 java optional 
libhibernate-validator4-java_4.3.4-3.debian.tar.xz
 70a5e824748b7bed4352f6fd8c4ae45b 15168 java optional 
libhibernate-validator4-java_4.3.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl9aHeYSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsM/cQAJmF0h+Iwgc6pKy+kbRdNw7/OepwId6W
MYxTEqmSNhBuNc5G/9BbiP6ncdNl1A0Q0+HiJY60ugB6ZHAH/wkjWHEFgGamHWM6
2YUELIIKtBCMK2NS7QRYFo9M0Ip/9hAu4CeoUqa3qOa/IEs495HyYmJzpxo3/TL4
QmqSN0FCCe0h3JaBoyroB6Mce7q5CnmLCobNHwv8O2Q6vQdpWefKnIJfFGK8+S+i
H7dqxIlkrJwOOMBAwhFQInVcS6tbtbXg46CP12l19ILOORKGiYCNiIkFMe/9A0zh
VKm9md8FCzdhkzoutzzmhK3L87P+tBC2DG0uYyYn0voaj3iEw3qJZaIvNCj8x/p9
VGjUyd/FQAFDgQME/3SNINM6QRJP36O4GKVHqyzODUkM5PY4D+tlCn7x2fvZ5zJW
qo3nIsqY7yam1H8

Processed: Bug#963979 marked as pending in libhibernate-validator4-java

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #963979 [libhibernate-validator-java,libhibernate-validator4-java] 
libhibernate-validator{,4}-java: both ship 
/usr/share/java/hibernate-validator.jar
Added tag(s) pending.

-- 
963979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#963979: marked as pending in libhibernate-validator4-java

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #963979 in libhibernate-validator4-java reported by you has been fixed in 
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/java-team/libhibernate-validator4-java/-/commit/c297582b72c1c04c18f5cc100617c029da584bd3


Renamed the /usr/share/java jar (Closes: #963979)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963979

Bug#969666: marked as done (cwltool: autopkgtest regression: No module named 'arcp')

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 12:33:36 +
with message-id 
and subject line Bug#969666: fixed in cwltool 3.0.20200807132242-2
has caused the Debian Bug report #969666,
regarding cwltool: autopkgtest regression: No module named 'arcp'
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.)


-- 
969666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cwltool
Version: 3.0.20200807132242-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of cwltool the autopkgtest of cwltool fails in
testing when that autopkgtest is run with the binary packages of cwltool
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
cwltoolfrom testing3.0.20200807132242-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
cwltool/3.0.20200807132242-1. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=cwltool

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cwltool/6927667/log.gz
 ERRORS

__ ERROR collecting tests/test_provenance.py
___
ImportError while importing test module
'/usr/lib/python3/dist-packages/cwltool/tests/test_provenance.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/cwltool/tests/test_provenance.py:11: in

import arcp
E   ModuleNotFoundError: No module named 'arcp'




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cwltool
Source-Version: 3.0.20200807132242-2
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
cwltool, 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 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated cwltool 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: Thu, 10 Sep 2020 13:43:51 +0200
Source: cwltool
Architecture: source
Version: 3.0.20200807132242-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 969666
Changes:
 cwltool (3.0.20200807132242-2) unstable; urgency=medium
 .
   * Team upload.
   * Depends: python3-arcp
 Closes: #969666
Checksums-Sha1:
 559c62a4056035b7775fd40688ddd7a7c05f7741 2674 cwltool_3.0.20200807132242-2.dsc
 ab7d5ae80b24f0958db99bafba59322ae545b539 14936 
cwltool_3.0.20200807132242-2.debian.tar.xz
 4c77f76ed2c266143d12cc80973d0e257295ae64 9563 
cwltool_3.0.20200807132242-2_amd64.buildinfo
Checksums-Sha256:
 d695aa80d5213401408c19e87c9db5ba59e87d7c169c00f7837d5227b833febd 2674 
cwltool_3.0.20200807132242-2.dsc
 93b92619b864fd64dcbccd4b804a20e661bbac2820eaf065d9f21959a074fcb4 14936 
cwltool_3.0.20200807132242-2.debian.tar.xz
 9145ea1a8880090a0380d14192e0478bc2541cbdafd702ae0c82a0b4127da448 9563 
cwltool_3.0.20200807132242-2_amd64.buildinfo
Files:
 410b97f904663fe105d854b6a964fcfa 2674 science optional 
cwltool_3.0.20200807132242-2.dsc
 7337dc4829c60614b445e19089673066 14936 science optional 
cwltool_3.0.20200807132242-2.debian.tar.xz
 f21fac605ced84a72bb1145df3a5d4f2 9563 science optional 
cwltool_3.0.20200807132242-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUH

Bug#969638: marked as done (gwyddion: Many modules (15) failed to register.)

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 12:33:44 +
with message-id 
and subject line Bug#969638: fixed in gwyddion 2.56-1
has caused the Debian Bug report #969638,
regarding gwyddion: Many modules (15) failed to register.
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.)


-- 
969638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Subject: gwyddion: Many modules (15) failed to register.
Package: gwyddion
Version: 2.55-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,


   * What led up to the situation?

aptitude full-upgrade

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Started gwyddion (ineffective).

Followed instructions to remove modules and reinstall with aptitude.

   * What was the outcome of this action?

Almost all functions of Gwyddion missing from the menu.  Received message:

Many modules (15) failed to register.
Most likely Gwyddion was not upgraded correctly.  Instead, one installation was 
just overwritten with another, and now it is a mess.
Please remove completely the module directory
/usr/lib/x86_64-linux-gnu/gwyddion/modules
and reinstall Gwyddion.
See Info → Module Browser for specific errors.

This bug is also in Ubuntu and is known upstream.
https://bugs.launchpad.net/ubuntu/+source/gwyddion/+bug/1882441
http://gwyddion.net/#news-2020-07-12
2020-07-29: To get working Gwyddion packages in Ubuntu you can use the Gwyddion-SPM PPA instead of the broken distro packages (bug 1882441). The PPA 
also provides more current versions of Gwyddion.


2020-07-12: Gwyddion package in Ubuntu 20.04 (possibly other versions?) is broken, failing to load any modules at startup due to linking issue. See 
bug 1882441 in Launchpad. At present there is no known workaround aside for compilation from source code (as dscribed in the bug report).


   * What outcome did you expect instead?

Menu options present.  Thanks in advance!



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gwyddion depends on:
ii  gwyddion-common 2.55-3
ii  libc6   2.31-3
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-5
ii  libglib2.0-02.64.4-1
ii  libgomp110.2.0-6
ii  libgtk2.0-0 2.24.32-4
ii  libgtkglext11.2.0-9
ii  libgwyddion2-0  2.55-3
ii  libminizip1 1.1-8+b1
ii  libpng16-16 1.6.37-2
ii  libx11-62:1.6.10-3
ii  libxml2 2.9.10+dfsg-5+b1
ii  libxmu6 2:1.1.2-2+b3
ii  zlib1g  1:1.2.11.dfsg-2

gwyddion recommends no packages.

gwyddion suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gwyddion
Source-Version: 2.56-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
gwyddion, 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 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated gwyddion 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: Thu, 10 Sep 2020 11:50:32 +0200
Source: gwyddion
Architecture: source
Version: 2.56-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 969638
Changes:
 gwyddion (2.56-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #969638
   * debhelper-compat 13 (routine-update)
   * Add salsa-ci file (routine-update)
   * Depends: sensible-utils
Checksums-Sha1:
 14e01f311d13ade15f7ad9086cbbaa1993d3fe1f 2532 gwyddion_2.56-1.dsc
 cb3e4b2899dbd4859cb931a7446034d15de05d0b 4645620 gwyddion_2.56.orig.tar.xz
 53644871e89b5f51ba32b0caeef93d1ef3ab1d09 114 gwyddion_2.56.orig.tar.xz.asc
 8818d20e4e028fe4362342d1005061113a0522ed 15836 gwyddion_2.56-1.debia

Bug#969638: gwyddion: Many modules (15) failed to register.

[Andreas Tille]

Hi Laszlo,

thanks a lot for your bug report.  I've just uploaded version 2.56 of
gwyddion to Debian.  Please note that I'm not a user of gwyddion nor do
I have the slightest idea how to use it nor what input files I could use
for testing.

Without having any input file it looks OK for me now and I did not
see any error message about module load failures.  It would be really
great if you could check (after some hours the package might need to
be available on Debian mirrors).

If the problem persists please reopen the bug report.  It would be
also great if you could point to some example input file.  It seems
the problem is solved in some PPA you pointed to.  If this is the
case I would love to get a pointer to a *.dsc file to check the
differences in the packaging.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#968884: marked as done (elisa-player FTBFS: elisaqmltests (Failed))

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 14:17:32 +0200
with message-id <4d79c0d5-c7d8-42af-b27f-cacb4ba07...@debian.org>
and subject line 
has caused the Debian Bug report #968884,
regarding elisa-player FTBFS: elisaqmltests (Failed)
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.)


-- 
968884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: elisa-player
Version: 20.08.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=elisa-player&suite=sid

...
13/15 Test #13: elisaqmltests ***Failed2.29 sec
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x564182a43dc0), parent's thread is 
QThread(0x564182a43f10), current thread is QThread(0x564182a69b40)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x564182a43dc0), parent's thread is 
QThread(0x564182a43f10), current thread is QThread(0x564182a69b40)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x564182a43dc0), parent's thread is 
QThread(0x564182a43f10), current thread is QThread(0x564182a69b40)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x564182a43dc0), parent's thread is 
QThread(0x564182a43f10), current thread is QThread(0x564182a69b40)
QObject::installEventFilter(): Cannot filter events for objects in a different 
thread.
* Start testing of ElisaQmlTests *
Config: Using QtTest library 5.14.2, Qt 5.14.2 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 10.2.0)
PASS   : ElisaQmlTests::TestGridBrowserDelegate::initTestCase()
PASS   : ElisaQmlTests::TestGridBrowserDelegate::test_focus()
PASS   : ElisaQmlTests::TestGridBrowserDelegate::test_keyboard()
PASS   : ElisaQmlTests::TestGridBrowserDelegate::test_mouse_clicks()
PASS   : ElisaQmlTests::TestGridBrowserDelegate::cleanupTestCase()
QWARN  : ElisaQmlTests::UnknownTestFunc() 
file:///<>/src/qml/NavigationActionBar.qml:207: ReferenceError: 
contentDirectoryView is not defined
QWARN  : ElisaQmlTests::UnknownTestFunc() 
file:///<>/src/qml/NavigationActionBar.qml:207: ReferenceError: 
contentDirectoryView is not defined
PASS   : ElisaQmlTests::TestNavigationActionBar::initTestCase()
PASS   : ElisaQmlTests::TestNavigationActionBar::test_enqueue()
PASS   : ElisaQmlTests::TestNavigationActionBar::test_filterRating()
QWARN  : ElisaQmlTests::TestNavigationActionBar::test_filterState() 
file:///<>/src/qml/NavigationActionBar.qml:207: ReferenceError: 
contentDirectoryView is not defined
QWARN  : ElisaQmlTests::TestNavigationActionBar::test_filterState() 
file:///<>/src/qml/NavigationActionBar.qml: ReferenceError: 
contentDirectoryView is not defined
QWARN  : ElisaQmlTests::TestNavigationActionBar::test_filterState() 
file:///<>/src/qml/NavigationActionBar.qml: ReferenceError: 
contentDirectoryView is not defined
QWARN  : ElisaQmlTests::TestNavigationActionBar::test_filterState() 
file:///<>/src/qml/NavigationActionBar.qml: ReferenceError: 
contentDirectoryView is not defined
PASS   : ElisaQmlTests::TestNavigationActionBar::test_filterState()
PASS   : ElisaQmlTests::TestNavigationActionBar::test_filterText()
PASS   : ElisaQmlTests::TestNavigationActionBar::test_goBack()
PASS   : ElisaQmlTests::TestNavigationActionBar::test_replaceAndPlay()
PASS   : ElisaQmlTests::TestNavigationActionBar::test_showArtist()
PASS   : ElisaQmlTests::TestNavigationActionBar::cleanupTestCase()
QSYSTEM: ElisaQmlTests::UnknownTestFunc() "Session bus not found\nTo circumvent 
this problem try the following command (with Linux and bash)\nexport 
$(dbus-launch)"

  Start 14: filescannerTest
14/15 Test #14: filescannerTest ..   Passed0.89 sec
  Start 15: filewriterTest
15/15 Test #15: filewriterTest ...   Passed0.06 sec

93% tests passed, 1 tests failed out of 15

Total Test time (real) =  83.57 sec

The following tests FAILED:
 13 - elisaqmltests (Failed)
Errors while running CTest
make[2]: *** [Makefile:110: test] Error 8
--- End Message ---
--- Begin Message ---

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.--- End Message ---

Bug#969493: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

[Andreas Tille]

Hi Paul,

On Thu, Sep 10, 2020 at 12:02:10PM +0200, Paul Gevers wrote:
> On 08-09-2020 22:21, Andreas Tille wrote:
> >> I'm back on internet. I have just uploaded to DELAYED/15. Please let me
> >> know if I should delay or cancel.
> > 
> > Thanks a lot.  There is no point in any delay for Debian Med packages.
> 
> Ack, but the NMU is scripted [1]. If I need to change the delay for Med
> packages, it's more work for me (but feel free to provide patches/MR to
> add options to change the delay if this is important to you :) ).

Its not important to me.  However, I *personally* consider DELAYED/x
with x>7 way to carefully.  If I would use x>3 I would have forgotten
that I even did something on a package and if there might be any
questions I would need to refresh my mind which I would try to avoid.

Thanks again for all your effort which is really appreciated

  Andreas.
 
> [1]
> https://salsa.debian.org/elbrus/ci-regression-scripts/-/blob/master/qa-process-out-of-sync


-- 
http://fam-tille.de

Bug#968210: statsmodels: still broken on armel

[Rebecca N. Palmer]

Control: severity -1 important
Control: retitle -1 statsmodels: on armel may give wrong answer or crash

This bug is no longer an FTBFS as the tests are now ignored on armel, 
but still exists.  (At least as a crash; we stopped using --forked, so 
don't know if there are still also wrong answers.)


There is now a warning on import.

Bug#969493: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

[Paul Gevers]

Hi Andreas,

On 08-09-2020 22:21, Andreas Tille wrote:
>> I'm back on internet. I have just uploaded to DELAYED/15. Please let me
>> know if I should delay or cancel.
> 
> Thanks a lot.  There is no point in any delay for Debian Med packages.

Ack, but the NMU is scripted [1]. If I need to change the delay for Med
packages, it's more work for me (but feel free to provide patches/MR to
add options to change the delay if this is important to you :) ).

Paul

[1]
https://salsa.debian.org/elbrus/ci-regression-scripts/-/blob/master/qa-process-out-of-sync



signature.asc
Description: OpenPGP digital signature

Bug#969804: bart: autopkgtest should be marked superficial

[Andreas Tille]

Hi Sudip,

On Thu, Sep 10, 2020 at 10:45:07AM +0100, Sudip Mukherjee wrote:
> Apologies for not mentioning it as 'serious' bug in my mass-bug mail
> on debian-devel. That was my first mass-bug mail and I was wondering
> what I have missed in it. :(

No need to apologize.  Its great that you care for the issue in
principle.  BTW, gnumed-client has a similarly primitive test.  I fixed
this in Git[1] and it will be fixed with next upstream version which
will happen quite regularly.  So if you stumble upon this one there is
no need to spent time on drafting a bug report.

> Thanks for pointing it out, I will let Paul and his team to decide if
> it should be serious or important and will mention accordingly in my
> next mass-bug mail.

Thanks again

Andreas.


[1] 
https://salsa.debian.org/med-team/gnumed-client/-/commit/cb8677c80b6a0e8b4f92c434c1b95461199331d9
 

-- 
http://fam-tille.de

Bug#969804: bart: autopkgtest should be marked superficial

[Sudip Mukherjee]

HI Andreas,

On Thu, Sep 10, 2020 at 8:02 AM Andreas Tille  wrote:
>
> Hi Sudip,
>
> I fully agree that this is a bug and I'm currently building a fix for
> this.  However, I fail to see in how far this bug fulfills the criterion
> for a serious bug.  IMHO, important or normal is OK, but if you think
> this kind of bug should be serious please discuss this on debian-devel
> first.

Apologies for not mentioning it as 'serious' bug in my mass-bug mail
on debian-devel. That was my first mass-bug mail and I was wondering
what I have missed in it. :(
Thanks for pointing it out, I will let Paul and his team to decide if
it should be serious or important and will mention accordingly in my
next mass-bug mail.

-- 
Regards
Sudip

Bug#969894: nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel

[Vincent Lefevre]

On 2020-09-10 13:00:10 +1000, Jiri Kanicky wrote:
> This issue has been resolved with new nvidia-kernel-dkms version 450.66-1

But what about the status of nvidia-legacy-390xx-kernel-dkms?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#969804: marked as done (bart: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Thu, 10 Sep 2020 07:18:23 +
with message-id 
and subject line Bug#969804: fixed in bart 0.6.00-2
has caused the Debian Bug report #969804,
regarding bart: autopkgtest should be marked superficial
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.)


-- 
969804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bart
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'bart' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'bart'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: bart
Source-Version: 0.6.00-2
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
bart, 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 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated bart 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: Thu, 10 Sep 2020 08:59:31 +0200
Source: bart
Architecture: source
Version: 0.6.00-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 969804
Changes:
 bart (0.6.00-2) unstable; urgency=medium
 .
   * Team upload.
   * Mark tests superficial
 Closes: #969804
   * debhelper-compat 13 (routine-update)
Checksums-Sha1:
 2b1b5d011e68b8db039f4f7a968f4ecf954f1092 2155 bart_0.6.00-2.dsc
 255b2ec75b9bcbc76df99863f816390eebd6c958 5244 bart_0.6.00-2.debian.tar.xz
 1fa17fc3cc7edcc443ffd132c2722e39da31da72 6652 bart_0.6.00-2_amd64.buildinfo
Checksums-Sha256:
 3209deb1710dc4497821489bf9bcfbcf8899c18c7d08e5930afe00b45062d6fa 2155 
bart_0.6.00-2.dsc
 62ab57d0cca1d9486f8f0abe17282d5e9ae3182386ed7fc2e5354da92e036362 5244 
bart_0.6.00-2.debian.tar.xz
 8b4bf41e6b904b0969ede6a7e53f42bc4e6e53ae3b73d608e1d4f5b3ad1078be 6652 
bart_0.6.00-2_amd64.buildinfo
Files:
 e2a6c667ba26d43ff0966c94d7a7f465 2155 science optional bart_0.6.00-2.dsc
 b10b5a0f8bd0e69fd677ef331da43a9e 5244 science optional 
bart_0.6.00-2.debian.tar.xz
 198cc9e7b5b009e5d5c051679d20cceb 6652 science optional 
bart_0.6.00-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl9Zz6gRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE9Nw//ZYOtuctCP3kgGoTJWz4NBF21Rd5t37OD
QcYgm23aeIH07B+nsf3eVz1qIt71/4odxCHb1gYC3EoQE9MASZd1RMkkhEZInJGU
AcK3I6tZVEX3sIpAire4idyQQ9jJ6RFTsqWdebApvTdmqLUw8gpnyCdUfmHm3+Yl
UM1Ig8EQ9+2BpFxLjTHP9WLEPkS3CQLty5TLqHgHE6fmfcJcgeQRoRlVmDNP0Li3
thGXeePdwRf/M4TrOyprbbE2L7D6zFR5o6DDdW5iijwd/ggMgeTWzFL0m3kRzYNe
48Sj/x15tW6neSLUqTuaqJkaZbny7RKCy4cGsYiKI1TcgdBVxdB8zTey+pC3Zz+l
ZswH8STIcN2ICtDH7X4/jbC05QG6UiNX+eTjsENxA4WpDaRg7RoXZpY+nOALZA5h
YBZ7A/9w3wr34MtHYjmPLft2jVHtI7lZEFGPoeFS5DSSPaE1Lo5eYsGWQuLqUTAX
rc8SYJ4Hrv0fkP3A8tNwY3JvGwLadfCkgY9iz5jscvuJ8277avVUWzftqItz4AX0
j/FZf4yTY4EHRPIhs22yd1xW+R9YcKb8HGD2pwHTixXjxWTv5ib6cet5g9/gjuS3
hYF+0nwN5mL49sCDOc2wrZ4/mVeG8v09SYIaxNnduEzrLpZGQfc0zDRAVWnc7GUd
l1FVg+DCIR0=
=fPOV
-END PGP SIGNATURE End Message ---

Processed: statsmodels: still broken on armel

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #968210 [python3-statsmodels] statsmodels: arm* test failures/crashes
Severity set to 'important' from 'serious'
> retitle -1 statsmodels: on armel may give wrong answer or crash
Bug #968210 [python3-statsmodels] statsmodels: arm* test failures/crashes
Changed Bug title to 'statsmodels: on armel may give wrong answer or crash' 
from 'statsmodels: arm* test failures/crashes'.

-- 
968210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#969804: bart: autopkgtest should be marked superficial

[Andreas Tille]

Hi Sudip,

I fully agree that this is a bug and I'm currently building a fix for
this.  However, I fail to see in how far this bug fulfills the criterion
for a serious bug.  IMHO, important or normal is OK, but if you think
this kind of bug should be serious please discuss this on debian-devel
first.

Thanks a lot for your work on Debian CI

   Andreas.

-- 
http://fam-tille.de