Your message dated Tue, 02 Feb 2021 07:34:15 +
with message-id
and subject line Bug#954303: fixed in tika 1.22-2
has caused the Debian Bug report #954303,
regarding tika: CVE-2020-1950
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Tue, 02 Feb 2021 07:34:15 +
with message-id
and subject line Bug#954302: fixed in tika 1.22-2
has caused the Debian Bug report #954302,
regarding tika: CVE-2020-1951
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Processing control commands:
> tag -1 pending
Bug #949276 [src:python-limits] python-limits: autopkgtest needs update
Added tag(s) pending.
--
949276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #949276 in python-limits 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:
Package: epoptes-client
Severity: serious
Control: forwarded -1 https://github.com/epoptes/epoptes/issues/127
X-Debbugs-Cc: Vagrant Cascadian
Reported upstream, but the short of it is socat 1.7.4.0 (recently
updated in bullseye) defaults to using Server Name Indication (SNI) and
epoptes-client
Processing control commands:
> forwarded -1 https://github.com/epoptes/epoptes/issues/127
Bug #981612 [epoptes-client] epoptes-client: socat[1483] E Failed to set SNI
host ""
Set Bug forwarded-to-address to 'https://github.com/epoptes/epoptes/issues/127'.
--
981612:
Your message dated Tue, 02 Feb 2021 02:37:16 +
with message-id
and subject line Bug#981579: fixed in rust-sequoia-sq 0.24.0-3
has caused the Debian Bug report #981579,
regarding sq: missing Breaks+Replaces: ispell (<< 3.4.00-6.1~)
to be marked as done.
This means that you claim that the
Processing control commands:
> severity 981393 important
Bug #981393 [ltsp] ltsp: Unable to generate image
Severity set to 'important' from 'grave'
> tags 981393 moreinfo
Bug #981393 [ltsp] ltsp: Unable to generate image
Added tag(s) moreinfo.
--
981393:
Control: severity 981393 important
Control: tags 981393 moreinfo
On 2021-01-30, peto wrote:
> Installing packages according to LTSP Documentation and running ltsp image
> command as recommended here: https://ltsp.org/docs/installation/
...
> # ltsp image /
...
> ltsp image /
> Using x86_64 as the
Your message dated Tue, 02 Feb 2021 01:34:45 +
with message-id
and subject line Bug#973082: fixed in python-biplist 1.0.3-3
has caused the Debian Bug report #973082,
regarding python-biplist: FTBFS: dh_auto_test: error: pybuild --test
--test-nose -i python{version} -p "3.9 3.8" returned exit
Processing commands for cont...@bugs.debian.org:
> reopen 852746
Bug #852746 {Done: Debian FTP Masters }
[libllvm7,libllvm9,libllvm10] crash if multiple ICDs dynamically linked to
LLVM: LLVM ERROR: inconsistency in registered CommandLine options
Bug #964810 {Done: Debian FTP Masters }
Your message dated Tue, 02 Feb 2021 00:23:34 +
with message-id
and subject line Bug#981079: fixed in request-tracker4 4.4.4+dfsg-1
has caused the Debian Bug report #981079,
regarding request-tracker4: RT4 does not ship with real ckeditor source
to be marked as done.
This means that you claim
Hello Simon,
Thank you for your efforts!
> Do you have the dbus-user-session package installed?
I had to install it. Indeed, it helps - now gnome-keyring is working fine with
latest package version of libglib.
> If you rely on the ability to have a separate D-Bus session bus per
> X11 display
Processing control commands:
> tag -1 pending
Bug #980192 [ruby2.7] ruby-2.7: autopkgtest regression in testing:
Errno::ENAMETOOLONG: File name too long
Added tag(s) pending.
--
980192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980192
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #980192 in ruby 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 Mon, 01 Feb 2021 23:22:36 +
with message-id
and subject line Bug#980581: fixed in schleuder-cli 0.1.0-4
has caused the Debian Bug report #980581,
regarding schleuder-cli: FTBFS: Could not find 'thor' (~> 0)
to be marked as done.
This means that you claim that the problem
This FTBFS was caused by version 8.1.0 of python3-pil migrating to
testing a couple of weeks ago. There's an upstream bug about this:
https://github.com/OpenTTD/nml/pull/182. Their solution of restricting
the maximum version of pillow won't work for Debian.
Pillow also has an issue open:
Your message dated Mon, 01 Feb 2021 21:55:21 +
with message-id
and subject line Bug#978418: Removed package(s) from unstable
has caused the Debian Bug report #979874,
regarding node-cross-spawn-async: Keep out of testing
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 01 Feb 2021 21:58:18 +
with message-id
and subject line Bug#978618: Removed package(s) from unstable
has caused the Debian Bug report #973119,
regarding odb-api: FTBFS: GribMetaData.h:23:10: fatal error:
eckit/types/Metadata.h: No such file or directory
to be marked
Your message dated Mon, 01 Feb 2021 21:59:21 +
with message-id
and subject line Bug#978710: Removed package(s) from unstable
has caused the Debian Bug report #979039,
regarding python3.8 is scheduled for removal and should not migrate to testing
to be marked as done.
This means that you
Your message dated Mon, 01 Feb 2021 21:52:58 +
with message-id
and subject line Bug#978085: Removed package(s) from unstable
has caused the Debian Bug report #981537,
regarding boinc-app-seti: SETT@home no longer exists
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> fixed -1 1.4.8+dfsg-1
Bug #981404 [zstd] compressed file is world readable, while zstd is running
Marked as fixed in versions libzstd/1.4.8+dfsg-1.
> tag -1 patch
Bug #981404 [zstd] compressed file is world readable, while zstd is running
Added tag(s) patch.
--
Your message dated Mon, 01 Feb 2021 22:00:05 +
with message-id
and subject line Bug#978740: Removed package(s) from unstable
has caused the Debian Bug report #957801,
regarding siproxd: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Control: fixed -1 1.4.8+dfsg-1
Control: tag -1 patch
Greetings,
This critical issue is affecting Stable. Permissions at
compression time are inherited from umask, this may be too
relaxed when handling sensitive files.
Fortunately, this seems to have been fixed upstream around
version 1.4.1.
Your message dated Mon, 01 Feb 2021 21:54:35 +
with message-id
and subject line Bug#978404: Removed package(s) from unstable
has caused the Debian Bug report #912941,
regarding mozjs52: No longer maintained upstream
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 01 Feb 2021 21:55:21 +
with message-id
and subject line Bug#978418: Removed package(s) from unstable
has caused the Debian Bug report #978309,
regarding node-cross-spawn-async: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 1
to be
Your message dated Mon, 01 Feb 2021 22:00:28 +
with message-id
and subject line Bug#978747: Removed package(s) from unstable
has caused the Debian Bug report #978340,
regarding proftpd-mod-dnsbl: FTBFS: Cannot compile mod_dnsbl using prxs
to be marked as done.
This means that you claim that
Your message dated Mon, 01 Feb 2021 22:04:08 +
with message-id
and subject line Bug#978996: Removed package(s) from unstable
has caused the Debian Bug report #977719,
regarding spotweb: CVE-2020-35545
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Package: ledgersmb
Version: 1.6.9+ds-1
Severity: grave
As of version 1.6.0, upstream has split the software over three
directories (lib/, old/bin/ and old/lib/), instead of bin/ and lib/ in
prior versions). The package should have been adapted to this change,
but wasn't completely: the package
Your message dated Mon, 01 Feb 2021 21:59:43 +
with message-id
and subject line Bug#978715: Removed package(s) from unstable
has caused the Debian Bug report #968313,
regarding simpleburn: FTBFS:
libcallbacks.a(callbacks.c.o):./obj-x86_64-linux-gnu/src/./src/simpleburn.h:57:
multiple
Your message dated Mon, 01 Feb 2021 21:55:46 +
with message-id
and subject line Bug#978539: Removed package(s) from unstable
has caused the Debian Bug report #980662,
regarding bro: FTBFS: Error copying file "bloom-filter.bif.bro" to
"/<>/build/scripts/base/bif/bloom-filter.bif.bro".
to be
Your message dated Mon, 01 Feb 2021 21:59:43 +
with message-id
and subject line Bug#978715: Removed package(s) from unstable
has caused the Debian Bug report #929381,
regarding needs cdrecord binary which isn't in Debian
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 01 Feb 2021 21:53:37 +
with message-id
and subject line Bug#978126: Removed package(s) from unstable
has caused the Debian Bug report #978123,
regarding node-postcss-filter-plugins: broken with node-postcss 8.x
to be marked as done.
This means that you claim that the
Your message dated Mon, 01 Feb 2021 21:53:55 +
with message-id
and subject line Bug#978130: Removed package(s) from unstable
has caused the Debian Bug report #979087,
regarding incompatible with node-postcss 8 and unmaintained
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 01 Feb 2021 22:01:54 +
with message-id
and subject line Bug#978979: Removed package(s) from unstable
has caused the Debian Bug report #967141,
regarding gmlive: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 01 Feb 2021 22:20:52 +
with message-id
and subject line Bug#981451: Removed package(s) from unstable
has caused the Debian Bug report #981439,
regarding liblivemedia: includes non-free code from RFC 3550
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 01 Feb 2021 22:17:59 +
with message-id
and subject line Bug#980241: Removed package(s) from unstable
has caused the Debian Bug report #909210,
regarding don't ship automake-1.15 in bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 01 Feb 2021 22:14:59 +
with message-id
and subject line Bug#979342: Removed package(s) from unstable
has caused the Debian Bug report #979223,
regarding src:moblin-icon-theme: invalid maintainer address
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 01 Feb 2021 21:50:32 +
with message-id
and subject line Bug#977879: Removed package(s) from unstable
has caused the Debian Bug report #981540,
regarding dtaus: Service no longer available
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 01 Feb 2021 21:48:48 +
with message-id
and subject line Bug#977644: Removed package(s) from unstable
has caused the Debian Bug report #981539,
regarding cloudprint: Service has been shutdown
to be marked as done.
This means that you claim that the problem has been
Source: nghttp2
Version: 1.42.0-1
Severity: serious
Tags: ftbfs
An arch-only build (but not a full build) of nghttp2 seems to reliably
fail at test util_localtime_date:
| Test: util_localtime_date ...FAILED
| 1. util_test.cc:454 - CU_ASSERT_STRING_EQUAL("02/Oct/2001:00:34:56
Your message dated Mon, 01 Feb 2021 22:43:45 +0100
with message-id <558db823ca4a04f9caf628a9b5ca7...@debian.org>
and subject line Re: dolfin: FTBFS: tests failed
has caused the Debian Bug report #980709,
regarding dolfin: FTBFS: tests failed
to be marked as done.
This means that you claim that
Your message dated Mon, 01 Feb 2021 21:43:04 +
with message-id
and subject line Bug#977475: Removed package(s) from unstable
has caused the Debian Bug report #969623,
regarding gnome-shell-extension-show-ip: load fails: ReferenceError: None is
not defined
to be marked as done.
This means
Your message dated Mon, 01 Feb 2021 21:35:25 +
with message-id
and subject line Bug#974788: Removed package(s) from unstable
has caused the Debian Bug report #975931,
regarding libgpuarray autopkgtest using pocl on armhf triggers segfault in LLVM
to be marked as done.
This means that you
Your message dated Mon, 01 Feb 2021 21:29:21 +
with message-id
and subject line Bug#969473: Removed package(s) from unstable
has caused the Debian Bug report #956881,
regarding enchant: Keep out of bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 01 Feb 2021 21:23:51 +
with message-id
and subject line Bug#960761: Removed package(s) from unstable
has caused the Debian Bug report #960748,
regarding node-babel: meta bug to keep out of testing
to be marked as done.
This means that you claim that the problem has
On 2/1/21 8:56 PM, Paul Gevers wrote:
> On 21-01-2021 16:33, Paolo Greppi wrote:
>> pocl 1.6-3 has migrated to testing on 2021-01-13, and upstream declares
>> that v1.6 includes "Support for Clang/LLVM 11".
>
> And the autopkgtest doesn't fail anymore indeed.
Because we are back to LLVM 9, due
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
Hi Paolo,
On 21-01-2021 16:33, Paolo Greppi wrote:
> pocl 1.6-3 has migrated to testing on 2021-01-13, and upstream declares
> that v1.6 includes "Support for Clang/LLVM 11".
And the autopkgtest doesn't fail anymore indeed.
> Can you try your reproducer now ?
I *expect* it to reproduce the
Processing commands for cont...@bugs.debian.org:
> # arch: all buildds run amd64
> severity 976907 normal
Bug #976907 [src:golang-github-boltdb-bolt] golang-github-boltdb-bolt: FTBFS on
ppc64el (arch:all-only src pkg): dh_auto_test: error: cd
obj-powerpc64le-linux-gnu && go test -vet=off -v -p
Processing commands for cont...@bugs.debian.org:
> # arch: all buildds run amd64
> severity 976945 important
Bug #976945 [src:ruby-awesome-print] ruby-awesome-print: FTBFS on ppc64el
(arch:all-only src pkg): ERROR: Test "ruby2.7" failed: [31mFailure/Error:
expect(my.ai(plain: true)).to
Hi again,
Am Mon, Feb 01, 2021 at 07:54:51PM +0100 schrieb Carsten Schoenert:
> > the problem tends to be getting arduino-mk updated, think last time it
> > needed a team upload (python3 fixes).
>
> If you need help let me know, currently I can't that Python3 fixes you
> mean.
hrhr, I need to
Processing commands for cont...@bugs.debian.org:
> # arch: all buildds run amd64
> severity 976937 normal
Bug #976937 [src:python-trio] python-trio: FTBFS on ppc64el (arch:all-only src
pkg): E: Build killed with signal TERM after 150 minutes of inactivity
Severity set to 'normal' from 'serious'
Great! Then it sounds like it should be included. It is a Python Team package
and the source code is on salsa, so feel free to go ahead and upload.
Your message dated Mon, 01 Feb 2021 19:19:11 +
with message-id
and subject line Bug#979051: fixed in aspell-hr 0.51-5
has caused the Debian Bug report #979051,
regarding src:aspell-hr: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been dealt
Hi Julien,
Thanks for pushing the changes to buster. Will this get backported to stretch
as well? If so, what is the timeframe users can expect?
> I'm not sure why this is blowing up again this week
See https://github.com/NuGet/Announcements/issues/49 for details on how this
affected
Hello Simon,
you need to add me to the recipients please, then I get the emails for
this report too. :)
Am Fri, Jan 29, 2021 at 12:22:18PM + schrieb Simon John:
> Hello Carsten,
>
> i rebuilt arduino-mk and removed its Depends and it worked, so changing it
> to "arduino-core (>=
Processing control commands:
> reassign -1 geoclue-2.0
Bug #892275 [redshift] redshift: Unable to connect to GeoClue.
Bug reassigned from package 'redshift' to 'geoclue-2.0'.
No longer marked as found in versions redshift/1.12-4, redshift/1.11-2, and
redshift/1.11-1.
Ignoring request to alter
Control: reassign -1 geoclue-2.0
Control: affects -1 redshift
Hi Gabriel, Mike, and Nicolas,
On Thu, Jan 07, 2021 at 09:14:46PM +, Mike Gabriel wrote:
> On Do 07 Jan 2021 22:03:11 CET, Debian Bug Tracking System wrote:
>
> > Package: redshift-gtk
> > Version: 1.12-4
> > Followup-For: Bug
Your message dated Mon, 01 Feb 2021 18:34:15 +
with message-id
and subject line Bug#981270: fixed in chromium 88.0.4324.96-2
has caused the Debian Bug report #981270,
regarding chromium: FTBFS after libopenjp2-7-dev upgrade
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> severity 981270 serious
Bug #981270 [chromium] chromium: FTBFS after libopenjp2-7-dev upgrade
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
981270:
Package: sq
Version: 0.24.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages
Your message dated Mon, 01 Feb 2021 17:26:11 +
with message-id
and subject line Bug#980576: fixed in mercurial 5.6.1-2
has caused the Debian Bug report #980576,
regarding mercurial: autopkgtest needs update for new version of git
to be marked as done.
This means that you claim that the
Your message dated Mon, 01 Feb 2021 17:26:11 +
with message-id
and subject line Bug#980576: fixed in mercurial 5.6.1-2
has caused the Debian Bug report #980576,
regarding mercurial autopkgtest breaks with newer git
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package sopel
> # 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.org
Setting
Package: ghdl-common
Version: 0.37+dfsg2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite
Processing control commands:
> tag -1 pending
Bug #980576 [src:mercurial] mercurial: autopkgtest needs update for new version
of git
Bug #981508 [src:mercurial] mercurial autopkgtest breaks with newer git
Added tag(s) pending.
Added tag(s) pending.
--
980576:
Control: tag -1 pending
Hello,
Bug #980576 in mercurial 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 commands for cont...@bugs.debian.org:
> reassign 981508 src:mercurial
Bug #981508 [mercurial] mercurial autopkgtest breaks with newer git
Bug reassigned from package 'mercurial' to 'src:mercurial'.
No longer marked as found in versions mercurial/5.6.1-1.
Ignoring request to alter fixed
Processing commands for cont...@bugs.debian.org:
> forcemerge 980576 981508
Bug #980576 [src:mercurial] mercurial: autopkgtest needs update for new version
of git
Unable to merge bugs because:
package of #981508 is 'mercurial' not 'src:mercurial'
Failed to forcibly merge 980576: Did not alter
Processing control commands:
> tag -1 upstream fixed-upstream patch
Bug #980576 [src:mercurial] mercurial: autopkgtest needs update for new version
of git
Added tag(s) fixed-upstream, patch, and upstream.
--
980576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980576
Debian Bug Tracking
Control: tag -1 upstream fixed-upstream patch
On Mon, Feb 01, 2021 at 05:42:04PM +0100, Julien Cristau wrote:
> On Mon, Feb 01, 2021 at 08:14:13AM -0800, Steve Langasek wrote:
> > Package: mercurial
> > Version: 5.6.1-1
> > Followup-For: Bug #980576
> > User: ubuntu-de...@lists.ubuntu.com
> >
On Mon, Feb 01, 2021 at 08:14:13AM -0800, Steve Langasek wrote:
> Package: mercurial
> Version: 5.6.1-1
> Followup-For: Bug #980576
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu hirsute ubuntu-patch
>
> Dear maintainers,
>
> Attached is a patch that makes the mercurial test
Your message dated Mon, 01 Feb 2021 16:37:28 +
with message-id
and subject line Bug#980602: fixed in libxcb 1.14-3
has caused the Debian Bug report #980602,
regarding libxcb: FTBFS: ../../tests/check_public.c:40:24: error: too many
arguments for format [-Werror=format-extra-args]
to be
Your message dated Mon, 01 Feb 2021 16:36:58 +
with message-id
and subject line Bug#980202: fixed in imagemagick 8:6.9.11.60+dfsg-1
has caused the Debian Bug report #980202,
regarding FTBFS: gscan2pdf tests fail
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 01 Feb 2021 16:34:34 +
with message-id
and subject line Bug#980189: fixed in flask-security 4.0.0-1
has caused the Debian Bug report #980189,
regarding flask-security: CVE-2021-21241
to be marked as done.
This means that you claim that the problem has been dealt with.
Re: Gregor Riepl
> If this is true and the failures are really only code style issues, I
> would suggest to silence the unit test and be done with it.
>
> But it does look a bit more serious from the error messages.
Well if it's really *that* serious I'd expect cura not to start.
> Here's a
Processing control commands:
> reopen -1
Bug #948739 {Done: Phillip Susi } [gparted] gparted should
not mask .mount units
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as
Control: reopen -1
Ivo De Decker writes:
> This new upstream version doesn't remove the code masking the systemd units.
> It just changes it a little. So it doesn't fix this bug.
Woops... you're right.
Hi Michael,
stretch is EOL, so I am not planning on touching it myself.
Cc:ing the team that looks after stretch-lts in case they want to handle
this.
Cheers,
Julien
On Mon, Feb 01, 2021 at 03:14:38PM +, Michael Simons (.NET) wrote:
> Hi Julien,
>
>
>
> Thanks for pushing the changes
Package: mercurial
Version: 5.6.1-1
Followup-For: Bug #980576
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Dear maintainers,
Attached is a patch that makes the mercurial test suite compatible with both
the old and new git behavior. It has been uploaded to
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 first (pyls-server,
> pyls-black, pyls-spyder, abydos, textdistance); once
Processing commands for cont...@bugs.debian.org:
> severity 981278 important
Bug #981278 [subdownloader] subdownloader: Crashes when trying to download
subtitle
Severity set to 'important' from 'grave'
> tags 981278 + confirmed
Bug #981278 [subdownloader] subdownloader: Crashes when trying to
Your message dated Mon, 01 Feb 2021 15:20:46 +
with message-id
and subject line Bug#948739: fixed in gparted 1.2.0-1
has caused the Debian Bug report #948739,
regarding gparted should not mask .mount units
to be marked as done.
This means that you claim that the problem has been dealt with.
Hi Hans-Christoph (2021.02.01_10:27:12_+)
> Do the tests pass with this patch?
Yes.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
Processing commands for cont...@bugs.debian.org:
> retitle 981420 libglib2.0-0: gnome-keyring unable to unlock login keyring on
> some systems since GLib 2.66.4-2
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login
keyring
Changed Bug title to 'libglib2.0-0:
Processing commands for cont...@bugs.debian.org:
> tags 99 + pending
Bug #99 [src:webkit2gtk] geary FTBFS on mipsel: test suite failure
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
99:
On Mon, Feb 01, 2021 at 01:34:46PM +, PICCA Frederic-Emmanuel wrote:
> > I have a package of Spyder 4 waiting to upload, but it requires five
> > packages to be accepted into unstable from NEW first (pyls-server,
> > pyls-black, pyls-spyder, abydos, textdistance); once that happens, the
> >
> Strangely enough, I've already done that ;-)
my bad.
Cheers
Fred
Processing commands for cont...@bugs.debian.org:
> found 980338 0.4.0-15.1
Bug #980338 [src:hotswap] hotswap: should ship with bullseye?
Marked as found in versions hotswap/0.4.0-15.1.
> found 980348 0.1.3-5.1
Bug #980348 [src:ruby-wirble] ruby-wirble: ship with bullseye?
Marked as found in
> I have a package of Spyder 4 waiting to upload, but it requires five
> packages to be accepted into unstable from NEW first (pyls-server,
> pyls-black, pyls-spyder, abydos, textdistance); once that happens, the
> rest of the packages are almost ready to go.
Maybe you can contact the ftpmaster
On Mon, Feb 01, 2021 at 04:21:15PM +0530, Nilesh Patra wrote:
> Hi Julian,
>
> On Sun, 13 Dec 2020 06:58:29 + Julian Gilbey wrote:
> > On Mon, Dec 07, 2020 at 05:38:26PM +0200, Adrian Bunk wrote:
> > > Package: spyder
> > > Version: 3.3.6+dfsg1-5
> > > Severity: serious
> > >
> > > Since
Your message dated Mon, 01 Feb 2021 12:18:55 +
with message-id
and subject line Bug#981562: fixed in python-django 2:2.2.18-1
has caused the Debian Bug report #981562,
regarding python-django: CVE-2021-3281
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> found 981562 2:2.2.17-2
Bug #981562 [python-django] python-django: CVE-2021-3281
There is no source info for the package 'python-django' at version '2:2.2.17-2'
with architecture ''
Unable to make a source version for version '2:2.2.17-2'
Marked
Package: python-django
Version: 1.7.11-1+deb8u10
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for python-django:
CVE-2021-3281[0]
https://www.djangoproject.com/weblog/2021/feb/01/security-releases/
At a first glance,
Your message dated Mon, 01 Feb 2021 11:34:01 +
with message-id
and subject line Bug#980637: fixed in git-buildpackage 0.9.22
has caused the Debian Bug report #980637,
regarding git-buildpackage: FTBFS: AttributeError: 'str' object has no
attribute 'decode'
to be marked as done.
This means
Your message dated Mon, 01 Feb 2021 11:34:01 +
with message-id
and subject line Bug#980256: fixed in git-buildpackage 0.9.22
has caused the Debian Bug report #980256,
regarding git-buildpackage: autopkgtest armhf regression: /usr/bin/python: not
found
to be marked as done.
This means that
Hi,
On Sun, Jan 31, 2021 at 11:41:07PM +0100, Jochen Sprickerhof wrote:
> * Guido Günther [2021-01-31 13:19]:
> > Awesome. I had fixed the rpm parts here already
> > https://github.com/agx/git-buildpackage/tree/rpm but went for your
> > patches so your work is not lost. The reason i wrote 'tip of
Hi Julian,
On Sun, 13 Dec 2020 06:58:29 + Julian Gilbey wrote:
> On Mon, Dec 07, 2020 at 05:38:26PM +0200, Adrian Bunk wrote:
> > Package: spyder
> > Version: 3.3.6+dfsg1-5
> > Severity: serious
> >
> > Since binNMUs are not possible for binary-all packages,
> > a source upload is needed for
Hi Julian,
On Sun, 13 Dec 2020 06:58:29 + Julian Gilbey wrote:
> On Mon, Dec 07, 2020 at 05:38:26PM +0200, Adrian Bunk wrote:
> > Package: spyder
> > Version: 3.3.6+dfsg1-5
> > Severity: serious
> >
> > Since binNMUs are not possible for binary-all packages,
> > a source upload is needed for
1 - 100 of 115 matches
Mail list logo
