Bug#963659: pybind11: FTBFS with Sphinx 3.1: File "/usr/lib/python3/dist-packages/sphinx/domains/c.py", line 3093, in object_type / raise NotImplementedError())

[Drew Parsons]

Wait for sphinx 3.2.1 I mean.

Processed: Re: Bug#937665: Waiting for Python 2-depending reverse dependencies

[Debian Bug Tracking System]

Processing control commands:

> block 967200 by -1
Bug #967200 [src:python-coverage] python-coverage: Unversioned Python removal 
in sid/bullseye
967200 was not blocked by any bugs.
967200 was blocking: 937695 938168
Added blocking bug(s) of 967200: 937665

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

Bug#937665: Waiting for Python 2-depending reverse dependencies

[Ben Finney]

Control: block 967200 by -1

On 17-Aug-2020, Ben Finney wrote:

> The updated package is ready, and waiting for reverse-dependencies (as
> described in bug reports blocking this one) to drop Python 2 support.

-- 
 \   “I have a map of the United States; it's actual size. It says |
  `\‘1 mile equals 1 mile’. Last summer, I folded it.” —Steven |
_o__)   Wright |
Ben Finney 

signature.asc
Description: PGP signature

Processed: tagging 968413

[Debian Bug Tracking System]

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

> tags 968413 + pending
Bug #968413 [src:oss4] failes to build on ppc64el with binutils 2.35
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed (with 1 error): Bug#937665: Waiting for Python 2-depending reverse dependencies

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 967200
Bug #937665 [src:python-coverage] python-coverage: Python2 removal in 
sid/bullseye
Bug #937665 [src:python-coverage] python-coverage: Python2 removal in 
sid/bullseye
Marked as found in versions python-coverage/5.1+dfsg.1-1.
Bug #967200 [src:python-coverage] python-coverage: Unversioned Python removal 
in sid/bullseye
937695 was blocked by: 936765 936978 937088 936319 937062 936941 936318 936979 
936867 936226 937089 937286 937217 946927 945658 945647 938674 966756 936612 
938268 936632 943161 936544 936543 938269 937237 943060 937201 938675 938141 
943257 938178 937791 936338 936339 938040 945692 953219 943046 943235 937221 
938631 936345 966785 937946 938095 943214 945716 937960 937255 943213 966784 
942979 945736 936343 942941 936344 942978 966783 937254 936539 937441 938094 
936796 938611 936206 936538 937479 937253 937161 936358 938591 943237 936610 
937271 938605 937257 938108 943201 937249 936652 939102 938097 966736 937428 
936392 936908 943062 936462 939260 945639 943286 936630 936909 938280 936489 
937429 945690 942929 943217 938604 942928 936699 936865 938391 942909 937233 
936558 938623 938461 936166 936559 939481 936767 937234 936928 937408 935657 
937962 943254 945645 943253 936276 936929 937989 938625 936863 938129 936864 
945644 937214 937891 938651 937213 945643 938677 945665 937942 912495 937094 
937611 936146 938479 936758 938478 936759 936845 946849 938441 945663 945732 
937997 945664 936844 947296 936792 936843 938237 937066 937269 937627 936687 
936222 937268 937179 936818 937040 937141 966752 937675 936819 943280 936839 
936838 966730 936890 966798 938217 943042 937673 936442 937129 936189 937940 
936685 937625 936162 938235 936188 945710 936718 937677 936495 943095 951902 
938234 936739 953372 947502 938233 936738 937391 927137 936683 936596 937461 
936790 938409 938408 936363 936493 938428 937993 945667 936565 883161 966750 
936858 936847 936859 936745 939106 937042 947302 939181 966732 943268 943282 
936744 938249 936440 938046 943040 937605 938271 936892 938248 936743 936564 
943141 942992 938637 965288 938595 937682 936329 937389 943205 937388 936328 
937275 938601 936216 937492 938686 938593 936508 938340 937164 942959 942958 
936509 93 938594 938862 943204 937274 937447 937458 938366 945706 937459 
937273 936191 943203 938617 936958 945726 936959 938465 943223 936670 938653 
937894 937211 937562 945678 937588 936528 936529 938192 966776 937742 938654 
938760 938464 936309 939483 943167 938394 943225 937231 938393 938540 938621 
938463 936992 938746 938147 938655 943277 937196 937895 936602 943164 937680 
883145 938467 937439 936578 936945 942990 936761 943163 939487 937490 937794 
943274 937204 942938 942939 937203 943273 937842 937793 936944 938860 943227 
938342 947730 942918 936943 938846 937418 938649 937897 943275 938648 938657 
938671 937419 936918 942943 937167 936341 942944 943231 936919 937225 936285 
937444 937740 943196 943207 938613 937251 938614 937560 937443 936672 938542 
937224 936284 938789 942945 936283 938762 938615 936939 939112 937445 936938 
937393 938231 943138 936681 937621 937463 937394 943091 936361 937159 942964 
942963 966772 938797 938196 937465 936996 938589 938742 943119 937654 936606 
938562 938211 938588 936809 937888 936828 966720 942996 937593 937889 936829 
938164 936778 938459 938273 936741 937617 943143 943144 936212 936561 937496 
938458 936779 938668 938682 938227 938866 938669 938362 943145 938388 938492 
938275 938840 938389 945702 945720 938223 936728 937788 912491 937762 937634 
938224 936729 945661 937119 938445 936841 943192 937615 937118 937597 937635 
937138 938546 938766 938167 943159 937614 937091 938560 938443 938444 938277 
938251 937860 966722 938795 937657 937648 937671 937145 938419 938418 938438 
938680 937397 938439 937467 938346 936708 937143 966800 936298 938793 938794 
938490 936299 938204 936709 937144 938360 937565 937847 938699 936604 938195 
937961 938698 938909 938489 939482 936994 938462 936993 883194 938488 938392 
937563 937440 937743 937892 942966 938610 936605 937396 938347 938358 936591 
938359 943222 942940 936995 936966 937718 937719 937495 942995 938592 937189 
938864 938863 936128 936625 937162 937364 938276 937494 938041 938559 938166 
942993 937684 942994 937596 943061 936391 938865 937738 938558 939114 937497 
936179 937819 937616 938390 943466 937687 936627 938543 938764 936269 938460 
936268 938763 938632 938544 937222 936282 938612 936674 937890 936673 938650 
939115 938545 938867 938029 938226 942942 937636 937838 936611 938009 937270 
937758 938796 937759 937845 938008 937160 936942 937061 938590 937844 937843 
937792 937202 936997 938345 936631 938518 943008 936962 937041 936988 937078 
945704 938363 937140 938364 937929 936215 937079 937276 943197 938790 943009 
938683 947027 938596 938738 937558 937547 937559 937166 938684 943142 936214 
938719 938365 936891 938272 938718 943281 936235 938188 938685 966731 937592 
938189 947301 938892 

Bug#937665: Waiting for Python 2-depending reverse dependencies

[Ben Finney]

Control: forcemerge -1 967200
Control: block -1 by 933750
Control: outlook -1 0

The updated package is ready, and waiting for reverse-dependencies (as
described in bug reports blocking this one) to drop Python 2 support.

On 16-Aug-2020, Jann Haber wrote:
> It seems like, there are no more rdeps of python-coverage now. Not
> sure about pypy-coverage.

Yes, I see no reverse dependencies for Python 2 ‘pypy-coverage’:

$ aptitude search '~Dpypy-coverage'

But one remaining for Python 2 ‘python-coverage’:

$ aptitude search '~Dpython-coverage'
p   paleomix

So, it seems we are waiting for ‘paleomix’ to drop Python 2 support. I
am recording bug#933750 as a blocker for bug#933750.

-- 
 \  “When I wake up in the morning, I just can't get started until |
  `\ I've had that first, piping hot pot of coffee. Oh, I've tried |
_o__)other enemas...” —Emo Philips |
Ben Finney 

signature.asc
Description: PGP signature

Bug#968210: statsmodels: arm* test failures/crashes

[Rebecca N. Palmer]

The TestZeroInflatedModel_probit issue appears to be a failure to 
converge: as it does trigger warnings of that, and it's already skipped 
on i386, I intend to ignore it.


qemu-arm64:

>>> a
object at 0x4000d31130>

>>> a.res1.params
Traceback (most recent call last):
  File "", line 1, in 
AttributeError: 'TestZeroInflatedModel_probit' object has no attribute 
'res1'

>>> a.setup_class()
/usr/lib/python3/dist-packages/statsmodels/base/model.py:567: 
ConvergenceWarning: Maximum Likelihood optimization failed to converge. 
Check mle_retvals

  warn("Maximum Likelihood optimization failed to converge. "
>>> a.res1.params
array([ 0.06225336, -0.64293239, -0.08217881,  0.00856726, -0.02679518,
1.4823691 ])
>>> 
alpha=np.ones(6);alpha[-2:]=0;res_reg=a.res1.model.fit_regularized(alpha=alpha*0.01,disp=0,maxiter=500)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:71: 
ConvergenceWarning: QC check did not pass for 4 out of 4 parameters
Try increasing solver accuracy or number of iterations, decreasing 
alpha, or switch solvers

  warnings.warn(message, ConvergenceWarning)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:144: 
ConvergenceWarning: Could not trim params automatically due to failed QC 
check. Trimming using trim_mode == 'size' will still work.

  warnings.warn(msg, ConvergenceWarning)
>>> res_reg.params
array([ 0.,  0.,  0.,  0., -0.02679517,
1.48236838])
>>> 
alpha=np.ones(6);alpha[-2:]=0;res_reg=a.res1.model.fit_regularized(alpha=alpha*0.0,disp=0,maxiter=500)

>>> res_reg.params
array([ 0.0622522 , -0.6429312 , -0.08217381,  0.00856762, -0.02679573,
1.48237116])
>>> 
alpha=np.ones(6);alpha[-2:]=0;res_reg=a.res1.model.fit_regularized(alpha=alpha*1e-6,disp=0,maxiter=500)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:71: 
ConvergenceWarning: QC check did not pass for 4 out of 4 parameters
Try increasing solver accuracy or number of iterations, decreasing 
alpha, or switch solvers

  warnings.warn(message, ConvergenceWarning)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:144: 
ConvergenceWarning: Could not trim params automatically due to failed QC 
check. Trimming using trim_mode == 'size' will still work.

  warnings.warn(msg, ConvergenceWarning)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:71: 
ConvergenceWarning: QC check did not pass for 4 out of 6 parameters
Try increasing solver accuracy or number of iterations, decreasing 
alpha, or switch solvers

  warnings.warn(message, ConvergenceWarning)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:144: 
ConvergenceWarning: Could not trim params automatically due to failed QC 
check. Trimming using trim_mode == 'size' will still work.

  warnings.warn(msg, ConvergenceWarning)
>>> res_reg.params
array([ 0.06225361, -0.64293282, -0.08218008,  0.0085677 , -0.02679533,
1.48236748])
>>> 
alpha=np.ones(6);alpha[-2:]=0;res_reg=a.res1.model.fit_regularized(alpha=alpha*1,disp=0,maxiter=500)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:71: 
ConvergenceWarning: QC check did not pass for 2 out of 4 parameters
Try increasing solver accuracy or number of iterations, decreasing 
alpha, or switch solvers

  warnings.warn(message, ConvergenceWarning)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:144: 
ConvergenceWarning: Could not trim params automatically due to failed QC 
check. Trimming using trim_mode == 'size' will still work.

  warnings.warn(msg, ConvergenceWarning)
>>> res_reg.params
array([ 0., -0.64270273, -0.08204933,  0., -0.02679321,
1.48237335])
>>> 
alpha=np.ones(6);alpha[-2:]=0;res_reg=a.res1.model.fit_regularized(alpha=alpha*100,disp=0,maxiter=500)

>>> res_reg.params
array([ 0.05531257, -0.62025715, -0.06936752,  0.00781262, -0.02661252,
1.48282813])
>>> 
alpha=np.ones(6);alpha[-2:]=0;res_reg=a.res1.model.fit_regularized(alpha=alpha*1e-4,disp=0,maxiter=500)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:71: 
ConvergenceWarning: QC check did not pass for 4 out of 4 parameters
Try increasing solver accuracy or number of iterations, decreasing 
alpha, or switch solvers

  warnings.warn(message, ConvergenceWarning)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:144: 
ConvergenceWarning: Could not trim params automatically due to failed QC 
check. Trimming using trim_mode == 'size' will still work.

  warnings.warn(msg, ConvergenceWarning)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:71: 
ConvergenceWarning: QC check did not pass for 4 out of 6 parameters
Try increasing solver accuracy or number of iterations, decreasing 
alpha, or switch solvers

  warnings.warn(message, ConvergenceWarning)
/usr/lib/python3/dist-packages/statsmodels/base/l1_solvers_common.py:144: 
ConvergenceWarning: Could not trim params 

Bug#963326: marked as done (seqmagick: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 19:48:47 +
with message-id 
and subject line Bug#963326: fixed in seqmagick 0.8.0-2
has caused the Debian Bug report #963326,
regarding seqmagick: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i 
python{version} -p 3.8 returned exit code 13
to be marked as done.

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

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


-- 
963326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seqmagick
Version: 0.8.0-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 --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py config 
> running config
> /usr/lib/python3/dist-packages/setuptools/dist.py:468: UserWarning: The 
> version specified ('') is an invalid version, this may not work as expected 
> with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more 
> details.
>   warnings.warn(
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8/build/seqmagick
> copying seqmagick/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick
> copying seqmagick/fileformat.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick
> copying seqmagick/transform.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick
> creating /<>/.pybuild/cpython3_3.8/build/seqmagick/scripts
> copying seqmagick/scripts/cli.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/scripts
> copying seqmagick/scripts/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/scripts
> creating /<>/.pybuild/cpython3_3.8/build/seqmagick/subcommands
> copying seqmagick/subcommands/convert.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/subcommands
> copying seqmagick/subcommands/primer_trim.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/subcommands
> copying seqmagick/subcommands/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/subcommands
> copying seqmagick/subcommands/quality_filter.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/subcommands
> copying seqmagick/subcommands/mogrify.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/subcommands
> copying seqmagick/subcommands/backtrans_align.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/subcommands
> copying seqmagick/subcommands/common.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/subcommands
> copying seqmagick/subcommands/extract_ids.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/subcommands
> copying seqmagick/subcommands/info.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/subcommands
> creating /<>/.pybuild/cpython3_3.8/build/seqmagick/test
> copying seqmagick/test/test_primer_trim.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test
> copying seqmagick/test/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test
> copying seqmagick/test/test_subcommands_backtrans_align.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test
> copying seqmagick/test/test_transform.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test
> copying seqmagick/test/test_subcommands_common.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test
> copying seqmagick/test/test_subcommands_convert.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test
> copying seqmagick/test/test_subcommands_quality_filter.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test
> creating 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test/integration
> copying seqmagick/test/integration/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test/integration
> copying seqmagick/test/integration/test_convert.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test/integration
> copying seqmagick/test/integration/test_info.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test/integration
> copying seqmagick/test/integration/test_mogrify.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test/integration
> copying seqmagick/test/integration/test_extract_ids.py -> 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test/integration
> creating 
> /<>/.pybuild/cpython3_3.8/build/seqmagick/test/integration/data
> copying seqmagick/test/integration/data/__init__.py -> 
> 

Bug#968176: marked as pending in gdcm

[Gert Wollny]

Control: tag -1 pending

Hello,

Bug #968176 in gdcm 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/med-team/gdcm/-/commit/adc0be5e36c5f180e5eaa54ccec4a449fddc40a1


d/control: update mono deps Closes: #968176


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/968176

Processed: Bug#968176 marked as pending in gdcm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #968176 [src:gdcm] gdcm: wrong debian/control file (mono archs missing)
Added tag(s) pending.

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

Processed: tagging 957642

[Debian Bug Tracking System]

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

> tags 957642 + patch
Bug #957642 [src:openrc] openrc: ftbfs with GCC-10
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#968174: llvm-toolchain-9: Re: Bug#968174: Prevent migration of ocaml-{integers,ctypes} to testing

[Sylvestre Ledru]

Hello,

I am off and I won't have time to work on it for the next 2 weeks.
NMU welcome :)

Cheers & sorry!
Sylvestre
Le 16/08/2020 à 08:01, Stéphane Glondu a écrit :

Hello,

These bugs are still on topic and prevent ocaml-{integers,ctypes} from
migrating to testing. Could you please fix them? Or have the faulty
packages removed from testing.


Cheers,

Bug#937665: fixed in python-coverage 4.5.2+dfsg.1-2

[Jann Haber]

It seems like, there are no more rdeps of python-coverage now. Not sure about 
pypy-coverage.
Dropping python-coverage would also fix #967200, which currently blocks 
migration to testing. :)

