Hi Kevin,
those 4 security issues were fixed via DSA-3798-1 in jessie-security, by
backporting the appropriate upstream changes (thanks to Thorsten for
doing that).
I've verified 1.4.13 only contains those security fixes, and no new
major evolution or feature, so could you please prepare and uplo
On 2017-03-01 00:50:59 [+0100], John Paul Adrian Glaubitz wrote:
> Hi!
Hi,
> The problem is that if the package was to be rebuilt now, it would be
> rebuilt with OpenSSL 1.1 and not OpenSSL 1.0 which is the original
> motivation for this bug report by Sebastian!
it already has been built with 1.1
Package: texlive-lang-japanese
Version: 2016.20170123-3
Severity: serious
Dear Norbert,
Two scripts, /usr/bin/kanji-config-updmap{,-sys}, are not provided
because of "debian/scripts.lst" doesn't follow upstream renaming:
jfontmaps -> ptex-fontmaps.
As you know, these scripts are very important
Processing control commands:
> severity 856152 important
Bug #856152 [src:python-apt] python-apt: FTBFS: AptKeyError: recv from
'hkp://localhost:19191' failed for '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553'
Severity set to 'important' from 'serious'
--
856152: http://bugs.debian.org/cgi-bin/bu
Control: severity 856152 important
On Wed, Mar 01, 2017 at 06:39:37AM +0800, Chris Lamb wrote:
> retitle 856152 python-apt: FTBFS: AptKeyError: recv from
> 'hkp://localhost:19191' failed for
> '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553'
> thanks
>
> Julian Andres Klode wrote:
>
> > Retry it.
Your message dated Wed, 01 Mar 2017 00:03:42 +
with message-id
and subject line Bug#850282: fixed in influxdb 1.1.1+dfsg1-4
has caused the Debian Bug report #850282,
regarding influxdb: FTBFS randomly (failing tests)
to be marked as done.
This means that you claim that the problem has been de
Processing control commands:
> tags -1 moreinfo
Bug #856416 [grub-efi-amd64] grub-efi-amd64: Updating grub-efi-amd64:amd64 to
2.02~beta3-5 is aborted with half-installed package and reboot
Added tag(s) moreinfo.
--
856416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856416
Debian Bug Track
Control: tags -1 moreinfo
Hi Reiner!
> Running apt-get again to complete the update, is aborted with the hint to use
> 'dpkg --configure -a'.
> But doing so, the update is also not completed, again a reboot is done.
> Finally, this leaves the system in a half-installed mode, without no
> automa
Control: tags -1 + fixed-upstream patch
Upstream addressed this by avoiding linking libxapianbackend.so to
openssl (apparently it doesn't use it anyway):
https://github.com/FabriceColin/pinot/commit/3a40d5abe159a106f3aabaedf1a199020946b3b5
Cheers,
Olly
Processing control commands:
> tags -1 + fixed-upstream patch
Bug #833692 [pinot] pinot: links GPLv2+ code with OpenSSL
Added tag(s) fixed-upstream and patch.
--
833692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: gitlab
Version: 8.13.11+dfsg-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
gitlab installs, but will not complete configuration, because (at least)
it is looking for a wrong version of a postgresql extension.
Possibly also incompatible with latest postgresql
Hi!
> We shouldn't be changing the way a package builds during freeze.
> It was last built with openssl 1.0, so that's what we should have for now.
The problem is that if the package was to be rebuilt now, it would be
rebuilt with OpenSSL 1.1 and not OpenSSL 1.0 which is the original
motivation f
Hi Ondřej,
Ondřej Surý wrote:
> d/copyright doesn't list all license holders and has wrong copyright
> for at least some files:
>
> Please convert to machine-readable copyright file and add missing copyrights:
> + Files: * is GPLv2+, e.g. any later version and not just GPL-2
I disagree here: Af
Processing commands for cont...@bugs.debian.org:
> tag 850282 + pending
Bug #850282 [src:influxdb] influxdb: FTBFS randomly (failing tests)
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
850282: http://bugs.debian.org/cgi-bin/bugreport.cgi?b
tag 850282 + pending
thanks
Some bugs in the influxdb package are closed in revision
c72b959213ca374ee4697d7fab28fa5a9bf83fb8 in branch 'master' by aviau
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/influxdb.git/commit/?id=c72b959
Commit message:
Disable Test
Processing commands for cont...@bugs.debian.org:
> forwarded 823865 https://github.com/phpsysinfo/phpsysinfo/issues/120
Bug #823865 [phpsysinfo] d/copyright is missing licenses for many files
Set Bug forwarded-to-address to
'https://github.com/phpsysinfo/phpsysinfo/issues/120'.
> thanks
Stopping
Bastian Blank wrote:
> On Tue, Feb 28, 2017 at 10:00:01PM +, Steven Chamberlain wrote:
> > That differs from the latest version of my patch, and from what I sent
> > earlier today to the release team when asking about a potential unblock:
> > https://lists.debian.org/debian-release/2017/02/msg0
Processing commands for cont...@bugs.debian.org:
> retitle 855929 mclibs: FTBFS: LOCB/LOCF: address 0x7f68e28cd740 exceeds the
> 32 bit address space or is not in the data segments
Bug #855929 [src:mclibs] mclibs: FTBFS: Test failures
Changed Bug title to 'mclibs: FTBFS: LOCB/LOCF: address 0x7f68
Processing commands for cont...@bugs.debian.org:
> retitle 855920 fail2ban: FTBFS: test_rewrite_file: AssertionError: False is
> not true
Bug #855920 [src:fail2ban] fail2ban: FTBFS: Test failures
Changed Bug title to 'fail2ban: FTBFS: test_rewrite_file: AssertionError: False
is not true' from 'f
On Tue, Feb 28, 2017 at 10:00:01PM +, Steven Chamberlain wrote:
> That differs from the latest version of my patch, and from what I sent
> earlier today to the release team when asking about a potential unblock:
> https://lists.debian.org/debian-release/2017/02/msg01033.html
This happens if yo
Processing commands for cont...@bugs.debian.org:
> retitle 855933 mod-gnutls: FTBFS: FAIL:
> test-22_TLS_reverse_proxy_crl_revoke.bash
Bug #855933 [src:mod-gnutls] mod-gnutls: FTBFS: Test failures
Changed Bug title to 'mod-gnutls: FTBFS: FAIL:
test-22_TLS_reverse_proxy_crl_revoke.bash' from 'mod
Processing commands for cont...@bugs.debian.org:
> retitle 856152 python-apt: FTBFS: AptKeyError: recv from
> 'hkp://localhost:19191' failed for
> '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553'
Bug #856152 [src:python-apt] python-apt: FTBFS: Testsuite failure
Changed Bug title to 'python-apt: FTBF
retitle 856152 python-apt: FTBFS: AptKeyError: recv from
'hkp://localhost:19191' failed for '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553'
thanks
Julian Andres Klode wrote:
> Retry it. Maybe it timed out or something.
I don't think this is a timeout issue, but if it is, surely the package
build s
Your message dated Tue, 28 Feb 2017 22:34:21 +
with message-id
and subject line Bug#849132: fixed in google-perftools 2.5-2.2
has caused the Debian Bug report #849132,
regarding google-perftools FTBFS on i386: FAIL: profiler_unittest.sh
to be marked as done.
This means that you claim that the
Package: libvcflib-tools
Version: 1.0.0~rc1+dfsg1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
I installed libvcflib-tools on testing/stretch. When I ran 'vcflib', I
saw this:
$ vcflib
Usage: /usr/bin/vcflib
xrdp-sesman is starting, but xrdp fails to start and automatically stops
xrdp-sesman.
output of journalctl -xn is:
Failed at step RUNTIME_DIRECTORY spawning /usr/sbin/xrdp-sesman: File exists
Actually, "socksetup" is now called more than once, which could be avoided by
removing one line from x
I believe the bug is not yet fixed.
xrdp-service is now starting, but starting xrdp leads to an error.
Proposed fix is to remove the line "RuntimeDirectory=xrdp" from xrdp.service:
--- a/instfiles/xrdp.service
+++ b/instfiles/xrdp.service
@@ -7,7 +7,6 @@ After=network.target xrdp-sesman.service
Bastian Blank wrote:
> Adopted and commited to
> https://anonscm.debian.org/git/d-i/libdebian-installer.git, branch
> sha256
That differs from the latest version of my patch, and from what I sent
earlier today to the release team when asking about a potential unblock:
https://lists.debian.org/debi
* Adrian Bunk:
> Doesn't seem to work:
> https://buildd.debian.org/status/fetch.php?pkg=google-perftools&arch=i386&ver=2.5-2.1&stamp=1488295669&raw=0
Yeah, those test scripts a bit crappier than I thought. Let's try that
again...
Cheers,
-Hilko
found 850282 1.1.1+dfsg1-3
thanks
On Tue, 28 Feb 2017, Alexandre Viau wrote:
>* Disable tests on i386 (Closes: #850282)
Disabling all the tests on i386 is unnecessary and also it does not fix
the bug I reported at all (so, no point in using Closes here).
Instead of disabling all the tests o
Processing commands for cont...@bugs.debian.org:
> found 850282 1.1.1+dfsg1-3
Bug #850282 {Done: Alexandre Viau } [src:influxdb] influxdb:
FTBFS randomly (failing tests)
Marked as found in versions influxdb/1.1.1+dfsg1-3; no longer marked as fixed
in versions influxdb/1.1.1+dfsg1-3 and reopened.
On Sun, Feb 26, 2017 at 06:30:31PM +, Steven Chamberlain wrote:
> I've attached only the most minimal patch to allow reverse-depends do
> implement SHA256. They must adapt to the new names of struct members
> *and* remember that the hash length is now different. (The hash data is
> stored in
Your message dated Tue, 28 Feb 2017 21:19:57 +
with message-id
and subject line Bug#841559: fixed in influxdb-python 3.0.0-2
has caused the Debian Bug report #841559,
regarding influxdb-python: FTBFS: dh_auto_test: pybuild --test -i
python{version} -p 2.7 returned exit code 13
to be marked as
Your message dated Tue, 28 Feb 2017 20:51:38 +
with message-id
and subject line Bug#850282: fixed in influxdb 1.1.1+dfsg1-3
has caused the Debian Bug report #850282,
regarding influxdb: FTBFS randomly (failing tests)
to be marked as done.
This means that you claim that the problem has been de
Processing commands for cont...@bugs.debian.org:
> tag 850282 + pending
Bug #850282 [src:influxdb] influxdb: FTBFS randomly (failing tests)
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
850282: http://bugs.debian.org/cgi-bin/bugreport.cgi?b
tag 850282 + pending
thanks
Some bugs in the influxdb package are closed in revision
3542a46462ca929c085a256b2f23c36c39579e3e in branch 'master' by aviau
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/influxdb.git/commit/?id=3542a46
Commit message:
Disable test
Package: grub-efi-amd64
Version: 2.02~beta3-5
Severity: critical
Justification: breaks the whole system
Running apt-get again to complete the update, is aborted with the hint to use
'dpkg --configure -a'.
But doing so, the update is also not completed, again a reboot is done.
Finally, this leaves
Hi,
Steven Chamberlain (2017-02-28):
> Changing the name, causes reverse-deps using that field to FTBFS. I
> think that is just anna and cdebootstrap, which we'd patch anyway.
Sure.
> The md5sum/sha256 field is a pointer to a dynamically-allocated field.
> The struct size, and the offset of ot
On Tue, 2017-02-28 at 20:12 +0100, Andreas Beckmann wrote:
> On 2017-02-28 14:55, Luca Boccassi wrote:
> >> Then, isn't this a kernel bug? I mean, the ABI has changed, so that
> >> the number should have changed to 4.9.0-3 instead of remaining at
> >> 4.9.0-2.
> >
> > It's within the kernel team p
On 2017-02-28 14:55, Luca Boccassi wrote:
>> Then, isn't this a kernel bug? I mean, the ABI has changed, so that
>> the number should have changed to 4.9.0-3 instead of remaining at
>> 4.9.0-2.
>
> It's within the kernel team prerogatives to decide what ABI to keep
> stable and what not.
> I assum
On 02/27/2017 11:50 PM, Allison Randal wrote:
> On 02/27/2017 05:34 PM, Thomas Goirand wrote:
>>
>> Yes, because it FTBFS as well.
>
> Thanks Thomas. How important would you rate vmware-nsx? It's currently
> removed from testing. It has no rdepends, so I'm thinking it's probably
> fine to leave it
Your message dated Tue, 28 Feb 2017 17:18:46 +
with message-id
and subject line Bug#855588: fixed in atheme-services 7.2.9-1
has caused the Debian Bug report #855588,
regarding memory leak could lead to Denial Of Service
to be marked as done.
This means that you claim that the problem has bee
Processing commands for cont...@bugs.debian.org:
> retitle 856406 wx3.0-headers shouldn't require C++11 in stretch
Bug #856406 [wx3.0-headers] wx3.0-headers shouldn't require C+11 in stretch
Changed Bug title to 'wx3.0-headers shouldn't require C++11 in stretch' from
'wx3.0-headers shouldn't requ
Processing control commands:
> clone -1 -2
Bug #856350 [src:qutemol] qutemol: FTBFS (#error This file requires compiler
and library support)
Bug 856350 cloned as bug 856406
> reassign -2 wx3.0-headers 3.0.2+dfsg-2
Bug #856406 [src:qutemol] qutemol: FTBFS (#error This file requires compiler
and l
Control: clone -1 -2
Control: reassign -2 wx3.0-headers 3.0.2+dfsg-2
Control: retitle -2 wx3.0-headers shouldn't require C+11 in stretch
Control: affects -2 src:qutemol
Control: tags -2 patch
Control: retitle -1 qutemol must be made C++11 compatible
Control: severity -1 important
On Tue, Feb 28, 2
Your message dated Tue, 28 Feb 2017 16:20:21 +
with message-id
and subject line Bug#856269: fixed in ruby-zip 1.2.0-1.1
has caused the Debian Bug report #856269,
regarding ruby-zip: CVE-2017-5946
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Control: tags -1 + patch
Hi,
The attached patch is based on having
libdebian-installer_bug856210_v3.patch applied:
* libdebian-installer4-dev would not change its name
* sum[1] is already empty/unusable
* sum[0] would become the sha256 field
Thanks,
Regards,
--
Steven Chamberlain
ste...@
Processing control commands:
> tags -1 + patch
Bug #856212 [src:cdebootstrap] cdebootstrap: please implement SHA256
verification of .deb files
Added tag(s) patch.
--
856212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Updated patch, which assumes the libdebian-installer4-dev package will
not be renamed. Build-Depend on a recent enough version that provides
sha256 fields.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index d6682ca..20e33a0 100644
--- a/debia
Steven Chamberlain wrote:
> replace sum[0] with sha256 and leave sum[1] empty;
> [...] (we would drop the MD5- and SHA1-parsing code
> and make absolutely sure nobody is still using those).
The new patch attached would do that, and it remains otherwise
ABI-compatible.
It aims to be the most mini
Processing control commands:
> reopen -1
Bug #849132 {Done: Hilko Bengen } [src:google-perftools]
google-perftools FTBFS on i386: FAIL: profiler_unittest.sh
'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
Control: reopen -1
On Tue, Feb 28, 2017 at 02:54:12PM +, Debian Bug Tracking System wrote:
>...
> google-perftools (2.5-2.1) unstable; urgency=medium
>...
>* Ignore result for profiler unit test that fails "randomly" on i386
> (Closes: #849132)
>...
Doesn't seem to work:
https://bui
Your message dated Tue, 28 Feb 2017 15:03:56 +
with message-id
and subject line Bug#856344: fixed in fwupd 0.8.1-3
has caused the Debian Bug report #856344,
regarding fwupd FTBFS on architectures where it does not build depend on
valgrind
to be marked as done.
This means that you claim that
Your message dated Tue, 28 Feb 2017 14:54:51 +
with message-id
and subject line Bug#837581: fixed in xfsdump 3.1.6+nmu2
has caused the Debian Bug report #837581,
regarding xfslibs-dev: Don't put the .so symlink to /lib/*.so
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 28 Feb 2017 14:54:43 +
with message-id
and subject line Bug#854950: fixed in seafile 6.0.4-1
has caused the Debian Bug report #854950,
regarding seafile-cli: Seafile-cli don't start (Python import problem)
to be marked as done.
This means that you claim that the proble
Your message dated Tue, 28 Feb 2017 14:54:51 +
with message-id
and subject line Bug#837581: fixed in xfsdump 3.1.6+nmu2
has caused the Debian Bug report #837581,
regarding xfsdump: FTBFS (could not find a current XFS handle library)
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 28 Feb 2017 14:52:03 +
with message-id
and subject line Bug#849132: fixed in google-perftools 2.5-2.1
has caused the Debian Bug report #849132,
regarding google-perftools FTBFS on i386: FAIL: profiler_unittest.sh
to be marked as done.
This means that you claim that the
Dear Samuel,
thanks for clearing things up.
And special thanks for your fast help getting Mbrola work again
- which is really appreciated!
GHPS
On 2017-02-28 13:44:46 +, Luca Boccassi wrote:
> The kernel headers packages have the name versioned after the ABI
> version. DKMS understanding is that as long as the package name (and
> thus the ABI version) does not change, then there is no need to rebuild
> as the ABI is (assumed to be) com
On Tue, 2017-02-28 at 14:52 +0100, Vincent Lefevre wrote:
> On 2017-02-28 13:44:46 +, Luca Boccassi wrote:
> > The kernel headers packages have the name versioned after the ABI
> > version. DKMS understanding is that as long as the package name (and
> > thus the ABI version) does not change, th
Your message dated Tue, 28 Feb 2017 13:48:38 +
with message-id
and subject line Bug#856331: fixed in mbrola 3.01h+2-2
has caused the Debian Bug report #856331,
regarding Mbrola-64 crashes immediately with a SEGFAULT
to be marked as done.
This means that you claim that the problem has been dea
On Tue, 2017-02-28 at 14:40 +0100, Vincent Lefevre wrote:
> On 2017-02-28 13:34:35 +, Luca Boccassi wrote:
> > Unfortunately if the linux-headers-* packages don't change names when
> > ABI compatibility is broken there's just no way to deal with it apart
> > from rebuilding manually with the ab
FTR, the backtrace:
#0 __GI___libc_free (mem=0x19191919) at malloc.c:2963
#1 0xf74f4d79 in __GI__IO_wsetb (f=0x8050988 <_IO_stdin_>, b=0x0, eb=0x0, a=0)
at wgenops.c:106
#2 0xf74ff6fc in _IO_unbuffer_all () at genops.c:924
#3 _IO_cleanup () at genops.c:966
#4 0xf74c1742 in __run_exit_handler
On 2017-02-28 13:34:35 +, Luca Boccassi wrote:
> Unfortunately if the linux-headers-* packages don't change names when
> ABI compatibility is broken there's just no way to deal with it apart
> from rebuilding manually with the above commands, that's just how DKMS
> works I'm afraid.
> So closin
Your message dated Tue, 28 Feb 2017 13:34:35 +
with message-id <1488288875.28111.6.ca...@gmail.com>
and subject line Re: Bug#856355: nvidia-driver: no longer works
has caused the Debian Bug report #856355,
regarding nvidia-driver: no longer works
to be marked as done.
This means that you claim
On Tue, 2017-02-28 at 14:30 +0100, Vincent Lefevre wrote:
> On 2017-02-28 13:15:43 +, Luca Boccassi wrote:
> > Please try to reinstall the latest version of the driver and report
> > back, and they should work.
>
> I've installed the latest version and rebooted, and everything is OK.
>
> So,
Processing control commands:
> severity -1 grave
Bug #856331 [mbrola] Mbrola-64 crashes immediately with a SEGFAULT
Severity set to 'grave' from 'normal'
> tags -1 + pending
Bug #856331 [mbrola] Mbrola-64 crashes immediately with a SEGFAULT
Added tag(s) pending.
--
856331: http://bugs.debian.org
Processing control commands:
> tags -1 - moreinfo
Bug #856355 [nvidia-driver] nvidia-driver: no longer works
Removed tag(s) moreinfo.
--
856355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 - moreinfo
On 2017-02-28 13:15:43 +, Luca Boccassi wrote:
> Please try to reinstall the latest version of the driver and report
> back, and they should work.
I've installed the latest version and rebooted, and everything is OK.
So, the problem was due to the fact that the mo
Processing control commands:
> tags -1 moreinfo
Bug #856355 [nvidia-driver] nvidia-driver: no longer works
Added tag(s) moreinfo.
--
856355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 moreinfo
On Tue, 2017-02-28 at 13:52 +0100, Vincent Lefevre wrote:
> On 2017-02-28 13:31:41 +0100, Vincent Lefevre wrote:
> > Package: nvidia-driver
> > Version: 375.39-1
> > Severity: grave
> > Justification: renders package unusable
> >
> > X no longer works with the NVIDIA dri
Thanks for your comments!
Cyril Brulebois wrote:
> Steven Chamberlain (2017-02-27):
> > (If we really wanted, we could maybe avoid the ABI bump: [...]
>
> Given the number of reverse dependencies, I doubt this is worth abusing
> md5 storage for sha256 things.
Maybe I should clarify that; the c
Hi Antonio!
On Tue, Feb 28, 2017 at 08:21:23AM -0300, Antonio Terceiro wrote:
> On Tue, Feb 28, 2017 at 08:08:21AM +0100, Salvatore Bonaccorso wrote:
> > Control: tags 856269 + pending
> >
> > Dear maintainer,
> >
> > I've prepared an NMU for ruby-zip (versioned as 1.2.0-1.1) and
> > uploaded it
On 2017-02-28 13:31:41 +0100, Vincent Lefevre wrote:
> Package: nvidia-driver
> Version: 375.39-1
> Severity: grave
> Justification: renders package unusable
>
> X no longer works with the NVIDIA driver. I get in the X logs:
>
> NVIDIA: Failed to initialize the NVIDIA kernel module. Please see
Processing control commands:
> severity -1 serious
Bug #773671 [src:libv8-3.14] libv8-3.14: multiple security issues
Severity set to 'serious' from 'normal'
--
773671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: nvidia-driver
Version: 375.39-1
Severity: grave
Justification: renders package unusable
X no longer works with the NVIDIA driver. I get in the X logs:
NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
NVIDIA: system's kernel log for additional error messages a
Processing control commands:
> severity -1 serious
Bug #773623 [libv8-3.14] nodejs: CVE-2014-7192
Severity set to 'serious' from 'normal'
--
773623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 serious
Bug #760385 [libv8-3.14] nodejs: CVE-2014-5256
Severity set to 'serious' from 'normal'
--
760385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: src:qutemol
Version: 0.4.1~cvs2008-6
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -B"
but it failed:
[...]
debian/rules build-arch
test -x debian/
On Tue, Feb 28, 2017 at 08:08:21AM +0100, Salvatore Bonaccorso wrote:
> Control: tags 856269 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for ruby-zip (versioned as 1.2.0-1.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
thanks - I have ju
Package: src:mpi4py
Version: 2.0.0-2
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:
[...]
debian/rules build-indep
dh build-indep --with pytho
On Sun, 26 Feb 2017 at 14:31:31 +, Simon McVittie wrote:
> * schroot/1.6.10-3:
> - sbuild profile: bind-mounts host /dev/pts only
> + in the real device node case, we're fine
Actually no - running script inside schroot inside an lxc container on a
jessie kernel, with lxc from jessie-back
Your message dated Tue, 28 Feb 2017 09:33:38 +
with message-id
and subject line Bug#854941: fixed in syncevolution 1.5.2-2
has caused the Debian Bug report #854941,
regarding sync-ui: fails to do anything
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Source: fwupd
Version: 0.8.1-2
Severity: serious
https://buildd.debian.org/status/package.php?p=fwupd
...
checking for VALGRIND... no
configure: error: Package requirements (valgrind) were not met:
No package 'valgrind' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
in
Your message dated Tue, 28 Feb 2017 09:04:03 +
with message-id
and subject line Bug#856227: fixed in ufraw 0.22-1.1
has caused the Debian Bug report #856227,
regarding ufraw FTBFS on architectures where char is unsigned
to be marked as done.
This means that you claim that the problem has been
Hi Nish,
I created a branch for 4.1.5 from upstream:
https://anonscm.debian.org/cgit/pkg-monitoring/loganalyzer.git/log/?h=debian/sid-839789
I notice upstream now uses jquery and jquery-ui, some tweaks may be
needed to make sure nothing non-free has crept in to the tarball and
symlink to the pa
On 02/28/2017 06:15 AM, Hubert Chathi wrote:
> Thanks for the quick fix. Please go ahead with the NMU.
Thanks! Just uploaded the fixed package.
Will take care of the unblock request.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Unive
87 matches
Mail list logo
