Your message dated Tue, 05 Feb 2019 07:39:13 +
with message-id
and subject line Bug#903406: fixed in gridengine 8.1.9+dfsg-9
has caused the Debian Bug report #903406,
regarding gridengine: FTBFS on armhf due to OpenJDK VM changes
to be marked as done.
This means that you claim that the
On 05/02/2019 07:23, Stephen Gelman wrote:
>> Ouch. More reason to hold the upgrade then.
>
> Sorry, I think you misinterpret what I mean: 0.34.1 works perfectly out of
> the box, I was referring to trying to get 0.9.0 working. At this point there
> have already been 7 debian revisions of
> On Feb 5, 2019, at 1:17 AM, Martín Ferrari wrote:
>
> On 05/02/2019 06:41, Stephen Gelman wrote:
>
>> I totally understand your concern. I’m at least a few backported bug fixes
>> deep and I am concerned the resulting package will have had so many changes
>> applied that it will be a bit
And then there is the unrelated #908269 that currently prevents testing
migration of pbbam.
Steve seems to be addressing this with
http://launchpadlibrarian.net/409374477/pbbam_0.19.0+dfsg-1ubuntu3_0.19.0+dfsg-1ubuntu4.diff.gz
Adrian
On Tue, Feb 05, 2019 at 12:04:16AM +0200, Adrian Bunk
On 05/02/2019 06:41, Stephen Gelman wrote:
> I totally understand your concern. I’m at least a few backported bug fixes
> deep and I am concerned the resulting package will have had so many changes
> applied that it will be a bit of a mess.
Ouch. More reason to hold the upgrade then.
> As a
> On Feb 4, 2019, at 11:59 PM, Martín Ferrari wrote:
>
> On 05/02/2019 04:44, Stephen Gelman wrote:
>
>> I have 0.34.1 almost ready to upload - just waiting on two deps to clear NEW.
>
> Sorry to be a killjoy, but are you sure a new version is needed to solve
> this problem? We are very close
Your message dated Tue, 05 Feb 2019 06:15:54 +
with message-id
and subject line Bug#920346: fixed in prometheus-postgres-exporter 0.4.7+ds-1
has caused the Debian Bug report #920346,
regarding prometheus-postgres-exporter: Incompatible with postgresql 11, "B"
suffix for bytes
to be marked as
On 05/02/2019 04:44, Stephen Gelman wrote:
> I have 0.34.1 almost ready to upload - just waiting on two deps to clear NEW.
Sorry to be a killjoy, but are you sure a new version is needed to solve
this problem? We are very close to the freeze, and way too many packages
depend on this. I am
> On Jan 21, 2019, at 9:14 AM, Adrian Bunk wrote:
>
> Source: golang-google-cloud
> Version: 0.9.0-7
> Severity: serious
> Tags: ftbfs
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-google-cloud.html
>
> ...
> dh_auto_build
> cd build && go install
>
On Sat, 2 Feb 2019 15:50:48 +0100 Mattia Rizzolo wrote:
> Source: qmath3d
> Version: 0~1.0-1
> Severity: serious
> Control: block 920171 by -1
> X-Debbugs-Cc: Wookey
>
> Dear maintainer,
>
> your new package qmath3d has
>
> Build-Depends: debhelper (>= 10), qbs, qtbase5-dev, dh-exec,
Processing commands for cont...@bugs.debian.org:
> limit source manpages-fr
Limiting to bugs with field 'source' containing at least one of 'manpages-fr'
Limit currently set to 'source':'manpages-fr'
> tags 832385 + pending
Bug #832385 [src:manpages-fr] Updating the manpages-fr Uploaders list
Processing commands for cont...@bugs.debian.org:
> limit source manpages-fr
Limiting to bugs with field 'source' containing at least one of 'manpages-fr'
Limit currently set to 'source':'manpages-fr'
> tags 871564 + pending
Bug #871564 [src:manpages-fr] manpages-fr outdated
Added tag(s) pending.
Control: tag -1 pending
Hello,
Bug #886836 in gtkmm2.4 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 Tue, 05 Feb 2019 00:22:04 +
with message-id
and subject line Bug#886836: fixed in gtkmm2.4 1:2.24.5-3
has caused the Debian Bug report #886836,
regarding libgtkmm-2.4-dev,libgtkmm-2.4-doc: both ship
usr/share/doc/libgtkmm-2.4-dev/examples/*
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> clone 910902 -1
Bug #910902 [mariadb-server] akonadi-backend-mysql: akonadi fails to start
creating new database/config - ~/.local/share/akonadi/db_data/ not created
Bug 910902 cloned as bug 921389
> retitle 910902 mariadb-server-core: do not
Processing control commands:
> reassign -1 mariadb-server 1:10.3.12-2
Bug #910902 [akonadi-backend-mysql] akonadi-backend-mysql: akonadi fails to
start creating new database/config - ~/.local/share/akonadi/db_data/ not created
Bug reassigned from package 'akonadi-backend-mysql' to
Processing commands for cont...@bugs.debian.org:
> notfound 921128 0+20180916-2
Bug #921128 [mailman3-web] mailman3-web fails to initialize mysql: Specified
key was too long
Ignoring request to alter found versions of bug #921128 to the same values
previously set
> thanks
Stopping processing
Processing control commands:
> tags -1 fixed-upstream patch
Bug #918206 [src:pandas] pandas: autopkgtest fails with python-numpy
(1:1.16.0~rc1-3)
Added tag(s) patch and fixed-upstream.
--
918206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918206
Debian Bug Tracking System
Contact
Control: tags -1 fixed-upstream patch
The test failure is that np.array @ pd.DataFrame (matrix product) tries
to keep both the DataFrame's indices, which fails because the new matrix
is a different shape.
This appears to be fixed in 0.24.1 from PyPI, but as previously noted,
this is a new
Your message dated Mon, 04 Feb 2019 22:21:20 +
with message-id
and subject line Bug#921349: fixed in frr 6.0.2-2
has caused the Debian Bug report #921349,
regarding frr: build dependency problems
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Mon, 04 Feb 2019 22:21:20 +
with message-id
and subject line Bug#921376: fixed in frr 6.0.2-2
has caused the Debian Bug report #921376,
regarding frr: missing Breaks+Replaces
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
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
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
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
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: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
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
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
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 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
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
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:
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
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 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 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 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 921357 + buster sid
Bug #921357 [node-dequeue] Not suitable for buster, package probably
unmaintained
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921357:
Processing commands for cont...@bugs.debian.org:
> tags 921368 + buster sid
Bug #921368 [node-base64id] Not suitable for buster, package probably
unmaintained
Bug #921360 [node-base64id] No suitable for buster, package probably
unmaintained
Added tag(s) sid and buster.
Added tag(s) buster and
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 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 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 commands for cont...@bugs.debian.org:
> tags 921361 + buster sid
Bug #921361 {Done: Xavier Guimard } [src:node-clean-css] 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 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:
> forcemerge 921360 921368
Bug #921360 [node-base64id] No suitable for buster, package probably
unmaintained
Bug #921368 [node-base64id] Not suitable for buster, package probably
unmaintained
Merged 921360 921368
> thanks
Stopping processing
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
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 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
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
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
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
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
Hi Andreas,
Thanks for the report!
On Mon, Feb 04, 2019 at 07:26:59PM +0100, Andreas Beckmann wrote:
> if I understood the changelog entry correctly, frr is a successor to
> quagga. There are a lot of Breaks+Replaces missing for taking over files
> owned by quagga-*:
FRR is indeed a (the?)
Source: frr
Version: 6.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Your message dated Mon, 04 Feb 2019 18:24:18 +
with message-id
and subject line Bug#921361: fixed in node-clean-css 4.2.1-1
has caused the Debian Bug report #921361,
regarding Not suitable for buster, package probably unmaintained
to be marked as done.
This means that you claim that the
Hi Adrian,
On Mon, Feb 04, 2019 at 04:11:45PM +0200, Adrian Bunk wrote:
> There are two bugs:
> 1. build depending on the shared library package is
>usually a bug, the -dev should pull in everything
> 2. the unstable buildds only consider the first alternative
Thanks for the report! Fix is
Control: tag -1 pending
Hello,
Bug #921361 in node-clean-css 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:
I can reproduce this with firefox-esr 60.5 on a Cubieboard 2 running
Stretch/armhf. However, in a Buster/armhf chroot Firefox works fine.
To make sure this is not a chroot effect I tried again in a Stretch/armhf
chroot and it shows the same error as the Stetch/armhf host.
For sake of
The upstream, Just packages the latest taurus.
So I think that you can defer your upload now.
thanks a lot for your help.
Frederic
Your message dated Mon, 04 Feb 2019 17:51:25 +
with message-id
and subject line Bug#920337: fixed in python-igraph 0.7.1.post6-7
has caused the Debian Bug report #920337,
regarding python3-igraph: ships header in /usr/include/python3.7/
to be marked as done.
This means that you claim that
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
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
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:
This is used in node-ws (popcon 92)
Paolo
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
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
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
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
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
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
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-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
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
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-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
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
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-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 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: 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
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
Your message dated Mon, 04 Feb 2019 16:10:34 +
with message-id
and subject line Bug#918830: fixed in sardana 2.6.1+dfsg-1
has caused the Debian Bug report #918830,
regarding sardana: FTBFS with Sphinx 1.8: No module named pngmath
to be marked as done.
This means that you claim that the
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 overworked
> > with these pb* packages. It might be that we will loose these
Source: gmsh
Version: 4.1.3+ds1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks
Hi Maintainer
The recent upload of gmsh 4.1.3+ds1-1 to unstable breaks the autopkgtest
of octave-msh 1.0.10-6 in testing with the following error:
1 - 100 of 178 matches
Mail list logo