On Mon, 11 Nov 2019 05:48:22 +1100 Ben Finney  wrote:
> Control: reopen -1
> Control: tags -1 + pending
> 
> On 10-Nov-2019, Sandro Tosi wrote:
> > please restore python-coverage, it has still plenty of rdeps,
> > http://sandrotosi.me/debian/py2removal/python-coverage_1.svg
> 
> You're right! I prepared the release for removing Python 2 binary
> packages, and then waited; but later uploaded it by mistake.
> 
> I will make a new release to restore those binary packages.
> 
> -- 
>  \“You can't have everything; where would you put it?” —Steven |
>   `\Wright |
> _o__)  |
> Ben Finney 

Bug#957496: Prevent migration of ocaml-{integers,ctypes} to testing

[Stéphane Glondu]

Le 16/08/2020 à 18:03, Stéphane Glondu a écrit :
>>> These bugs are still on topic and prevent ocaml-{integers,ctypes} from
>>> migrating to testing. Could you please fix them? Or have the faulty
>>> packages removed from testing.
>>
>> At the moment, llvm-toolchain-8 is a key package [1], preventing its
>> autoremoval from testing. I've filed [2] and [3] to sort this out.
>>
>> [1] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
>> [2] https://bugs.debian.org/968512
>> [3] https://bugs.debian.org/968513
> 
> Related to this, I've also filed [1], [2] and updated [3].
> 
> [1] https://bugs.debian.org/968497
> [1] https://bugs.debian.org/968496
> [1] https://bugs.debian.org/966007

I've usertagged the bugs relevant to the removal of llvm-toolchain-8:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=llvm-toolchain-8-removal;users=glo...@debian.org


Cheers,

-- 
Stéphane

Bug#957496: Prevent migration of ocaml-{integers,ctypes} to testing

[Stéphane Glondu]

Le 16/08/2020 à 17:59, Stéphane Glondu a écrit :
>> These bugs are still on topic and prevent ocaml-{integers,ctypes} from
>> migrating to testing. Could you please fix them? Or have the faulty
>> packages removed from testing.
> 
> At the moment, llvm-toolchain-8 is a key package [1], preventing its
> autoremoval from testing. I've filed [2] and [3] to sort this out.
> 
> [1] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
> [2] https://bugs.debian.org/968512
> [3] https://bugs.debian.org/968513

Related to this, I've also filed [1], [2] and updated [3].

[1] https://bugs.debian.org/968497
[1] https://bugs.debian.org/968496
[1] https://bugs.debian.org/966007


Cheers,

-- 
Stéphane

Bug#957496: Prevent migration of ocaml-{integers,ctypes} to testing

[Stéphane Glondu]

Le 16/08/2020 à 08:01, Stéphane Glondu a écrit :
> These bugs are still on topic and prevent ocaml-{integers,ctypes} from
> migrating to testing. Could you please fix them? Or have the faulty
> packages removed from testing.

At the moment, llvm-toolchain-8 is a key package [1], preventing its
autoremoval from testing. I've filed [2] and [3] to sort this out.

[1] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
[2] https://bugs.debian.org/968512
[3] https://bugs.debian.org/968513


Cheers,

-- 
Stéphane

Processed: Re: Bug#968511: libgtk-3-0: Segfaults many apps depending on it

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libpango-1.0-0 1.46.0-1
Bug #968511 [libgtk-3-0] libgtk-3-0: Segfaults many apps depending on it
Bug reassigned from package 'libgtk-3-0' to 'libpango-1.0-0'.
No longer marked as found in versions gtk+3.0/3.24.22-1.
Ignoring request to alter fixed versions of bug #968511 to the same values 
previously set
Bug #968511 [libpango-1.0-0] libgtk-3-0: Segfaults many apps depending on it
Marked as found in versions pango1.0/1.46.0-1.
> severity -1 grave
Bug #968511 [libpango-1.0-0] libgtk-3-0: Segfaults many apps depending on it
Severity set to 'grave' from 'important'
> forcemerge 968337 -1
Bug #968337 {Done: Simon McVittie } [libpango-1.0-0] 
libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit
Bug #968372 {Done: Simon McVittie } [libpango-1.0-0] 
libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit
Bug #968511 [libpango-1.0-0] libgtk-3-0: Segfaults many apps depending on it
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/pango/-/issues/497'.
Marked Bug as done
Added indication that 968511 affects sylpheed
Marked as fixed in versions pango1.0/1.46.0-2.
Added tag(s) upstream.
Bug #968372 {Done: Simon McVittie } [libpango-1.0-0] 
libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit
Merged 968337 968372 968511
> affects 968337 + libgtk-3-0 libgtk2.0-0 libcogl20 libmutter-6-0 libmuffin0
Bug #968337 {Done: Simon McVittie } [libpango-1.0-0] 
libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit
Bug #968372 {Done: Simon McVittie } [libpango-1.0-0] 
libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit
Bug #968511 {Done: Simon McVittie } [libpango-1.0-0] 
libgtk-3-0: Segfaults many apps depending on it
Added indication that 968337 affects libgtk-3-0, libgtk2.0-0, libcogl20, 
libmutter-6-0, and libmuffin0
Added indication that 968372 affects libgtk-3-0, libgtk2.0-0, libcogl20, 
libmutter-6-0, and libmuffin0
Added indication that 968511 affects libgtk-3-0, libgtk2.0-0, libcogl20, 
libmutter-6-0, and libmuffin0

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

Bug#963652: Patch to build with current sphinx

[Benjamin Hof]

Control: tags -1 patch
Control: block 964387 by -1

Hi,

I believe this issue also affects packages that use python3-m2r as
build dependency.

In the upstream repo there is a patch, which I have attached here.


Kind regards,
Benjamin
diff --git a/debian/patches/0001_suffix_arg_removed_from_sphinx_v3.0.0.patch b/debian/patches/0001_suffix_arg_removed_from_sphinx_v3.0.0.patch
new file mode 100644
index 000..18a3ced
--- /dev/null
+++ b/debian/patches/0001_suffix_arg_removed_from_sphinx_v3.0.0.patch
@@ -0,0 +1,28 @@
+Subject: suffix arg removed from sphinx v3.0.0
+
+Origin: other
+Forwarded: https://github.com/miyakogi/m2r/pull/55
+From: CrossNox 
+Last-Update: 2020-04-06
+Applied-Upstream: no
+---
+ m2r.py | 6 +-
+ 1 file changed, 5 insertions(+), 1 deletion(-)
+
+diff --git a/m2r.py b/m2r.py
+index 897338d..6bd580e 100644
+--- a/m2r.py
 b/m2r.py
+@@ -649,7 +649,11 @@ def setup(app):
+ app.add_config_value('m2r_parse_relative_links', False, 'env')
+ app.add_config_value('m2r_anonymous_references', False, 'env')
+ app.add_config_value('m2r_disable_inline_math', False, 'env')
+-app.add_source_parser('.md', M2RParser)
++try:
++app.add_source_parser(".md", M2RParser)  # for older sphinx versions
++except TypeError:
++app.add_source_suffix(".md", "markdown")
++app.add_source_parser(M2RParser)
+ app.add_directive('mdinclude', MdInclude)
+ metadata = dict(
+ version=__version__,
diff --git a/debian/patches/series b/debian/patches/series
index 0819c7b..861d3c2 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
+0001_suffix_arg_removed_from_sphinx_v3.0.0.patch
 2001_privacy.patch
 2002_use_system_mathjax.patch

Processed: Patch to build with current sphinx

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #963652 [src:python-m2r] python-m2r: FTBFS with Sphinx 3.1: TypeError: 
add_source_parser() takes 2 positional arguments but 3 were given
Added tag(s) patch.
> block 964387 by -1
Bug #964387 [src:python-aiosqlite] python-aiosqlite: Update the package to the 
latest upstream version 0.13.0
964387 was not blocked by any bugs.
964387 was not blocking any bugs.
Added blocking bug(s) of 964387: 963652

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

Bug#968474: marked as done (Please include ocamlvars.mk to avoid FTBFS because of dh_dwz)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 15:22:36 +
with message-id 
and subject line Bug#968474: fixed in pplacer 1.1~alpha19-3
has caused the Debian Bug report #968474,
regarding Please include ocamlvars.mk to avoid FTBFS because of dh_dwz
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.)


-- 
968474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pplacer
Version: 1.1~alpha19-2
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org

Dear Maintainer,

Your package FTBFS at the moment, because of a failure in dh_dwz. This
failure is common to many packages written in OCaml (see for example
[1] and [2]).

As a workaround, an empty dh_dwz override has been added in the
/usr/share/ocaml/ocamlvars.mk snippet in dh-ocaml/1.1.2, which is
included in the debian/rules of most of packages written in
OCaml. However, it is not the case of your package. Please do so.


Cheers,

-- 
Stéphane

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967005
[2] 
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/pplacer_1.1~alpha19-2.rbuild.log.gz


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: pplacer
Source-Version: 1.1~alpha19-3
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated pplacer 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: Sun, 16 Aug 2020 16:59:18 +0200
Source: pplacer
Architecture: source
Version: 1.1~alpha19-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 968474
Changes:
 pplacer (1.1~alpha19-3) unstable; urgency=medium
 .
   * Include /usr/share/ocaml/ocamlvars.mk
 Closes: #968474
   * Adapt to new version of ocaml-batteries
Checksums-Sha1:
 c1d5b920cfe92c47713cd690a75a8b906cfda5ef 2206 pplacer_1.1~alpha19-3.dsc
 9b78d4eb9d249270471c9e1554f92f2623306835 11268 
pplacer_1.1~alpha19-3.debian.tar.xz
 d48b9f08d9293fa3d9d84c780da671115dbc3f48 6685 
pplacer_1.1~alpha19-3_amd64.buildinfo
Checksums-Sha256:
 422ba12afba3b729a035dcb6e6e38eea834df9b23a1ab380dd7a545e36cac605 2206 
pplacer_1.1~alpha19-3.dsc
 f9a59a4c616ac438218869eaf2702a6e94987d570ee374248d5a50a02f99 11268 
pplacer_1.1~alpha19-3.debian.tar.xz
 8d082773caeb2738b97cf9dbf6b67ca230f7430154f5c4dfcf0ac7c9808cb949 6685 
pplacer_1.1~alpha19-3_amd64.buildinfo
Files:
 733c59e0ecc52801b2cd0c570a1bf6da 2206 science optional 
pplacer_1.1~alpha19-3.dsc
 61152e2375df704e324a85689339e157 11268 science optional 
pplacer_1.1~alpha19-3.debian.tar.xz
 c53c922833456ada6bea18b870326833 6685 science optional 
pplacer_1.1~alpha19-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl85StARHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGHdQ//f+sWsSTHACIDcnqO4F/kOm7t6MjP9y8q
cBwQBQ9lXcHx1WhUNQw56lzFOBE063QcPlEZaZN78kYFv4AQsC/5TrVognW16Bs3
o/o+hVOSE0bcgh0oi93yAnsttqe/N8+gQ2MVz/e6L2mkmscI6G1kMSInG5gHiRZU
zlyyhSyoxwp4rwai2YKNbQ5L545BNYk/iQXfd6wTVrXlkz9Ze1x+6K4AtYK+ENtl
OChALdZBl5qS9ZmtU+7TitosAeiJuU13XHKUgiSVxbjAdC2gitk429RPWM3T9Oa2
oxZtiMbecIenBfVHxkNilf6jrFCrlNEy5G1UUF9DyS1FhP9Rc5Grg65WnfAA+az+
9lvd3bErZgVA+23sP8tHVRzh60+g9NST4l6+rPhMAD3MIo1bhz2g8mO9w7gtGPrp
0FGXdBKFiFcuvmB9tl4xdKpZcCpfRroOPswfAw6p9g9EgVKPp0LPVhze1R3RZfCz
77iEIocdMJJjFAD8H2Q1YsVVkTCoy2ycXM9OEhauEMh8tHrD335DyTWuuf/j1KSC
c7zw1jZUoW9GRBtS7aBlpdrOKkyj1l6q5sO56J8FM3OJfLbRihzJVpMxI4XsNUqD

Bug#968509: linux-image-4.19.0-10-amd64: System hangs within a few minutes of booting

[Richard Kettlewell]

Package: src:linux
Version: 4.19.132-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Upgraded from 4.19.0-9 to 4.19.0-10.

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

"apt-get dist-upgrade" and subsequent reboot.

   * What was the outcome of this action?

With kernel 4.19.0-10 the system hangs within minutes.



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 1101
board_vendor: ASUSTeK COMPUTER INC.
board_name: PRIME H370M-PLUS
board_version: Rev 1.xx

** Network interface configuration:

auto lo
iface lo inet loopback

auto br0
iface br0 inet static
  network 172.17.207.0
  address 172.17.207.18
  netmask 255.255.255.0
  broadcast 172.17.207.255
  gateway 172.17.207.1
  bridge_ports eno1
  bridge_maxwait 2
  bridge_stp off
  up echo 0 > /proc/sys/net/ipv6/conf/br0/accept_ra
  up ip address add 2001:470:1f09:11ed::12/64 dev br0
  up ip route add default via 2001:470:1f09:11ed::1






** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host 
Bridge/DRAM Registers [8086:3ec2] (rev 07)
Subsystem: ASUSTeK Computer Inc. 8th Gen Core Processor Host 
Bridge/DRAM Registers [1043:8694]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 
(Desktop) [8086:3e92] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI 
Host Controller [8086:a36d] (rev 10) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Cannon Lake PCH USB 3.1 xHCI Host 
Controller [1043:8694]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 RAM memory [0500]: Intel Corporation Cannon Lake PCH Shared SRAM 
[8086:a36f] (rev 10)
Subsystem: ASUSTeK Computer Inc. Cannon Lake PCH Shared SRAM [1043:8694]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:16.0 Communication controller [0780]: Intel Corporation Cannon Lake PCH HECI 
Controller [8086:a360] (rev 10)
Subsystem: ASUSTeK Computer Inc. Cannon Lake PCH HECI Controller 
[1043:8694]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel Corporation Cannon Lake PCH SATA AHCI 
Controller [8086:a352] (rev 10) (prog-if 01 [AHCI 1.0])
Subsystem: ASUSTeK Computer Inc. Cannon Lake PCH SATA AHCI Controller 
[1043:8694]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ahci
Kernel modules: ahci

00:1c.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root 
Port [8086:a33a] (rev f0) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1d.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root 
Port [8086:a330] (rev f0) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- 

Bug#957858: marked as done (syslinux: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 15:04:29 +
with message-id 
and subject line Bug#957858: fixed in syslinux 
3:6.04~git20190206.bf6db5b4+dfsg1-3
has caused the Debian Bug report #957858,
regarding syslinux: 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.)


-- 
957858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:syslinux
Version: 3:6.04~git20190206.bf6db5b4+dfsg1-2
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/syslinux_6.04~git20190206.bf6db5b4+dfsg1-2_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

[...]
  225 |  snprintf(connection, sizeof_connection, "%s%u", connection, code & 
0x0F);
  |  
^~~~
/<>/com32/gpllib/dmi/dmi_memory.c:217:56: note: destination object 
referenced by ‘restrict’-qualified argument 1 was declared here
  217 | void dmi_memory_module_connections(uint8_t code, char *connection, int 
sizeof_connection)
  |  ~~^~
/<>/com32/gpllib/dmi/dmi_memory.c: In function 
‘dmi_memory_module_size’:
/<>/com32/gpllib/dmi/dmi_memory.c:257:2: warning: ‘snprintf’ 
argument 4 overlaps destination object ‘size’ [-Wrestrict]
  257 |  snprintf(size, sizeof_size, "%s %s", size, "(Single-bank Connection)");
  |  ^~
/<>/com32/gpllib/dmi/dmi_memory.c:237:49: note: destination object 
referenced by ‘restrict’-qualified argument 1 was declared here
  237 | void dmi_memory_module_size(uint8_t code, char *size, int sizeof_size)
  |   ~~^~~~
/<>/com32/gpllib/dmi/dmi_memory.c:255:2: warning: ‘snprintf’ 
argument 4 overlaps destination object ‘size’ [-Wrestrict]
  255 |  snprintf(size, sizeof_size, "%s %s", size, "(Double-bank Connection)");
  |  ^~
/<>/com32/gpllib/dmi/dmi_memory.c:237:49: note: destination object 
referenced by ‘restrict’-qualified argument 1 was declared here
  237 | void dmi_memory_module_size(uint8_t code, char *size, int sizeof_size)
  |   ~~^~~~
gcc -MT dmi/dmi_processor.o -MD -MF dmi/.dmi_processor.o.d -Os -march=i386 
-falign-functions=0 -falign-jumps=0 -falign-labels=0 -ffast-math 
-fomit-frame-pointer -std=gnu99 -m32 -mpreferred-stack-boundary=2 
-fno-stack-protector -fwrapv -freg-struct-return -fPIC -fno-exceptions 
-fno-asynchronous-unwind-tables -fno-strict-aliasing -falign-functions=0 
-falign-jumps=0 -falign-labels=0 -falign-loops=0 -g -D__COM32__ 
-D__FIRMWARE_BIOS__ -nostdinc -iwithprefix include -I. 
-I/<>/com32/gpllib/sys -I/<>/com32/gpllib/../include 
-I/<>/com32/include/sys -I/<>/core/include 
-I/<>/com32/lib/ -I/<>/com32/lib/sys/module 
-I/<>/bios/com32/gpllib//../.. 
-I/<>/com32/gpllib/../gplinclude 
-I/<>/com32/gpllib/../gplinclude/zzjson -W -Wall 
-Wstrict-prototypes  -Wpointer-arith -Wwrite-strings -Wstrict-prototypes 
-Winline -DDYNAMIC_CRC_TABLE -mregparm=3 -DREGPARM=3 -c -o dmi/dmi_processor.o 
/<>/com32/gpllib/dmi/dmi_processor.c
gcc -MT vpd/vpd.o -MD -MF vpd/.vpd.o.d -Os -march=i386 -falign-functions=0 
-falign-jumps=0 -falign-labels=0 -ffast-math -fomit-frame-pointer -std=gnu99 
-m32 -mpreferred-stack-boundary=2 -fno-stack-protector -fwrapv 
-freg-struct-return -fPIC 

Bug#968372: marked as done (libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 14:36:08 +
with message-id 
and subject line Bug#968337: fixed in pango1.0 1.46.0-2
has caused the Debian Bug report #968337,
regarding libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit
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.)


-- 
968337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sylpheed
Version: 3.7.0-8
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: bugzilla...@gmail.com

Dear Maintainer,

Following libpango-1.0-0 (and others) upgrade this morning, gdb reports:


Thread 1 "sylpheed" received signal SIGSEGV, Segmentation fault.
0xb73cfebf in pango_renderer_part_changed ()
   from /usr/lib/i386-linux-gnu/libpango-1.0.so.0


-- System Information:
Debian Release: bullseye/sid
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 5.7.0-2-686-pae (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sylpheed depends on:
ii  libc62.31-3
ii  libcairo21.16.0-4
ii  libcompfaceg11:1.5.2-5+b2
ii  libenchant-2-2   2.2.8-1
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.64.4-1
ii  libgpgme11   1.14.0-1
ii  libgtk2.0-0  2.24.32-4
ii  libgtkspell0 2.0.16-1.3
ii  libldap-2.4-22.4.50+dfsg-1+b1
ii  libonig5 6.9.5-2
ii  libpango-1.0-0   1.46.0-1
ii  libpangocairo-1.0-0  1.46.0-1
ii  libssl1.11.1.1g-1
ii  pinentry-gtk21.1.0-4
ii  sensible-utils   0.0.12+nmu1

Versions of packages sylpheed recommends:
ii  aspell-en [aspell-dictionary]  2018.04.16-0-1
ii  ca-certificates20200601
ii  sylfilter  0.8-7
ii  sylpheed-i18n  3.7.0-8

Versions of packages sylpheed suggests:
pn  claws-mail-tools  
ii  curl  7.68.0-1+b1
pn  sylpheed-doc  
pn  sylpheed-plugins  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pango1.0
Source-Version: 1.46.0-2
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
pango1.0, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 968...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated pango1.0 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 16 Aug 2020 14:07:31 +0100
Source: pango1.0
Architecture: source
Version: 1.46.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 968337
Changes:
 pango1.0 (1.46.0-2) unstable; urgency=medium
 .
   * Team upload
   * d/p/renderer-Move-overline-to-priv-data-structure.patch:
 Revert ABI break on 32-bit architectures in 1.45.1 (Closes: #968337)
Checksums-Sha1:
 3da7a1bbcd60b84455dc17440ff35bbd9748bea0 3581 pango1.0_1.46.0-2.dsc
 dad27368f3be3ff01b34f6fbdaff743217cfab3c 34332 pango1.0_1.46.0-2.debian.tar.xz
 33ec68f24ebadbea5ac32bcbfa3e5d91834386db 8999 
pango1.0_1.46.0-2_source.buildinfo
Checksums-Sha256:
 2f66f2050614ba0d51852549bb9790baa5ebd3245987614b9557af75692cee34 3581 
pango1.0_1.46.0-2.dsc
 3d6acb8c28e148381043a939b30218769db06a768e54e23e1b741070f066631d 34332 
pango1.0_1.46.0-2.debian.tar.xz
 aafd7b8b336d9f0f2754385fb0050930d67f38a87bf0cd1c8b108b9d965b1ebb 8999 
pango1.0_1.46.0-2_source.buildinfo
Files:
 0ea42b0811a21708ed1327791820e825 3581 libs optional pango1.0_1.46.0-2.dsc
 759b9407058545c4f5f02bbc4035 34332 libs optional 
pango1.0_1.46.0-2.debian.tar.xz
 7aca07d0a1267d5fc43c097677a4ba49 8999 libs optional 
pango1.0_1.46.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl85N9wQHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMT4jWEACJVQqJll6Uu5oAuzxO5MTai4SaYToOPpmm

Bug#968337: marked as done (libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 14:36:08 +
with message-id 
and subject line Bug#968337: fixed in pango1.0 1.46.0-2
has caused the Debian Bug report #968337,
regarding libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit
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.)


-- 
968337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sylpheed
Version: 3.7.0-8
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: bugzilla...@gmail.com

Dear Maintainer,

Following libpango-1.0-0 (and others) upgrade this morning, gdb reports:


Thread 1 "sylpheed" received signal SIGSEGV, Segmentation fault.
0xb73cfebf in pango_renderer_part_changed ()
   from /usr/lib/i386-linux-gnu/libpango-1.0.so.0


-- System Information:
Debian Release: bullseye/sid
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 5.7.0-2-686-pae (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sylpheed depends on:
ii  libc62.31-3
ii  libcairo21.16.0-4
ii  libcompfaceg11:1.5.2-5+b2
ii  libenchant-2-2   2.2.8-1
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.64.4-1
ii  libgpgme11   1.14.0-1
ii  libgtk2.0-0  2.24.32-4
ii  libgtkspell0 2.0.16-1.3
ii  libldap-2.4-22.4.50+dfsg-1+b1
ii  libonig5 6.9.5-2
ii  libpango-1.0-0   1.46.0-1
ii  libpangocairo-1.0-0  1.46.0-1
ii  libssl1.11.1.1g-1
ii  pinentry-gtk21.1.0-4
ii  sensible-utils   0.0.12+nmu1

Versions of packages sylpheed recommends:
ii  aspell-en [aspell-dictionary]  2018.04.16-0-1
ii  ca-certificates20200601
ii  sylfilter  0.8-7
ii  sylpheed-i18n  3.7.0-8

Versions of packages sylpheed suggests:
pn  claws-mail-tools  
ii  curl  7.68.0-1+b1
pn  sylpheed-doc  
pn  sylpheed-plugins  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pango1.0
Source-Version: 1.46.0-2
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
pango1.0, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 968...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated pango1.0 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 16 Aug 2020 14:07:31 +0100
Source: pango1.0
Architecture: source
Version: 1.46.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 968337
Changes:
 pango1.0 (1.46.0-2) unstable; urgency=medium
 .
   * Team upload
   * d/p/renderer-Move-overline-to-priv-data-structure.patch:
 Revert ABI break on 32-bit architectures in 1.45.1 (Closes: #968337)
Checksums-Sha1:
 3da7a1bbcd60b84455dc17440ff35bbd9748bea0 3581 pango1.0_1.46.0-2.dsc
 dad27368f3be3ff01b34f6fbdaff743217cfab3c 34332 pango1.0_1.46.0-2.debian.tar.xz
 33ec68f24ebadbea5ac32bcbfa3e5d91834386db 8999 
pango1.0_1.46.0-2_source.buildinfo
Checksums-Sha256:
 2f66f2050614ba0d51852549bb9790baa5ebd3245987614b9557af75692cee34 3581 
pango1.0_1.46.0-2.dsc
 3d6acb8c28e148381043a939b30218769db06a768e54e23e1b741070f066631d 34332 
pango1.0_1.46.0-2.debian.tar.xz
 aafd7b8b336d9f0f2754385fb0050930d67f38a87bf0cd1c8b108b9d965b1ebb 8999 
pango1.0_1.46.0-2_source.buildinfo
Files:
 0ea42b0811a21708ed1327791820e825 3581 libs optional pango1.0_1.46.0-2.dsc
 759b9407058545c4f5f02bbc4035 34332 libs optional 
pango1.0_1.46.0-2.debian.tar.xz
 7aca07d0a1267d5fc43c097677a4ba49 8999 libs optional 
pango1.0_1.46.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl85N9wQHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMT4jWEACJVQqJll6Uu5oAuzxO5MTai4SaYToOPpmm

Bug#957858: syslinux GCC-10 patch

[Lukas Schwaighofer]

I was kindly pointed to
  https://bugzilla.suse.com/show_bug.cgi?id=1166605#c5
privately (thanks!), which explains that __builtin_strlen is not
actually a "builtin" and relying on that without providing a strlen
implementation is not correct (and in fact broken with GCC-10).

I'm updating the patch's description accordingly and will upload this
to unstable.


pgpPDfIl5NilL.pgp
Description: OpenPGP digital signature

Bug#968337: marked as pending in pango

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #968337 in pango 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/gnome-team/pango/-/commit/28e040e5dc11c32e0ca0b8c544ce888e8bf41b51


Revert ABI break on 32-bit architectures in 1.45.1

Closes: #968337


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/968337

Processed: Bug#968337 marked as pending in pango

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #968337 [libpango-1.0-0] libpango-1.0-0: ABI break in PangoRenderer, more 
serious on 32-bit
Bug #968372 [libpango-1.0-0] libpango-1.0-0: ABI break in PangoRenderer, more 
serious on 32-bit
Added tag(s) pending.
Added tag(s) pending.

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

Bug#964908: tomcat9: Catalina fails to load due to missing MbeansDescriptorsIntrospectionSource

[Michael Welsh Duggan]

I concur that this seems to be fixed in 9.0.37-3.

-- 
Michael Welsh Duggan
(m...@md5i.com)

Bug#957496: Please build with llvm-9 (or more recent)

[Stéphane Glondu]

tags 968497 + patch
thanks

Le 16/08/2020 à 14:04, Stéphane Glondu a écrit :
> astra-toolbox is one of the 3 packages (along with qtcreator and
> oclgrind) that still depend on llvm-toolchain-8 (which FTBFS on all
> architectures, see #957496), and that prevents removing it from
> testing.

It builds fine (on amd64) with the attached patch.


Cheers,

-- 
Stéphane
>From dd1c1884de69afd664fcb647bde76fc3e731bdcc Mon Sep 17 00:00:00 2001
From: Stephane Glondu 
Date: Sun, 16 Aug 2020 14:09:53 +0200
Subject: [PATCH] Build with llvm-9 (Closes: #968497)

---
 debian/changelog | 7 +++
 debian/control   | 2 +-
 debian/rules | 2 +-
 3 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index ef14fd7..628338b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+astra-toolbox (1.8.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with llvm-9 (Closes: #968497)
+
+ -- Stéphane Glondu   Sun, 16 Aug 2020 14:09:39 +0200
+
 astra-toolbox (1.8.3-1) unstable; urgency=medium
 
   * Initial release (Closes: #955357)
diff --git a/debian/control b/debian/control
index 4509422..0d8963c 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: non-free/python
 Priority: optional
 Maintainer: Freexian Packaging Team 
 Uploaders: Sebastien Delafond 
-Build-Depends: debhelper (>= 11), libboost-dev, nvidia-cuda-toolkit, clang-8, python3-dev, cython3, python3-numpy, python3-six, python3-scipy, liboctave-dev
+Build-Depends: debhelper (>= 11), libboost-dev, nvidia-cuda-toolkit, clang-9, python3-dev, cython3, python3-numpy, python3-six, python3-scipy, liboctave-dev
 Standards-Version: 4.4.1
 Homepage: https://github.com/centreon/astra-toolbox
 Vcs-Browser: https://salsa.debian.org/centreon-team/astra-toolbox
diff --git a/debian/rules b/debian/rules
index 427dcd1..15ebd68 100755
--- a/debian/rules
+++ b/debian/rules
@@ -23,7 +23,7 @@ override_dh_auto_configure:
 
 	# python package
 	mkdir -p $(BUILD_DIRECTORY_PYTHON)
-	export NVCCFLAGS="-ccbin clang-8" ; dh_auto_configure --builddirectory $(BUILD_DIRECTORY_PYTHON) --sourcedirectory=$(SOURCE_DIRECTORY) -- $(CONFIGURE_FLAGS_PYTHON)
+	export NVCCFLAGS="-ccbin clang-9" ; dh_auto_configure --builddirectory $(BUILD_DIRECTORY_PYTHON) --sourcedirectory=$(SOURCE_DIRECTORY) -- $(CONFIGURE_FLAGS_PYTHON)
 
 	# octave package
 	mkdir -p $(BUILD_DIRECTORY_OCTAVE)
-- 
2.28.0

Bug#968474: [Help] Re: Bug#968474: Please include ocamlvars.mk to avoid FTBFS because of dh_dwz

[Stéphane Glondu]

Le 16/08/2020 à 10:33, Andreas Tille a écrit :
> I've fixed this in Git.  However, when trying to build I get:
> 
> + ocamlfind ocamlc -c -annot -w Z -package batteries -package csv -package 
> xmlm -package gsl -package sqlite3 -package zip -package mcl -thread -I 
> pplacer_src -I json_src -I pam_src -I tests -I common_src -I pdprune_src -I 
> cdd_src -I tests/rppr -I tests/json -I tests/pplacer -I tests/guppy -o 
> pplacer_src/gcat_model.cmo pplacer_src/gcat_model.ml
> File "pplacer_src/gcat_model.ml", line 439, characters 22-73:
> 439 | (Enum.combine (Array.enum model.site_categories, Array.enum 
> mask)
> 
> ^^^
> Error: This expression has type 'a * 'b
>but an expression was expected of type
>  'weak3 Ppatteries.Enum.t = 'weak3 BatEnum.t
> Command exited with code 2.
> 
> 
> Any hint how to fix this?

I think this is due to a new version of ocaml-batteries.

The attached patch fixes that.


Cheers,

-- 
Stéphane
diff --git a/pplacer_src/gcat_model.ml b/pplacer_src/gcat_model.ml
index 525d354..bd16994 100644
--- a/pplacer_src/gcat_model.ml
+++ b/pplacer_src/gcat_model.ml
@@ -436,7 +436,7 @@ struct
  * invalid and `check` will raise an error. *)
 if Array.length model.site_categories = Array.length mask then begin
   model.site_categories <-
-(Enum.combine (Array.enum model.site_categories, Array.enum mask)
+(Enum.combine (Array.enum model.site_categories) (Array.enum mask)
  |> Enum.filter_map (function x, true -> Some x | _, false -> None)
  |> Array.of_enum);
   setup_occupied_rates model
diff --git a/pplacer_src/guppy_cmdobjs.ml b/pplacer_src/guppy_cmdobjs.ml
index 7e04319..44ffc82 100644
--- a/pplacer_src/guppy_cmdobjs.ml
+++ b/pplacer_src/guppy_cmdobjs.ml
@@ -612,7 +612,7 @@ object (self)
 
   method private filter_fal orig_length fal edges =
 List.map (Array.filteri (fun i _ -> IntSet.mem i edges)) fal,
-Enum.combine (Enum.range 0, IntSet.enum edges) |> IntMap.of_enum,
+Enum.combine (Enum.range 0) (IntSet.enum edges) |> IntMap.of_enum,
 orig_length
 
   method private filter_rep_edges prl fal =
diff --git a/pplacer_src/guppy_mcl.ml b/pplacer_src/guppy_mcl.ml
index 76538d1..39a03f1 100644
--- a/pplacer_src/guppy_mcl.ml
+++ b/pplacer_src/guppy_mcl.ml
@@ -6,7 +6,7 @@ let of_pql ?inflation criterion pql =
   let pqa = Array.of_list pql in
   let name_map =
 Enum.combine
-  (Array.enum pqa |> Enum.map Pquery.name, Enum.range 0)
+  (Array.enum pqa |> Enum.map Pquery.name) (Enum.range 0)
 |> StringMap.of_enum
   in
   let count = StringMap.cardinal name_map in
diff --git a/pplacer_src/guppy_rarefact.ml b/pplacer_src/guppy_rarefact.ml
index 80f65cb..0d7171f 100644
--- a/pplacer_src/guppy_rarefact.ml
+++ b/pplacer_src/guppy_rarefact.ml
@@ -66,7 +66,6 @@ object (self)
   @ (if is_uniform_mass then [fmt qm] else [""]))
 |> begin
   if fv variance then
-curry
   Enum.combine
   (Rarefaction.variance_of_placerun criterion ?k_max pr)
 |- Enum.map (fun ((_, uv, rv), sl) -> sl @ [fmt uv; fmt rv])
diff --git a/pplacer_src/pplacer_run.ml b/pplacer_src/pplacer_run.ml
index 65e787d..83f071c 100644
--- a/pplacer_src/pplacer_run.ml
+++ b/pplacer_src/pplacer_run.ml
@@ -85,7 +85,7 @@ let premask ?(discard_nonoverlapped = false) seq_type ref_align query_list =
* informative column of the reference sequence. *)
   let overlaps_mask s = String.enum s
 |> Enum.map Alignment.informative
-|> curry Enum.combine (Array.enum ref_mask)
+|> Enum.combine (Array.enum ref_mask)
 |> Enum.exists (uncurry (&&))
   in
   let query_list = List.filter

Bug#966301: guile oom test fails on ppc64el

[Graham Inggs]

Control: found -1 2.2.7+1-5

Adjusting version to the one in testing.

Processed: guile oom test fails on ppc64el

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.2.7+1-5
Bug #966301 [src:guile-2.2] guile oom test fails on ppc64el
Marked as found in versions guile-2.2/2.2.7+1-5.

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

Bug#957496: Please build with llvm-9 (or more recent)

[Stéphane Glondu]

tags 968496 + patch
thanks

Le 16/08/2020 à 13:57, Stéphane Glondu a écrit :
> oclgrind is one of the 3 packages (along with qtcreator and
> astra-toolbox) that still depend on llvm-toolchain-8 (which FTBFS on
> all architectures, see #957496), and that prevents removing it from
> testing.

It builds fine (on amd64) with the attached patch.


Cheers,

-- 
Stéphane
>From df0eb67d3a05325eef9518d07dfce0fa2b3d00ab Mon Sep 17 00:00:00 2001
From: Stephane Glondu 
Date: Sun, 16 Aug 2020 14:05:39 +0200
Subject: [PATCH] Build with llvm-9 (Closes: #968496)

---
 debian/changelog | 7 +++
 debian/control   | 6 +++---
 debian/rules | 2 +-
 3 files changed, 11 insertions(+), 4 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 7ef266b..08063bf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+oclgrind (19.10-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with llvm-9 (Closes: #968496)
+
+ -- Stéphane Glondu   Sun, 16 Aug 2020 14:05:14 +0200
+
 oclgrind (19.10-1) unstable; urgency=medium
 
   [ James Price ]
diff --git a/debian/control b/debian/control
index a41eb94..8577232 100644
--- a/debian/control
+++ b/debian/control
@@ -9,9 +9,9 @@ Build-Depends:
  debhelper-compat (= 12),
  dh-exec,
  cmake,
- llvm-8-dev,
- libclang-8-dev,
- clang-8,
+ llvm-9-dev,
+ libclang-9-dev,
+ clang-9,
  libedit-dev,
  zlib1g-dev,
  libreadline-dev,
diff --git a/debian/rules b/debian/rules
index 6d740a8..62acfc4 100755
--- a/debian/rules
+++ b/debian/rules
@@ -14,7 +14,7 @@ include /usr/share/dpkg/default.mk
 
 override_dh_auto_configure:
 	if [ -d src/CL ]; then mv src/CL src/CL-Do-Not-Use ; fi
-	dh_auto_configure -- -DLLVM_DIR=/usr/lib/llvm-8/lib/cmake/llvm
+	dh_auto_configure -- -DLLVM_DIR=/usr/lib/llvm-9/lib/cmake/llvm
 
 override_dh_auto_clean:
 	dh_auto_clean
-- 
2.28.0

Bug#967161: marked as done (libgtkdatabox: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 13:54:31 +0200
with message-id 

and subject line libgtkdatabox: Unversioned Python removal in sid/bullseye
has caused the Debian Bug report #967161,
regarding libgtkdatabox: 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.)


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

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 ---
I think this was due to libglade2-dev not being installable (#967157)--- End Message ---

Bug#963648: closing 963648

[Tomasz Buchert]

close 963648 1.41.0-3
thanks

Processed: closing 963648

[Debian Bug Tracking System]

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

> close 963648 1.41.0-3
Bug #963648 [src:nghttp2] nghttp2: FTBFS with Sphinx 3.1: Could not import 
extension sphinxcontrib.rubydomain (exception: cannot import name 'l_' from 
'sphinx.locale' (/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))
The source 'nghttp2' and version '1.41.0-3' do not appear to match any binary 
packages
Marked as fixed in versions nghttp2/1.41.0-3.
Bug #963648 [src:nghttp2] nghttp2: FTBFS with Sphinx 3.1: Could not import 
extension sphinxcontrib.rubydomain (exception: cannot import name 'l_' from 
'sphinx.locale' (/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#968126: marked as done (mricron: FTBFS with fpc 3.2.0)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 11:18:24 +
with message-id 
and subject line Bug#968126: fixed in mricron 0.20140804.1~dfsg.1-3.1
has caused the Debian Bug report #968126,
regarding mricron: FTBFS with fpc 3.2.0
to be marked as done.

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

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


-- 
968126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mricron
Version: 0.20140804.1~dfsg.1-3
Severity: serious
Tags: ftbfs bullseye sid
X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net

Hi Maintainer

As can be seen on reproducible builds [1], this package FTBFS since
the upload of fpc 3.2.0+dfsg-5 to unstable.

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mricron.html


(3104) Compiling /build/1st/mricron-0.20140804.1~dfsg.1/common/distr.pas
/build/1st/mricron-0.20140804.1~dfsg.1/common/distr.pas(561,10)
Warning: (2005) Comment level 2 found
/build/1st/mricron-0.20140804.1~dfsg.1/common/distr.pas(545,1) Fatal:
(2000) Unexpected end of file
Fatal: (1018) Compilation aborted
--- End Message ---
--- Begin Message ---
Source: mricron
Source-Version: 0.20140804.1~dfsg.1-3.1
Done: Graham Inggs 

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated mricron package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Aug 2020 10:52:31 +
Source: mricron
Architecture: source
Version: 0.20140804.1~dfsg.1-3.1
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Graham Inggs 
Closes: 968126
Changes:
 mricron (0.20140804.1~dfsg.1-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Close comments to be compatible with FPC 3.2 (Closes: #968126)
Checksums-Sha1:
 facb5fe3c586ccdee65e84522534c6a0a07298ba 2257 
mricron_0.20140804.1~dfsg.1-3.1.dsc
 6e23b02c8ef3f46e2b9a7b2e8522e10498dfdfbd 10808 
mricron_0.20140804.1~dfsg.1-3.1.debian.tar.xz
Checksums-Sha256:
 adfc27b4440f9413dc64d1180c1228752383e9d0be268c78916d0e1102e1c154 2257 
mricron_0.20140804.1~dfsg.1-3.1.dsc
 3cbbf274c3d98ba4b33b9986ce64354593be1c464fa2175ec07f7d030801bfa4 10808 
mricron_0.20140804.1~dfsg.1-3.1.debian.tar.xz
Files:
 8105f2c4a67743209bc0e950af243bba 2257 science optional 
mricron_0.20140804.1~dfsg.1-3.1.dsc
 f09a62be3b233c03fed608fb15821082 10808 science optional 
mricron_0.20140804.1~dfsg.1-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl85EHAACgkQr8/sjmac
4cJ+hQ//doPkpotoZwPvNOox2Y7ObA7fHwtr9p8RiZtVA5NycAmIpDc0qB50wnlM
WTTkho7GL6nOVgP8x4A+VS7U2JRHi2xlotn5aQXv5uRudWIrKr2cIKFV+jZbmaXR
lnJEU4AgqbftxgYsAVM8E5aWJWqljhTs98sgfGu21iwQsHm+1SSbLd4x4ZpMVyFP
hEOFyAVUuGMTlKJvngRKFQq3bheBou46A/DMxTgng01wheF2fVyu0646JGUEP4+9
DpmRY/5Zr+PnlUNDxz1bfjABasz6ocdIA87stpxQ5MoP2fyeqEGySC0SCJWBNBdj
Wsu2lyubqbas7nRwABkSO+8K/zrxU9eAEILo0ZMyLWTpY5Oq60yOM7tXTiG0tYEs
ipt/Tfp2RW3HW0Wyw3FVLJbOCJh/Y6V6/KisrWOipSQ1dl+6cf2Uq/hu2IUkBYlB
Os8690FuZpoVk6BuN8aOU9l6RcCWaUeXlv+h3l/CPFvmD3tdBCPVmg8But70bQWK
lKW3RLzpFOLIKkYLZELZO5RLRAedlILVuDbaIV6SwAKsz6BNQc5dPsTYw9ddZz3T
YHPw4m7ZN1qNpH4/aTejUMehtV4ALx32CgbcqAa/f8G9qBz2NUMtheWZN4hVFO4z
OwS0rhBIDdV7iewLB/KtNMboCqO7QjGlulkr5stolmzPFSzpnS0=
=fStg
-END PGP SIGNATURE End Message ---

Bug#957496: qtcreator: link to library libclang-1.9 (instead libclang-1.8)

[Stéphane Glondu]

tags 966007 + patch
thanks

Antonio wrote:
> I can't remove the old version of clang because it is a dependency of
> qtcreator (and only he uses it): is it possible to recompile this package
> with the next version of clang library?

qtcreator is one of the 3 packages (along with oclgrind and
astra-toolbox) that still depend on llvm-toolchain-8 (which FTBFS on all
architectures, see #957496), and that prevents removing it from testing.

It builds fine (on amd64) with the attached patch.


Cheers,

-- 
Stéphane
From 018d4204689c95836adc621eb77088eacdace248 Mon Sep 17 00:00:00 2001
From: Stephane Glondu 
Date: Sun, 16 Aug 2020 10:59:53 +0200
Subject: [PATCH] Build with llvm-9 (Closes: #966007)

---
 debian/changelog | 7 +++
 debian/control   | 4 ++--
 debian/rules | 2 +-
 3 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index d7f0b2fc..0f41c77f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+qtcreator (4.12.3-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with llvm-9 (Closes: #966007)
+
+ -- Stéphane Glondu   Sun, 16 Aug 2020 10:59:33 +0200
+
 qtcreator (4.12.3-3) unstable; urgency=medium
 
   * Team upload.
diff --git a/debian/control b/debian/control
index 2124f813..c418e465 100644
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,7 @@ Uploaders: Adam Majer ,
Lisandro Damián Nicanor Pérez Meyer ,
Simon Quigley 
 Build-Depends: debhelper-compat (= 12),
-   libclang-8-dev,
+   libclang-9-dev,
libdw-dev,
libicu-dev,
libjs-jquery,
@@ -17,7 +17,7 @@ Build-Depends: debhelper-compat (= 12),
libqt5serialport5-dev (>= 5.11.0~),
libqt5sql5-sqlite (>= 5.11.0~),
libqt5x11extras5-dev (>= 5.11.0~),
-   llvm-8-dev,
+   llvm-9-dev,
pkg-config,
qml-module-qtquick-controls (>= 5.11.0~),
qml-module-qtquick2 (>= 5.11.0~),
diff --git a/debian/rules b/debian/rules
index 98464ee9..16241f2c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,7 +6,7 @@
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 
 export QT_SELECT := qt5
-export LLVM_INSTALL_DIR := "/usr/lib/llvm-8"
+export LLVM_INSTALL_DIR := "/usr/lib/llvm-9"
 
 # Upstream changelog
 upstream_changes := $(wildcard dist/changes-*)
-- 
2.28.0

Bug#968121: marked as done (ddrescueview: FTBFS with fpc 3.2.0)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 11:03:31 +
with message-id 
and subject line Bug#968121: fixed in ddrescueview 0.4~alpha3-4
has caused the Debian Bug report #968121,
regarding ddrescueview: FTBFS with fpc 3.2.0
to be marked as done.

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

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


-- 
968121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ddrescueview
Version: 0.4~alpha3-3
Severity: serious
Tags: ftbfs bullseye sid
X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net

Hi Maintainer

As can be seen on reproducible builds [1], this package FTBFS since
the upload of fpc 3.2.0+dfsg-5 to unstable.

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ddrescueview.html


(3104) Compiling Parser.pas
/build/1st/ddrescueview-0.4~alpha3/source/Parser.pas(78,56) Error:
(5098) Record or object type expected
/build/1st/ddrescueview-0.4~alpha3/source/Parser.pas(79,46) Error:
(5098) Record or object type expected
/build/1st/ddrescueview-0.4~alpha3/source/Parser.pas(80,50) Error:
(5098) Record or object type expected
/build/1st/ddrescueview-0.4~alpha3/source/Parser.pas(81,50) Error:
(5098) Record or object type expected
/build/1st/ddrescueview-0.4~alpha3/source/Parser.pas(85,1) Fatal:
(10026) There were 4 errors compiling module, stopping
Fatal: (1018) Compilation aborted
--- End Message ---
--- Begin Message ---
Source: ddrescueview
Source-Version: 0.4~alpha3-4
Done: Graham Inggs 

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated ddrescueview package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Aug 2020 10:47:46 +
Source: ddrescueview
Architecture: source
Version: 0.4~alpha3-4
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Graham Inggs 
Closes: 968121
Changes:
 ddrescueview (0.4~alpha3-4) unstable; urgency=medium
 .
   [ Peter Michael Green ]
   * Use getters rather than direct access for properties that
 access fields in other classes to fix build with fpc 3.2.
 (Closes: #968121)
 .
   [ Graham Inggs ]
   * Switch to debhelper 13
   * Set Rules-Requires-Root: no
   * Bump Standards-Version to 4.5.0, no changes
Checksums-Sha1:
 3010a416f14d240286f1e8987b7880e231c41b2a 2060 ddrescueview_0.4~alpha3-4.dsc
 24770d852830f4052d13ae5296da04d0cb42f11f 4064 
ddrescueview_0.4~alpha3-4.debian.tar.xz
Checksums-Sha256:
 a83c2354b5d90267a979c81600ed523e6fb9e3058f53929fea280bc67b1d2579 2060 
ddrescueview_0.4~alpha3-4.dsc
 e1cd3d62d7e19a1871a46cd52afe71d53f6f327b5b4f455c62a2aae993a9a6cc 4064 
ddrescueview_0.4~alpha3-4.debian.tar.xz
Files:
 572d985bcc226c11cc9af3aaa8161a6c 2060 utils optional 
ddrescueview_0.4~alpha3-4.dsc
 371fc4b7b158dfc430a03be7e4c0da8b 4064 utils optional 
ddrescueview_0.4~alpha3-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl85D5UACgkQr8/sjmac
4cKY5g//a3Xg+k/0/OQ7932ziRd7djpHKnBQ3W+GDxvOwG0kYhg+xUJnadAV/EZC
/doCfzeI3xCNyKsm+kNlIuDaY3M8rXn9P7wBz3+H9zaUgT5f7ttiuNpWOONewIzl
+iqXfEDkbdxk6BCaZFARoxua6w+LdJwTT79bk2RYzOeyC7bh598tDPgjjnnXy+9s
hbo8IB+sKpT2adf1uLg0jwBiTxHpBpaVgTi6d9btDX3fNSyWhNIJiJ17YeeE/CDp
RF1D4ia6crW80leFrJk8FLaNIx0gDtPVuBuHVs56Iaf1vhUDnKKUizg5AQ2x8StU
cBVTRDLZk4kSF+AdTEm5EiT3RYIkq69kQQQ9EplpJwNw908ehov9RTkAsyCRly6R
raL3wn1vGa8KK/0csPyIfjd+UYAWxDusym0Awh8lcfkVlLjP6ezK3Q7R5A2/RAyb
neOZinYgkQAi1dvVuVF6Ty79fTRQW8k1w2QUkK20iOclsqmLVZSPeXPdu/9YQkAG
KtgEyQjRjno0XF2U+xXSih+wBeJ2PliaujleCKVaB4IpzE9YlQ1rC3w8u5+Dmmz7
yfXUzZbXhs7dz9sa6rrHekyn0cnLit1dZ3RscltQlTvFBN+dnyGQvD2QWGtw9sEc
zFdHt8dTbI1UHNKT4YtJaIw3PFVKqXnVY5uAfhAAXyQZWGnnQb4=
=XWQ3
-END PGP SIGNATURE End Message ---

Bug#967012: marked as done (vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 10:50:29 +
with message-id 
and subject line Bug#967012: fixed in vmem 1.8-2
has caused the Debian Bug report #967012,
regarding vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern
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.)


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

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/src/test'
> out_err/TEST0: SETUP (check/debug)
> out_err/TEST0: PASS   [00.025 s]
> out_err_mt/TEST0: SETUP (check/debug)
> out_err_mt/TEST0: PASS[00.027 s]
> out_err_mt/TEST0: SETUP (check/nondebug)
> out_err_mt/TEST0: PASS[00.026 s]
> out_err_mt/TEST1: SETUP (check/debug/drd)
> out_err_mt/TEST1: PASS[00.589 s]
> out_err_mt/TEST1: SETUP (check/nondebug/drd)
> out_err_mt/TEST1: PASS[00.564 s]
> out_err_mt/TEST2: SETUP (check/debug/helgrind)
> out_err_mt/TEST2: PASS[00.534 s]
> out_err_mt/TEST2: SETUP (check/nondebug/helgrind)
> out_err_mt/TEST2: PASS[00.511 s]
> scope/TEST0: SETUP (check/debug)
> [MATCHING FAILED, COMPLETE FILE (out0.log) BELOW]
> ../../debug/libvmem.so.1:
> vmem_aligned_alloc@@LIBVMEM_1.0
> vmem_calloc@@LIBVMEM_1.0
> vmem_check@@LIBVMEM_1.0
> vmem_check_version@@LIBVMEM_1.0
> vmem_create@@LIBVMEM_1.0
> vmem_create_in_region@@LIBVMEM_1.0
> vmem_delete@@LIBVMEM_1.0
> vmem_errormsg@@LIBVMEM_1.0
> vmem_free@@LIBVMEM_1.0
> vmem_malloc@@LIBVMEM_1.0
> vmem_malloc_usable_size@@LIBVMEM_1.0
> vmem_realloc@@LIBVMEM_1.0
> vmem_set_funcs@@LIBVMEM_1.0
> vmem_stats_print@@LIBVMEM_1.0
> vmem_strdup@@LIBVMEM_1.0
> vmem_wcsdup@@LIBVMEM_1.0
> 
> [EOF]
> out0.log.match:1   $(*)
> out0.log:1 ../../debug/libvmem.so.1:
> out0.log.match:2   vmem_aligned_alloc
> out0.log:2 vmem_aligned_alloc@@LIBVMEM_1.0
> FAIL: match: out0.log.match:2 did not match pattern
> RUNTESTS: stopping: scope/TEST0 failed, BUILD=debug
> make[4]: *** [Makefile:158: check] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/vmem_1.8-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: vmem
Source-Version: 1.8-2
Done: Adam Borowski 

We believe that the bug you reported is fixed in the latest version of
vmem, 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.
Adam Borowski  (supplier of updated vmem package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Aug 2020 12:26:47 +0200
Source: vmem
Architecture: source
Version: 1.8-2
Distribution: unstable
Urgency: medium
Maintainer: Adam Borowski 
Changed-By: Adam Borowski 
Closes: 967012
Changes:
 vmem (1.8-2) unstable; urgency=medium
 .
   * Fix FTBFS with binutils 2.35.  Closes: #967012.
Checksums-Sha1:
 fdcc71bb6cae6f169ed27ba20a19ba93f2653ad7 2327 vmem_1.8-2.dsc
 099115b43df94892c3e7617bd72de9dbf570faf1 10644 vmem_1.8-2.debian.tar.xz
 73115a8ad0491efd016a727e1527dbcdac65b9fa 5327 vmem_1.8-2_source.buildinfo
Checksums-Sha256:
 c9b2fb2d2c814a9d21f4e2b2faca91487e01df04dbbc5ab58b10c6218a236bfb 2327 
vmem_1.8-2.dsc
 9b45e11aa2d544a95dc216cf4d790d89c57606b070eda3ac075839241ba987ad 10644 
vmem_1.8-2.debian.tar.xz
 e59505037493d1e35faa9f3b52e7207f99136185d297c67ed97b5552314f98c5 5327 
vmem_1.8-2_source.buildinfo
Files:
 e271d0a89a7149af9b487112e8f3ef2c 2327 libs optional vmem_1.8-2.dsc
 

Bug#961444: marked as done (grcompiler FTBFS on architectures where char is unsigned)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 10:03:29 +
with message-id 
and subject line Bug#961444: fixed in grcompiler 5.2-2
has caused the Debian Bug report #961444,
regarding grcompiler FTBFS on architectures where char is unsigned
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.)


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

https://buildd.debian.org/status/package.php?p=grcompiler=sid

...
 7/15 Test #13: compile_PadaukTest_v3 ...Child aborted***Exception: 
  0.20 sec
Frexx C Preprocessor v1.5 Copyright (C) by FrexxWare 1993 - 1997.
Revised by SIL International for Graphite Description Language, May 24 2020
grcompiler: /<>/compiler/GdlExpression.cpp:3259: virtual void 
GdlSlotRefExpression::GenerateEngineCode(int, std::vector&, int, 
std::vector*, int, bool, int, int*): Assertion `(int)bOffset == nOffset' 
failed.
...


