On Sunday, 30 August 2020 3:01:34 AM AEST Shengjing Zhu wrote:
> Please see the patches attached.
Thank you very much!
> BTW, is there any instruction to work with the docker.io git repo?
> It seems `gbp buildpackage` or `gbp pq` are hard to use with it.
Something like the following:
Your message dated Sat, 29 Aug 2020 23:48:34 +
with message-id
and subject line Bug#966189: fixed in cuneiform 1.1.0+dfsg-8
has caused the Debian Bug report #966189,
regarding cuneiform: FTBFS with GCC 10: multiple definition of ... due to
-fno-common
to be marked as done.
This means that
Your message dated Sat, 29 Aug 2020 23:34:43 +
with message-id
and subject line Bug#957720: fixed in pyparted 3.11.6-0.1
has caused the Debian Bug report #957720,
regarding pyparted: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Aug 2020 22:33:38 +
with message-id
and subject line Bug#956876: fixed in dulwich 0.20.6-1
has caused the Debian Bug report #956876,
regarding dulwich: FTBFS on s390x
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 29 Aug 2020 22:04:43 +
with message-id
and subject line Bug#968883: fixed in mame 0.224+dfsg.1-1
has caused the Debian Bug report #968883,
regarding mame FTBFS on !x86
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing commands for cont...@bugs.debian.org:
> severity 953533 normal
Bug #953533 [src:opensc] opensc: Fails to build due to missing bash_completion
files
Severity set to 'normal' from 'serious'
> thank
Stopping processing here.
Please contact me if you need assistance.
--
953533:
Your message dated Sat, 29 Aug 2020 21:34:49 +
with message-id
and subject line Bug#957827: fixed in spacenavd 0.7.1-1
has caused the Debian Bug report #957827,
regarding spacenavd: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Aug 2020 21:34:49 +
with message-id
and subject line Bug#958617: fixed in spacenavd 0.7.1-1
has caused the Debian Bug report #958617,
regarding spacenavd: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you claim
severity 953533 normal
thank
On Tue, 10 Mar 2020 08:10:06 + "Cirujano Cuesta, Silvano"
wrote:
> Package: opensc
> Version: 0.20.0-3
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> Tags: ftbfs
>
> Trying to build fails. I've tried
I can see two options here:
1) drop support for architectures not supported by upstream
2) disable the unsupported architecture check somehow
* either by setting the environment variable
* by patching out the check in the source code
I'm not entirely sure what the right thing is for our
Your message dated Sat, 29 Aug 2020 21:03:53 +
with message-id
and subject line Bug#941175: fixed in lptools 0.2.0-7
has caused the Debian Bug report #941175,
regarding lp-shell: invalid syntax error on start
to be marked as done.
This means that you claim that the problem has been dealt
Control: tags 957224 + patch
Control: tags 957224 + pending
Dear maintainer,
I've prepared an NMU for fped (versioned as 0.1+201210-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -Nru fped-0.1+201210/debian/changelog
Processing control commands:
> tags 957224 + patch
Bug #957224 [src:fped] fped: ftbfs with GCC-10
Added tag(s) patch.
> tags 957224 + pending
Bug #957224 [src:fped] fped: ftbfs with GCC-10
Added tag(s) pending.
--
957224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957224
Debian Bug
Processing commands for cont...@bugs.debian.org:
> # just checked this patch doesn't work
> tags 957039 - patch
Bug #957039 [src:biloba] biloba: ftbfs with GCC-10
Removed tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
957039:
Hi
Not the maintainer here, but given coturn is going to be removed from
testing otherwise I quickly looked at this. In default install this
does not seem to be a problem, turnserver uses the syslog option and
logfile settings are commented out.
So while there is probably some room of
Processing commands for cont...@bugs.debian.org:
> severity 961926 normal
Bug #961926 [rr] rr: record fails on i386
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
961926:
Package: glaurung
Version: 2.2-3
Severity: grave
Tags: patch
X-Debbugs-Cc: Asher Gordon
Dear Maintainer,
Glaurung segfaults when the 'go' command is used, making it
unusable. For example:
$ glaurung
Glaurung 2.2. Copyright (C) 2004-2008 Tord Romstad.
go
Segmentation fault
Your message dated Sat, 29 Aug 2020 17:19:03 +
with message-id
and subject line Bug#966863: fixed in gmap 2020-06-30+ds-2
has caused the Debian Bug report #966863,
regarding gmap: FTBFS: ld: gmap_nosimd-dynprog_end.o:./src/dynprog_end.c:112:
multiple definition of `homopolymerp';
Package: docker.io
Version: 19.03.12+dfsg1-3
Severity: serious
Please see the patches attached.
BTW, is there any instruction to work with the docker.io git repo?
It seems `gbp buildpackage` or `gbp pq` are hard to use with it.
Description: Fix build with runc 1.0.0~rc92
Author: Shengjing Zhu
Processing commands for cont...@bugs.debian.org:
> severity 969226 serious
Bug #969226 [cryptsetup-suspend] cryptsetup-suspend: missing dependency on
/bin/openvt (kbd)
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
969226:
Control: -1 severity -1 serious
Hi Jochen,
On Sat, 29 Aug 2020 at 18:24:44 +0200, Jochen Sprickerhof wrote:
> Severity: grave
> Justification: renders package unusable
> […r
> /lib/systemd/system/systemd-suspend.service.d/systemd_cryptsetup-suspend.conf
> tries to call /bin/openvt which is in
Package: cryptsetup-suspend
Version: 2:2.3.3-3+exp1
Severity: grave
Justification: renders package unusable
Hi,
/lib/systemd/system/systemd-suspend.service.d/systemd_cryptsetup-suspend.conf
tries to call /bin/openvt which is in the optional package kbd. Please
add a dependency to make sure it's
Am 28.08.2020 um 10:42 teilte Adrian Bunk mit:
Hi all,
> ...
> 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:
Your message dated Sat, 29 Aug 2020 16:04:56 +
with message-id
and subject line Bug#965951: fixed in twms 0.07z+git20200829+cb7d39a-1
has caused the Debian Bug report #965951,
regarding twms fails to start
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Aug 2020 16:04:56 +
with message-id
and subject line Bug#958601: fixed in twms 0.07z+git20200829+cb7d39a-1
has caused the Debian Bug report #958601,
regarding twms: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you
On 2020-08-16, the Technical Committee was informally (by the means of
a single IRC message) notified that we should probably look into bug
#959828. We thus discussed it in our monthly meeting, that was held
three days later.
During our last meeting, we all thought sharing the points we all
Please see the installation instructions:
https://www.debian.org/releases/stable/installmanual
It is not correct to pre-format your install media, and pre-copy other files
onto it, before copying the installation .iso
The correct instructions for writing a USB (or other) installation medium are
Processing control commands:
> severity -1 important
Bug #969177 [debmake] debmake: cannot create deb for nodejs modeule
Severity set to 'important' from 'grave'
--
969177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: severity -1 important
Hi,
Thanks for the log which helps
It only breaks for javascript/nodejs.
Javascript/nodejs support is new and needs help. Besides
(You shouldn't file a grave RC bug without throurough review against
policy.)
On Fri, 2020-08-28 at 21:39 +0530, Pirate
Your message dated Sat, 29 Aug 2020 15:18:54 +
with message-id
and subject line Bug#966896: fixed in fatsort 1.6.3.622-0.1
has caused the Debian Bug report #966896,
regarding fatsort: FTBFS: ld: entrylist.o:./src/options.h:38: multiple
definition of `OPT_LOCALE';
Upstream already fixed this issue in a newer version.
After asking Jordi his permission in private, I've prepared a NMU.
Cheers,
Alex
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Alex Muntada
⢿⡄⠘⠷⠚⠋ Debian Developer log.alexm.org
⠈⠳⣄
signature.asc
Description: PGP signature
This is not a well supported method. Just use dd to write a netinst or a
DVD image straight to the stick and then boot from it directly.
dd if=debian-10.5.0-amd64-DVD-1.iso of=/dev/sdX bs=4M oflag=sync
status=progress
That will put a bootable partition on the stick and then the install will
Hi Richard,
On Sat, Aug 22, 2020 at 12:58:47PM +0100, Richard Kettlewell wrote:
> I've had further crashes under 4.19.0-10-amd64 on a second machine.
> Again, after reverting to 4.19.0-9-amd64 this second machine seems to be
> stable.
>
> The full logs are at
Package: cdimage.debian.org
Severity: critical
Justification: breaks the whole system
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads)
Locale:
Package: cyrus-caldav
Version: 3.2.2-1~bpo10+1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Installation of cyrus (3.2.2-1~bpo10+1) including
Package: paxctld
Severity: serious
Version: 1.2.1-1
Tags: bullseye sid
Hi,
as far as I understand, paxctld is only useful with the semi-proprietary
GRsec kernel patches. As these are now more or less proprietary,
paxctld doesn't seem useful in Debian.
I therefore suggest to remove paxctld from
Processing commands for cont...@bugs.debian.org:
> severity 966992 normal
Bug #966992 [fdisk] Regression in sfdisk
Severity set to 'normal' from 'serious'
> tags 966992 + upstream confirmed
Bug #966992 [fdisk] Regression in sfdisk
Added tag(s) confirmed and upstream.
> thanks
Stopping processing
It seems both libMesaOpenCL.so and libLLVM-10.so links llvm-polly
statically, so its static constructor called twice.
Processing control commands:
> reassign -1 fdisk 2.36-2
Bug #966992 [src:nbdkit] nbdkit: FTBFS: dh_auto_test: error: make -j1 check
VERBOSE=1 returned exit code 2
Bug reassigned from package 'src:nbdkit' to 'fdisk'.
No longer marked as found in versions nbdkit/1.20.5-1.
Ignoring request to alter
control: reassign -1 fdisk 2.36-2
control: retitle -1 Regression in sfdisk
I have traced the cause fo the nbdkit build failures (e.g. [1] to what
seems to be a regression in sfdisk that manifests itself in a "No space
left on device" error when creating some trivial partitioned disk
images.
Package: libcmark-gfm-extensions-dev
Version: 0.29.0.gfm.0-5
Severity: grave
Justification: renders package unusable
Dear maintainer,
Thanks for fixing bug #968709. While trying to use
libcmark-gfm-extensions-dev (v0.29.0.gfm.0-5 from unstable) to build
haskell-cmark-gfm, it fails with:
Hi,
On Thu, 9 Jul 2020 13:10:03 +0200 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
I backported a commit from upstream that fixes this issue:
https://github.com/dex4er/fakechroot/commit/b42d1fb9538f680af2f31e864c555414ccba842a
and
Processing commands for cont...@bugs.debian.org:
> tags 936129 + pending
Bug #936129 [src:apr-util] apr-util: Python2 removal in sid/bullseye
Added tag(s) pending.
> tags 969064 + pending
Bug #969064 [src:apr-util] apr-util: Cannot fulfill the build dependencies
Added tag(s) pending.
> thanks
Your message dated Sat, 29 Aug 2020 10:48:27 +
with message-id
and subject line Bug#969065: fixed in apr 1.7.0-1
has caused the Debian Bug report #969065,
regarding apr: Cannot fulfill the build dependencies
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> severity -1 important
Bug #969196 [src:zimlib] zimlib: symbols updates for architectures built with
-O3
Severity set to 'important' from 'serious'
--
969196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969196
Debian Bug Tracking System
Contact
Control: severity -1 important
On 2020-08-29 09:47:28 +0200, Gianfranco Costamagna wrote:
> Source: zimlib
> Version: 6.2.0-2
> Severity: serious
> tags: patch
>
> Hello, zimlib symbols file seems to be really difficult to maintain, breaking
> on each icu upload, each new gcc upload,
>
Eric,
I do plan to fix this issue and upload a fixed OpenSC to Debian.
I will do an delayed upload to you can react if you want.
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#delayed-incoming
Bye
On Wed, 11 Mar 2020 11:38:58 + "Cirujano Cuesta, Silvano"
wrote:
Package: redmine
Version: 4.0.7-1
Severity: serious
User: pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: rails6-transition
redmine autopkgtest fails with rails 6. Full log
https://ci.debian.net/data/autopkgtest/testing/amd64/r/redmine/6840219/log.gz
Processing commands for cont...@bugs.debian.org:
> unarchive 949793
Bug #949793 {Done: Jonas Smedegaard } [src:d-shlibs] dh-shlibs
fails for Python 3.8 libs
Unarchived Bug 949793
> fixed 949793 shlibs/0.94
Bug #949793 {Done: Jonas Smedegaard } [src:d-shlibs] dh-shlibs
fails for Python 3.8 libs
Processing commands for cont...@bugs.debian.org:
> forcemerge 949793 969199
Bug #949793 {Done: Jonas Smedegaard } [src:d-shlibs] dh-shlibs
fails for Python 3.8 libs
Unable to merge bugs because:
package of #969199 is 'd-shlibs' not 'src:d-shlibs'
Failed to forcibly merge 949793: Did not alter
Your message dated Sat, 29 Aug 2020 07:51:34 +
with message-id
and subject line Bug#952496: fixed in python-whiteboard 1.0+git20170915-5
has caused the Debian Bug report #952496,
regarding python3-whiteboard, depends on package that is not in Debian.
to be marked as done.
This means that you
Source: zimlib
Version: 6.2.0-2
Severity: serious
tags: patch
Hello, zimlib symbols file seems to be really difficult to maintain, breaking
on each icu upload, each new gcc upload,
different gcc optimization levels (such as -O2 and -O3) and so on.
Somebody thinks that symbols files for c++
52 matches
Mail list logo
