Processing commands for cont...@bugs.debian.org:
> tags 921365 + buster sid
Bug #921365 [node-async-stacktrace] Not suitable for buster, package probably
unmaintained
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921365:
Processing commands for cont...@bugs.debian.org:
> tags 921360 + buster sid
Bug #921360 [node-base64id] No suitable for buster, package probably
unmaintained
Bug #921368 [node-base64id] Not suitable for buster, package probably
unmaintained
Ignoring request to alter tags of bug #921360 to the
Processing commands for cont...@bugs.debian.org:
> tags 921363 + buster sid
Bug #921363 [src:ejs.js] Not suitable for buster, package unmaintained
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921363:
Processing commands for cont...@bugs.debian.org:
> tags 921362 + buster sid
Bug #921362 [src:bignumber.js] Not suitable for buster, package unmaintained
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921362:
Processing commands for cont...@bugs.debian.org:
> tags 921367 + buster sid
Bug #921367 [src:unorm.js] Not suitable for buster, package probably
unmaintained
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921367:
Processing commands for cont...@bugs.debian.org:
> tags 921358 + buster sid
Bug #921358 [node-yajsml] Not suitable for buster, package probably unmaintained
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921358:
Processing commands for cont...@bugs.debian.org:
> tags 921359 + buster sid
Bug #921359 [node-security] Not suitable for buster, package probably
unmaintained
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921359:
Processing commands for cont...@bugs.debian.org:
> tags 921366 + buster sid
Bug #921366 [src:zeparser.js] Not suitable for buster, package probably
unmaintained
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921366:
Processing commands for cont...@bugs.debian.org:
> tags 921364 + buster sid
Bug #921364 [node-active-x-obfuscator] Not suitable for buster, package
unmaintained
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921364:
Processing commands for cont...@bugs.debian.org:
> tags 921356 + buster sid
Bug #921356 {Done: Xavier Guimard } [node-tinycolor] Not
suitable for buster, package probably unmaintained
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> tags 921369 + buster sid
Bug #921369 [node-xmlhttprequest] Not suitable for buster, package probably
unmaintained
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921369:
Processing commands for cont...@bugs.debian.org:
> tags 921370 + buster sid
Bug #921370 [src:yamm3] Not suitable for buster, package probably unmaintained
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921370:
Processing commands for cont...@bugs.debian.org:
> tags 921371 + buster sid
Bug #921371 [node-log4js] Not suitable for buster, package probably unmaintained
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921371:
Processing control commands:
> reopen -1
Bug #915657 {Done: Helge Kreutzmann }
[src:google-android-installers] google-android-installers NMU binaries cannot
be installed due to unchanged version of the binary packages
'reopen' may be inappropriate when a bug has been closed with a version;
all
Control: reopen -1
On Mon, Feb 04, 2019 at 12:36:08PM +, Debian Bug Tracking System wrote:
>...
> google-android-installers (1472023576+nmu2) unstable; urgency=medium
> .
>* Non-maintainer upload
>* Explicitly increment version numbers. Closes: #915657.
>...
Your upload included
Control: tag -1 pending
Hello,
Bug #921369 in node-xmlhttprequest 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:
Hi Andreas,
I've added Conflicts: lines, as that seemed to be the most conservative
option to me. ("Replaces: quagga" is a 'layer 9' discussion that I
think it's a bit early to have at this point.)
If you have any comments/opinions/input, I'd appreciate that.
Diff is at:
Hi Xavier,
On Monday, 4 February 2019, Xavier Guimard wrote:
> Control: tag -1 pending
>
> Hello,
>
> Bug #921369 in node-xmlhttprequest 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
Processing commands for cont...@bugs.debian.org:
> reassign 909165 linkchecker
Bug #909165 [linkchecker-gui] linkchecker-gui: linkcheker-gui does not start
Bug reassigned from package 'linkchecker-gui' to 'linkchecker'.
No longer marked as found in versions linkchecker/9.3-4.
Ignoring request to
Hi David,
On 2019-02-04 22:01, David Lamparter wrote:
> I've added Conflicts: lines, as that seemed to be the most conservative
> option to me. ("Replaces: quagga" is a 'layer 9' discussion that I
> think it's a bit early to have at this point.)
>
> If you have any comments/opinions/input, I'd
Your message dated Mon, 04 Feb 2019 19:36:46 +
with message-id
and subject line Bug#921356: fixed in node-tinycolor 0.0.1-1
has caused the Debian Bug report #921356,
regarding Not suitable for buster, package probably unmaintained
to be marked as done.
This means that you claim that the
Processing control commands:
> merge 909165 901780
Bug #909165 [linkchecker-gui] linkchecker-gui: linkcheker-gui does not start
Unable to merge bugs because:
done of #901780 is 'Antoine Beaupré ' not ''
package of #901780 is 'linkchecker' not 'linkchecker-gui'
Failed to merge 909165: Did not
Your message dated Mon, 04 Feb 2019 19:49:40 +
with message-id
and subject line Bug#915023: fixed in horizon 3:14.0.2-1
has caused the Debian Bug report #915023,
regarding openstack-dashboard: fails to install in buster along
python3-senlin-dashboard
to be marked as done.
This means that
Control: merge 909165 901780
This is a duplicate of #901780 which was reported in june 2018 and
fixed, although no fix has been done in stretch yet.
A.
On Wed, Sep 19, 2018 at 09:40:28AM +0200, jEsuSdA wrote:
> Package: linkchecker-gui
> Version: 9.3-4
> Severity: important
>
> Dear
Processing control commands:
> merge 909165 901780
Bug #909165 [linkchecker-gui] linkchecker-gui: linkcheker-gui does not start
Unable to merge bugs because:
done of #901780 is 'Antoine Beaupré ' not ''
package of #901780 is 'linkchecker' not 'linkchecker-gui'
Failed to merge 909165: Did not
Processing control commands:
> tags 920645 + pending
Bug #920645 [src:libgd2] libgd2: CVE-2019-6977
Added tag(s) pending.
> tags 920728 + patch
Bug #920728 [src:libgd2] libgd2: CVE-2019-6978
Added tag(s) patch.
> tags 920728 + pending
Bug #920728 [src:libgd2] libgd2: CVE-2019-6978
Added tag(s)
Control: tags 920645 + pending
Control: tags 920728 + patch
Control: tags 920728 + pending
Dear maintainer,
I've prepared an NMU for libgd2 (versioned as 2.2.5-5.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru
Processing control commands:
> tags 920645 + pending
Bug #920645 [src:libgd2] libgd2: CVE-2019-6977
Ignoring request to alter tags of bug #920645 to the same tags previously set
> tags 920728 + patch
Bug #920728 [src:libgd2] libgd2: CVE-2019-6978
Ignoring request to alter tags of bug #920728 to
Processing commands for cont...@bugs.debian.org:
> unarchive 901780
Bug #901780 {Done: Antoine Beaupré } [linkchecker]
linkchecker: Should depend on python-xdg
Unarchived Bug 901780
> reopen 901780
Bug #901780 {Done: Antoine Beaupré } [linkchecker]
linkchecker: Should depend on python-xdg
On Mon, Feb 04, 2019 at 03:04:41PM +0100, Markus Koschany wrote:
> I would add a NEWS file to OpenJDK 8 and explain the situation and in
> addition create a wrapper around the OpenJDK 8 java command that prints
> out a message and quits. javac shall continue to work because it is
> needed to build
On Mon, Feb 04, 2019 at 05:49:24PM +, PICCA Frederic-Emmanuel wrote:
> The upstream, Just packages the latest taurus.
>
> So I think that you can defer your upload now.
Thanks, I've cancelled my NMU.
> thanks a lot for your help.
>
> Frederic
cu
Adrian
--
"Is there not promise
Hi Andreas,
So I improved the upstream libmurmurhash, adapted the package and filed
an ITP (#921353). I even managed to locally build mash against the new
package. So hereby I kindly ask you to fix the last lintian issue about
NMU which I don't fully understand and then maybe sponsor an
Source: libpng1.6
Version: 1.6.36-3
Severity: grave
Tags: security upstream
Forwarded: https://github.com/glennrp/libpng/issues/275
Control: found -1 1.6.28-1
Control: found -1 1.6.36-2
Hi,
The following vulnerability was published for libpng1.6.
CVE-2019-7317[0]:
| png_image_free in png.c in
Processing control commands:
> found -1 1.6.28-1
Bug #921355 [src:libpng1.6] libpng1.6: CVE-2019-7317: use-after-free in
png_image_free in png.c
Marked as found in versions libpng1.6/1.6.28-1.
> found -1 1.6.36-2
Bug #921355 [src:libpng1.6] libpng1.6: CVE-2019-7317: use-after-free in
Source: unorm.js
Version: 1.0.5-1
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked by
Source: yamm3
Version: 1.1.0+dfsg1-1
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked by
Package: node-log4js
Version: 0.6.18-1
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked
Package: node-async-stacktrace
Version: 0.0.2-2
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be
Package: node-xmlhttprequest
Version: 1.6.0-1
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be
This is used in: flashproxy (popcon 25), node-d3-request (popcon 2),
node-xmlhttprequest-ssl (popcon 14)
Paolo
Il 04/02/19 17:35, Mike Gabriel ha scritto:
> Package: node-xmlhttprequest
> Version: 1.6.0-1
> Severity: serious
>
> Dear all,
>
> In 2016/12 I removed my name from this package's
This is used in node-ws (popcon 92)
Paolo
Control: tag -1 pending
Hello,
Bug #920337 in python-igraph 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 #920337 [python3-igraph] python3-igraph: ships header in
/usr/include/python3.7/
Added tag(s) pending.
--
920337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> forwarded 921227 https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4218
Bug #921227 [dnssec-trigger] dnssec-trigger: crashes (SIGSEGV)
Set Bug forwarded-to-address to
'https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4218'.
> thanks
Package: node-security
Version: 1.0.0~git20130515-2
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to
Source: bignumber.js
Version: 1.3.0+dfsg-1
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be
Package: node-yajsml
Version: 1.1.5-2
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked by
Source: node-clean-css
Version: 1.0.12-2
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked
Package: node-base64id
Version: 0.1.0-3
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked
Package: node-dequeue
Version: 1.0.5-1
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked
Source: ejs.js
Version: 1.0.0+dfsg1-1
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked by
Package: node-base64id
Version: 0.1.0-3
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked
Package: node-active-x-obfuscator
Version: 0.0.2-1
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to
Source: zeparser.js
Version: 0.0.7+dfsg-1
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs to be
Package: node-tinycolor
Version: 0.0.1~git20130725-1
Severity: serious
Dear all,
In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.
Due to this, the package might not be suitable for the Debian buster
release. This needs
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:matplotlib2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Processing commands for cont...@bugs.debian.org:
> found 909165 9.3-4
Bug #909165 [linkchecker] linkchecker-gui: linkcheker-gui does not start
Bug #901780 [linkchecker] linkchecker: Should depend on python-xdg
Marked as found in versions linkchecker/9.3-4.
Marked as found in versions
Hi Fabian,
On Mon, Feb 04, 2019 at 05:26:08PM +0100, Fabian Klötzl wrote:
> So I improved the upstream libmurmurhash, adapted the package and filed an
> ITP (#921353). I even managed to locally build mash against the new package.
Thanks a lot - that's really cool.
> So hereby I kindly ask you
Your message dated Mon, 04 Feb 2019 21:38:22 +
with message-id
and subject line Bug#921369: fixed in node-xmlhttprequest 1.8.0-1
has caused the Debian Bug report #921369,
regarding Not suitable for buster, package probably unmaintained
to be marked as done.
This means that you claim that the
Your message dated Mon, 04 Feb 2019 21:47:13 +
with message-id
and subject line Bug#916034: fixed in sl-modem 2.9.11~20110321-12+deb9u1
has caused the Debian Bug report #916034,
regarding sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64
to be marked as done.
This means that you
Your message dated Mon, 04 Feb 2019 21:47:14 +
with message-id
and subject line Bug#773720: fixed in sox 14.4.1-5+deb9u1
has caused the Debian Bug report #773720,
regarding sox: CVE-2014-8145
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Mon, 04 Feb 2019 21:47:08 +
with message-id
and subject line Bug#774527: fixed in arc 5.21q-4+deb9u1
has caused the Debian Bug report #774527,
regarding arc: CVE-2015-9275: directory traversal
to be marked as done.
This means that you claim that the problem has been dealt
Hi Felipe,
Felipe Sateler wrote:
> > > Upstream asks if cgroup is in v2-mode in the affected systems.
> With `findmnt -R /sys/fs/cgroup`. It should list controllers in the cgroup
> or cgroup2 filesystems.
root@lorenz:~# findmnt -R /sys/fs/cgroup
TARGET SOURCE FSTYPE
On Mon, Feb 04, 2019 at 04:36:22PM +0100, Andreas Tille wrote:
> Hi Adrian,
>
> On Mon, Feb 04, 2019 at 01:06:35PM +0200, Adrian Bunk wrote:
> > >Bug#916576: pbdagcon: FTBFS pbdata/Types.h: No such file or directory
> > >
> > > I need to make some noise in the team since I'm definitely
On 2019, ഫെബ്രുവരി 4 1:20:11 PM IST, Chris Lamb wrote:
>Hi,
>
>> redis-server service is failing to start in buster lxc container
>
>Any update on this? :)
I'm traveling. hopefully tonight or tomorrow night I can try.
Adding Raju, and Abhijith, who may be able to try this before.
>
>Regards,
Dear all,
As one of the developers of ProbABEL I can confirm this is a rounding
error. We have had similar problems in the past. The test run by make is
simply diff-ing the output of a test run with a 'known good' file. Back
when ProbABEL was still actively developed, I tried my best to maintain
Your message dated Mon, 04 Feb 2019 08:45:01 +
with message-id
and subject line Bug#921316: fixed in python-sqt 0.8.0-3
has caused the Debian Bug report #921316,
regarding python3-sqt: Depends: python3 (< 3.6) but 3.7.2-1 is to be installed
to be marked as done.
This means that you claim
Your message dated Mon, 04 Feb 2019 08:45:07 +
with message-id
and subject line Bug#915266: fixed in python-wither 1.1-2
has caused the Debian Bug report #915266,
regarding python-wither FTBFS with Pyrhon 3.7
to be marked as done.
This means that you claim that the problem has been dealt
Hi Florian,
> It's probably a bit late in the release cycle to "just find out" by
> uploading a -2 with that modified patch.
... but its even worse to do nothing since this is an RC bug and this
package as well as its rdepends would be excluded from next release if
the bug is not fixed.
Kind
Your message dated Mon, 04 Feb 2019 09:34:23 +
with message-id
and subject line Bug#921271: fixed in buildbot 2.0.0-1
has caused the Debian Bug report #921271,
regarding buildbot: CVE-2019-7313: CRLF injection in Buildbot login and logout
redirect code
to be marked as done.
This means that
Source: ruby-rspec-rails
Version: 3.8.1-2
Severity: serious
Tags: ftbfs
Control: block -1 by 900156
ruby-rspec-rails build depends on ruby-capybara (>= 2.15~)
that is currently not in buster due to #900156.
On Mon, 04 Feb 2019 08:43:08 +0200 Adrian Bunk wrote:
> Source: samtools
> Version: 1.9-2
> Severity: serious
> Tags: patch
>
> SSE is not part of the i386 baseline, fix:
>
> --- debian/rules.old 2019-02-03 20:43:51.747130097 +
> +++ debian/rules 2019-02-03 20:44:04.383129977 +
> @@ -5,7
Hi Adrian,
On Mon, Feb 04, 2019 at 09:01:55AM +0200, Adrian Bunk wrote:
> The following packages have unmet dependencies:
> python3-sqt : Depends: python3 (< 3.6) but 3.7.2-1 is to be installed
>
> Was this binary built in an old/outdated chroot with Python 3.6
> as default?
I'm always using
Processing control commands:
> block -1 by 900156
Bug #921320 [src:ruby-rspec-rails] ruby-rspec-rails build depends on
ruby-capybara (>= 2.15~) that is currently not in buster
921320 was not blocked by any bugs.
921320 was not blocking any bugs.
Added blocking bug(s) of 921320: 900156 and 907022
Source: astropy-healpix
Version: 0.4-4
Severity: serious
Tags: ftbfs patch
https://buildd.debian.org/status/fetch.php?pkg=astropy-healpix=i386=0.4-4=1548693347=0
...
=== FAILURES ===
___ test_boundaries
Processing control commands:
> severity 921295 important
Bug #921295 [src:wcslib] wcslib: FTBFS with upcoming doxygen 1.8.15
Severity set to 'important' from 'serious'
> severity -1 normal
Bug #919413 [sponsorship-requests] RFS: doxygen/1.8.15-1 [ITA]
Severity set to 'normal' from 'important'
--
Your message dated Mon, 04 Feb 2019 09:20:37 +
with message-id
and subject line Bug#921185: fixed in picard-tools 2.18.25+dfsg-2
has caused the Debian Bug report #921185,
regarding picard-tools should become Architecture: amd64
to be marked as done.
This means that you claim that the problem
On 2019-02-04 01:04, Paolo Greppi wrote:
> Source: ccfits
> Severity: serious
>
> Dear Maintainer,
>
> I tested your package against a draft package for doxygen 1.8.15:
> https://bugs.debian.org/919413
>
> and it FTBFS with this error:
> make[2]: *** [Makefile:8: refman.pdf] Error 1
>
That
101 - 178 of 178 matches
Mail list logo