The build passes if I rewrite the line above the assert to
  signed char bOffset = (signed char)nOffset;
but someone who knows the code better should check what
is actually the correct fix.
--- End Message ---
--- Begin Message ---
Source: grcompiler
Source-Version: 5.2-2
Done: Hideki Yamane 

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated grcompiler package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Aug 2020 18:41:30 +0900
Source: grcompiler
Architecture: source
Version: 5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Hideki Yamane 
Closes: 961444
Changes:
 grcompiler (5.2-2) unstable; urgency=medium
 .
   * Team upload
   * debian/patches
 - Add 0004-Bug#961444.patch, taken from upstream git to deal with
   "FTBFS on architectures where char is unsigned" (Closes: #961444)
Checksums-Sha1:
 664317d34c3113b9711155238f82d3a4714368d4 2014 grcompiler_5.2-2.dsc
 32f2671f56b52f497b7ec70edf5a1ed3e72773d8 12780 grcompiler_5.2-2.debian.tar.xz
 68d8ae7eac91276510f2a0719e55dd3fa24d238a 8165 grcompiler_5.2-2_amd64.buildinfo
Checksums-Sha256:
 27d583a5466ac25f0fdfd6a72e97cd0522005679cdb6d32d4e84ab66206db12b 2014 
grcompiler_5.2-2.dsc
 148362a7c5cf0254bb0726746cdd4c94b720c087312dd2e74e99597f3f3f3b10 12780 
grcompiler_5.2-2.debian.tar.xz
 9fdc980b23dcd2554e38716144e1dab34951df085ff95991da01e51a8a4ce802 8165 
grcompiler_5.2-2_amd64.buildinfo
Files:
 762cbd6f73a207f859185dcfb526a558 2014 devel optional grcompiler_5.2-2.dsc
 1598f687633bd90bdb9a23bc9cd77c41 12780 devel optional 
grcompiler_5.2-2.debian.tar.xz
 97935a2bd42909f93534f0fba5d39d60 8165 devel optional 
grcompiler_5.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWOEiL5aWyIWjzRBMXTKNCCqqsUAFAl85AlgACgkQXTKNCCqq
sUA9MA//cnF5jZ0ctr4DF+FkIxJ5O1KU2hMSVCx9vpct2ofjUB+kl73DRy1zuSj/
cZBys6IIthhZvK++WgVMKe+rlrHJsAe/sOxU5zS0jIktskOtMgcGNGWLNPNIymAr
J2iTT3CebcwMNuVYVM5f/zRpUq0SfzGsK1hMpWrRwt2r43A67A6l0AL/5TEJl1ln
Lt+u7fOsw7Tb8gyiNh5yFv1uVe+rRBarRjrB7rISaQkGo5RA9f4LzXYMzWJVz3fV
RSuo57V8XIOjAKARP3xHhfvNPDzoq5x5UXpHru5GCikQgNPPr8Y6JHVcs2RuuuH2
9JeIMH4qjbcndpWgirMksLJoBbsLB5BotTS+CCjxRwXk6xEFyU4NQNXvDh5q8Ji8
HRbocjMnJsRl7JArcPQ4rp2iZYi6YkD7x27BRqWpSWsIZ6QLWGeTPhajq/KasFNX
H8dCeSmxfL7I8Gmsh/QfPTjiS+3iTFmoecQcmrBHrFNy5mOPfEGfw25qL0FeZfXw
0IfS/9xnoKV1OdPQ6glw43z7HLR+4E4ZpvMJOOCYtM7Zk5GISCmKTdVf+gjdlhWK
wL5oP2xfJ1WSvyl//7/+O4KAmcuspJUaCoWk8MJDrNO9bCC10oRFld8O4x4vxLSc
5ImZYG9itDXWILmqW7ztTnmk+dpaPV7RihAYgb/7kvZOLw6514Y=
=2Z3O
-END PGP SIGNATURE End Message ---

Bug#960120: node-yarnpkg: I found an older commit that still builds

[Paolo Greppi]

Il 15/08/20 14:00, Pirate Praveen ha scritto:
>> With this build:
>> https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/915568#L2420
> 
>> I get a different error while building:
>> [17:58:12] Starting 'build'...
>> 2420[17:58:13] Error: [BABEL] 
>> /builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.22.4/src/api.js: 
>> Cannot find module
>> 'babel-plugin-transform-strict-mode'
> 
>> ?
> 
> With sbuild, I can reproduce the error. But on a sid schroot, 
> dpkg-buildpackage works. May be I have some things locally installed.
> 
> If you go back to commit 3f1ab4d62789670ee39648eb35078ce244ba2d09 it is 
> building fine. We need to analyze the commits that came after this I think.

The autopkgtest failure you mention in your message to the BTS of May 17th is a 
side effect.
The root cause is that the webpack build itself is broken, but the error 
message ("Unhandled rejection TypeError: fileDependencies.map is not a 
function") is not really helpful.
(I had pointed that out here already: https://bugs.debian.org/958780#39)

I have rebased my last commit (that patches scripts/build-webpack.js so that it 
prints the actual errors) on top of 3f1ab4d6, in the wip/paolog/babel7 branch.
In the log a bunch of new ERRORS appear:

ERROR in ./src/errors.js
Module not found: Error: Can't resolve 
'@babel/runtime/helpers/assertThisInitialized' in 
'/builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.22.4/src'
@ ./src/errors.js 12:53-108
@ ./src/cli/index.js
...
ERROR in ./src/config.js
Module not found: Error: Can't resolve 
'@babel/runtime/helpers/asyncToGenerator' in 
'/builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.22.4/src'
@ ./src/config.js 17:48-98
@ ./src/cli/index.js
...
ERROR in ./src/errors.js
Module not found: Error: Can't resolve 
'@babel/runtime/helpers/classCallCheck' in 
'/builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.22.4/src'
@ ./src/errors.js 10:46-94
@ ./src/cli/index.js
...

for the full list see the salsa CI run: 
https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/937269#L2529

I think we've been too eager to upgrade to babel 7, while upstream does not 
really care (see https://github.com/yarnpkg/yarn/issues/8083)
Also our patches should be easy to forward.

Unfortunately I am not able to help with troubleshooting this babel.

Paolo

Bug#968474: [Help] Re: Bug#968474: Please include ocamlvars.mk to avoid FTBFS because of dh_dwz

[Andreas Tille]

Control: tags -1 pending
Control: tags -1 help

On Sun, Aug 16, 2020 at 07:17:13AM +0200, Stéphane Glondu wrote:
> As a workaround, an empty dh_dwz override has been added in the
> /usr/share/ocaml/ocamlvars.mk snippet in dh-ocaml/1.1.2, which is
> included in the debian/rules of most of packages written in
> OCaml. However, it is not the case of your package. Please do so.

I've fixed this in Git.  However, when trying to build I get:

+ ocamlfind ocamlc -c -annot -w Z -package batteries -package csv -package xmlm 
-package gsl -package sqlite3 -package zip -package mcl -thread -I pplacer_src 
-I json_src -I pam_src -I tests -I common_src -I pdprune_src -I cdd_src -I 
tests/rppr -I tests/json -I tests/pplacer -I tests/guppy -o 
pplacer_src/gcat_model.cmo pplacer_src/gcat_model.ml
File "pplacer_src/gcat_model.ml", line 439, characters 22-73:
439 | (Enum.combine (Array.enum model.site_categories, Array.enum mask)
^^^
Error: This expression has type 'a * 'b
   but an expression was expected of type
 'weak3 Ppatteries.Enum.t = 'weak3 BatEnum.t
Command exited with code 2.


Any hint how to fix this?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: [Help] Re: Bug#968474: Please include ocamlvars.mk to avoid FTBFS because of dh_dwz

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #968474 [src:pplacer] Please include ocamlvars.mk to avoid FTBFS because of 
dh_dwz
Added tag(s) pending.
> tags -1 help
Bug #968474 [src:pplacer] Please include ocamlvars.mk to avoid FTBFS because of 
dh_dwz
Added tag(s) help.

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

Bug#966964: marked as done (libgpiod: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 08:23:57 +
with message-id 
and subject line Bug#966654: fixed in libgpiod 1.5.1-2
has caused the Debian Bug report #966654,
regarding libgpiod: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # fix lintian useless-autogenerated-doxygen-file
> dh_installdocs -X.md5
> make[1]: Leaving directory '/<>'
>dh_installchangelogs -O--exclude=.la
>dh_installexamples -O--exclude=.la
>dh_installman -O--exclude=.la
>dh_python3 -O--exclude=.la
> I: dh_python3 fs:343: renaming gpiod.so to 
> gpiod.cpython-38-x86_64-linux-gnu.so
>dh_installsystemduser -O--exclude=.la
>dh_perl -O--exclude=.la
>dh_link -O--exclude=.la
>dh_strip_nondeterminism -O--exclude=.la
>dh_compress -O--exclude=.la
>dh_fixperms -O--exclude=.la
>dh_missing -O--exclude=.la
>dh_dwz -a -O--exclude=.la
> dwz: debian/libgpiod2/usr/lib/x86_64-linux-gnu/libgpiodcxx.so.1.1.0: DWARF 
> compression not beneficial - old size 702881 new size 707535
>dh_strip -a -O--exclude=.la
>dh_makeshlibs -a -O--exclude=.la
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libgpiod2/DEBIAN/symbols doesn't match 
> completely debian/libgpiod2.symbols
> --- debian/libgpiod2.symbols (libgpiod2_1.5.1-1_amd64)
> +++ dpkg-gensymbolsUfEYK9 2020-08-02 17:33:34.381100033 +
> @@ -99,6 +99,8 @@
>   gpiod_line_update@Base 1.1
>   gpiod_version_string@Base 1.1
>  libgpiodcxx.so.1 libgpiod2 #MINVER#
> + _ZNSt14_Function_baseD1Ev@Base 1.5.1-1
> + _ZNSt14_Function_baseD2Ev@Base 1.5.1-1
>   (c++)"gpiod::begin(gpiod::chip_iter)@Base" 1.1
>   (c++)"gpiod::begin(gpiod::line_iter)@Base" 1.1
>   (c++)"gpiod::chip::chip(std::__cxx11::basic_string std::char_traits, std::allocator > const&, int)@Base" 1.1
> @@ -200,8 +202,8 @@
>   (c++)"gpiod::line_request::FLAG_OPEN_DRAIN@Base" 1.1
>   (c++)"gpiod::line_request::FLAG_OPEN_SOURCE@Base" 1.1
>   (c++)"gpiod::make_chip_iter()@Base" 1.1
> - (c++)"std::_Function_base::_Base_manager (*)(std::__cxx11::basic_string, 
> std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data 
> const&, std::_Manager_operation)@Base" 1.1
> - (c++)"std::_Rb_tree, 
> std::_Select1st >, std::less, 
> std::allocator > 
> >::_M_erase(std::_Rb_tree_node >*)@Base" 1.1
> +#MISSING: 1.5.1-1# (c++)"std::_Function_base::_Base_manager (*)(std::__cxx11::basic_string, 
> std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data 
> const&, std::_Manager_operation)@Base" 1.1
> +#MISSING: 1.5.1-1# (c++)"std::_Rb_tree, 
> std::_Select1st >, std::less, 
> std::allocator > 
> >::_M_erase(std::_Rb_tree_node >*)@Base" 1.1
>   (c++|arch=amd64 arm64 ppc64el mips64el riscv64)"std::_Rb_tree std::pair, std::_Select1st >, 
> std::less, std::allocator > 
> >::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator const, int> >, int const&)@Base" 1.1
>   (c++|optional)"std::_Rb_tree, 
> std::_Select1st >, std::less, 
> std::allocator > >::_M_get_insert_unique_pos(int 
> const&)@Base" 1.1
>   (c++|arch= armel 
> riscv64)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)1>::_M_destroy()@Base"
>  1.2
> @@ -215,7 +217,7 @@
>   (c++)"std::system_error::system_error(int, std::_V2::error_category const&, 
> std::__cxx11::basic_string, std::allocator 
> > const&)@Base" 1.1
>   (c++)"std::system_error::system_error(std::error_code, char const*)@Base" 
> 1.1
>   (c++|optional|arch-bits=32)"std::vector 
> >::_M_default_append(unsigned int)@Base" 1.5.1
> - (c++|optional|arch-bits=64)"std::vector 
> >::_M_default_append(unsigned long)@Base" 1.1
> +#MISSING: 1.5.1-1# (c++|optional|arch-bits=64)"std::vector std::allocator >::_M_default_append(unsigned long)@Base" 1.1
>   (c++|arch= armel riscv64)"typeinfo for __gnu_cxx::__mutex@Base" 1.2
>   (c++|arch= armel riscv64)"typeinfo for 
> std::_Mutex_base<(__gnu_cxx::_Lock_policy)1>@Base" 1.2
>   (c++|arch= !armel 

Bug#966964: marked as done (libgpiod: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 08:23:57 +
with message-id 
and subject line Bug#966964: fixed in libgpiod 1.5.1-2
has caused the Debian Bug report #966964,
regarding libgpiod: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # fix lintian useless-autogenerated-doxygen-file
> dh_installdocs -X.md5
> make[1]: Leaving directory '/<>'
>dh_installchangelogs -O--exclude=.la
>dh_installexamples -O--exclude=.la
>dh_installman -O--exclude=.la
>dh_python3 -O--exclude=.la
> I: dh_python3 fs:343: renaming gpiod.so to 
> gpiod.cpython-38-x86_64-linux-gnu.so
>dh_installsystemduser -O--exclude=.la
>dh_perl -O--exclude=.la
>dh_link -O--exclude=.la
>dh_strip_nondeterminism -O--exclude=.la
>dh_compress -O--exclude=.la
>dh_fixperms -O--exclude=.la
>dh_missing -O--exclude=.la
>dh_dwz -a -O--exclude=.la
> dwz: debian/libgpiod2/usr/lib/x86_64-linux-gnu/libgpiodcxx.so.1.1.0: DWARF 
> compression not beneficial - old size 702881 new size 707535
>dh_strip -a -O--exclude=.la
>dh_makeshlibs -a -O--exclude=.la
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libgpiod2/DEBIAN/symbols doesn't match 
> completely debian/libgpiod2.symbols
> --- debian/libgpiod2.symbols (libgpiod2_1.5.1-1_amd64)
> +++ dpkg-gensymbolsUfEYK9 2020-08-02 17:33:34.381100033 +
> @@ -99,6 +99,8 @@
>   gpiod_line_update@Base 1.1
>   gpiod_version_string@Base 1.1
>  libgpiodcxx.so.1 libgpiod2 #MINVER#
> + _ZNSt14_Function_baseD1Ev@Base 1.5.1-1
> + _ZNSt14_Function_baseD2Ev@Base 1.5.1-1
>   (c++)"gpiod::begin(gpiod::chip_iter)@Base" 1.1
>   (c++)"gpiod::begin(gpiod::line_iter)@Base" 1.1
>   (c++)"gpiod::chip::chip(std::__cxx11::basic_string std::char_traits, std::allocator > const&, int)@Base" 1.1
> @@ -200,8 +202,8 @@
>   (c++)"gpiod::line_request::FLAG_OPEN_DRAIN@Base" 1.1
>   (c++)"gpiod::line_request::FLAG_OPEN_SOURCE@Base" 1.1
>   (c++)"gpiod::make_chip_iter()@Base" 1.1
> - (c++)"std::_Function_base::_Base_manager (*)(std::__cxx11::basic_string, 
> std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data 
> const&, std::_Manager_operation)@Base" 1.1
> - (c++)"std::_Rb_tree, 
> std::_Select1st >, std::less, 
> std::allocator > 
> >::_M_erase(std::_Rb_tree_node >*)@Base" 1.1
> +#MISSING: 1.5.1-1# (c++)"std::_Function_base::_Base_manager (*)(std::__cxx11::basic_string, 
> std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data 
> const&, std::_Manager_operation)@Base" 1.1
> +#MISSING: 1.5.1-1# (c++)"std::_Rb_tree, 
> std::_Select1st >, std::less, 
> std::allocator > 
> >::_M_erase(std::_Rb_tree_node >*)@Base" 1.1
>   (c++|arch=amd64 arm64 ppc64el mips64el riscv64)"std::_Rb_tree std::pair, std::_Select1st >, 
> std::less, std::allocator > 
> >::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator const, int> >, int const&)@Base" 1.1
>   (c++|optional)"std::_Rb_tree, 
> std::_Select1st >, std::less, 
> std::allocator > >::_M_get_insert_unique_pos(int 
> const&)@Base" 1.1
>   (c++|arch= armel 
> riscv64)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)1>::_M_destroy()@Base"
>  1.2
> @@ -215,7 +217,7 @@
>   (c++)"std::system_error::system_error(int, std::_V2::error_category const&, 
> std::__cxx11::basic_string, std::allocator 
> > const&)@Base" 1.1
>   (c++)"std::system_error::system_error(std::error_code, char const*)@Base" 
> 1.1
>   (c++|optional|arch-bits=32)"std::vector 
> >::_M_default_append(unsigned int)@Base" 1.5.1
> - (c++|optional|arch-bits=64)"std::vector 
> >::_M_default_append(unsigned long)@Base" 1.1
> +#MISSING: 1.5.1-1# (c++|optional|arch-bits=64)"std::vector std::allocator >::_M_default_append(unsigned long)@Base" 1.1
>   (c++|arch= armel riscv64)"typeinfo for __gnu_cxx::__mutex@Base" 1.2
>   (c++|arch= armel riscv64)"typeinfo for 
> std::_Mutex_base<(__gnu_cxx::_Lock_policy)1>@Base" 1.2
>   (c++|arch= !armel 

Bug#966654: marked as done (libgpiod: symbol mismatches with gcc-10/O3 optimization)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 08:23:57 +
with message-id 
and subject line Bug#966654: fixed in libgpiod 1.5.1-2
has caused the Debian Bug report #966654,
regarding libgpiod: symbol mismatches with gcc-10/O3 optimization
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.)


