Petter Reinholdtsen (2014-11-23):
> Control: notfound -1 1.0.51
>
> Probably a good idea to make BTS aware of when this issue was fixed.
notfound != fixed.
> Not sure if it should be closed or if an stable update is needed, so I
> leave it open.
Figuring it out is the plan:
https://lists.deb
Your message dated Sun, 23 Nov 2014 05:18:46 +
with message-id
and subject line Bug#770647: fixed in libclamunrar 0.98.5-1
has caused the Debian Bug report #770647,
regarding double free in libclamunrar_iface + memory leak in read_block()
to be marked as done.
This means that you claim that t
Osamu Aoki wrote:
> On Sat, Nov 22, 2014 at 01:30:41PM -0600, Charles Cazabon wrote:
> >
> > As Linus Torvalds says, there's no real difference between "bugfix" and
> > "security fix", and I would argue there's almost as little difference
> > between "bugfix" and "new feature".
>
> If you added
On 11/22/2014 03:34 PM, Markus Koschany wrote:
> tags 769301 patch
> severity 765933 important
> thanks
>
> On Wed, 12 Nov 2014 16:57:45 +0100 Markus Koschany wrote:
> [...]
>> apparently bug #765933 in mesa causes a FTBFS in java3d. I think this is
>> a regression and easier to fix in mesa itsel
Your message dated Sun, 23 Nov 2014 03:35:04 +
with message-id
and subject line Bug#769301: fixed in java3d 1.5.2+dfsg-10
has caused the Debian Bug report #769301,
regarding java3d: FTBFS error: unknown type name 'GLintptr'
to be marked as done.
This means that you claim that the problem has
On 2014-11-23 00:30, Rebecca N. Palmer wrote:
> I think the trigger is nvidia-opencl-icd adding a new dependency on
> libcuda1 (changelog: Add libcuda1 dependency to libraries that seem to
> be capable of doing dlopen("libcuda.so") or dlopen("libcuda.so.1").),
> which pulls in the rest of nvidia-*
On Sun, Nov 23, 2014 at 02:07:42AM +0100, Christian Kastner wrote:
> On 2014-11-23 01:16, Adam Borowski wrote:
> > On Sat, Nov 22, 2014 at 09:09:55PM +0100, Tomasz Buchert wrote:
> >> On 10/11/14 10:56, Christian Kastner wrote:
> >> I cannot confirm this bug in both cases I've tried:
> >>
> >> *
Control: tag -1 +confirmed -unreproducible
On 2014-11-23 01:16, Adam Borowski wrote:
> amd64 vanilla 3.16.7: builds ok
> amd64 vanilla 3.17.3: FTBFS
I can confirm that is issue exists with 3.17.
The syscall is returning ENOKEY where until 3.16 it was returning EPERM.
I'll try to investigate the
Processing control commands:
> tag -1 +confirmed -unreproducible
Bug #768905 [src:keyutils] FTBFS: fails test "CHECK INVALID KEY TYPE"
Added tag(s) confirmed.
Bug #768905 [src:keyutils] FTBFS: fails test "CHECK INVALID KEY TYPE"
Removed tag(s) unreproducible.
--
768905: http://bugs.debian.org/cg
On Sun, 23 Nov 2014, Osamu Aoki wrote:
> By the way, I uploaded getmail4_4.46.0-1~bpo70+1_amd64
>
> https://ftp-master.debian.org/new/getmail4_4.46.0-1~bpo70%2B1.html
>
> What do I have to do to get it pushed to backports? Did I have to
> upload it to another server? I do not know why it is sta
On 2014-11-23 01:16, Adam Borowski wrote:
> On Sat, Nov 22, 2014 at 09:09:55PM +0100, Tomasz Buchert wrote:
>> On 10/11/14 10:56, Christian Kastner wrote:
>> I cannot confirm this bug in both cases I've tried:
>>
>> * amd64 (Linux 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64
>> GNU/L
On Sun, 23 Nov 2014, Holger Levsen wrote:
> Hi owner@bugs + listmasters,
>
> any idea why #769557 (Message-ID: <20141114122853.ga11...@xanadu.blop.info>)
> wasn't send to debian-...@lists.debian.org?
Nov 14 12:46:12 s_local@bendel postfix/smtp[22501]: A9DE96F5:
to=, orig_to=,
relay=127.0.0.1[
Your message dated Sun, 23 Nov 2014 00:48:50 +
with message-id
and subject line Bug#770621: fixed in ruby-twitter-text 1.10.0+gem-1
has caused the Debian Bug report #770621,
regarding ruby-twitter-text cannot be loaded
to be marked as done.
This means that you claim that the problem has been
Control: tags 767559 + patch
Control: tags 767559 + pending
Dear maintainer,
to solve the #767559 RC bug, I've prepared an NMU for geoip-database-contrib
(versioned as 1.17+nmu1) and uploaded it to DELAYED/5.
It adds to debian/control Conflicts/Replaces/Provides:
geoip-database-extra.
Please fe
Processing control commands:
> tags 767559 + patch
Bug #767559 [geoip-database-contrib] geoip-database-extra,
geoip-database-contrib: error when trying to install together
Added tag(s) patch.
> tags 767559 + pending
Bug #767559 [geoip-database-contrib] geoip-database-extra,
geoip-database-contri
Hi,
By the way, I uploaded getmail4_4.46.0-1~bpo70+1_amd64
https://ftp-master.debian.org/new/getmail4_4.46.0-1~bpo70%2B1.html
What do I have to do to get it pushed to backports? Did I have to
upload it to another server? I do not know why it is stack there. I
just used "dput". In
https://qa.
Hello,
Please go ahead with the NMU.
Due to lack of public CC to me, I had not noticed the bugreport, that's why
I had not uploaded it myself.
Thank you
On Sun, Nov 23, 2014 at 1:04 AM, Sebastian Ramacher
wrote:
> Control: tags 769215 + patch
> Control: tags 769215 + pending
>
> Dear maint
Hi,
Thanks for your comment. (Charles is the upstream,)
On Sat, Nov 22, 2014 at 01:30:41PM -0600, Charles Cazabon wrote:
> Osamu Aoki wrote:
> >
> > In Debian, its security update policy prohibits any new feature added
> > with security updates.
>
> It's kind of a bogus distinction. As Linus
On Sat, Nov 22, 2014 at 09:09:55PM +0100, Tomasz Buchert wrote:
> On 10/11/14 10:56, Christian Kastner wrote:
> I cannot confirm this bug in both cases I've tried:
>
> * amd64 (Linux 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64
> GNU/Linux)
> * amrhf (Linux 3.14.4.1-bone-armhf.com
Control: notfound -1 1.0.51
Probably a good idea to make BTS aware of when this issue was fixed.
Not sure if it should be closed or if an stable update is needed, so I
leave it open.
--
Happy hacking
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with
Hi owner@bugs + listmasters,
any idea why #769557 (Message-ID: <20141114122853.ga11...@xanadu.blop.info>)
wasn't send to debian-...@lists.debian.org?
+thanks for all your work on keeping the infrastructure running so nicely
99,999% of the time! :-)
signature.asc
Description: This is a digital
Processing control commands:
> notfound -1 1.0.51
Bug #753442 [debootstrap] debootstrap: host's /run/shm gets unmounted after
debootstrap run
Ignoring request to alter found versions of bug #753442 to the same values
previously set
--
753442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=75
Processing control commands:
> tags 769215 + patch
Bug #769215 [src:witty] witty: FTBFS in jessie: Error parsing arguments in:
AuthModel.js
Added tag(s) patch.
> tags 769215 + pending
Bug #769215 [src:witty] witty: FTBFS in jessie: Error parsing arguments in:
AuthModel.js
Added tag(s) pending.
Control: tags 769215 + patch
Control: tags 769215 + pending
Dear maintainer,
Andreas Stührk has prepared an NMU for witty (versioned as
3.3.3+dfsg-4.1) and I have uploaded it for him to DELAYED/2. Please feel
free to tell me if I should delay it longer.
Cheers
--
Sebastian Ramacher
diff -u witt
I suspect this metapackage upgrade problem was triggered by bug #768600
fixed in readahead-fedora version 2:1.5.6-5.2. If I got it right, it
was a problem exposed/triggered by a new dpkg version changing how
triggers were handled, and not really something we can fix in
education-common.
--
Happ
Processing control commands:
> found -1 1.2~alpha-1
Bug #770591 [creepy] Creepy: Plugins not working
Marked as found in versions creepy/1.2~alpha-1.
> notfound -1 1.2~alpha
Bug #770591 [creepy] Creepy: Plugins not working
There is no source info for the package 'creepy' at version '1.2~alpha' with
Control: found -1 1.2~alpha-1
Control: notfound -1 1.2~alpha
I suspect this only affect trying to change the plugin configuration,
which is required to add personal login credentials for flickr and
twitter (and perhaps instagram, but that plugin is missing a python
dependency too).
So if we coul
I don't seem to have ever had pyopencl installed, so that can't be the culprit.
Looking through my apt history, it looks like the critical operation
that gave me nvidia stuff was the installation of libboost (!?):
Start-Date: 2014-06-01 13:05:09
Commandline: apt-get install libboost-all-dev
Inst
Processing commands for cont...@bugs.debian.org:
> tags 769301 patch
Bug #769301 [java3d] java3d: FTBFS error: unknown type name 'GLintptr'
Added tag(s) patch.
> severity 765933 important
Bug #765933 [mesa-common-dev] mesa-common-dev: glx.h should not include
glxext.h when GL_GLEXT_LEGACY is defi
Hey.
On Tue, 2014-11-11 at 20:01 +0100, Michael Biebl wrote:
> We discussed this a bit more yesterday, and we came to the conclusion,
> that for jessie, it's probably the simplest solution, if we explicitly
> call "udevadm settle" in /etc/init.d/networking before it ifup's any
> devices.
> A "ude
tags 769301 patch
severity 765933 important
thanks
On Wed, 12 Nov 2014 16:57:45 +0100 Markus Koschany wrote:
[...]
> apparently bug #765933 in mesa causes a FTBFS in java3d. I think this is
> a regression and easier to fix in mesa itself during the freeze instead
> of patching affected packages.
Control: severity -1 important
Hi,
On Fri, Oct 10, 2014 at 06:21:34PM +0200, Bernd Zeimetz wrote:
> On 10/10/2014 06:14 PM, Michael Biebl wrote:
> > Do you have an example where this actually is a practical issue and not
> > just a theoretical one? I.e, which package makes use escaped unit names
Processing control commands:
> severity -1 important
Bug #764730 [dh-systemd] dh_systemd_start: un-escapes - in unit/directory names
Severity set to 'important' from 'serious'
--
764730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764730
Debian Bug Tracking System
Contact ow...@bugs.debian.
I think the trigger is nvidia-opencl-icd adding a new dependency on
libcuda1 (changelog: Add libcuda1 dependency to libraries that seem to
be capable of doing dlopen("libcuda.so") or dlopen("libcuda.so.1").),
which pulls in the rest of nvidia-* as libcuda1 Recommends:
nvidia-kernel-dkms which R
I just tried to get this building for raspbian (due to our setup I
preffer not to remove stuff from raspbian jessie until/unless it is
removed from debian sid) but even making some pretty horrible hacks I
just hit problem after problem after problem.
My final debdiff is attached . It now fails
Hi Emmanuel,
Emmanuel Bourg wrote (16 Nov 2014 12:06:07 GMT) :
> The new LTS is probably too big to be pushed to testing now. As an
> alternative I'm considering either disabling the master/slave mechanism,
> or adding a big red warning in the UI to inform the user about the risks.
Disabling the
On Mon, 2014-11-10 at 04:36 +0100, Michael Biebl wrote:
> To provide such a syncronisation point, i.e. having network.target and
> network-online.target [1] properly hooked up, I've implemented a PoC
> ifupdown-wait-online service. You can get it from [2] and enable it via
> "systemctl enable ifup
Your message dated Sat, 22 Nov 2014 23:39:54 +0100
with message-id
and subject line Not reproducible
has caused the Debian Bug report #768677,
regarding node-redis: FTBFS in jessie: Tests failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Hey guys...
On Mon, 2014-11-10 at 04:08 +0100, Michael Biebl wrote:
> > But you have seen what I've wrote previously,.. that I *do* in fact also
> > have issues with allow-hotplug... so there most likely is something
> > fishy there (or in unit files of services) as well..
> > So is this somethin
Processing commands for cont...@bugs.debian.org:
> merge 766740 770646
Bug #766740 [gamera] gamera FTBFS on arm64, testsuite failure.
Bug #766740 [gamera] gamera FTBFS on arm64, testsuite failure.
There is no source info for the package 'gamera' at version '3.4.1+svn1423-1'
with architecture ''
U
Processing commands for cont...@bugs.debian.org:
> retitle 770644 systemd: systemd is completely unusable after a fatal signal
Bug #770644 [systemd] systemd: can't start dbus if dbus is not running
Changed Bug title to 'systemd: systemd is completely unusable after a fatal
signal' from 'systemd:
I find that by setting the AC coefficients to alternating values of
32767 and -32768 in the JPEG scanning order (1, 8, 16, 9, 2, 3, etc.), I
can make the Huffman encoder exceed 200 bytes/block every single time.
So that further confirms that 256 is the worst case. I've checked in an
upstream p
Source: hiredis
Version: 0.11.0-4
Severity: serious
>From my pbuilder build log (on amd64):
echo \
"daemonize yes\n" \
"pidfile /tmp/hiredis-test-redis.pid\n" \
"port 56379\n" \
"bind 127.0.0.1\n" \
"unixsocket /tmp/hiredis-test-redis.sock" \
Your message dated Sat, 22 Nov 2014 23:05:31 +0100
with message-id <2014110528.ga7...@ugent.be>
and subject line Re: Bug#768798: libgdbm3:i386: changelog.Debian.gz different
from libgdbm3:amd64
has caused the Debian Bug report #768798,
regarding libgdbm3:i386: changelog.Debian.gz different fro
Package: libclamunrar
Version: 0.96.4-1
Severity: serious
Tags: security pending
The debian security tracker references a problem ("clamav: double-free
error libclamunrar_iface/unrar_iface.c") which it learned from
http://www.openwall.com/lists/oss-security/2013/11/29/6
This got marked as fixed in
package: gamera
severity: serious
version: 3.4.1+svn1423-2
Hi,
The latest upload of gamera FTBFS on arm64, but builds fine on other
architectures. As it built on arm64 before, this is blocking migration to
testing (even though it was unblocked).
Cheers,
Ivo
--
To UNSUBSCRIBE, email to debian
On Sun, 16 Nov 2014 at 22:18:29 +0100, Bastien ROUCARIES wrote:
> Package: src:subsurface
[...]
> Your package seems to include some files that lack sources
> in prefered forms of modification:
>
> theme/jquery.min.js
This appears to be a virtually unmodified jquery 1.6.4: it only differs from
ht
Your message dated Sat, 22 Nov 2014 21:34:12 +
with message-id
and subject line Bug#754003: fixed in el-get 3.1-1.1
has caused the Debian Bug report #754003,
regarding el-get: please switch to emacs24
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Sat, 22 Nov 2014 16:24:14 -0500
with message-id <20141122212414.gb3...@morgul.net>
and subject line Re: Bug#770084: spamassassin: Spamassassin not installable
has caused the Debian Bug report #770084,
regarding spamassassin: Spamassassin not installable
to be marked as done.
Thi
Your message dated Sat, 22 Nov 2014 21:20:00 +
with message-id
and subject line Bug#766944: fixed in slime 2:2.10.1-3
has caused the Debian Bug report #766944,
regarding slime: Emacs"M-x slime"+sbcl fails with "Package SWANK-REPL does not
exist." if cl-swank cache not deleted
to be marked as
Processing control commands:
> retitle 770193 glib2.0: FTBFS if built by root: gsettings test hangs during
> /gsettings/no-write-binding
Bug #770193 [libglib2.0-0] glib2.0: FTBFS in jessie: gsettings test hangs
during /gsettings/no-write-binding
Changed Bug title to 'glib2.0: FTBFS if built by r
Control: retitle 770193 glib2.0: FTBFS if built by root: gsettings test hangs
during /gsettings/no-write-binding
On Sat, 22 Nov 2014 at 19:26:53 +, Simon McVittie wrote:
> Actually, spoke too soon; a build under sudo does eventually fail
> for me. I'm re-running the build as an ordinary user
Processing commands for cont...@bugs.debian.org:
> severity 766944 serious
Bug #766944 [slime] slime: Emacs"M-x slime"+sbcl fails with "Package SWANK-REPL
does not exist." if cl-swank cache not deleted
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.
Please con
On Sat, Nov 22, 2014 at 03:20:26PM -0500, Paul Brossier wrote:
> thanks a lot for looking at this. it sounds like a fairly safe option,
> given how awkward and ancient this code is.
>
> i will give it a go and upload it in a few days.
OTOH, I couldn't get it to run in order to test it - even afte
severity 768816 important
thanks
On Fri, Nov 14, 2014 at 11:01:45AM +0100, Sylvestre Ledru wrote:
> Could you provide the backtrace? I cannot reproduce this issue on
> amd64
I tried in a i386 chroot and cannot reproduce it there either, so
downgrading this bug to non-RC severity.
Michael
--
Processing commands for cont...@bugs.debian.org:
> severity 768816 important
Bug #768816 [fwbuilder] fwbuilder crashes in libqtgui
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
768816: http://bugs.debian.org/cgi-bin/bugre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Michael,
thanks a lot for looking at this. it sounds like a fairly safe option,
given how awkward and ancient this code is.
i will give it a go and upload it in a few days.
best, Paul
On 22/11/2014 15:14, Michael Banck wrote:
> tags 769264 +pat
On Sat, 22 Nov 2014 19:13:26 +1100 Craig Small wrote:
> On Fri, Nov 21, 2014 at 08:19:03AM +0100, Salvatore Bonaccorso wrote:
> > Setting this as severity grave as it is mentioned as critical update.
> > See https://wordpress.org/news/2014/11/wordpress-4-0-1/ for details.
> Thanks for the heads-up
Never mind. I think I answered my own question. Although I don't
understand the Huffman algorithm well enough to know whether this is
algorithmically possible, a naive analysis of the code shows that it
calls PUT_BITS 128 times for each block, and the "size" argument in all
of those cases can
reassign 770605 libssl1.0.0 1.0.2~beta3-1
thanks
* Pirate Praveen [141122 16:12]:
> package: ruby
> version: 1:2.1.0.4
> severity: critical
> justification: bundle command fails
>
> On a sid chroot, bundle install fails with the following error message
>
> when following steps at https://wiki.
Processing commands for cont...@bugs.debian.org:
> reassign 770605 libssl1.0.0 1.0.2~beta3-1
Bug #770605 [ruby] bundle install fails with missing openssl error
Bug reassigned from package 'ruby' to 'libssl1.0.0'.
No longer marked as found in versions ruby-defaults/1:2.1.0.4.
Ignoring request to al
tags 769264 +patch
thanks
Hi,
On Wed, Nov 12, 2014 at 11:45:28AM +0100, Lucas Nussbaum wrote:
> > ./fusebirth > fused_loop.c 2>/dev/null
> > make[1]: *** [fused_loop.c] Error 139
So what happens here is that fusebirth segfaults on i386 in topo_sort(),
while trying to sort whatever in order to g
Processing commands for cont...@bugs.debian.org:
> tags 769264 +patch
Bug #769264 [src:freebirth] freebirth: FTBFS in jessie/i386: XXX
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
769264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=7692
Processing commands for cont...@bugs.debian.org:
> tags 768905 +unreproducible
Bug #768905 [src:keyutils] FTBFS: fails test "CHECK INVALID KEY TYPE"
Added tag(s) unreproducible.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
768905: http://bugs.debian.org/cgi-bin
On 10/11/14 10:56, Christian Kastner wrote:
> Darn, I CCed submit. Sorry about that. I blame my webmail.
>
Hi,
I cannot confirm this bug in both cases I've tried:
* amd64 (Linux 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64
GNU/Linux)
* amrhf (Linux 3.14.4.1-bone-armhf.com #1 SMP T
On Sat, Nov 22, 2014 at 6:58 PM, DRC wrote:
> I can readily reproduce the failure with the supplied test case, but what
> I'm tripping on right now is understanding why a Huffman-encoded block can
> grow so much larger than the size of the source block (128 bytes.) While
> this test case is very
Control: tags -1 pending
Uploaded to DELAYED/5
Thanks Thomasz!
--
tobi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing control commands:
> tags -1 pending
Bug #768690 [src:latex-mk] latex-mk: FTBFS in jessie: build-dependency not
installable: tgif
Added tag(s) pending.
--
768690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with prob
Processing control commands:
> tags 770193 - unreproducible
Bug #770193 [libglib2.0-0] glib2.0: FTBFS in jessie: gsettings test hangs
during /gsettings/no-write-binding
Removed tag(s) unreproducible.
> severity 770193 serious
Bug #770193 [libglib2.0-0] glib2.0: FTBFS in jessie: gsettings test han
Source: statsmodels
Version: 0.6.0~rc2-1
Severity: serious
Justification: fails to build from source
statsmodels now build-depends on nodejs, but nodejs is not available on
some architectures where statsmodels built before. This affects at least
mipsel, powerpc, and s390x.
Cheers
--
Sebastian Ra
3.8.0-2 is ready...
http://anonscm.debian.org/cgit/collab-maint/gedit-latex.git/log/
I'm just waiting a couple of days to see if #768134 gets fixed, then I
will upload in any case.
Pietro
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Troubl
Control: reassign 769646 android-libcutils-dev
Control: found 769646 21-3
Control: fixed 769646 21-4
> You closed 769646 with version 21-4, but 769646 is assigned to
> android-libutils, which doesn't seem to have a version 21-4.
Sorry, I had intended to reassign to android-libcutils-dev, but then
Processing control commands:
> reassign 769646 android-libcutils-dev
Bug #769646 [android-libutils] android-libutils: undefined references in
/usr/lib/android/libutils.so
Bug reassigned from package 'android-libutils' to 'android-libcutils-dev'.
No longer marked as found in versions android-platf
Your message dated Sat, 22 Nov 2014 19:04:35 +
with message-id
and subject line Bug#768494: fixed in imagemagick 8:6.6.0.4-3+squeeze5
has caused the Debian Bug report #768494,
regarding [imagemagick] Some special crafted jpeg file could lead to DOS
to be marked as done.
This means that you cl
Processing commands for cont...@bugs.debian.org:
> close 769231
Bug #769231 [xul-ext-adblock-plus] xul-ext-adblock-plus: incompatible with
iceweasel in stable-security
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
769231: http://bugs.debian.o
close 769231
thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Your message dated Sat, 22 Nov 2014 18:48:50 +
with message-id
and subject line Bug#769265: fixed in libmarpa-r2-perl 2.086000~dfsg-4
has caused the Debian Bug report #769265,
regarding libmarpa-r2-perl: FTBFS in jessie/i386: Bailout called. Further
testing stopped: Could not load Marpa::R2
Your message dated Sat, 22 Nov 2014 18:48:50 +
with message-id
and subject line Bug#769265: fixed in libmarpa-r2-perl 2.086000~dfsg-4
has caused the Debian Bug report #769265,
regarding libmarpa-r2-perl: FTBFS on i386: Could not load XS
to be marked as done.
This means that you claim that the
Processing control commands:
> reopen 769646
Bug #769646 {Done: Simon McVittie } [android-libutils]
android-libutils: undefined references in /usr/lib/android/libutils.so
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need
Control: reopen 769646
Control: tags 769646 sid
Hi Simon,
On Sat, Nov 22, 2014 at 02:53:22PM +, Simon McVittie wrote:
> Version: 21-4
You closed 769646 with version 21-4, but 769646 is assigned to
android-libutils, which doesn't seem to have a version 21-4. Either the fix is
in another packa
Control: tags 769508 + patch
Control: tags 769508 + pending
Dear maintainer,
I've prepared an NMU for apt-spacewalk (versioned as 1.0.6-4.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer. Also attached are the two commits which I
haven't pushed to collab-ma
Processing control commands:
> tags 769508 + patch
Bug #769508 [apt-transport-spacewalk] apt-transport-spacewalk: package removal
fails
Added tag(s) patch.
> tags 769508 + pending
Bug #769508 [apt-transport-spacewalk] apt-transport-spacewalk: package removal
fails
Added tag(s) pending.
--
7695
Control: retitle 770193 glib2.0: FTBFS in jessie: gsettings test hangs during
/gsettings/no-write-binding
Control: tags 770193 + unreproducible
Control: severity 770193 important
On Wed, 19 Nov 2014 at 15:57:34 +, Pietro wrote:
> I am running a testing debian system and I would like to upgrad
Processing commands for cont...@bugs.debian.org:
> # found and fixed version can't be the same
> notfixed 770071 0.11.0-1.1
Bug #770071 {Done: Johann Felix Soden } [src:cpp-netlib]
cpp-netlib: FTBFS under pbuilder: Test failure
No longer marked as fixed in versions 0.11.0-1.1.
> thanks
Stopping p
Processing control commands:
> retitle 770193 glib2.0: FTBFS in jessie: gsettings test hangs during
> /gsettings/no-write-binding
Bug #770193 [libglib2.0-0] libglib2.0-0: Failing to compile package libglibc
(importing a unstable package on a testing system)
Changed Bug title to 'glib2.0: FTBFS i
Processing commands for cont...@bugs.debian.org:
> found 769264 0.3.2-9
Bug #769264 [src:freebirth] freebirth: FTBFS in jessie/i386: XXX
Marked as found in versions freebirth/0.3.2-9.
> tags 769264 + confirmed
Bug #769264 [src:freebirth] freebirth: FTBFS in jessie/i386: XXX
Added tag(s) confirmed.
Of course I meant:
" by DISABLING tgif in ..." (spurious "not")
Tomasz
On 22/11/14 19:06, Tomasz Buchert wrote:
> Hi,
>
> this is a lazy solution to this bug: we remove tgif dependency
> altogether by not disabling tgif in latex-mk. tgif does not seem to be
> available anyway so it is a comprom
Hi,
this is a lazy solution to this bug: we remove tgif dependency
altogether by not disabling tgif in latex-mk. tgif does not seem to be
available anyway so it is a compromise that has to be made. The user
will see an error message if tgif functionality will be used.
You may notice that some un
I can readily reproduce the failure with the supplied test case, but
what I'm tripping on right now is understanding why a Huffman-encoded
block can grow so much larger than the size of the source block (128
bytes.) While this test case is very unusual, there may be others out
there, and I wan
Your message dated Sat, 22 Nov 2014 18:56:06 +0100
with message-id <1416678966.23390.1.ca...@debian.org>
and subject line blockdiag: Fails to build from source in stable
has caused the Debian Bug report #736139,
regarding blockdiag: Fails to build from source in stable
to be marked as done.
This m
On Sat, Nov 22, 2014 at 06:44:31PM +0100, Jonas Smedegaard wrote:
> Quoting Michael Banck (2014-11-22 17:33:17)
> > Attached is a proposed NMU debdiff with an expanded comment in the patch.
>
> Are you ok licensing your patch as "Same as Marpa::R2 code",
Sure.
Michael
--
To UNSUBSCRIBE, ema
Control: tags -1 + moreinfo unreproducible
Control: severity -1 normal
Hi,
After looking a bit into this, it looks as if the parser state of
xsltproc got messed up for some reason. Note that I am unable to
reproduce this in any way, so I tend to think this might have been a
problem with the bu
Processing control commands:
> tags -1 + moreinfo unreproducible
Bug #768881 [src:drbd-utils] FTBFS: unable to parse drbdsetup.xml.in
Added tag(s) unreproducible and moreinfo.
> severity -1 normal
Bug #768881 [src:drbd-utils] FTBFS: unable to parse drbdsetup.xml.in
Severity set to 'normal' from 's
Quoting Michael Banck (2014-11-22 17:33:17)
> Attached is a proposed NMU debdiff with an expanded comment in the patch.
Are you ok licensing your patch as "Same as Marpa::R2 code", or do you
prefer not claiming copyright for it, or something else?
- Jonas
--
* Jonas Smedegaard - idealist & I
Control: tags 768708 + patch
Control: tags 768708 + pending
Dear maintainer,
I've prepared an NMU for sphinxcontrib-nwdiag (versioned as 0.9.0-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru sphinxcontrib-nwdiag-0.9.0/debian/changelo
Processing control commands:
> tags 768708 + patch
Bug #768708 [src:sphinxcontrib-nwdiag] sphinxcontrib-nwdiag: FTBFS in jessie:
unsatisfiable build-dependencies: python-sphinx-testing, python3-sphinx-testing
Added tag(s) patch.
> tags 768708 + pending
Bug #768708 [src:sphinxcontrib-nwdiag] sphin
Processing control commands:
> tags -1 + moreinfo unreproducible
Bug #765071 [mediatomb] mediatomb: No icons in web ui
Added tag(s) unreproducible and moreinfo.
> severity -1 normal
Bug #765071 [mediatomb] mediatomb: No icons in web ui
Severity set to 'normal' from 'grave'
--
765071: http://bugs
Control: tags -1 + moreinfo unreproducible
Control: severity -1 normal
On 2014-11-17 20:38:25, Michele Cane wrote:
> Hi,
>
> I decided to change the severity to grave since I am not able to use
> the program.
> When I reach the webpage from any device the icons are not displayed
> and therefore I
Processing control commands:
> tags 768765 + patch
Bug #768765 [src:sphinxcontrib-seqdiag] sphinxcontrib-seqdiag: FTBFS in jessie:
unsatisfiable build-dependencies: python-sphinx-testing, python3-sphinx-testing
Added tag(s) patch.
> tags 768765 + pending
Bug #768765 [src:sphinxcontrib-seqdiag] sp
Control: tags 768765 + patch
Control: tags 768765 + pending
Dear maintainer,
I've prepared an NMU for sphinxcontrib-seqdiag (versioned as 0.8.0-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru sphinxcontrib-seqdiag-0.8.0/debian/change
1 - 100 of 198 matches
Mail list logo