Your message dated Thu, 17 Sep 2020 05:04:19 +
with message-id
and subject line Bug#969396: fixed in sleef 3.5.0-1
has caused the Debian Bug report #969396,
regarding sleef FTBFS on arm64 with gcc-10, sve code requires __sizeless_struct
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> severity 969850 normal
Bug #969850 [src:netstress] netstress: autopkgtest should be marked superficial
Severity set to 'normal' from 'serious'
> severity 969835 normal
Bug #969835 [src:iwatch] iwatch: autopkgtest should be marked superficial
Thank you Samuel.
In my personal opinion, this bug is not serious. So, I will set it as
"normal" soon.
I will wait for forensics-samples (in NEW) to fix this bug.
Regards,
Eriberto
This issue still occurs as of 5.8.0-1. The work around to make it compile
is to symlink the missing folder from kernel source:
`sudo ln -s /usr/src/linux-headers-5.8.0-1-common/include/linux
/lib/modules/5.8.0-1-amd64/build/include/linux`
Processing commands for cont...@bugs.debian.org:
> severity 970473 serious
Bug #970473 [libgs9-common] libgs9-common: Fails to install
Severity set to 'serious' from 'grave'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
970473:
Package: libgs9-common
Version: 9.53.1~dfsg-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: eribe...@debian.org
Dear Maintainer,
When trying to install libgs9-common in Sid, I got the following message:
The following packages have unmet dependencies:
libgs9-common :
Your message dated Wed, 16 Sep 2020 21:21:20 +
with message-id
and subject line Bug#969867: fixed in sane-frontends 1.0.14-16
has caused the Debian Bug report #969867,
regarding sane-frontends: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the
Your message dated Wed, 16 Sep 2020 21:20:31 +
with message-id
and subject line Bug#969843: fixed in makebootfat 1.4-8
has caused the Debian Bug report #969843,
regarding makebootfat: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem
Le mercredi 16 septembre 2020 à 22:08:24+0200, Pierre-Elliott Bécue a écrit :
> Le vendredi 11 septembre 2020 à 11:12:25+0200, Iñaki Malerba a écrit :
> > Hi Pebs,
> >
> > Thanks for checking this.
> >
> > On Sat, 5 Sep 2020 23:23:30 +0200 Pierre-Elliott =?utf-8?B?QsOpY3Vl?=
> > wrote:>
> > >
Le samedi 25 juillet 2020 à 22:28:08+0200, Paul Gevers a écrit :
> Source: lxc
> Version: 1:3.1.0+really3.0.4-3
> Severity: serious
> Control: close -1 1:4.0.2-1
> Tags: sid bullseye
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
> Control: block -1 by 961584
>
> Dear
Your message dated Wed, 16 Sep 2020 20:34:02 +
with message-id
and subject line Bug#969830: fixed in git-review 1.28.0-1
has caused the Debian Bug report #969830,
regarding git-review: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem
Le vendredi 11 septembre 2020 à 11:12:25+0200, Iñaki Malerba a écrit :
> Hi Pebs,
>
> Thanks for checking this.
>
> On Sat, 5 Sep 2020 23:23:30 +0200 Pierre-Elliott =?utf-8?B?QsOpY3Vl?=
> wrote:>
> > LXC's devs told me that 4.0.4 should solve it. I'm uploading this
> > release now. Please don't
Processing control commands:
> severity -1 grave
Bug #895851 [gkrellweather] sh: 1: /usr/local/share/gkrellm/GrabWeather: not
found
Severity set to 'grave' from 'important'
--
895851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895851
Debian Bug Tracking System
Contact
Source: golang-github-biogo-graph
Version: 0.0~git20150317.057c198-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package
golang-github-biogo-graph, great. However,
Processing control commands:
> tag -1 pending
Bug #969830 [src:git-review] git-review: autopkgtest should be marked
superficial
Added tag(s) pending.
--
969830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: golang-github-biogo-biogo
Version: 1.0.2-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package
golang-github-biogo-biogo, great. However, it fails on
Control: tag -1 pending
Hello,
Bug #969830 in git-review 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:
Source: singularity-container
Version: 3.5.2+ds1-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerabilities were published for singularity-container.
CVE-2020-25039[0]:
| Sylabs Singularity
Hi,
On Tue, 8 Sep 2020 11:26:24 +0100 Sudip Mukherjee
wrote:
> The test done in the autopkgtest of 'pylast' does not provide
> significant test coverage and it should be marked with "Restrictions:
> superficial".
The irony of this bug report is that the coverage is enough to block the
migration
Source: rust-log
Version: 0.4.11-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of rust-log the autopkgtest of rust-log fails in
testing when that autopkgtest is run with the binary
Source: sweed
Version: 3.2.1+dfsg-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package sweed, great. However,
it fails on arm64. Currently this failure is
Your message dated Wed, 16 Sep 2020 17:49:27 +
with message-id
and subject line Bug#957567: fixed in mrs 6.0.5+dfsg-8
has caused the Debian Bug report #957567,
regarding mrs: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 16 Sep 2020 17:19:25 +
with message-id
and subject line Bug#939962: fixed in sks 1.1.6+git20200620.9e9d504-1
has caused the Debian Bug report #939962,
regarding FTBFS with OCaml 4.08.0 (safe strings)
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> severity 969171 normal
Bug #969171 [akonadi-server] akonadi-server expects akonadi-backend-mysql
allthough any sql backend should work
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need
severity 969171 normal
thanks
Dear Eric.
Akonadi will use whatever database is set in the configuration file, by
default on first startup MySQL if the MySQL backend has been installed at
first startup. So if you use it with an existing home directory that has
MySQL specified as database
On Tue, 15 Sep 2020 18:51:14 +0200 Tobias Frost wrote:
> Package: sponsorship-requests
> Followup-For: Bug #969910
> Control: close -1
>
> Hi Bastian,
>
> the NMU looks good. I uploaded it to DELAYED/5 and send a nmudiff to the
> package.
> (I'm closing the bug, if something happens to the NMU
Processing commands for cont...@bugs.debian.org:
> unarchive 961444
Bug #961444 {Done: Hideki Yamane } [src:grcompiler]
grcompiler FTBFS on architectures where char is unsigned
Unarchived Bug 961444
> reopen 961444
Bug #961444 {Done: Hideki Yamane } [src:grcompiler]
grcompiler FTBFS on
Source: coq-float
Version: 1:8.10.0-1
Severity: serious
Hello, this is the build log (attached)
make[1]: Leaving directory '/<>'
dh_clean
dpkg-source -Zxz -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building coq-float using existing
Your message dated Wed, 16 Sep 2020 14:48:47 +
with message-id
and subject line Bug#970339: fixed in libobject-pad-perl 0.33-1
has caused the Debian Bug report #970339,
regarding libobject-pad-perl breaks libtickit-console-perl autopkgtest: Failed
test 'all modules in libtickit-console-perl
Your message dated Wed, 16 Sep 2020 14:48:47 +
with message-id
and subject line Bug#970339: fixed in libobject-pad-perl 0.33-1
has caused the Debian Bug report #970339,
regarding libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest:
Failed test 'all modules in
Package: libopenmpi-dev
Version: 4.0.5-3
Severity: serious
Justification: Policy 7.4
During an apt run on a machine that runs a mix of stable and
testing/unstable I hit:
dpkg: error processing archive
/tmp/apt-dpkg-install-HP9Wwp/08-libopenmpi-dev_4.0.5-3_amd64.deb (--unpack):
Your message dated Wed, 16 Sep 2020 11:33:58 +
with message-id
and subject line Bug#937187: fixed in olefile 0.46-3
has caused the Debian Bug report #937187,
regarding olefile: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 16 Sep 2020 12:06:16 +0100
with message-id <1a55487d-76b3-d505-538c-4b8503b10...@p10link.net>
and subject line Closing bugs after chromium NMU
has caused the Debian Bug report #965960,
regarding chromium 83.0.4103.116-3+b1 crash immediately, SEGV_MAPERR
to be marked as
Your message dated Wed, 16 Sep 2020 12:06:16 +0100
with message-id <1a55487d-76b3-d505-538c-4b8503b10...@p10link.net>
and subject line Closing bugs after chromium NMU
has caused the Debian Bug report #967124,
regarding chromium: Unversioned Python removal in sid/bullseye
to be marked as done.
Your message dated Wed, 16 Sep 2020 12:06:16 +0100
with message-id <1a55487d-76b3-d505-538c-4b8503b10...@p10link.net>
and subject line Closing bugs after chromium NMU
has caused the Debian Bug report #965960,
regarding chromium: Received signal 11 SEGV_ACCERR 04c03193. can't load
pages and
Your message dated Wed, 16 Sep 2020 10:03:34 +
with message-id
and subject line Bug#969757: fixed in python-py2bit 0.3.0-5
has caused the Debian Bug report #969757,
regarding src:python-py2bit: fails to migrate to testing for too long: FTBFS on
s390x
to be marked as done.
This means that
Your message dated Wed, 16 Sep 2020 09:41:20 +
with message-id <20200916094120.ga7...@sarek.noreply.org>
and subject line fixed in 0.4.4.4-rc-1
has caused the Debian Bug report #958622,
regarding tor: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means
ping
ping
Your message dated Wed, 16 Sep 2020 09:03:28 +
with message-id
and subject line Bug#963634: fixed in aodh 10.0.0-2
has caused the Debian Bug report #963634,
regarding aodh: FTBFS with Sphinx 3.1: Could not import extension
wsmeext.sphinxext (exception: cannot import name 'l_' from
Control: severity -1 important
Control: merge -1 970375
On 9/16/20 3:45 AM, Koutheir Attouchi wrote:
> Package: python
> Version: 2.7.17-2
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: kouth...@gmail.com
>
> Dear Maintainer,
>
> What led up to the situation?
>
>
Processing control commands:
> severity -1 important
Bug #970420 [python] python: Unmet dependencies when installing python package
Severity set to 'important' from 'grave'
> merge -1 970375
Bug #970420 [python] python: Unmet dependencies when installing python package
Bug #970375 [python]
Control: tag -1 pending
Hello,
Bug #963634 in aodh 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:
Processing control commands:
> tag -1 pending
Bug #963634 [src:aodh] aodh: FTBFS with Sphinx 3.1: Could not import extension
wsmeext.sphinxext (exception: cannot import name 'l_' from 'sphinx.locale'
(/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))
Added tag(s) pending.
--
963634:
Control: tag -1 pending
Hello,
Bug #963634 in aodh 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:
Processing control commands:
> tag -1 pending
Bug #963634 [src:aodh] aodh: FTBFS with Sphinx 3.1: Could not import extension
wsmeext.sphinxext (exception: cannot import name 'l_' from 'sphinx.locale'
(/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))
Ignoring request to alter tags of
Processing commands for cont...@bugs.debian.org:
> severity 966653 important
Bug #966653 [ruby-grpc] gitlab: [BUG] Segmentation fault at 0x
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
966653:
Hi Jean-Marc,
Please check if a core file is available related to the segmentation
fault. If there is any please make it available for me/us.
Also, can you run syslog-ng-debun with the -r parameter and send the
generated report bundle?
Another question, is the segmentation fault reproducible?
Processing commands for cont...@bugs.debian.org:
> fixed 873699 3.15.2-3
Bug #873699 [cfengine3] cfengine3: use upstream configure support for FHS file
layout
Marked as fixed in versions cfengine3/3.15.2-3.
> fixed 963341 3.15.2-3
Bug #963341 [cfengine3] cfengine3: New cfengine 3.15.2 package is
fixed 873699 3.15.2-3
fixed 963341 3.15.2-3
thanks
Sorry, it seems I've messed up the changelog entries for 3.15.2-3.
This must now be closed manually.
I'm (unsurprisingly) experiencing the same problem on sid. This appears to be
the relevant section of the make.log
CC [M]
/var/lib/dkms/openafs/1.8.6/build/src/libafs/MODLOAD-5.8.0-1-amd64-SP/rx_kmutex.o
In file included from
Your message dated Wed, 16 Sep 2020 07:18:26 +
with message-id
and subject line Bug#970340: fixed in rna-star 2.7.5c+dfsg-3
has caused the Debian Bug report #970340,
regarding rna-star: autopkgtest regression: --genomeSAindexNbases 8 is too
large for the genome size=99940
to be marked as
52 matches
Mail list logo