-- 
966654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgpiod
Version: 1.5.1-1
Severity: serious
tags: patch

Hello, looks like some symbols are disappearing when built with -O3 
optimization level, and some other
changed in armhf and ppc64el (probably due to gcc-10)

the following patch seems to be enough to make everybody happy, by making some 
symbols optional.
thanks for considering it

G.


--- libgpiod-1.5.1/debian/changelog 2020-07-01 05:27:41.0 +0200
+++ libgpiod-1.5.1/debian/changelog 2020-07-31 20:08:33.0 +0200
@@ -1,3 +1,9 @@
+libgpiod (1.5.1-1.1) unstable; urgency=medium
+
+  * Refresh symbols (Closes: #-1)
+
+ -- Gianfranco Costamagna   Fri, 31 Jul 2020 
20:08:33 +0200
+
 libgpiod (1.5.1-1) unstable; urgency=medium
 
   * Import new upstream release
diff -Nru libgpiod-1.5.1/debian/libgpiod2.symbols 
libgpiod-1.5.1/debian/libgpiod2.symbols
--- libgpiod-1.5.1/debian/libgpiod2.symbols 2020-07-01 05:27:19.0 
+0200
+++ libgpiod-1.5.1/debian/libgpiod2.symbols 2020-07-31 20:08:33.0 
+0200
@@ -99,6 +99,8 @@
  gpiod_line_update@Base 1.1
  gpiod_version_string@Base 1.1
 libgpiodcxx.so.1 libgpiod2 #MINVER#
+ (c++|optional)"std::_Function_base::~_Function_base()@Base" 1.5.1
+ (c++|optional)"std::_Function_base::~_Function_base()@Base" 1.5.1
  (c++)"gpiod::line_request::FLAG_ACTIVE_LOW@Base" 1.1
  (c++)"gpiod::line_request::FLAG_OPEN_DRAIN@Base" 1.1
  (c++)"gpiod::line_request::FLAG_OPEN_SOURCE@Base" 1.1
@@ -209,7 +211,7 @@
  (c++)"std::system_error::system_error(int, std::_V2::error_category const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.1
  (c++)"std::system_error::system_error(std::error_code, char const*)@Base" 1.1
  (c++)"std::system_error::system_error(int, std::_V2::error_category const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.1
- (c++)"std::_Function_base::_Base_manager, 
std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data 
const&, std::_Manager_operation)@Base" 1.1
+ (c++|optional)"std::_Function_base::_Base_manager, 
std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data 
const&, std::_Manager_operation)@Base" 1.1
  (c++|arch= !armel !riscv64)"std::_Sp_counted_ptr::_M_dispose()@Base" 1.1
  (c++|arch= !armel 
!riscv64)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_destroy()@Base" 
1.1
  (c++)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release()@Base" 
