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'
--
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,
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 reg
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 up
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
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 that
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 with
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
Source: astropy-healpix
Version: 0.4-4
Severity: serious
Tags: ftbfs patch
https://buildd.debian.org/status/fetch.php?pkg=astropy-healpix&arch=i386&ver=0.4-4&stamp=1548693347&raw=0
...
=== FAILURES ===
___
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
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 y
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 act
Processing commands for cont...@bugs.debian.org:
> retitle 921324 astropy-healpix FTBFS on i386: test failure
Bug #921324 [src:astropy-healpix] astropy-healpix FTBFS on i386: test filure
Changed Bug title to 'astropy-healpix FTBFS on i386: test failure' from
'astropy-healpix FTBFS on i386: test f
Your message dated Mon, 04 Feb 2019 10:04:17 +
with message-id
and subject line Bug#879937: fixed in libqtdbustest 0.2+bzr42+repack1-5
has caused the Debian Bug report #879937,
regarding libqtdbustest: FTBFS: unit test fails with BadAddress DBusException
to be marked as done.
This means that
Hi Andreas,
On Sun, 27 Jan 2019 at 16:23, Andreas Tille wrote:
> Control: tags -1 help upstream
> Control: forwarded -1 https://github.com/cbcrg/tcoffee/issues/13
>
> Hi Liubov,
>
> On Sun, Jan 27, 2019 at 04:06:51PM +0100, Liubov Chuprikova wrote:
> > I was trying to figure out the reason for t
On Mon, Feb 04, 2019 at 12:37:03AM +0100, Andreas Beckmann wrote:
> Package: openhft-chronicle-bytes
> Version: 1.16.25-1
> Severity: serious
> Justification: fails to build from source
>
> Hi,
>
> openhft-chronicle-bytes FTBFS in a i386 pbuilder chroot, while it builds
> successfully in an amd64
On തി, ഫെബ്രു 4, 2019 at 1:26 വൈകു, Pirate
Praveen wrote:
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,
Your message dated Mon, 04 Feb 2019 10:50:33 +
with message-id
and subject line Bug#917143: fixed in t-coffee 12.00.7fb08c2-2
has caused the Debian Bug report #917143,
regarding t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest:
COREDUMP
to be marked as done.
This means tha
Your message dated Mon, 04 Feb 2019 10:49:47 +
with message-id
and subject line Bug#919415: fixed in isight-firmware-tools 1.6-4
has caused the Debian Bug report #919415,
regarding isight-firmware-tools: Build-Depends on cruft package libgcrypt11-dev
to be marked as done.
This means that you
Your message dated Mon, 04 Feb 2019 10:50:33 +
with message-id
and subject line Bug#917143: fixed in t-coffee 12.00.7fb08c2-2
has caused the Debian Bug report #917143,
regarding libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make
-j2 test TEST_VERBOSE=1 returned exit code 2
to
As promised, I pushed my packaging attempt. However, I didn't manage to
create a repository under med-team, thus it is under my account [1].
Best
Fabian
1: https://salsa.debian.org/kloetzl-guest/libmurmurhash
Your message dated Mon, 04 Feb 2019 11:06:36 +
with message-id
and subject line Bug#820308: fixed in qiime 2019.1.0-1
has caused the Debian Bug report #820308,
regarding qiime: many unsatisfiable dependencies
to be marked as done.
This means that you claim that the problem has been dealt with
Control: tag -1 pending
Hello,
Bug #896494 in libqtdbusmock 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:
https://salsa.debian.org/debian-ayatana-team/libqtdbusmock/commit/05980cbb68c
Control: tag -1 pending
Hello,
Bug #902525 in xorg-gtest 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:
https://salsa.debian.org/debian-ayatana-team/xorg-gtest/commit/d43df71418ae89fa1
Your message dated Mon, 04 Feb 2019 11:23:34 +
with message-id
and subject line Bug#909071: fixed in pbbam 0.19.0+dfsg-3
has caused the Debian Bug report #909071,
regarding pbbam: FTBFS on every release architecture where it previously built
to be marked as done.
This means that you claim tha
Your message dated Mon, 04 Feb 2019 11:35:44 +
with message-id
and subject line Bug#896494: fixed in libqtdbusmock 0.7+bzr49+repack1-3
has caused the Debian Bug report #896494,
regarding FTBFS: test-suite failures
to be marked as done.
This means that you claim that the problem has been dealt
Hi Fabian,
thanks a lot. I've moved it to med-team and fixed Vcs fields.
If you issue an ITP I can sponsor the package immediately.
Thanks for your work on this
Andreas.
On Mon, Feb 04, 2019 at 12:02:37PM +0100, Fabian Klötzl wrote:
> As promised, I pushed my packaging attempt. However,
On 2019-02-04 11:13, Adrian Bunk wrote:
>> openhft-chronicle-bytes FTBFS in a i386 pbuilder chroot, while it builds
>> successfully in an amd64 pbuilder chroot.
>
> Why is FTBFS on a binary-all package on !amd64 itself an RC bug?
I haven looked in detail in the FTBFS. It just smells fishy ...
Fee
Another comment: For libsmithwaterman I added a patch for automake including
pkg-config input. I'd consider it more flexible than a fixed Makefile.
On Mon, Feb 04, 2019 at 12:02:37PM +0100, Fabian Klötzl wrote:
> As promised, I pushed my packaging attempt. However, I didn't manage to
> create a r
Your message dated Mon, 04 Feb 2019 11:53:45 +
with message-id
and subject line Bug#902525: fixed in xorg-gtest 0.7.1-5
has caused the Debian Bug report #902525,
regarding xorg-gtest only succeeds its tests in a minimal
to be marked as done.
This means that you claim that the problem has been
Source: r-cran-taxize
Version: 0.9.5+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 0.9.5+dfsg-1 to unstable, r-cran-taxize has been
failing its own autopkgtests [1] with the following err
Your message dated Mon, 04 Feb 2019 12:04:17 +
with message-id
and subject line Bug#921216: fixed in circlator 1.5.5-3
has caused the Debian Bug report #921216,
regarding circlator should become Architecture: amd64 to allow testing migration
to be marked as done.
This means that you claim tha
Processing control commands:
> forwarded -1 https://github.com/pysam-developers/pysam/issues/761
Bug #920250 [src:python-pysam] python-pysam ftbfs from source (test failures)
Set Bug forwarded-to-address to
'https://github.com/pysam-developers/pysam/issues/761'.
> tags -1 upstream help
Bug #92025
Processing commands for cont...@bugs.debian.org:
> severity 921266 serious
Bug #921266 [linphone] linphone: Segfault and crash with "error 4 in
libc-2.28.so" on password entry
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Control: forwarded -1 https://github.com/pysam-developers/pysam/issues/761
COntrol: tags -1 upstream help
Hi Michael,
are you aware that it seems that your latest change
htslib (1.9-10) unstable; urgency=medium
* Bring the libdeflate, GCS, and S3 updates back to unstable.
-- Michael R. Crusoe Wed, 16 Jan 2019 05:23:22
-0800
seems to have broken python-pysam? I have reported this to upstre
Processing commands for cont...@bugs.debian.org:
> severity 921015 normal
Bug #921015 [kamailio] kamailio 5.2 invalid permissions at run dir cuases
several issues
Severity set to 'normal' from 'grave'
> ---
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.
P
Processing commands for cont...@bugs.debian.org:
> retitle 902525 FTBFS in buster/sid (failing tests)
Bug #902525 {Done: Mike Gabriel } [src:xorg-gtest]
xorg-gtest only succeeds its tests in a minimal
Changed Bug title to 'FTBFS in buster/sid (failing tests)' from 'xorg-gtest
only succeeds its t
Processing commands for cont...@bugs.debian.org:
> severity 921247 serious
Bug #921247 [libboost1.67-dev] Boost.Compute users FTBFS with GCC 8
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921247: https://bugs.debian.org/c
retitle 902525 FTBFS in buster/sid (failing tests)
thanks
Note: I can offer ssh access to a machine where this happens all the
time using sbuild if you like (please contact me privately for details).
Thanks.
Processing commands for cont...@bugs.debian.org:
> severity 921224 serious
Bug #921224 [anki] anki: Syncing to AnkiWeb fails with Unknown response code:
400
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921224: https://bu
Processing commands for cont...@bugs.debian.org:
> severity 921224 important
Bug #921224 [anki] anki: Syncing to AnkiWeb fails with Unknown response code:
400
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921224: https
Your message dated Mon, 04 Feb 2019 12:34:11 +
with message-id
and subject line Bug#849390: fixed in google-android-installers 1472023576+nmu2
has caused the Debian Bug report #849390,
regarding google-android-ndk-installer: Superseded by google-android-installers?
to be marked as done.
This
Your message dated Mon, 04 Feb 2019 12:34:11 +
with message-id
and subject line Bug#915657: fixed in google-android-installers 1472023576+nmu2
has caused the Debian Bug report #915657,
regarding google-android-installers NMU binaries cannot be installed due to
unchanged version of the binary
On Sun, 25 Nov 2018 20:15:08 +0100 bret curtis wrote:
> Thanks Fred!
>
> We're tracking it upstream. Will keep this bug posted with results.
>
> https://gitlab.com/OpenMW/openmw/issues/4737
Hello Bret,
we are running out of time for Debian 10 "Buster" because the soft
freeze starts next week.
Your message dated Mon, 04 Feb 2019 13:23:21 +
with message-id
and subject line Bug#921217: Removed package(s) from unstable
has caused the Debian Bug report #915739,
regarding openjdk-8-jre-dcevm still uses GCC 7 to build
to be marked as done.
This means that you claim that the problem has b
Your message dated Mon, 04 Feb 2019 13:23:21 +
with message-id
and subject line Bug#921217: Removed package(s) from unstable
has caused the Debian Bug report #915540,
regarding openjdk-8-jre-dcevm should likely not be in buster
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 04 Feb 2019 13:20:22 +
with message-id
and subject line Bug#921338: fixed in r-cran-taxize 0.9.5+dfsg-2
has caused the Debian Bug report #921338,
regarding r-cran-taxize: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Markus,
as it turns out, we're about to have another release 0.45 that has been in
'the-works' for the past month. It's been ready for awhile, we've just been
waiting on PR to make a release video and finish up a write-up.
I'll ask the team i
Processing commands for cont...@bugs.debian.org:
> severity 872439 serious
Bug #872439 [libsoc-dev] libsoc-dev: libsoc_gpio.h is missing stdlib.h include
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
872439: https://bug
Am 04.02.19 um 14:31 schrieb psi...@gmail.com:
> Hello Markus,
>
> as it turns out, we're about to have another release 0.45 that has been in
> 'the-works' for the past month. It's been ready for awhile, we've just been
> waiting on PR to make a release video and finish up a write-up.
>
> I'll a
Your message dated Mon, 04 Feb 2019 13:50:37 +
with message-id
and subject line Bug#918807: fixed in taurus 4.5.0+dfsg-1
has caused the Debian Bug report #918807,
regarding taurus: FTBFS with Sphinx 1.8: No module named pngmath
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 04 Feb 2019 13:50:07 +
with message-id
and subject line Bug#921183: fixed in pysurfer 0.9.0-2
has caused the Debian Bug report #921183,
regarding python3-surfer: missing Breaks+Replaces: python-surfer (<< 0.9.0)
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> severity 873719 serious
Bug #873719 [libsc-dev] /usr/bin/sc-libtool: Command not found
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
873719: https://bugs.debian.org/cgi
On 2/1/19 11:20 AM, Matthias Klose wrote:
> On 01.02.19 10:03, Emmanuel Bourg wrote:
>> This is an excellent suggestion. We should file a bug for openjdk-8 to
>> implement that.
> please attach the patch.
Sure, I should be able to write something up. Forbear my ignorance:
should I use debconf to
Am 04.02.19 um 14:56 schrieb Per Lundberg:
> On 2/1/19 11:20 AM, Matthias Klose wrote:
>> On 01.02.19 10:03, Emmanuel Bourg wrote:
>
>>> This is an excellent suggestion. We should file a bug for openjdk-8 to
>>> implement that.
>> please attach the patch.
>
> Sure, I should be able to write som
Your message dated Mon, 4 Feb 2019 16:04:52 +0200
with message-id <20190204140452.GA10852@localhost>
and subject line Re: Bug#911507: offlineimap: fails to load imaplib2
has caused the Debian Bug report #911507,
regarding offlineimap: fails to load imaplib2
to be marked as done.
This means that yo
Processing commands for cont...@bugs.debian.org:
> tags 917083 + confirmed
Bug #917083 [mysql-workbench] mysql-workbench: Cannot Connect to Database:
Unsupported option provided to mysql_options()
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance
Processing commands for cont...@bugs.debian.org:
> tags 917083 + upstream help
Bug #917083 [mysql-workbench] mysql-workbench: Cannot Connect to Database:
Unsupported option provided to mysql_options()
Added tag(s) upstream and help.
> thanks
Stopping processing here.
Please contact me if you nee
Processing commands for cont...@bugs.debian.org:
> forwarded 917083 https://bugs.mysql.com/bug.php?id=78947
Bug #917083 [mysql-workbench] mysql-workbench: Cannot Connect to Database:
Unsupported option provided to mysql_options()
Set Bug forwarded-to-address to 'https://bugs.mysql.com/bug.php?id=
Source: frr
Version: 6.0.2-1
Severity: serious
Tags: ftbfs
Build-Depends:
...
libjson0 | libjson-c2 | libjson-c3,
libjson0-dev | libjson-c-dev,
...
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 build
On Sun, Feb 3, 2019 at 6:41 PM Felipe Sateler wrote:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/11645
>
> I have forwarded the bug upstream, and proposed two solutions. If upstream
> likes one, we can apply that in the debian package.
>
>
Upstream asks if cgroup is in v2-mo
Package: prometheus-postfix-exporter
Version: 0.1.2-1
Severity: serious
Justification: Policy 9.11
Excerpt from policy 9.11:
However, any package integrating with other init systems
must also be backwards-compatible with sysvinit by providing a SysV-
style init script with the same name as and eq
Hi Felipe,
Felipe Sateler wrote:
> Upstream asks if cgroup is in v2-mode in the affected systems.
How do I recognize this? I have no idea of how to check that.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.o
On Mon, Feb 4, 2019 at 11:34 AM Axel Beckert wrote:
> Hi Felipe,
>
> Felipe Sateler wrote:
> > Upstream asks if cgroup is in v2-mode in the affected systems.
>
> How do I recognize this? I have no idea of how to check that.
>
With `findmnt -R /sys/fs/cgroup`. It should list controllers in the cg
Your message dated Mon, 04 Feb 2019 14:45:32 +
with message-id
and subject line Bug#921247: fixed in boost1.67 1.67.0-13
has caused the Debian Bug report #921247,
regarding Boost.Compute users FTBFS with GCC 8
to be marked as done.
This means that you claim that the problem has been dealt wit
Hi Felipe,
Felipe Sateler wrote:
> > > Upstream asks if cgroup is in v2-mode in the affected systems.
> >
> > How do I recognize this? I have no idea of how to check that.
>
> With `findmnt -R /sys/fs/cgroup`. It should list controllers in the cgroup
> or cgroup2 filesystems.
Thanks!
This curre
Your message dated Mon, 04 Feb 2019 14:48:42 +
with message-id
and subject line Bug#916867: fixed in hkl 5.0.0.2456-1
has caused the Debian Bug report #916867,
regarding hkl: FTBFS: ../../hkl/ccan/generator/generator.h:23:2: error: #error
Generators require coroutines
to be marked as done.
T
Your message dated Mon, 04 Feb 2019 15:44:29 +0100
with message-id <1891567.C0YfhY37kB@tuxin>
and subject line done with 4:18.07.90-1
has caused the Debian Bug report #907148,
regarding kmail: FTBFS in buster/sid (invalid use of incomplete type 'class
QButtonGroup')
to be marked as done.
This mea
Your message dated Mon, 04 Feb 2019 15:45:19 +0100
with message-id <2801459.TEKKCr9l1F@tuxin>
and subject line Done with 4:18.07.90-1
has caused the Debian Bug report #907230,
regarding kmail-account-wizard: FTBFS with Qt 5.11
to be marked as done.
This means that you claim that the problem has be
Your message dated Mon, 04 Feb 2019 15:50:21 +0100
with message-id <2412149.45o5CatmPR@tuxin>
and subject line Done with 4:18.07.90-1
has caused the Debian Bug report #907154,
regarding akonadi-import-wizard: FTBFS in buster/sid (invalid use of incomplete
type 'class QAction')
to be marked as done
Your message dated Mon, 04 Feb 2019 15:06:40 +
with message-id
and subject line Bug#60: fixed in node-js-beautify 1.7.5+dfsg-2
has caused the Debian Bug report #60,
regarding jsbeautifier,node-js-beautify: both ship /usr/bin/js-beautify
to be marked as done.
This means that you claim
Your message dated Mon, 04 Feb 2019 15:06:46 +
with message-id
and subject line Bug#916576: fixed in pbdagcon 0.3+git20161121.000+ds-1
has caused the Debian Bug report #916576,
regarding pbdagcon: FTBFS pbdata/Types.h: No such file or directory
to be marked as done.
This means that you cl
Your message dated Mon, 04 Feb 2019 15:06:34 +
with message-id
and subject line Bug#921119: fixed in libdfp 1.0.13-3
has caused the Debian Bug report #921119,
regarding libdfp: missing build-dependency on python3
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 04 Feb 2019 15:06:40 +
with message-id
and subject line Bug#60: fixed in node-js-beautify 1.7.5+dfsg-2
has caused the Debian Bug report #60,
regarding node-js-beautify: cannot install: wants to overwrite
/usr/bin/js-beautify from package jsbeautifier
to be mark
> This currently looks like this now (after I have uninstalled
> cgroupfs-mount):
>
> → findmnt -R /sys/fs/cgroup
> TARGET SOURCE FSTYPE OPTIONS
> /sys/fs/cgroup tmpfs tmpfs rw,nosuid,nodev,noexec,mode=755
> ├─/sys/fs/cgroup/unified cgroup2 cgroup2
> rw,nosuid,n
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:
[in
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 for
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 proble
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 upload
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 li
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
png_image_f
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 to
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 checke
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 b
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 by
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 b
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 b
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 checke
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 c
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 che
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 some
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 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 by
1 - 100 of 178 matches
Mail list logo
