Hi Sunil,
Quoting Sunil Mohan Adapa (2021-02-04 03:17:55)
> tag 970633 + patch
> tag 932924 + patch
> thanks
>
> Hello,
>
> Eagerly looking forward to tt-rss being in good shape for FreedomBox in
> Bullseye, I have done the packaging work needed for uploading 21.1
> version of tt-rss. Please
Processing commands for cont...@bugs.debian.org:
> severity 953728 important
Bug #953728 [src:gambc] gambc: FTBFS on s390x
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
953728:
On Mon, Feb 01, 2021 at 09:45:24PM +0530, Nilesh Patra wrote:
> Hi Julian
> I read through the rest of the thread.
>
> On Mon, 1 Feb, 2021, 6:31 pm Julian Gilbey, wrote:
>
> I have a package of Spyder 4 waiting to upload, but it requires five
> packages to be accepted into unstable from NEW
Source: python-fabio
Version: 0.11.0+dfsg-1
Severity: serious
Hello,
autopkgtests are failing, please check the logs at:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-fabio/10229362/log.gz
The same tests are not executed during build time, and that's why the package
builds fine
On 2/3/21 12:37 PM, Sebastiaan Couwenberg wrote:
> On 2/3/21 12:03 PM, Sebastiaan Couwenberg wrote:
>> On 2/3/21 10:48 AM, Gianfranco Costamagna wrote:
>>> Hello, the new libdap broke in some way the gdal configure script, and now
>>> the configure step fails with:
>>>
>>> checking for
Your message dated Thu, 04 Feb 2021 04:18:22 +
with message-id
and subject line Bug#981765: fixed in docknot 4.00-2
has caused the Debian Bug report #981765,
regarding docknot: autopkgtest failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 03 Feb 2021 22:19:19 -0500
with message-id
and subject line Re: pylev: Another source-only upload is needed
has caused the Debian Bug report #981403,
regarding pylev: Another source-only upload is needed
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> tag 970633 + patch
Bug #970633 [src:tt-rss] tt-rss: CVE-2020-25787 CVE-2020-25788 CVE-2020-25789
Added tag(s) patch.
> tag 932924 + patch
Bug #932924 [src:tt-rss] tt-rss: privacy violation -- ttrss Forum und New
Releases subscribed to by default
tag 970633 + patch
tag 932924 + patch
thanks
Hello,
Eagerly looking forward to tt-rss being in good shape for FreedomBox in
Bullseye, I have done the packaging work needed for uploading 21.1
version of tt-rss. Please merge and upload the package into Debian
unstable before the Bullseye Soft
Followup-For: Bug #980609
source: gcc-10
Is this fix going to be backported to bullseye/sid? I'm too facing this issue
with gcc-10 10.2.1-6.
howdy nicoo,
nicoo, 2021-01-30 20:21 -0500:
> python-fido2 had minor API-breaking changes, which breaks (at least)
> yubikey-manager. Let's hold it back from transitionning to testing until
> upstream cuts a new release.
fyi the breaking of yubikey-manager seems to break yubioath-desktop too,
It seems some Python files got missing, the stderr gives
nhandled PyOtherSide error: Cannot import module: yubikey (Traceback (most
recent call last):
File "qrc:///py/yubikey.py", line 12, in
from ykman.descriptor import (
ModuleNotFoundError: No module named 'ykman.descriptor'
)
Package: yubioath-desktop
Version: 5.0.4-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: norb...@preining.info
Hi all,
A flush of updates came in, besides that some yubi package updates,
and this morning the yubioath desktop application does not recognize my
yubikey (4,
Your message dated Wed, 03 Feb 2021 23:50:34 +
with message-id
and subject line Bug#957822: fixed in snapd-glib 1.58-1
has caused the Debian Bug report #957822,
regarding snapd-glib: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> forcemerge 964139 -1
Bug #964139 [network-manager] network-manager: Please restore removed init
script.
Bug #981747 [network-manager] network-manager: NetworkManager does not start in
sysvinit system
Severity set to 'wishlist' from 'grave'
981747 was not blocked
Control: forcemerge 964139 -1
Control: tags 964139 + wontfix
Merging with the duplicate.
I don't intend to restore the deprecated SysV init script. So marking as
wontfix.
Your message dated Wed, 03 Feb 2021 21:48:44 +
with message-id
and subject line Bug#981555: fixed in glib2.0 2.66.5-1
has caused the Debian Bug report #981555,
regarding libglib2.0-0: gnome-keyring unable to unlock login keyring on some
systems since GLib 2.66.4-2
to be marked as done.
This
Your message dated Wed, 03 Feb 2021 21:48:44 +
with message-id
and subject line Bug#981555: fixed in glib2.0 2.66.5-1
has caused the Debian Bug report #981555,
regarding gnome-keyring: unable to connect to D-Bus when using dbus-x11
to be marked as done.
This means that you claim that the
Your message dated Wed, 03 Feb 2021 21:48:43 +
with message-id
and subject line Bug#981420: fixed in glib2.0 2.66.5-1
has caused the Debian Bug report #981420,
regarding gnome-keyring: unable to connect to D-Bus when using dbus-x11
to be marked as done.
This means that you claim that the
Your message dated Wed, 03 Feb 2021 21:48:43 +
with message-id
and subject line Bug#981420: fixed in glib2.0 2.66.5-1
has caused the Debian Bug report #981420,
regarding libglib2.0-0: gnome-keyring unable to unlock login keyring on some
systems since GLib 2.66.4-2
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> forwarded 981404 https://github.com/facebook/zstd/issues/1630
Bug #981404 [zstd] compressed file is world readable, while zstd is running
Set Bug forwarded-to-address to 'https://github.com/facebook/zstd/issues/1630'.
> tags 981404 + upstream
This is more or less a duplicate of #980202
To unblock gscan2pdf, in case -60 didn't fix things, I uploaded
gscan2pdf-2.11.0-1 yesterday and replaced imagemagick with
graphicsmagick for the tests in question.
However, this doesn't solve the problem in imagemagick, which is
described in
Processing commands for cont...@bugs.debian.org:
> fixed 979521 openboard/1.5.4+dfsg1-1
Bug #979521 {Done: Mike Gabriel } [openboard-common]
openboard-common depends on libjs-jquery-i18n-properties that was removed from
unstable
Marked as fixed in versions openboard/1.5.4+dfsg1-1.
> thanks
Package: kworkflow
Followup-For: Bug #980575
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Hello,
Please find attached a trivial patch to make the kworkflow autopkgtest
compatible with git 2.30. I have uploaded this change to Ubuntu to unblock
the transition
Processing commands for cont...@bugs.debian.org:
> # version tracking gets confused is bug is closed in different package
> reassign 979480 openmpi
Bug #979480 {Done: Alastair McKinstry } [src:mpi4py]
mpi4py: autopkgtest failure on arm64, armhf and ppc64el
Bug reassigned from package
Source: imagemagick, gscan2pdf
Control: found -1 imagemagick/8:6.9.11.60+dfsg-1
Control: found -1 gscan2pdf/2.10.2-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
Processing control commands:
> found -1 imagemagick/8:6.9.11.60+dfsg-1
Bug #981798 [src:imagemagick, src:gscan2pdf] imagemagick breaks gscan2pdf
autopkgtest: expected format changed
Marked as found in versions imagemagick/8:6.9.11.60+dfsg-1.
> found -1 gscan2pdf/2.10.2-1
Bug #981798
Processing commands for cont...@bugs.debian.org:
> # this bug is about the issue in its-tools, which isn't fixed yet
> # the FTBFS in debmake-doc (which is fixed) is tracked in #948781
> reopen 919058
Bug #919058 {Done: Osamu Aoki } [itstool] its-tools: crashes
when freeing xmlDocs
'reopen' may
Processing commands for cont...@bugs.debian.org:
> # this bug is about the FTBFS in debmake-doc, so reassign it there, to make
> # sure version tracking is correct
> # the bug in its-tools is 919058
> reassign 948781 debmake-doc
Bug #948781 {Done: Osamu Aoki } [itstool] debmake-doc: FTBFS:
Processing commands for cont...@bugs.debian.org:
> tags 979641 + pending
Bug #979641 [src:kboot-utils] src:kboot-utils: invalid maintainer address
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979641:
Processing commands for cont...@bugs.debian.org:
> # this is about the FTBFS in debmake-doc - see #919058 for the bug in itstool
> notfound 948781 itstool/2.0.4-1
Bug #948781 {Done: Osamu Aoki } [itstool] debmake-doc: FTBFS:
Segmentation fault
No longer marked as found in versions
Hi Salvatore,
On Wed, Feb 03, 2021 at 09:39:25PM +0100, Salvatore Bonaccorso wrote:
> HI Benjamin,
>
> On Mon, Jan 18, 2021 at 07:19:14PM -0800, Benjamin Kaduk wrote:
> > On Mon, Jan 18, 2021 at 06:04:39PM +, Jeremy Stanley wrote:
> > > Thanks for pulling this into unstable and testing! Is
On 2021/02/03 07:10 PM, Antonio Ospite wrote:
> On Wed, 3 Feb 2021 09:43:30 +0100
> Baptiste Beauplat wrote:
>
> [...]
> >
> > I could open the RM bug on your behalf if you want me to.
> >
>
> Thank you, I would appreciate that.
Created as #981795
https://bugs.debian.org/981795
--
Your message dated Wed, 03 Feb 2021 21:00:11 +
with message-id
and subject line Bug#979521: fixed in jquery-i18n-properties 1.2.7+dfsg1-1
has caused the Debian Bug report #979521,
regarding openboard-common depends on libjs-jquery-i18n-properties that was
removed from unstable
to be marked
Processing commands for cont...@bugs.debian.org:
> # fix meta data, otherwise bts and britney can't figure it out
> reassign 980956 src:r-cran-dbplyr 1.4.4-1
Bug #980956 {Done: Michael R. Crusoe } [src:r-cran-magrittr,
src:r-cran-dbplyr] r-cran-magrittr breaks r-cran-dbplyr autopkgtest: could
HI Benjamin,
On Mon, Jan 18, 2021 at 07:19:14PM -0800, Benjamin Kaduk wrote:
> On Mon, Jan 18, 2021 at 06:04:39PM +, Jeremy Stanley wrote:
> > Thanks for pulling this into unstable and testing! Is there any work
> > in progress to fix it in stable as well? I took a quick peek in
> > Salsa and
Your message dated Wed, 03 Feb 2021 20:33:37 +
with message-id
and subject line Bug#980626: fixed in pocl 1.6-4
has caused the Debian Bug report #980626,
regarding pocl: FTBFS: E: Build killed with signal TERM after 150 minutes of
inactivity
to be marked as done.
This means that you claim
Source: varmon
Version: 1.2.1-1
Severity: serious
Julien Danjou is no longer a Debian Developer, and
his mail address has started bouncing.
Someone will need to take care of this package.
Chris
Your message dated Wed, 03 Feb 2021 20:21:55 +
with message-id
and subject line Bug#981763: fixed in json2file-go 1.14
has caused the Debian Bug report #981763,
regarding json2file-go: missing dependency on libcap2-bin
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 03 Feb 2021 20:22:00 +
with message-id
and subject line Bug#981672: fixed in libnitrokey 3.5-3.3
has caused the Debian Bug report #981672,
regarding libnitrokey FTBFS on !amd64/arm64: symbol differences
to be marked as done.
This means that you claim that the problem
Hi James,
Le Thu, Jan 14, 2021 at 07:05:21PM -0500, James Valleroy a écrit :
[…]
> While the packaged shaarli is technically usable, it is missing both
> functionality and styling that would be expected by users. Therefore
> it should be kept out of stable releases until this issue is fixed.
Your message dated Wed, 03 Feb 2021 19:33:21 +
with message-id
and subject line Bug#981555: fixed in glib2.0 2.66.4-4
has caused the Debian Bug report #981555,
regarding libglib2.0-0: gnome-keyring unable to unlock login keyring on some
systems since GLib 2.66.4-2
to be marked as done.
This
Your message dated Wed, 03 Feb 2021 19:33:21 +
with message-id
and subject line Bug#981555: fixed in glib2.0 2.66.4-4
has caused the Debian Bug report #981555,
regarding gnome-keyring: unable to connect to D-Bus when using dbus-x11
to be marked as done.
This means that you claim that the
Your message dated Wed, 03 Feb 2021 19:33:21 +
with message-id
and subject line Bug#981420: fixed in glib2.0 2.66.4-4
has caused the Debian Bug report #981420,
regarding gnome-keyring: unable to connect to D-Bus when using dbus-x11
to be marked as done.
This means that you claim that the
Your message dated Wed, 03 Feb 2021 19:33:21 +
with message-id
and subject line Bug#981420: fixed in glib2.0 2.66.4-4
has caused the Debian Bug report #981420,
regarding libglib2.0-0: gnome-keyring unable to unlock login keyring on some
systems since GLib 2.66.4-2
to be marked as done.
This
Processing control commands:
> tag -1 pending
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login
keyring on some systems since GLib 2.66.4-2
Bug #981555 [libglib2.0-0] gnome-keyring: unable to connect to D-Bus when using
dbus-x11
Added tag(s) pending.
Added tag(s)
Control: tag -1 pending
Hello,
Bug #981555 in glib2.0 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 #981555 [libglib2.0-0] gnome-keyring: unable to connect to D-Bus when using
dbus-x11
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login
keyring on some systems since GLib 2.66.4-2
Ignoring request to alter tags of bug
Control: tag -1 pending
Hello,
Bug #981420 in glib2.0 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:
Control: tags -1 + patch
Attached is a simple patch fixing this issue in my local test build.
Adrian Bunk, you marked this bug as pending, are you planning to upload a
fixed version or has this been a mix up in bug numbers like in your other mail
in this bug?
Thanks,
Maxidiff -ur
Processing control commands:
> tags -1 + patch
Bug #975822 [src:pyramid-jinja2] pyramid-jinja2: Missing build dependency on
python3-webtest
Added tag(s) patch.
--
975822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> retitle 981720 eventlet: doc build fails when no resolv.conf
Bug #981720 [python-eventlet] FTBFS: FileNotFoundError: [Errno 2] No such file
or directory: '/etc/resolv.conf'
Changed Bug title to 'eventlet: doc build fails when no resolv.conf'
On 2/3/21 4:10 PM, Ritesh Raj Sarraf wrote:
> On Wed, 2021-02-03 at 14:11 +0100, Thomas Goirand wrote:
>> Hi,
>>
>
> Hi Thomas,
>
>> Could you please explain in which build environment you don't have a
>> resolv.conf file?
>>
>
> In an OBS build environment, where it creates chroots for the
Adrian Bunk writes:
> Source: docknot
> Version: 4.00-1
> Severity: serious
> https://ci.debian.net/data/autopkgtest/testing/amd64/d/docknot/10221864/log.gz
Thank you for relaying those results! I forgot to go explicitly check.
Will fix shortly.
--
Russ Allbery (r...@debian.org)
Processing commands for cont...@bugs.debian.org:
> fixed 964195 1.3.0-1
Bug #964195 [src:guacamole-server] CVE-2020-9497 CVE-2020-9498
Marked as fixed in versions guacamole-server/1.3.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964195:
On Wed, 3 Feb 2021 09:43:30 +0100
Baptiste Beauplat wrote:
[...]
>
> I could open the RM bug on your behalf if you want me to.
>
Thank you, I would appreciate that.
Ciao,
Antonio
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which
Your message dated Wed, 3 Feb 2021 20:06:55 +0200
with message-id <20210203180655.GA14117@localhost>
and subject line Re: Bug#888321: guacamole-server: migrate to freerdp2
has caused the Debian Bug report #888321,
regarding guacamole-server: migrate to freerdp2
to be marked as done.
This means
Your message dated Wed, 3 Feb 2021 20:06:55 +0200
with message-id <20210203180655.GA14117@localhost>
and subject line Re: Bug#888321: guacamole-server: migrate to freerdp2
has caused the Debian Bug report #888321,
regarding Build against freerdp2
to be marked as done.
This means that you claim
Source: fastnetmon
Version: 1.1.4-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fastnetmon.html
...
/build/1st/fastnetmon-1.1.4/src/fast_dpi.cpp: In function
'ndpi_detection_module_struct* init_ndpi()':
Package: erfs
Version: 1.3-1
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/e/erfs/10222343/log.gz
...
autopkgtest [02:03:35]: test upstream-tests: [---
/usr/bin/erfs: line 146: openssl: command not found
/usr/bin/erfs: line 146: openssl: command not
Source: python-javaobj
Version: 0.4.1-1
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-javaobj/10222335/log.gz
...
autopkgtest [02:02:41]: test command2: python3 setup.py test
autopkgtest [02:02:41]: test command2: [---
Traceback (most recent
Your message dated Wed, 03 Feb 2021 17:33:33 +
with message-id
and subject line Bug#981342: fixed in mpich 3.4.1-2
has caused the Debian Bug report #981342,
regarding mpich: autopkgtest failure on s390x
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Source: docknot
Version: 4.00-1
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/d/docknot/10221864/log.gz
...
Test Summary Report
---
t/cli/generate.t (Wstat: 512 Tests: 2 Failed: 0)
Non-zero exit status: 2
Parse errors: Bad plan. You planned
Package: json2file-go
Version: 1.13
Severity: serious
https://piuparts.debian.org/sid/fail/json2file-go_1.13.log
...
Unpacking json2file-go (1.13) ...
Setting up json2file-go (1.13) ...
/var/lib/dpkg/info/json2file-go.postinst: 23: setcap: not found
dpkg: error processing package
Package: chibi-scheme-images
Version: 0.9.1-3
Severity: serious
https://piuparts.debian.org/sid/fail/chibi-scheme-images_0.9.1-3.log
...
Setting up chibi-scheme-images (0.9.1-3) ...
/var/lib/dpkg/info/chibi-scheme-images.postinst: 26: chibi-scheme: not found
dpkg: error processing package
Package: netopeer2
Version: 1.1.39-1
Severity: serious
https://piuparts.debian.org/sid/fail/netopeer2_1.1.39-1.log
...
ERROR: BAD PERMISSIONS
drwxrwxrwx 4 root root 100 Feb 1 03:12 /etc/sysrepo
drwxrwxrwx 3 root root 500 Feb 1 03:12 /etc/sysrepo/data
-rw-rw-rw- 1 root root7 Feb
Package: usbguard
Version: 1.0.0+ds-1
Severity: serious
https://piuparts.debian.org/sid/fail/usbguard_1.0.0+ds-1.log
...
Setting up libusbguard0 (1.0.0+ds-1) ...
Setting up usbguard (1.0.0+ds-1) ...
ERROR: loadFiles: /sys/bus/usb/devices: No such file or directory
dpkg: error processing
Your message dated Wed, 03 Feb 2021 17:04:12 +
with message-id
and subject line Bug#979133: fixed in rails 2:6.0.3.4+dfsg-3
has caused the Debian Bug report #979133,
regarding rails: build failure is silently ignored
to be marked as done.
This means that you claim that the problem has been
Source: apt-clone
Version: 0.4.3
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/i386/a/apt-clone/10238817/log.gz
...
==
ERROR: test_clone_upgrade_synthetic (__main__.TestCloneUpgrade)
test clone upgrade with
Processing commands for cont...@bugs.debian.org:
> archive 937166
Bug #937166 [src:nuitka] nuitka: Python2 removal in sid/bullseye
Bug #966764 [src:nuitka] nuitka: Unversioned Python removal in sid/bullseye
Bug 937166 cannot be archived
> thanks
Stopping processing here.
Please contact me if you
Your message dated Wed, 03 Feb 2021 16:34:16 +
with message-id
and subject line Bug#981681: fixed in python-ansicolors 1.1.8-4
has caused the Debian Bug report #981681,
regarding python3-colors: missing Breaks+Replaces: python3-ansicolors
to be marked as done.
This means that you claim that
Your message dated Wed, 03 Feb 2021 16:34:22 +
with message-id
and subject line Bug#981640: fixed in python-easy-ansi 0.3-4
has caused the Debian Bug report #981640,
regarding python3-easyansi: Missing Breaks and Replaces headers → trying to
overwrite
Processing control commands:
> tag -1 pending
Bug #981640 [python3-easyansi] python3-easyansi: Missing Breaks and Replaces
headers → trying to overwrite
'/usr/lib/python3/dist-packages/easy_ansi-0.3.egg-info/PKG-INFO', which is also
in package python3-easy-ansi 0.3-1
Added tag(s) pending.
--
Control: tag -1 pending
Hello,
Bug #981640 in python-easy-ansi 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:
Your message dated Wed, 03 Feb 2021 16:22:35 +
with message-id
and subject line Bug#981428: fixed in yubikey-manager 4.0.0~a1-1
has caused the Debian Bug report #981428,
regarding python3-fido2: Version 0.9 breaks yubikey-manager
to be marked as done.
This means that you claim that the
Your message dated Wed, 03 Feb 2021 16:22:25 +
with message-id
and subject line Bug#957828: fixed in sparskit 2.0.0-4
has caused the Debian Bug report #957828,
regarding sparskit: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Package: freewheeling
Followup-For: Bug #946863
X-Debbugs-Cc: bill-au...@programmer.net
this RC bug has caused freewheeling to be dropped from [testing]
this week
i have uploaded a patched v0.6.4 to the mentors repo (0.6.4-1.1);
which includes the necessary changes for fluidsynth2 support,
Processing commands for cont...@bugs.debian.org:
> severity 981646 normal
Bug #981646 [libarpack2-dev] arpack: dseupd randomly fails on mips64el arch
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
981646:
Processing commands for cont...@bugs.debian.org:
> forwarded 981646 https://github.com/opencollab/arpack-ng/issues/294
Bug #981646 [libarpack2-dev] arpack: dseupd randomly fails on mips64el arch
Set Bug forwarded-to-address to
'https://github.com/opencollab/arpack-ng/issues/294'.
> thanks
On Wed, 2021-02-03 at 14:11 +0100, Thomas Goirand wrote:
> Hi,
>
Hi Thomas,
> Could you please explain in which build environment you don't have a
> resolv.conf file?
>
In an OBS build environment, where it creates chroots for the target,
on the fly. I haven't thoroughly checked but given the
Package: network-manager
Version: 1.28.0-2+b1
Severity: grave
Tags: newcomer
Justification: renders package unusable
X-Debbugs-Cc: lui...@mailnesia.com
(Alternatively taggable as Severity: critical - see below)
Dear Maintainer,
*** Reporter, please consider answering these questions, where
Source: cyrus-sasl2
Version: 2.1.27+dfsg-2
Followup-For: Bug #955095
Hi,
We've hit this build failure when re-building the package in our
downstream. As it stands now, this issue is also seen on the
Reproducible Builds.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
Your message dated Wed, 03 Feb 2021 13:51:41 +
with message-id
and subject line Bug#956822: fixed in xpra 3.0.9+dfsg1-1.1
has caused the Debian Bug report #956822,
regarding xpra: FTBFS on armel and armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing control commands:
> retitle -1 gnome-keyring: unable to connect to D-Bus when using dbus-x11
Bug #981555 [gnome-keyring] does not appear to respond to DBUS interface anymore
Changed Bug title to 'gnome-keyring: unable to connect to D-Bus when using
dbus-x11' from 'does not appear to
On 2021-02-02 23:42 -0700, Antonio Russo wrote:
> I am looking for a sponsor for my NMU of the "xpra" package, which is blocked
> migrating to testing for the last ~6 months [1] due to a FTBS on armel and
> armhf [2].
>
> Also, I do not have access to arm* hardware to test this on, so, while I
Processing commands for cont...@bugs.debian.org:
> severity 961896 serious
Bug #961896 [src:nuitka] nuitka: Please make another source-only upload to
allow testing migration
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Your message dated Wed, 03 Feb 2021 13:35:21 +
with message-id
and subject line Bug#981673: fixed in puppet-module-puppetlabs-mount-core
1.0.4+dfsg1-2
has caused the Debian Bug report #981673,
regarding puppet-module-puppetlabs-mount-core fails to install
to be marked as done.
This means
Your message dated Wed, 03 Feb 2021 13:34:36 +
with message-id
and subject line Bug#981739: fixed in manpages-posix 2017a-2
has caused the Debian Bug report #981739,
regarding manpages-posix: no-one built the package for debian archive
(non-free, source-only upload)
to be marked as done.
Your message dated Wed, 03 Feb 2021 13:33:37 +
with message-id
and subject line Bug#980844: fixed in libbiblio-isis-perl 0.24-1.3
has caused the Debian Bug report #980844,
regarding src:libbiblio-isis-perl: invalid maintainer address
to be marked as done.
This means that you claim that the
Your message dated Wed, 03 Feb 2021 13:34:42 +
with message-id
and subject line Bug#979052: fixed in nam 1.15-5.2
has caused the Debian Bug report #979052,
regarding src:nam: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> block 981428 by -1
Bug #981428 [python3-fido2] python3-fido2: Version 0.9 breaks yubikey-manager
981428 was not blocked by any bugs.
981428 was not blocking any bugs.
Added blocking bug(s) of 981428: 981742
--
981428:
Hi,
Could you please explain in which build environment you don't have a
resolv.conf file?
Also, could you please send the full build log? Because like this, I
can't tell at which stage this happened. Was it during the build of the
documentation?
Cheers,
Thomas Goirand (zigo)
On Wed, Feb 03, 2021 at 02:58:27PM +0200, Juhani Numminen wrote:
Package: manpages-posix
Version: 2017a-1
Severity: grave
Hello,
The latest upload of manpages-posix was source-only but was not built
on the buildd network either. So, no binaries are available.
I think the text of this lintian
Your message dated Wed, 03 Feb 2021 13:06:22 +
with message-id
and subject line Bug#980773: fixed in python-pysaml2 6.5.1-1
has caused the Debian Bug report #980773,
regarding python-pysaml2: CVE-2021-21238: Processing of invalid SAML XML
documents
to be marked as done.
This means that you
Your message dated Wed, 03 Feb 2021 13:06:22 +
with message-id
and subject line Bug#980772: fixed in python-pysaml2 6.5.1-1
has caused the Debian Bug report #980772,
regarding python-pysaml2: CVE-2021-21239: Unspecified xmlsec1 key-type
preference
to be marked as done.
This means that you
Package: manpages-posix
Version: 2017a-1
Severity: grave
Hello,
The latest upload of manpages-posix was source-only but was not built
on the buildd network either. So, no binaries are available.
I think the text of this lintian tag applies in this case:
Processing control commands:
> tag -1 pending
Bug #980773 [src:python-pysaml2] python-pysaml2: CVE-2021-21238: Processing of
invalid SAML XML documents
Added tag(s) pending.
--
980773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980773
Debian Bug Tracking System
Contact
Processing control commands:
> tag -1 pending
Bug #980772 [src:python-pysaml2] python-pysaml2: CVE-2021-21239: Unspecified
xmlsec1 key-type preference
Added tag(s) pending.
--
980772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980772
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #980773 in python-pysaml2 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:
Control: tag -1 pending
Hello,
Bug #980772 in python-pysaml2 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:
1 - 100 of 135 matches
Mail list logo