1.4.1
@@ -219,8 +221,8 @@
  (c++|optional|arch-bits=32)"std::vector 
>::_M_default_append(unsigned int)@Base" 1.5.1
  (c++|optional)"void std::__cxx11::basic_string, 
std::allocator >::_M_construct(char const*, char const*, 
std::forward_iterator_tag)@Base" 1.1
  (c++|optional)"std::_Rb_tree, 
std::_Select1st >, std::less, 
std::allocator > >::_M_get_insert_unique_pos(int 
const&)@Base" 1.1
- (c++|arch=amd64 arm64 ppc64el mips64el riscv64)"std::_Rb_tree, std::_Select1st >, 
std::less, std::allocator > 
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator >, int const&)@Base" 1.1
- (c++)"std::_Rb_tree, 
std::_Select1st >, std::less, 
std::allocator > 
>::_M_erase(std::_Rb_tree_node >*)@Base" 1.1
+ (c++|optional|arch=amd64 arm64 ppc64el mips64el riscv64)"std::_Rb_tree, std::_Select1st >, 
std::less, std::allocator > 
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator >, int const&)@Base" 1.1
+ (c++|optional)"std::_Rb_tree, 
std::_Select1st >, std::less, 
std::allocator > 
>::_M_erase(std::_Rb_tree_node >*)@Base" 1.1
  (c++|arch= !armel !riscv64)"typeinfo for 
