Package: packer
Version: 0.10.2+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Since the tests are not fail safed anymore the package starts to FTBFS on arm64,
armel and armhf. There is a single test failure:
=== RUN TestConfigInstantiat
Processing control commands:
> tags 853075 + pending
Bug #853075 [src:ruby-minitar] ruby-minitar: CVE-2016-10173: directory
traversal vulnerability
Added tag(s) pending.
--
853075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853075
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Control: tags 853075 + pending
Dear Markus,
I've prepared an NMU for ruby-minitar (versioned as 0.5.4-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru ruby-minitar-0.5.4/debian/changelog ruby-minitar-0.5.4/debian/changelog
-
Your message dated Mon, 30 Jan 2017 05:48:31 +
with message-id
and subject line Bug#851605: fixed in emacs-goodies-el 36.3+nmu1
has caused the Debian Bug report #851605,
regarding emacs-goodies-el: fails to upgrade lenny -> squeeze -> wheezy ->
jessie
to be marked as done.
This means that yo
On 17-01-26 09:36 AM, Andrew Shadura wrote:
> Hi everyone,
>
> I have cherry-picked a few patches from the upstream Git repository.
>
> While I don't have much hope they fix all of your issues, there's still
> some chance they do improve the state of things.
>
> Please test this version, ensurin
Your message dated Mon, 30 Jan 2017 04:44:38 +
with message-id
and subject line Bug#853090: Removed package(s) from unstable
has caused the Debian Bug report #850991,
regarding liblicense: FTBFS: ../../../modules/io/exempi.c:48:26: error:
'XMP_OPEN_OPNLYXMP' undeclared (first use in this func
Jeffrey,
On 29/01/17 21:09, Jeffrey Walton wrote:
> As a stopgap, you might consider adding a small swapfile and setting
> swapiness to a low value.
I am talking about buildds, and a package prevented from migrating to
testing because of this :)
> Nearly every ARM gadget I had was suffering OOM
On Sat, 28 Jan 2017, Antonio Valentino wrote:
> Hi,
> the RC bug #852906 has been fixed and a new version of the debian
> package for numexpr (2.6.1-4) is now available [1,2].
> Can anyone please upload it?
building now -- will upload tomorrow morning whenever get to it unless
somewhat beats me
Thanks for uploading. Please feel free to takeover the maintainership of
python-whoosh as I am MIA since 1.5 year.
On January 22, 2017 9:06:35 PM GMT+02:00, Simon McVittie
wrote:
>Control: tags 812768 + patch
>Control: tags 812768 + pending
>
>Dear maintainer,
>
>I've prepared an NMU for python
Package: pulseaudio-module-jack
Version: 9.0-5
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After installing pulseaudio-module-jack, running jackd via
$ jackd -d alsa
and executing
$ pactl load-module module-jack-sink
$ pactl load-module module-jack-sour
Source: node-browserify-lite
Version: 0.3.0-1
Severity: serious
When I rebuild node-browserify-lite under pbuilder, the resulting contents are:
drwxr-xr-x root/root 0 2015-07-07 14:10 ./
drwxr-xr-x root/root 0 2015-07-07 14:10 ./usr/
drwxr-xr-x root/root 0 2015-07-07 14:10
On Sun, Jan 29, 2017 at 12:11:11PM +, Andy Simpkins wrote:
> Hi Ted,
>
> I am currently sat at the Cambridge BSP looking at Debian RC bugs [1].
>
> Looking at this bug report we believe that on balance the best course of
> action would be to remove lib/et/test_cases/imap_err.et from e2fsprogs
> Sadly, it turns out armhf fails to build due to one test taking a bit
> too much memory[1], and there is an RC bug open for that: #852959[2].
>
> So now I don't know what to do, except asking for removal of prometheus
> from armhf.
As a stopgap, you might consider adding a small swapfile and set
Your message dated Mon, 30 Jan 2017 01:56:40 +0200
with message-id <20170129235640.ozbb6p3itxfqlslm@localhost>
and subject line Closing, already fixed in stable
has caused the Debian Bug report #757771,
regarding rar: Incorrect handling of file names containing international
characters when creati
Hello ARM porters,
I am the maintainer for the prometheus suite, which is in testing. Last
week, just before the deadline I prepared and uploaded a new upstream
release (which I even tested in an armel porterbox to be sure).
Sadly, it turns out armhf fails to build due to one test taking a bit
to
Processing commands for cont...@bugs.debian.org:
> notfound 853124 2.4.9.1+dfsg-1+deb8u1
Bug #853124 [src:opencv] opencv: Add Breaks to old packages to assist in
upgrades
No longer marked as found in versions opencv/2.4.9.1+dfsg-1+deb8u1.
> found 853124 2.4.9.1+dfsg-2.1
Bug #853124 [src:opencv] o
Processing control commands:
> severity -1 serious
Bug #853103 [src:a52dec] a52dec: FTBFS [i386]: Test failure in "globals"
Severity set to 'serious' from 'normal'
> tags -1 - moreinfo
Bug #853103 [src:a52dec] a52dec: FTBFS [i386]: Test failure in "globals"
Removed tag(s) moreinfo.
--
853103: ht
Processing control commands:
> severity -1 normal
Bug #853103 [src:a52dec] a52dec: FTBFS [i386]: Test failure in "globals"
Severity set to 'normal' from 'serious'
> tags -1 moreinfo
Bug #853103 [src:a52dec] a52dec: FTBFS [i386]: Test failure in "globals"
Added tag(s) moreinfo.
--
853103: http://
Control: severity -1 normal
Control: tags -1 moreinfo
Hi Daniel,
It does build fine with sbuild:
$ sbuild --arch-all --dist=unstable a52dec_0.7.4-18
...
Status: successful
...
This seems to be a local/pbuilder issue.
Cheers,
Balint
2017-01-29 20:00 GMT+01:00 Daniel Schepler :
> Source: a52de
Your message dated Sun, 29 Jan 2017 22:23:58 +
with message-id
and subject line Bug#852317: fixed in curl 7.52.1-2
has caused the Debian Bug report #852317,
regarding libcurl3: Connection timeout on https streams
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 29 Jan 2017 22:24:06 +
with message-id
and subject line Bug#852072: fixed in packer 0.10.2+dfsg-2
has caused the Debian Bug report #852072,
regarding packer: build time tests are failing
to be marked as done.
This means that you claim that the problem has been dealt wi
Processing commands for cont...@bugs.debian.org:
> tags 852914 - stretch
Bug #852914 [src:latex-make] latex-make: FTBFS: dh_auto_test: make -j1 check
VERBOSE=1 returned exit code 2
Removed tag(s) stretch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
852914: ht
Processing commands for cont...@bugs.debian.org:
> block 852914 with 853119
Bug #852914 [src:latex-make] latex-make: FTBFS: dh_auto_test: make -j1 check
VERBOSE=1 returned exit code 2
852914 was not blocked by any bugs.
852914 was not blocking any bugs.
Added blocking bug(s) of 852914: 853119
> t
Package: texlive-luatex
Version: 2016.20170123-1
Severity: serious
Justification: makes other packages FTBFS
With the last uploaded version in sid (ie 2016.20170123-1), a very
simple lualatex file cannot be compiled anymore with only
texlive-luatex and texlive-latex-base (and their dependencies)
Hi Sebastian,
that looks perfect. I just emailed Dennis (my direct colleague) asking
him to apply the exact same patch!
Best wishes,
Mischa Sallé
On Sun, Jan 29, 2017 at 09:57:59PM +0100, Sebastian Andrzej Siewior wrote:
> On 2017-01-28 15:38:40 [+0200], Adrian Bunk wrote:
> > Hi,
> Hi,
On 29-01-17 22:07, Mischa Salle wrote:
> Hi Sebastian,
>
> that looks perfect. I just emailed Dennis (my direct colleague) asking
> him to apply the exact same patch!
Hi Sebastian,
You are free to go ahead with the NMU; alternatively I could upload the
fix through Mentors but it amounts to the s
Source: tightvnc
Version: 1:1.3.9-9
Severity: serious
https://buildd.debian.org/status/package.php?p=tightvnc
...
gcc -o Xvnc -O2 -ansi -pedantic -L../.././/exports/lib dix/libdix.a
os/libos.a ../.././/lib/Xau/libXau.a ../.././/lib/Xdmcp/libXdmcp.a
../.././/exports/lib/libfont.a hw/vnc/li
On 2017-01-28 15:38:40 [+0200], Adrian Bunk wrote:
> Hi,
Hi,
> #828375 lcmaps-plugins-verify-proxy: FTBFS with openssl 1.1.0
> #828376 lcmaps-plugins-voms: FTBFS with openssl 1.1.0
>
> When trying to fix these FTBFS with OpenSSL 1.1 by switching LCMAPS to
> 1.0.2 I end up also moving VOMS and Gl
Source: python-whoosh
Version: 2.7.0-1.1
Severity: serious
Justification: FTBFS
python-whoosh fails to build from source again. It has regressed since
I prepared my 2.7.0-1.1 NMU (which spent 7 days in the DELAYED queue).
That might indicate a regression in some other package.
In my local sbuild
On 2017-01-29 15:54:36 +, Andy Simpkins wrote:
> Back in August *2015* there was a short discussion regarding removing
> sonsord from lm-sensors as a result of this bug.
>
> Because it is marked as GRAVE, this bug is release critical for Stretch.
>
> Is this really a grave bug, should it be d
Your message dated Sun, 29 Jan 2017 20:36:16 +
with message-id <1485722176.2900.12.ca...@decadent.org.uk>
and subject line Re: linux-image-3.16: md: bug with re-adding a partially
recovered device to a mirror
has caused the Debian Bug report #777511,
regarding linux-image-3.16: md: bug with re
Processing commands for cont...@bugs.debian.org:
> fixed 777511 4.2.6-1
Bug #777511 [src:linux] linux-image-3.16: md: bug with re-adding a partially
recovered device to a mirror
Marked as fixed in versions linux/4.2.6-1.
> thanks
Stopping processing here.
Please contact me if you need assistance
Control: tags 838116 + patch
On Sun, 29 Jan 2017 at 18:52:58 +, Simon McVittie wrote:
> I am probably not going to NMU this, because I can't test this package
> (I don't have an iPod); but I'm build-testing a patch.
See attached (based on pkg-gtkpod git). It seems to work: I was able
to upgra
Processing control commands:
> tags 838116 + patch
Bug #838116 [libgpod-nogtk-dev] libgpod-nogtk-dev: fails to install in sid/i386
with --install-recommends
Added tag(s) patch.
--
838116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838116
Debian Bug Tracking System
Contact ow...@bugs.debia
Your message dated Sun, 29 Jan 2017 22:28:55 +0200
with message-id <20170129202855.nhq4nn3kuzizw3lx@localhost>
and subject line This has been fixed in 2.27-2
has caused the Debian Bug report #853109,
regarding grep-2.27-1 fails when >/dev/null 2>&1
to be marked as done.
This means that you claim t
Processing commands for cont...@bugs.debian.org:
> notfixed 777511 4.0.2-1
Bug #777511 [src:linux] linux-image-3.16: md: bug with re-adding a partially
recovered device to a mirror
No longer marked as fixed in versions linux/4.0.2-1.
> thanks
Stopping processing here.
Please contact me if you ne
control: tags -1 pending
fixed in SVN.
Sebastian
Processing control commands:
> tags -1 pending
Bug #852900 [src:openssl] openssl: FTBFS: Cannot create directory
/<>/debian/tmp/usr/lib/ssl/certs: No such file or directory
Added tag(s) pending.
--
852900: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852900
Debian Bug Tracking System
Contac
Processing control commands:
> tags -1 pending
Bug #852920 [libssl1.1] libnet-ssleay-perl: FTBFS: Test failures
Added tag(s) pending.
--
852920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: grep
Version: 2.27-1
Severity: serious
Tags: patch fixed-upstream
Control: forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25283
This is a bug that was reported to debian-testing.
Severity is based on the fact that grep is a tool where a wrong
return value has the potential to
Processing control commands:
> forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25283
Bug #853109 [grep] grep-2.27-1 fails when >/dev/null 2>&1
Set Bug forwarded-to-address to
'https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25283'.
--
853109: http://bugs.debian.org/cgi-bin/bugreport.cg
package: src:chromium-browser
severity: grave
version: 56.0.2924.76-1
The upload to experimental fails to build on armhf due to new NEON code.
Best wishes,
Mike
Your message dated Sun, 29 Jan 2017 19:33:28 +
with message-id
and subject line Bug#827744: fixed in bzip2 1.0.6-8.1
has caused the Debian Bug report #827744,
regarding bzip2: CVE-2016-3189: heap use after free in bzip2recover
to be marked as done.
This means that you claim that the problem h
Your message dated Sun, 29 Jan 2017 19:33:33 +
with message-id
and subject line Bug#812768: fixed in python-whoosh 2.7.0-1.1
has caused the Debian Bug report #812768,
regarding python-whoosh: FTBFS - tests fail with "No such file or directory:
... english-words.10.gz"
to be marked as done.
T
On Mon, 28 Dec 2015 23:27:34 +0100 Christian Kastner wrote:
> Hi,
>
> thank you for your report. I've already spent a good amount of time
> analyzing the potential impact of this flaw, but I would like to refrain
> from further public comments until I have discussed this with security@d.o.
...an
Control: fixed -1 3.16.36-1
Control: fixed -1 4.0.2-1
signature.asc
Description: This is a digitally signed message part
Processing control commands:
> fixed -1 3.16.36-1
Bug #777511 [src:linux] linux-image-3.16: md: bug with re-adding a partially
recovered device to a mirror
Marked as fixed in versions linux/3.16.36-1.
> fixed -1 4.0.2-1
Bug #777511 [src:linux] linux-image-3.16: md: bug with re-adding a partially
Ben
I have tested against the following kernels on snapshot.d.o
Pass
4.2.1-1
4.0.0-1
3.16.36-1
Fails
3.16.7-ckt4-3
/Andy
Source: a52dec
Version: 0.7.4-18
Severity: serious
>From my pbuilder build log:
...
Making check in test
make[2]: Entering directory '/build/a52dec-0.7.4/test'
make check-TESTS
make[3]: Entering directory '/build/a52dec-0.7.4/test'
make[4]: Entering directory '/build/a52dec-0.7.4/test'
SKIP: reg
On Sat, 17 Sep 2016 at 16:03:19 +0200, Andreas Beckmann wrote:
> This was observed during a test on i386 with --install-recommends enabled.
> I cannot reproduce it on amd64.
...
> Package: libgpod-common
...
> Depends: ..., libgpod4 (>= 0.7.90), ...
Compare with, on amd64:
> Package: libgpod-comm
Your message dated Sun, 29 Jan 2017 18:18:31 +
with message-id
and subject line Bug#852984: fixed in audacious-plugins 3.7.2-2.1
has caused the Debian Bug report #852984,
regarding audacious-plugins: please do not build-depend on oss4-dev on Linux
to be marked as done.
This means that you cla
Your message dated Sun, 29 Jan 2017 18:19:01 +
with message-id
and subject line Bug#852986: fixed in qmmp 1.1.6-1.1
has caused the Debian Bug report #852986,
regarding qmmp: please do not build-depend on oss4-dev on Linux
to be marked as done.
This means that you claim that the problem has be
On Sun, 29 Jan 2017, narf wrote:
> I have the same problem on debian jessie in i386 architecture.
> When will the fixed version (ß-9-6-4) are available i386?
Normally we would have to wait for the next stable to happen, but since
this bug makes the package not to work at all, I'll make an upload
On Sun, Jan 29, 2017 at 06:04:09PM +, Simon McVittie wrote:
> On Sat, 18 May 2013 at 23:29:22 +0200, Richard Hartmann wrote:
> > Broken Python upgrade left me without working debconf.
>
> I can't help thinking that this would be a lot more robust if debconf.deb
> (which is pseudo-Essential) di
Your message dated Sun, 29 Jan 2017 18:04:25 +
with message-id
and subject line Bug#787956: fixed in zlib 1:1.2.8.dfsg-5
has caused the Debian Bug report #787956,
regarding lib32z1-dev: Compiling anything that includes with -m32 fails
to be marked as done.
This means that you claim that the
On Sat, 18 May 2013 at 23:29:22 +0200, Richard Hartmann wrote:
> Broken Python upgrade left me without working debconf.
I can't help thinking that this would be a lot more robust if debconf.deb
(which is pseudo-Essential) didn't ship language bindings for a
non-Essential programming language. perl
Your message dated Sun, 29 Jan 2017 18:04:25 +
with message-id
and subject line Bug#845793: fixed in zlib 1:1.2.8.dfsg-5
has caused the Debian Bug report #845793,
regarding lib64z1-dev doesn't provide a shlibs file, causing package build
failures
to be marked as done.
This means that you cla
On Sun, 29 Jan 2017 at 18:30:09 +0100, Sebastian Ramacher wrote:
> > On Sat, 28 Jan 2017 at 17:54:43 +, Simon McVittie wrote:
> > I have done a non-maintainer upload to DELAYED/7
>
> Thank you. Feel free to reschedule it to DELAYED/0.
Rescheduled. I'll open an unblock bug when it's been accep
On Sun, 29 Jan 2017 at 11:33:11 -0500, Matteo Cypriani wrote:
> > Le 29 janv. 2017 à 11:06, Simon McVittie a écrit :
> > I have uploaded a NMU to DELAYED/7
>
> Looks good to me, thanks. You can go ahead and skip DELAYED if you wish.
Rescheduled to 0-day. I'll write an unblock request when it get
Processing commands for cont...@bugs.debian.org:
> tags 840733 + upstream
Bug #840733 [src:e2fsprogs] e2fsprogs contains non-free file
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
840733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8
Quoting Simon McVittie (2017-01-29 17:57:26)
> On Mon, 01 Aug 2016 at 17:42:36 +0200, Jonas Smedegaard wrote:
> > I agree that sugar-base-0.88 makes sense to drop from Debian.
>
> Let's make that happen.
Thanks!
> According to `dak rm -R -n` this would involve removal of the
> following source
Your message dated Sun, 29 Jan 2017 17:49:03 +
with message-id
and subject line Bug#852840: fixed in xsane 0.999-5
has caused the Debian Bug report #852840,
regarding xsane: FTBFS against libsane-dev 1.0.25-3 - sane-config not found
to be marked as done.
This means that you claim that the pro
Hi,
it has been a while since there has been any activity against this bug.
it is marked as grave, this means that it is Release Critical for Stretch.
I have just run Cyril's md-mirror-resync-broken-v2.sh script on a
machine running stretch rc1 (Linux debian 4.4.0-2amd64 #1 SMP Debian
4.8.15-2 (2
Processing control commands:
> reassign -1 libssl1.1 1.1.0d-1
Bug #852920 [src:libnet-ssleay-perl] libnet-ssleay-perl: FTBFS: Test failures
Bug reassigned from package 'src:libnet-ssleay-perl' to 'libssl1.1'.
No longer marked as found in versions libnet-ssleay-perl/1.80-1.
Ignoring request to alte
Control: reassign -1 libssl1.1 1.1.0d-1
Control: forwarded -1 https://github.com/openssl/openssl/issues/2313
Control: affects -1 src:libnet-ssleay-perl
I have double-checked that libnet-ssleay-perl builds with 1.1.0c-4.
Re-assigning to libssl1.1, so that this bug can be closed with
an OpenSSL upl
On 2017-01-29 16:13:49, Simon McVittie wrote:
> Control: tags 852984 + patch pending
>
> On Sat, 28 Jan 2017 at 17:54:43 +, Simon McVittie wrote:
> > This package build-depends on oss4-dev, which is built by RC-buggy source
> > package oss4.
>
> I have done a non-maintainer upload to DELAYED/
Processing commands for cont...@bugs.debian.org:
> fixed 832864 2.9.4+dfsg1-2.2
Bug #832864 {Done: Mònica Ramírez Arceda } [libxml2]
xmlstarlet: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
Marked as fixed in versions libxml2/2.9.4+dfsg1-2.2.
> thanks
Stopping processing her
On 2017-01-29 10:08, Andy Simpkins wrote:
On 29/01/17 13:18, Paul Wise wrote:
On Sun, Jan 29, 2017 at 7:35 PM, Andy Simpkins wrote:
It is our belief that this is sufficient; that the package FontForge,
and type 1 fonts generated by this package are now DFSG compliant
because Apache 2.0 is GPL2+
Control: retitle -1 Locale hash tables are not built from source; rebuilding
requires gperf
Control: tag -1 - moreinfo
Control: severity -1 normal
On Sun, 18 Dec 2016 22:28:33 +0100 Aurelien Jarno wrote:
> control: tag -1 + moreinfo
>
> On 2016-12-08 16:42, Ximin Luo wrote:
> > Package: glibc
>
Hello Antoine,
Antoine Beaupré [2017-01-29 10:48 -0500]:
> Next time could you coordinate more closely with the security team?
Point taken, sorry about that.
> 3. (optionnally) request a CVE at OSS-security with a CC upstream:
>http://oss-security.openwall.org/wiki/mailing-lists/oss-security
Processing control commands:
> retitle -1 Locale hash tables are not built from source; rebuilding requires
> gperf
Bug #847478 [glibc] FTBFS: needs to Build-Depends on gperf
Changed Bug title to 'Locale hash tables are not built from source; rebuilding
requires gperf' from 'FTBFS: needs to Buil
Control: reassign 832864 libxml2 2.9.4+dfsg1-1
Control: affects 832864 + xmlstarlet
On Wed, 03 Aug 2016 at 17:06:20 +0200, Mònica Ramírez Arceda wrote:
> I am afraid that the problem is a libxml2 bug
Adjusting metadata so the bug tracking system won't think that
xmlstarlet still has a release-cri
Processing control commands:
> reassign 832864 libxml2 2.9.4+dfsg1-1
Bug #832864 {Done: Mònica Ramírez Arceda } [src:xmlstarlet]
xmlstarlet: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
Bug reassigned from package 'src:xmlstarlet' to 'libxml2'.
No longer marked as found in v
Your message dated Sun, 29 Jan 2017 17:04:20 +
with message-id
and subject line Bug#787956: fixed in zlib 1:1.2.8.dfsg-4.1
has caused the Debian Bug report #787956,
regarding lib32z1-dev: Compiling anything that includes with -m32 fails
to be marked as done.
This means that you claim that th
Your message dated Sun, 29 Jan 2017 17:04:20 +
with message-id
and subject line Bug#845793: fixed in zlib 1:1.2.8.dfsg-4.1
has caused the Debian Bug report #845793,
regarding lib64z1-dev doesn't provide a shlibs file, causing package build
failures
to be marked as done.
This means that you c
Processing control commands:
> clone 833157 -2
Bug #833157 [src:sugar-base-0.88] sugar-base-0.88: don't release with Stretch
Bug 833157 cloned as bug 853088
> reassign -2 ftp.debian.org
Bug #853088 [src:sugar-base-0.88] sugar-base-0.88: don't release with Stretch
Bug reassigned from package 'src:s
Control: clone 833157 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: sugar-base-0.88 -- RoQA; superseded by sugar-base
Control: severity -2 normal
On Mon, 01 Aug 2016 at 17:42:36 +0200, Jonas Smedegaard wrote:
> I agree that sugar-base-0.88 makes sense to drop from Debian.
Let's m
Am 29.01.2017 um 17:47 schrieb Lucas Nussbaum:
> On 29/01/17 at 17:28 +0100, Michael Biebl wrote:
>> Am 29.01.2017 um 17:10 schrieb Lucas Nussbaum:
>>
>>> Yes, tzdata is no longer build-essential, and is not installed in the
>>> chroot.
>>
>> [..]
>>
>>> Actually, I did a rebuild specifically for t
On 29/01/17 at 17:28 +0100, Michael Biebl wrote:
> Am 29.01.2017 um 17:10 schrieb Lucas Nussbaum:
>
> > Yes, tzdata is no longer build-essential, and is not installed in the
> > chroot.
>
> [..]
>
> > Actually, I did a rebuild specifically for that some time ago (to file
> > all bugs in that cat
> Andrew, since you've been asking on IRC: if this turns out to be a huge
> problem for many users, we can change that default in NM. For now it
> looks like isolated incidents so I'd keep the current configuration for now.
I just wanted to add some noise here. I couldn't reliably connect to
any w
> Le 29 janv. 2017 à 11:06, Simon McVittie a écrit :
>
> Please see attached patch (against pkg-multimedia git). I have uploaded
> a NMU to DELAYED/7 since it's rather trivial, to make sure qmmp doesn't
> get removed from testing as a result of its oss4 dependency; I'm happy
> to cancel it or ha
Am 29.01.2017 um 17:10 schrieb Lucas Nussbaum:
> Yes, tzdata is no longer build-essential, and is not installed in the
> chroot.
[..]
> Actually, I did a rebuild specifically for that some time ago (to file
> all bugs in that category). I assume that something changed on the
> systemd side, caus
Dear maintainer,
I've prepared an NMU for symfony (versioned as 2.8.7+dfsg-1.2). The diff
is attached to this message. This fixes the test suite failures on the
buildd which I failed to notice when preparing my previous NMU (I was
using an outdated chroot). I have uploaded directly to unstable aga
Processing control commands:
> tags 852985 + patch
Bug #852985 [src:gsequencer] gsequencer: please do not build-depend on oss4-dev
on Linux
Added tag(s) patch.
--
852985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with proble
Control: tags 852985 + patch
On Sat, 28 Jan 2017 at 17:55:43 +, Simon McVittie wrote:
> This package build-depends on oss4-dev, which is built by RC-buggy source
> package oss4.
I attach a possible patch.
I don't know how to test gsequencer, so I am not intending to do a
NMU for this bug.
R
Processing control commands:
> tags 852984 + patch pending
Bug #852984 [src:audacious-plugins] audacious-plugins: please do not
build-depend on oss4-dev on Linux
Added tag(s) patch and pending.
--
852984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852984
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> tags 852986 + patch pending
Bug #852986 [src:qmmp] qmmp: please do not build-depend on oss4-dev on Linux
Added tag(s) patch and pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
852986: http://bugs.debian.o
Control: tags 852984 + patch pending
On Sat, 28 Jan 2017 at 17:54:43 +, Simon McVittie wrote:
> This package build-depends on oss4-dev, which is built by RC-buggy source
> package oss4.
I have done a non-maintainer upload to DELAYED/7 to make sure this doesn't
result in audacious getting remo
On 29/01/17 at 17:00 +0100, Michael Biebl wrote:
> Hi Lucas
>
> Am 29.01.2017 um 08:15 schrieb Lucas Nussbaum:
> > On 28/01/17 at 10:40 +0100, Michael Biebl wrote:
> >> The package built fine on the buildds just a couple of days ago. Do you
> >> have an idea how the aws build environment differs?
On Sat, 28 Jan 2017 at 17:56:33 +, Simon McVittie wrote:
> This package build-depends on oss4-dev, which is built by RC-buggy source
> package oss4.
Please see attached patch (against pkg-multimedia git). I have uploaded
a NMU to DELAYED/7 since it's rather trivial, to make sure qmmp doesn't
g
Your message dated Sun, 29 Jan 2017 16:03:25 +
with message-id
and subject line Bug#852889: fixed in liblatex-driver-perl 0.300.2-2
has caused the Debian Bug report #852889,
regarding liblatex-driver-perl: FTBFS: Test failures
to be marked as done.
This means that you claim that the problem h
On 29/01/17 at 15:45 +, Simon McVittie wrote:
> On Sun, 29 Jan 2017 at 15:50:38 +0100, Lucas Nussbaum wrote:
> > On 29/01/17 at 11:06 +, Simon McVittie wrote:
> > > If my understanding of TSX (as discussed with the Cambridge BSP) is
> > > correct, this is not release-critical for stretch [.
Hi Lucas
Am 29.01.2017 um 08:15 schrieb Lucas Nussbaum:
> On 28/01/17 at 10:40 +0100, Michael Biebl wrote:
>> The package built fine on the buildds just a couple of days ago. Do you have
>> an idea how the aws build environment differs?
>
> No, sorry
I had a closer look at the log files today.
Hi there,
Back in August *2015* there was a short discussion regarding removing
sonsord from lm-sensors as a result of this bug.
Because it is marked as GRAVE, this bug is release critical for Stretch.
Is this really a grave bug, should it be down graded? Can Sensord be
removed? Is there anoth
* Lucas Nussbaum:
> Source: dfwinreg
> Version: 20160428-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170128 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
Control: affects -1 dfvfs dfwinreg
Control: block 852922 by -1
Control: block 852881 by -1
Source: construct
Version: 2.8.8-0.1
Severity: grave
Dear maintainer,
dfvfs and dfwinreg fail to build from source (test failures) after the
recent construct update:
,
| ImportError: Failed to import
Processing control commands:
> affects -1 dfvfs dfwinreg
Bug #853082 [src:construct] construct: construct 2.8 broke the API -- return to
2.5?
Added indication that 853082 affects dfvfs and dfwinreg
> block 852922 by -1
Bug #852922 [src:dfvfs] dfvfs: FTBFS: Test failures
852922 was not blocked by
* Lucas Nussbaum:
> Source: dfvfs
> Version: 20160918-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170128 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
I
Processing commands for cont...@bugs.debian.org:
> # mark as fixed in version 2.75.1+dfsg-1
> close 853004 2.75.1+dfsg-1
Bug #853004 [calibre] security: javascript in the book can access files on the
computer using XMLHttpRequest?
Marked as fixed in versions calibre/2.75.1+dfsg-1.
Bug #853004 [ca
On Fri, Jan 27, 2017 at 10:34:29AM +0100, lopiuh wrote:
> as discussed in https://lists.debian.org/debian-ssh/2017/01/msg00059.html
> PermitRootLogin gets wrong default in /etc/ssh/sshd_config
>
>* What led up to the situation?
> Clean installation, no old config file (/etc/ssh/sshd_config) pr
1 - 100 of 161 matches
Mail list logo
