Your message dated Fri, 18 Sep 2020 06:48:35 +
with message-id
and subject line Bug#968885: fixed in bandage 0.8.1-4
has caused the Debian Bug report #968885,
regarding bandage: binary-any FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Fri, 18 Sep 2020 03:19:37 +
with message-id
and subject line Bug#969817: fixed in diffmon 20020222-7
has caused the Debian Bug report #969817,
regarding diffmon: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem has be
Your message dated Fri, 18 Sep 2020 01:48:42 +
with message-id
and subject line Bug#969840: fixed in lxmms2 0.1.3-5
has caused the Debian Bug report #969840,
regarding lxmms2: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem has been de
Your message dated Thu, 17 Sep 2020 21:50:21 +
with message-id
and subject line Bug#969832: fixed in gox 0.3.0-6
has caused the Debian Bug report #969832,
regarding gox: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Thu, 17 Sep 2020 21:48:55 +
with message-id
and subject line Bug#969811: fixed in changetrack 4.7-8
has caused the Debian Bug report #969811,
regarding changetrack: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 17 Sep 2020 21:50:46 +
with message-id
and subject line Bug#957483: fixed in libvisual-plugins 1:0.4.0+dfsg1-16
has caused the Debian Bug report #957483,
regarding libvisual-plugins: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 17 Sep 2020 21:02:11 +
with message-id
and subject line Bug#968947: fixed in qemu 1:3.1+dfsg-8+deb10u8
has caused the Debian Bug report #968947,
regarding qemu: CVE-2020-14364: usb: out-of-bounds r/w access issue
to be marked as done.
This means that you claim that the
Your message dated Thu, 17 Sep 2020 20:34:01 +
with message-id
and subject line Bug#970507: fixed in chezscheme 9.5.4+dfsg-3
has caused the Debian Bug report #970507,
regarding chezscheme-doc: trying to overwrite
'/usr/lib/csv9.5.4/ta6le/chezscheme.boot', which is also in package chezscheme
Your message dated Thu, 17 Sep 2020 20:34:18 +
with message-id
and subject line Bug#969826: fixed in flpsed 0.7.3-8
has caused the Debian Bug report #969826,
regarding flpsed: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem has been de
Package: openjdk-11-jdk
Version: 11.0.8+10-1
Severity: serious
Justification: violates a "must" directive in policy section 12.5.
The current /usr/share/doc/openjdk-*/copyright files incorrectly
states that the upstream source is from download.java.net; that has
not been the case for a long time.
There is now a Python 3 port of offlineimap underway:
https://github.com/OfflineIMAP/offlineimap/issues/670
AFAICS it looks promising. Please wait with removing from
unstable.
Gaudenz
--
PGP: 836E 4F81 EFBB ADA7 0852 79BF A97A 7702 BAF9 1EF5
signature.asc
Description: PGP signature
Processing commands for cont...@bugs.debian.org:
> severity 969796 serious
Bug #969796 [src:afterstep] afterstep: autopkgtest should be marked superficial
Severity set to 'serious' from 'normal'
> severity 969798 serious
Bug #969798 [src:android-platform-external-libselinux]
android-platform-exte
Hi Ritesh,
On 17-09-2020 16:45, Ritesh Raj Sarraf wrote:
> So, since you've already made the delayed upload, I don't have to act
> on anything. If so, thanks for taking care of this.
Correct.
On the other hand, personally I would love to not be the uploader of
tens of packages that I don't have
Processing commands for cont...@bugs.debian.org:
> block 966907 by 965130
Bug #966907 [src:logrotate] logrotate: FTBFS: logrotate.c:310:5: error:
‘security_context_t’ is deprecated [-Werror=deprecated-declarations]
966907 was not blocked by any bugs.
966907 was not blocking any bugs.
Added blocki
Processing commands for cont...@bugs.debian.org:
> unblock 966907 965130
Unknown command or malformed arguments to command.
> merge 966016 966907
Bug #966016 [src:logrotate] logrotate FTBFS with libselinux 3.1
Unable to merge bugs because:
blockedby of #966907 is '' not '965130'
Failed to merge 96
Processing commands for cont...@bugs.debian.org:
> merge 966016 966907
Bug #966016 [src:logrotate] logrotate FTBFS with libselinux 3.1
Unable to merge bugs because:
blockedby of #966907 is '' not '965130'
Failed to merge 966016: Did not alter merged bugs.
> thanks
Stopping processing here.
Pleas
Your message dated Thu, 17 Sep 2020 17:33:44 +
with message-id
and subject line Bug#967148: fixed in ispell-lt 1.3.2-1
has caused the Debian Bug report #967148,
regarding ispell-lt: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:python-bleach
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.o
Your message dated Thu, 17 Sep 2020 16:48:36 +
with message-id
and subject line Bug#970415: fixed in aseba 1.6.99+dfsg-1
has caused the Debian Bug report #970415,
regarding aseba build-depends unsatisfiable in testing and unstable.
to be marked as done.
This means that you claim that the prob
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-an
Hi,
Axel Beckert wrote:
> Upgrading chezscheme-doc (with chezscheme also being installed and
> already upgraded to 9.5.4+dfsg-2) fails for me as follows:
Small correction: It seems as if it was an installation and not an
upgrade of chezscheme-doc (due being suggested by chezscheme) after
chezsche
Just wanted to note in this copy of the bug that the recommendation from
upstream systemd was that gparted should not be masking mounts but
instead should take a bsd lock on the device to prevent auto mounts.
Your message dated Thu, 17 Sep 2020 14:44:29 +
with message-id
and subject line Bug#969715: fixed in petsc4py 3.13.0-6
has caused the Debian Bug report #969715,
regarding petsc4py: autopkgtest regression on ppc64el
to be marked as done.
This means that you claim that the problem has been deal
Hello Paul,
So, since you've already made the delayed upload, I don't have to act
on anything. If so, thanks for taking care of this.
Ritesh
On Thu, 2020-09-17 at 10:30 +0200, Paul Gevers wrote:
>
> Your package is only blocked because the arch:all binary package(s)
> aren't built on a buildd.
Package: chezscheme-doc, chezscheme
Severity: serious
Version: 9.5.4+dfsg-2
Upgrading chezscheme-doc (with chezscheme also being installed and
already upgraded to 9.5.4+dfsg-2) fails for me as follows:
Preparing to unpack .../chezscheme-doc_9.5.4+dfsg-2_all.deb ...
Unpacking chezscheme-doc (9.5.4
Your message dated Thu, 17 Sep 2020 13:49:55 +
with message-id
and subject line Bug#957997: fixed in xserver-xorg-video-amdgpu 19.1.0-2
has caused the Debian Bug report #957997,
regarding xserver-xorg-video-amdgpu: ftbfs with GCC-10
to be marked as done.
This means that you claim that the pro
Hi,
On Wed, Sep 16, 2020 at 11:14:58PM +0200, Pierre-Elliott Bécue wrote:
> 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
Control: tags -1 normal
On Thu, Sep 17, 2020 at 01:40:29PM +0200, Paul Gevers wrote:
> The thread starts here:
> https://lists.debian.org/debian-devel/2020/09/msg00071.html
>
> mostly follow-ups from here on:
> https://lists.debian.org/debian-devel/2020/09/msg00219.html
Thanks for the pointers a
Processing commands for cont...@bugs.debian.org:
> severity 969796 normal
Bug #969796 [src:afterstep] afterstep: autopkgtest should be marked superficial
Severity set to 'normal' from 'serious'
> severity 969798 normal
Bug #969798 [src:android-platform-external-libselinux]
android-platform-extern
Control: severity -1 important
Control: tag -1 moreinfo
On Mon, Sep 07, 2020 at 11:59:34AM -0400, Christophe Kalt wrote:
> Package: xserver-xorg-core
> Version: 2:1.20.9-1
> Severity: grave
>
> Same setup was working with 2:1.20.7-2, but with 2:1.20.9-1 crashes on startup
> (xinit). /var/log/Xorg
Processing control commands:
> severity -1 important
Bug #969739 [xserver-xorg-core] Segmentation fault on startup
Severity set to 'important' from 'grave'
> tag -1 moreinfo
Bug #969739 [xserver-xorg-core] Segmentation fault on startup
Added tag(s) moreinfo.
--
969739: https://bugs.debian.org/cg
Your message dated Thu, 17 Sep 2020 13:03:31 +
with message-id
and subject line Bug#969660: fixed in cpio 2.13+dfsg-4
has caused the Debian Bug report #969660,
regarding src:cpio: fails to migrate to testing for too long: maintainer built
arch:all binaries
to be marked as done.
This means th
Processing control commands:
> severity -1 important
Bug #969136 [xserver-xorg-video-amdgpu] xserver-xorg-video-amdgpu: Xserver
keeps crashing inside of /usr/lib/xorg/modules/drivers/amdgpu_drv.so
Severity set to 'important' from 'grave'
> reassign -1 mesa
Bug #969136 [xserver-xorg-video-amdgpu]
Control: severity -1 important
Control: reassign -1 mesa
On Thu, Aug 27, 2020 at 06:36:27PM -0700, Phil Dibowitz wrote:
> Package: xserver-xorg-video-amdgpu
> Version: 19.1.0-1
> Severity: grave
> Justification: causes non-serious data loss
>
> Dear Maintainer,
>
> About once a day my Xserver cr
Your message dated Thu, 17 Sep 2020 14:48:52 +0200
with message-id <20200917124852.GA407211@jcristau-z4>
and subject line Re: Bug#868068: [xserver-xorg-core] Upgrade from 2:1.16.4-1 to
2:1.16.4-1+deb8u1 loses keyboard and mouse
has caused the Debian Bug report #868068,
regarding [xserver-xorg-core
> autopkgtest [03:13:34]: test command1: python3 setup.py test
> autopkgtest [03:13:34]: test command1: [---
> running test
> WARNING: Testing via this command is deprecated and will be removed in a
> future version. Users looking for a generic test entry point independent
> of
Your message dated Thu, 17 Sep 2020 12:33:35 +
with message-id
and subject line Bug#961438: fixed in grcompiler 5.2-2.1
has caused the Debian Bug report #961438,
regarding grcompiler FTBFS on i386: compare_PigLatinTest_v2 failed
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 17 Sep 2020 12:33:36 +
with message-id
and subject line Bug#961445: fixed in grcompiler 5.2-2.1
has caused the Debian Bug report #961445,
regarding grcompiler FTBFS on big endian
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Thu, 17 Sep 2020 12:33:36 +
with message-id
and subject line Bug#961444: fixed in grcompiler 5.2-2.1
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
Source: picard-tools
Version: 2.23.4+dfsg-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
Your package was recently removed from testing and now needs passing
autopkgtests to migrate to testing instead of mer
Your message dated Thu, 17 Sep 2020 11:48:38 +
with message-id
and subject line Bug#970442: fixed in openmpi 4.0.5-4
has caused the Debian Bug report #970442,
regarding libopenmpi-dev/sid and openmpi-bin/stable ship the same file
to be marked as done.
This means that you claim that the proble
Hi Andreas,
On 17-09-2020 11:46, Andreas Tille wrote:
> Was there any outcome on your discussion of the severity of those
> bugs (and where did this discussion happened - I can not find anything
> on debian-devel or debian-ci list)?
The thread starts here:
https://lists.debian.org/debian-devel/20
On 9/17/20 12:39 AM, Debian testing autoremoval watch wrote:
> wmxres 1.4-1 is marked for autoremoval from testing on 2020-10-07
>
> It is affected by these RC bugs:
> 969882: wmxres: autopkgtest should be marked superficial
> https://bugs.debian.org/969882
I've prepared a new version of wmxres
Processing control commands:
> found -1 rhino/1.7.7.2-1
Bug #970501 [src:rhino, src:dojo] rhino breaks dojo autopkgtest: Cannot set
property "dojo" of null to "[object Object]"
Marked as found in versions rhino/1.7.7.2-1.
> found -1 dojo/1.15.3+dfsg1-1
Bug #970501 [src:rhino, src:dojo] rhino brea
Source: rhino, dojo
Control: found -1 rhino/1.7.7.2-1
Control: found -1 dojo/1.15.3+dfsg1-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of rhino the autopkgtes
Your message dated Thu, 17 Sep 2020 10:35:27 +
with message-id
and subject line Bug#969669: fixed in node-node-forge 0.10.0~dfsg-1
has caused the Debian Bug report #969669,
regarding node-node-forge: CVE-2020-7720
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> forwarded 969715 https://gitlab.com/petsc/petsc4py/-/issues/4
Bug #969715 [src:petsc4py] petsc4py: autopkgtest regression on ppc64el
Set Bug forwarded-to-address to 'https://gitlab.com/petsc/petsc4py/-/issues/4'.
> thanks
Stopping processing here.
Your message dated Thu, 17 Sep 2020 10:23:20 +
with message-id
and subject line Bug#957874: fixed in tgt 1:1.0.79-3
has caused the Debian Bug report #957874,
regarding tgt: 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 t
Your message dated Thu, 17 Sep 2020 10:03:50 +
with message-id
and subject line Bug#968628: fixed in cucumber 2.4.0-4
has caused the Debian Bug report #968628,
regarding ruby-diff-lcs breaks cucumber autopkgtest: 578 examples, 7 failures
to be marked as done.
This means that you claim that th
Your message dated Thu, 17 Sep 2020 10:03:50 +
with message-id
and subject line Bug#966946: fixed in cucumber 2.4.0-4
has caused the Debian Bug report #966946,
regarding cucumber: FTBFS: ERROR: Test "ruby2.7" failed:expected no
Exception, got # with
backtrace:
to be marked as done.
Control: tag -1 pending
Hello,
Bug #968628 in cucumber 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/ruby-team/cucumber/-/commit/6f1fc5ed4f038995a2ed38350b151
Hi again,
I did not expected to do any more on this issue since the bug was fixed
quickly. Unfortunately the build failed on s390x (see my mail to
debian-devel) and we are now ending up with a package that is IMHO
affected by a "testing removal" warning for no good reason.
Was there any outcome
Processing control commands:
> tag -1 pending
Bug #968628 [src:ruby-diff-lcs, src:cucumber] ruby-diff-lcs breaks cucumber
autopkgtest: 578 examples, 7 failures
Added tag(s) pending.
--
968628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968628
Debian Bug Tracking System
Contact ow...@bugs
Control: forwarded -1 https://github.com/igraph/igraph/issues/1469
Processing control commands:
> forwarded -1 https://github.com/igraph/igraph/issues/1469
Bug #970497 [src:igraph] igraph: FTBFS on mips64el
Set Bug forwarded-to-address to 'https://github.com/igraph/igraph/issues/1469'.
--
970497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970497
Debian B
Hi,
the s390x build log[1] ends with:
...
./test_flpmath: 9/ 9 passed.
./test_splines
*** stack smashing detected ***: terminated
make[3]: *** [Makefile:685: utests-all] Aborted
...
The package has built before and the latest changes are:
bart (0.6.00-2) unstable; urgency=medium
*
Source: igraph
Severity: serious
Tags: ftbfs upstream
Justification: Policy 1.2.3
Hi,
the package does not build from source on mips64el as you can see here
https://buildd.debian.org/status/fetch.php?pkg=igraph&arch=mips64el&ver=0.8.2%2Bds-2&stamp=1596624159&raw=0
Kind regards
Andreas
The following merge request applies the relevant upstream commit as a
patch to relax the dependency on gvfs-bin:
https://salsa.debian.org/debian/gedit-latex-plugin/-/merge_requests/1
Source: python-livereload
Version: 2.6.3-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 python-livereload the autopkgtest of
python-livereload fails in testing when that autopkgtest is
Your message dated Thu, 17 Sep 2020 08:33:50 +
with message-id
and subject line Bug#969808: fixed in cfourcc 0.1.2-11
has caused the Debian Bug report #969808,
regarding cfourcc: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem has been
Source: laptop-mode-tools
Version: 1.73.1-3
Severity: serious
Control: close -1 1.74-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between
Processing control commands:
> close -1 1.74-1
Bug #970493 [src:laptop-mode-tools] src:laptop-mode-tools: fails to migrate to
testing for too long: maintainer built arch:all binaries
Marked as fixed in versions laptop-mode-tools/1.74-1.
Bug #970493 [src:laptop-mode-tools] src:laptop-mode-tools: f
Processing commands for cont...@bugs.debian.org:
> tags 895851 + patch
Bug #895851 [gkrellweather] sh: 1: /usr/local/share/gkrellm/GrabWeather: not
found
Ignoring request to alter tags of bug #895851 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need
Your message dated Thu, 17 Sep 2020 07:48:54 +
with message-id
and subject line Bug#966300: fixed in guile-3.0 3.0.4-2
has caused the Debian Bug report #966300,
regarding guile oom test fails on ppc64el
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Thu, 17 Sep 2020 07:48:54 +
with message-id
and subject line Bug#969707: fixed in guile-3.0 3.0.4-2
has caused the Debian Bug report #969707,
regarding guile-3.0: FTBFS in test suite "FAIL: test-out-of-memory" fails
to be marked as done.
This means that you claim that the p
Your message dated Thu, 17 Sep 2020 07:48:54 +
with message-id
and subject line Bug#968403: fixed in guile-3.0 3.0.4-2
has caused the Debian Bug report #968403,
regarding numbers.test fails on i386
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Processing commands for cont...@bugs.debian.org:
> forcemerge 970448 970473
Bug #970448 [libgs9-common] libgs9-common: gnome metapackage in uninstallable
because of broken dependencies in libgs9-common
Bug #970473 [libgs9-common] libgs9-common: Fails to install
Severity set to 'important' from 's
Processing commands for cont...@bugs.debian.org:
> severity 969820 normal
Bug #969820 [src:dnsenum] dnsenum: autopkgtest should be marked superficial
Severity set to 'normal' from 'serious'
> severity 969824 normal
Bug #969824 [src:ext3grep] ext3grep: autopkgtest should be marked superficial
Sever
68 matches
Mail list logo