std::_Mutex_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.1
  (c++|arch= !armel !riscv64)"typeinfo for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.1
  (c++|arch= !armel !riscv64)"typeinfo name for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.4
@@ -235,6 +237,6 @@
  (c++|arch= armel riscv64)"typeinfo name for __gnu_cxx::__mutex@Base" 1.2
  (c++|arch= armel riscv64)"typeinfo name for 
std::_Mutex_base<(__gnu_cxx::_Lock_policy)1>@Base" 1.2
  (c++|arch= armel riscv64)"typeinfo name for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)1>@Base" 1.2
- (c++|arch= i386 armel mipsel armhf s390x)"std::map, 
std::allocator > 
>::map(std::initializer_list >, 

Bug#966654: marked as done (libgpiod: symbol mismatches with gcc-10/O3 optimization)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 08:23:57 +
with message-id 
and subject line Bug#966964: fixed in libgpiod 1.5.1-2
has caused the Debian Bug report #966964,
regarding libgpiod: symbol mismatches with gcc-10/O3 optimization
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.)


-- 
966964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgpiod
Version: 1.5.1-1
Severity: serious
tags: patch

Hello, looks like some symbols are disappearing when built with -O3 
optimization level, and some other
changed in armhf and ppc64el (probably due to gcc-10)

the following patch seems to be enough to make everybody happy, by making some 
symbols optional.
thanks for considering it

G.


--- libgpiod-1.5.1/debian/changelog 2020-07-01 05:27:41.0 +0200
+++ libgpiod-1.5.1/debian/changelog 2020-07-31 20:08:33.0 +0200
@@ -1,3 +1,9 @@
+libgpiod (1.5.1-1.1) unstable; urgency=medium
+
+  * Refresh symbols (Closes: #-1)
+
+ -- Gianfranco Costamagna   Fri, 31 Jul 2020 
20:08:33 +0200
+
 libgpiod (1.5.1-1) unstable; urgency=medium
 
   * Import new upstream release
diff -Nru libgpiod-1.5.1/debian/libgpiod2.symbols 
libgpiod-1.5.1/debian/libgpiod2.symbols
--- libgpiod-1.5.1/debian/libgpiod2.symbols 2020-07-01 05:27:19.0 
+0200
+++ libgpiod-1.5.1/debian/libgpiod2.symbols 2020-07-31 20:08:33.0 
+0200
@@ -99,6 +99,8 @@
  gpiod_line_update@Base 1.1
  gpiod_version_string@Base 1.1
 libgpiodcxx.so.1 libgpiod2 #MINVER#
+ (c++|optional)"std::_Function_base::~_Function_base()@Base" 1.5.1
+ (c++|optional)"std::_Function_base::~_Function_base()@Base" 1.5.1
  (c++)"gpiod::line_request::FLAG_ACTIVE_LOW@Base" 1.1
  (c++)"gpiod::line_request::FLAG_OPEN_DRAIN@Base" 1.1
  (c++)"gpiod::line_request::FLAG_OPEN_SOURCE@Base" 1.1
@@ -209,7 +211,7 @@
  (c++)"std::system_error::system_error(int, std::_V2::error_category const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.1
  (c++)"std::system_error::system_error(std::error_code, char const*)@Base" 1.1
  (c++)"std::system_error::system_error(int, std::_V2::error_category const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.1
- (c++)"std::_Function_base::_Base_manager, 
std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data 
const&, std::_Manager_operation)@Base" 1.1
+ (c++|optional)"std::_Function_base::_Base_manager, 
std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data 
const&, std::_Manager_operation)@Base" 1.1
  (c++|arch= !armel !riscv64)"std::_Sp_counted_ptr::_M_dispose()@Base" 1.1
  (c++|arch= !armel 
!riscv64)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_destroy()@Base" 
1.1
  (c++)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release()@Base" 
1.4.1
@@ -219,8 +221,8 @@
  (c++|optional|arch-bits=32)"std::vector 
>::_M_default_append(unsigned int)@Base" 1.5.1
  (c++|optional)"void std::__cxx11::basic_string, 
std::allocator >::_M_construct(char const*, char const*, 
std::forward_iterator_tag)@Base" 1.1
  (c++|optional)"std::_Rb_tree, 
std::_Select1st >, std::less, 
std::allocator > >::_M_get_insert_unique_pos(int 
const&)@Base" 1.1
- (c++|arch=amd64 arm64 ppc64el mips64el riscv64)"std::_Rb_tree, std::_Select1st >, 
std::less, std::allocator > 
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator >, int const&)@Base" 1.1
- (c++)"std::_Rb_tree, 
std::_Select1st >, std::less, 
std::allocator > 
>::_M_erase(std::_Rb_tree_node >*)@Base" 1.1
+ (c++|optional|arch=amd64 arm64 ppc64el mips64el riscv64)"std::_Rb_tree, std::_Select1st >, 
std::less, std::allocator > 
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator >, int const&)@Base" 1.1
+ (c++|optional)"std::_Rb_tree, 
std::_Select1st >, std::less, 
std::allocator > 
>::_M_erase(std::_Rb_tree_node >*)@Base" 1.1
  (c++|arch= !armel !riscv64)"typeinfo for 
std::_Mutex_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.1
  (c++|arch= !armel !riscv64)"typeinfo for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.1
  (c++|arch= !armel !riscv64)"typeinfo name for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.4
@@ -235,6 +237,6 @@
  (c++|arch= armel riscv64)"typeinfo name for __gnu_cxx::__mutex@Base" 1.2
  (c++|arch= armel riscv64)"typeinfo name for 
std::_Mutex_base<(__gnu_cxx::_Lock_policy)1>@Base" 1.2
  (c++|arch= armel riscv64)"typeinfo name for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)1>@Base" 1.2
- (c++|arch= i386 armel mipsel armhf s390x)"std::map, 
std::allocator > 
>::map(std::initializer_list >, 

Processed: bug 968438 is forwarded to https://bugs.kde.org/show_bug.cgi?id=425354

[Debian Bug Tracking System]

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

> forwarded 968438 https://bugs.kde.org/show_bug.cgi?id=425354
Bug #968438 [okular] okular: Annotation menu displayed incorrectly
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=425354'.
> thanks
Stopping processing here.

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

Bug#962762: Should monotone-viz be removed from unstable?

[Stéphane Glondu]

reassign 962762 ftp.debian.org
retitle 962762 RM: monotone-viz -- RoQA; obsolete, unmaintained
thanks

Adrian Bunk  wrote:
> Neither monotone-viz nor monotone are in the current stable,
> and monotone was already removed from unstable.
> 
> Should monotone-viz also be removed from unstable?

Yes, it is an unnecessary burden: it does not build, depends on
deprecated libraries, is probably useless without monotone, has low popcon.

Hence, I am turning this into a RM bug.


Cheers,

-- 
Stéphane

Bug#955066: marked as done (mako: FTBFS with Sphinx 2.4: Theme error: no theme named 'zzzeeksphinx' found (missing theme.conf?))

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 16:24:44 +0900
with message-id <20200816162444.8f46dd0de6759dc067609...@clear-code.com>
and subject line mako: FTBFS with Sphinx 2.4: Theme error: no theme named 
'zzzeeksphinx' found (missing theme.conf?)
has caused the Debian Bug report #955066,
regarding mako: FTBFS with Sphinx 2.4: Theme error: no theme named 
'zzzeeksphinx' found (missing theme.conf?)
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.)


-- 
955066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mako
Version: 1.1.2+ds1-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

mako fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package mako
> dpkg-buildpackage: info: source version 1.1.2+ds1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Piotr Ożarowski 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-*
> rm -rf build
> find . -name '*\.py[co]' -delete
> rm -rf .pytest_cache
> rm -rf Mako.egg-info
> dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building mako using existing ./mako_1.1.2+ds1.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building mako in mako_1.1.2+ds1-1.debian.tar.xz
> dpkg-source: info: building mako in mako_1.1.2+ds1-1.dsc
>  debian/rules binary
> python3.7 setup.py build_scripts  --executable=/usr/bin/python3
> running build_scripts
> python3.7 setup.py install  \
>   --root /<>/debian/python3-mako --prefix=/usr
> running install
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/mako
> copying mako/cache.py -> build/lib/mako
> copying mako/cmd.py -> build/lib/mako
> copying mako/parsetree.py -> build/lib/mako
> copying mako/__init__.py -> build/lib/mako
> copying mako/ast.py -> build/lib/mako
> copying mako/lookup.py -> build/lib/mako
> copying mako/runtime.py -> build/lib/mako
> copying mako/lexer.py -> build/lib/mako
> copying mako/compat.py -> build/lib/mako
> copying mako/util.py -> build/lib/mako
> copying mako/pygen.py -> build/lib/mako
> copying mako/template.py -> build/lib/mako
> copying mako/exceptions.py -> build/lib/mako
> copying mako/pyparser.py -> build/lib/mako
> copying mako/_ast_util.py -> build/lib/mako
> copying mako/filters.py -> build/lib/mako
> copying mako/codegen.py -> build/lib/mako
> creating build/lib/mako/ext
> copying mako/ext/beaker_cache.py -> build/lib/mako/ext
> copying mako/ext/__init__.py -> build/lib/mako/ext
> copying mako/ext/linguaplugin.py -> build/lib/mako/ext
> copying mako/ext/autohandler.py -> build/lib/mako/ext
> copying mako/ext/babelplugin.py -> build/lib/mako/ext
> copying mako/ext/pygmentplugin.py -> build/lib/mako/ext
> copying mako/ext/preprocessors.py -> build/lib/mako/ext
> copying mako/ext/turbogears.py -> build/lib/mako/ext
> copying mako/ext/extract.py -> build/lib/mako/ext
> running install_lib
> creating /<>/debian/python3-mako
> creating /<>/debian/python3-mako/usr
> creating /<>/debian/python3-mako/usr/lib
> creating /<>/debian/python3-mako/usr/lib/python3.7
> creating /<>/debian/python3-mako/usr/lib/python3.7/site-packages
> creating 
> /<>/debian/python3-mako/usr/lib/python3.7/site-packages/mako
> copying build/lib/mako/cache.py -> 
> /<>/debian/python3-mako/usr/lib/python3.7/site-packages/mako
> copying build/lib/mako/cmd.py -> 
> /<>/debian/python3-mako/usr/lib/python3.7/site-packages/mako
> copying build/lib/mako/parsetree.py -> 
> /<>/debian/python3-mako/usr/lib/python3.7/site-packages/mako
> copying build/lib/mako/__init__.py -> 
> /<>/debian/python3-mako/usr/lib/python3.7/site-packages/mako
> copying build/lib/mako/ast.py -> 
> /<>/debian/python3-mako/usr/lib/python3.7/site-packages/mako
> copying build/lib/mako/lookup.py -> 
> /<>/debian/python3-mako/usr/lib/python3.7/site-packages/mako
> copying build/lib/mako/runtime.py -> 
> /<>/debian/python3-mako/usr/lib/python3.7/site-packages/mako
> copying build/lib/mako/lexer.py -> 
> /<>/debian/python3-mako/usr/lib/python3.7/site-packages/mako
> copying build/lib/mako/compat.py -> 
> /<>/debian/python3-mako/usr/lib/python3.7/site-packages/mako
> copying 

Processed: Re: Should monotone-viz be removed from unstable?

[Debian Bug Tracking System]

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

> reassign 962762 ftp.debian.org
Bug #962762 [monotone-viz] Should monotone-viz be removed from unstable?
Bug reassigned from package 'monotone-viz' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #962762 to the same values 
previously set
Ignoring request to alter fixed versions of bug #962762 to the same values 
previously set
> retitle 962762 RM: monotone-viz -- RoQA; obsolete, unmaintained
Bug #962762 [ftp.debian.org] Should monotone-viz be removed from unstable?
Changed Bug title to 'RM: monotone-viz -- RoQA; obsolete, unmaintained' from 
'Should monotone-viz be removed from unstable?'.
> thanks
Stopping processing here.

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

Bug#944601: marked as done (FTBFS with OCaml 4.08.1 (safe strings))

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 07:33:23 +
with message-id 
and subject line Bug#944601: fixed in ocamlviz 1.01-4
has caused the Debian Bug report #944601,
regarding FTBFS with OCaml 4.08.1 (safe strings)
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.)


-- 
944601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ocamlviz
Version: 1.01-3
Severity: serious

Dear Maintainer,

ocamlviz FTBFS with OCaml 4.08.1 because -safe-string is now the
default:

  https://buildd.debian.org/status/package.php?p=ocamlviz


Cheers,

-- 
Stéphane

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: ocamlviz
Source-Version: 1.01-4
Done: =?utf-8?q?St=C3=A9phane_Glondu?= 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated ocamlviz package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Aug 2020 09:12:38 +0200
Source: ocamlviz
Architecture: source
Version: 1.01-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 944601
Changes:
 ocamlviz (1.01-4) unstable; urgency=medium
 .
   * Team upload
   * Compile with -unsafe-string for now (Closes: #944601)
   * Bump debhelper compat level to 13
   * Bump Standards-Version to 4.5.0
   * Add Rules-Requires-Root: no
   * libocamlviz-ocaml-doc: add Multi-Arch: foreign
Checksums-Sha1:
 da1833dfdf1771e8eb887fe84b52259d90122793 2018 ocamlviz_1.01-4.dsc
 191132936195349039bd72135aa73ee8ddecb412 4096 ocamlviz_1.01-4.debian.tar.xz
Checksums-Sha256:
 2870b9d7226d0af4e2d04a416263e8ebe3b83559434c27c6d58077bbcc9bde1d 2018 
ocamlviz_1.01-4.dsc
 92c1c8b272b0fcc059baef7e5e9ed128978b7911573812bdcb1ba804cdf964c8 4096 
ocamlviz_1.01-4.debian.tar.xz
Files:
 50ac8bca65a7a4a1b399f00906398e8e 2018 ocaml optional ocamlviz_1.01-4.dsc
 9e9d68d622cd791c3e89770525f2b994 4096 ocaml optional 
ocamlviz_1.01-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl843MISHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCB/lkH/R4rW4AEAqNlOq13FI35NwOthoh2VFOg
oftlqctBk+cLKo9ejtgtdN87e5/IJEOqCF2jzc5SUFMU4KiJVs/wayqObVa9SQS1
M7G/bR7QUhECmUW5oNmwprDKn1ZlrUs5UiAT93jt18gUqzngdNQCvbun2YM1o+Cq
kPEqEFbopUd4LWBCYffRoGw7SqtlEytduBoQyB9dj6YvVX9+T2XACzCDBHlnogpl
+OSYRyaZxfut44M5KJ7Wv5RLiOCqlMmNDbcRTSdir7mTcjVa2OD2yQ3YfIHoBZgu
m2XLYDeTDhzNppHKP1kY8e6MLO7BEG3HT+Dp9cT/an+ESt2yMhhzhzw=
=AZFO
-END PGP SIGNATURE End Message ---

Bug#959624: marked as done (ruby-faraday: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `split' for nil:NilClass)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 16:26:24 +0900
with message-id 
and subject line Re: ruby-faraday: FTBFS: ERROR: Test "ruby2.7" failed:
has caused the Debian Bug report #959624,
regarding ruby-faraday: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: 
undefined method `split' for nil:NilClass
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.)


-- 
959624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-faraday
Version: 0.15.4-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> NoMethodError: undefined method `split' for nil:NilClass
> /usr/lib/ruby/vendor_ruby/rack/mock.rb:236:in `identify_cookie_attributes'
> /usr/lib/ruby/vendor_ruby/rack/mock.rb:220:in `block in 
> parse_cookies_from_header'
> /usr/lib/ruby/vendor_ruby/rack/mock.rb:218:in `each'
> /usr/lib/ruby/vendor_ruby/rack/mock.rb:218:in `parse_cookies_from_header'
> /usr/lib/ruby/vendor_ruby/rack/mock.rb:169:in `initialize'
> /usr/lib/ruby/vendor_ruby/rack/mock_session.rb:32:in `new'
> /usr/lib/ruby/vendor_ruby/rack/mock_session.rb:32:in `request'
> /usr/lib/ruby/vendor_ruby/rack/test.rb:249:in `process_request'
> /usr/lib/ruby/vendor_ruby/rack/test.rb:125:in `request'
> 
> /<>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/adapter/rack.rb:54:in
>  `execute_request'
> 
> /<>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/adapter/rack.rb:46:in
>  `call'
> 
> /<>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/response.rb:8:in
>  `call'
> 
> /<>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/request/url_encoded.rb:15:in
>  `call'
> 
> /<>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/request/multipart.rb:15:in
>  `call'
> 
> /<>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/rack_builder.rb:143:in
>  `build_response'
> 
> /<>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/connection.rb:387:in
>  `run_request'
> 
> /<>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/connection.rb:138:in
>  `get'
> /usr/lib/ruby/2.7.0/forwardable.rb:235:in `get'
> /<>/test/adapters/integration.rb:98:in 
> `test_GET_handles_headers_with_multiple_values'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun'
> 
> 265 runs, 414 assertions, 0 failures, 1 errors, 6 skips
> 
> You have skipped tests. Run with --verbose for details.
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/ruby-faraday_0.15.4-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
 NoMethodError:
 undefined method `split' for nil:NilClass
Message-Id: 

Bug#961444: Fix for grcompiler FTBFS on architectures where char is unsigned

[Tim Eves]

I've reworked the assert to be explicit about checking the integer range
could fit in a signed 8 bit value in commit
https://github.com/silnrsi/grcompiler/commit/a60a04691c42f3f99543c83f9911c84e44a268fe

Hopefully this will fix the issue and it isn't really managing to generate
an offset outside the -128 <->127 range.
-- 
Tim Eves
Writing Systems Technology - SIL International

Processed: Bug#944601 marked as pending in ocamlviz

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #944601 [src:ocamlviz] FTBFS with OCaml 4.08.1 (safe strings)
Added tag(s) pending.

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

Bug#944601: marked as pending in ocamlviz

[Stéphane Glondu]

Control: tag -1 pending

Hello,

Bug #944601 in ocamlviz 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/ocaml-team/ocamlviz/-/commit/53e0b684bd10de0e6ace951fcd9a0d162bd4d46f


Compile with -unsafe-string for now (Closes: #944601)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/944601

Bug#961445: Fixes in upstream repo commits.

[Tim Eves]

I believe the upstream commits 19c55e0

and 89fa0b3

in the upstream Github repo should fix this bug. I have tested this on on
32bit emulated MIPS system running Debian 10 and it
passes all the regression tests.
-- 
Tim Eves
Writing Systems Technology - SIL International

Bug#957496: Prevent migration of ocaml-{integers,ctypes} to testing

[Stéphane Glondu]

Hello,

These bugs are still on topic and prevent ocaml-{integers,ctypes} from
migrating to testing. Could you please fix them? Or have the faulty
packages removed from testing.


Cheers,

-- 
Stéphane

Bug#964880: marked as done (npm: test failures in ppc64el and s390x)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 06:03:24 +
with message-id 
and subject line Bug#964854: fixed in npm 6.14.7+ds-2
has caused the Debian Bug report #964854,
regarding npm: test failures in ppc64el and s390x
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.)


-- 
964854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: npm
Version: 6.14.6+ds-1
Severity: serious

Hello, looks like one test is failing on ppc64el and s390x.
Could you please have a look?

this on s390x
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/n/npm/20200711_092356_eb5fd@/log.gz
# Subtest: test/tap/legacy-platform-all.js
# Subtest: setup
1..0
ok 1 - setup # time=2.926ms

# Subtest: platform-all
not ok 1 - no error messages
  ---
  found: >
npm ERR! code EBADPLATFORM
  
npm ERR! notsup Unsupported platform for 
npm-test-platform-all@9.9.9-9: wanted

{"os":"darwin,linux,win32,solaris,haiku,sunos,freebsd,openbsd,netbsd","arch":"arm,arm64,mips,ia32,x64,sparc"}
(current: {"os":"linux","arch":"s390x"})
  
npm ERR! notsup Valid OS:   
darwin,linux,win32,solaris,haiku,sunos,freebsd,openbsd,netbsd
  
npm ERR! notsup Valid Arch:  arm,arm64,mips,ia32,x64,sparc
  
npm ERR! notsup Actual OS:   linux
  
npm ERR! notsup Actual Arch: s390x
  
  
npm ERR! A complete log of this run can be found in:
  
npm ERR!

/tmp/autopkgtest.TwzxSV/autopkgtest_tmp/smokeh0DzIy/test/npm_cache_legacy-platform-all/_logs/2020-07-11T09_18_58_795Z-debug.log
  wanted: ''
  compare: ===
  at:
line: 55
column: 7
file: test/tap/legacy-platform-all.js
type: global
function: installCheckAndTest
  stack: |
installCheckAndTest (test/tap/legacy-platform-all.js:55:7)
f (/usr/lib/nodejs/once/once.js:25:25)
ChildProcess. (test/common-tap.js:175:5)
  source: |
t.is(stderr, '', 'no error messages')
  ...

not ok 2 - install went ok
  ---
  found: 1
  wanted: 0
  compare: ===
  at:
line: 56
column: 7
file: test/tap/legacy-platform-all.js
type: global
function: installCheckAndTest
  stack: |
installCheckAndTest (test/tap/legacy-platform-all.js:56:7)
f (/usr/lib/nodejs/once/once.js:25:25)
ChildProcess. (test/common-tap.js:175:5)
  source: |
t.is(code, 0, 'install went ok')
  ...

1..2
# failed 2 of 2 tests
not ok 2 - platform-all # time=767.548ms

# Subtest: cleanup
1..0
ok 3 - cleanup # time=1.651ms

1..3
# failed 1 of 3 tests
# time=782.166ms
not ok 103 - test/tap/legacy-platform-all.js # time=1350.563ms


and this on ppc64el
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/n/npm/20200711_093200_7007f@/log.gz
# Subtest: test/tap/legacy-platform-all.js
# Subtest: setup
1..0
ok 1 - setup # time=4.916ms

# Subtest: platform-all
not ok 1 - no error messages
  ---
  found: >
npm ERR! code EBADPLATFORM
  
npm ERR! notsup Unsupported platform for 
npm-test-platform-all@9.9.9-9: wanted

{"os":"darwin,linux,win32,solaris,haiku,sunos,freebsd,openbsd,netbsd","arch":"arm,arm64,mips,ia32,x64,sparc"}
(current: {"os":"linux","arch":"ppc64"})
  
npm ERR! notsup Valid OS:   
darwin,linux,win32,solaris,haiku,sunos,freebsd,openbsd,netbsd
  
npm ERR! notsup Valid Arch:  arm,arm64,mips,ia32,x64,sparc
  
npm ERR! notsup Actual OS:   linux
  
npm ERR! notsup Actual Arch: ppc64
  
  
npm ERR! A complete log of this run can be found in:
  
npm ERR!

/tmp/autopkgtest.RvsIrP/autopkgtest_tmp/smokevhVLkX/test/npm_cache_legacy-platform-all/_logs/2020-07-11T09_24_22_560Z-debug.log
  wanted: ''
  compare: ===
  at:
line: 55
column: 7
  

Bug#964854: marked as done (npm: autopkgtests failures on s390x)

[Debian Bug Tracking System]

Your message dated Sun, 16 Aug 2020 06:03:24 +
with message-id 
and subject line Bug#964854: fixed in npm 6.14.7+ds-2
has caused the Debian Bug report #964854,
regarding npm: autopkgtests failures on s390x
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.)


-- 
964854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: npm
Version: 6.14.5+ds-1
Severity: serious

Hello, looks like npm is failing again its autopkgtests...

On armhf there is a timeout that I "fixed" with: 
https://github.com/npm/cli/pull/1454

on ppc64el there is another failure:
https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/npm/6017343/log.gz

and I also spot a s390x failure on Ubuntu:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/n/npm/20200505_235736_15e60@/log.gz

can you please have another look?
(in the meanwhile I'm marking that test as flaky in Ubuntu)

thanks!

Gianfranco
--- End Message ---
--- Begin Message ---
Source: npm
Source-Version: 6.14.7+ds-2
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated npm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Aug 2020 07:39:45 +0200
Source: npm
Architecture: source
Version: 6.14.7+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 964854
Changes:
 npm (6.14.7+ds-2) unstable; urgency=medium
 .
   * Add ppc64 in supported platforms list (Closes: #964854)
Checksums-Sha1: 
 c77d18376ee8f03064300af20237d178f27c864c 6736 npm_6.14.7+ds-2.dsc
 1f7f61b38b5dff999b9ad63787f277e4260465ed 42900 npm_6.14.7+ds-2.debian.tar.xz
Checksums-Sha256: 
 05ef1e6a2789382511e7600db38a5b48efddeae509d5888e609a472a855e31db 6736 
npm_6.14.7+ds-2.dsc
 aed159ba0baf2861ea1721dc46135f1dec6b703cc75a99675a66488dae17fea6 42900 
npm_6.14.7+ds-2.debian.tar.xz
Files: 
 283606eef070ed4a1990ff7c603cc4f8 6736 javascript optional npm_6.14.7+ds-2.dsc
 0428d743db5479c1ce2771a41d5785d4 42900 javascript optional 
npm_6.14.7+ds-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl84x+kACgkQ9tdMp8mZ
7ulgTQ//Q9b6nHsSkDMlU4NkhoyjXpxuqB+waMJs5+onE+vy1WBa9SP7ZTyOs+dr
uza3s7MgQfVVf0QXUMSZvYc0inh6V23PN4AwluRrBNsUQt75vlRiAWq/whsZiLtZ
tpa5BwJMQpxKdIWBEARK+jFs2cdm0GAOurhYXmiWxrZgaUVUx+iYjJngLI0uQIQj
LznuVDXUiMyKsHgjILNkm+qtqUZ8xVzQDzn3x2dS6UQmDz5ibWLmaiguTBNVewqt
Kr8c0RUD9LXzdb7i69I/rTt6yJQh1AwGOV9nplRKVt8YFxWLOhDWyjyfxrXgpsBe
+0M1BAYixmDb0uonhaBRPLbb1oB/sGEIp/v6eAjGM/zFl2xHY6U7C23rG41JXAlq
QkQ778CwkYWzhlNOqRF+SAoDYzWTN4UwacQJZmy4TrWFDOA7LclJRxU24oitHcIW
aD9uMuu3t7WOJv3Di9/CSdJs2fkg3M354p2fV0aZC2uDJn6ynXXU6Y0dAkcj4t2B
pXO6QEC6YC4UWdJGKm6HJP4sUJyTFtEgPmvtaG0KPBU1Z/otk7iwg39kyia8ycX7
pOHPj9r/o0Rn0tT33Jk7k5FV0H8aCN6qH2TfSJ+6ZwUIB9Q9sHVVmT1FhY8O4yEH
zdQyD9ILUNMIzk67HZhnJ0fozi1XT8YhLSCsbu866aE80onDzIQ=
=BlH9
-END PGP SIGNATURE End Message ---