Why the severity? The fonts-liberation2 package is now a transitional package
which pulls in the actual fonts-liberation package. Von meinem/meiner Galaxy
gesendet
Why the severity? The fonts-liberation2 package is now a transitional package
which pulls in the actual fonts-liberation package. Von meinem/meiner Galaxy
gesendet
Do you have the heif-gdk-pixbuf package installed? Von meinem/meiner Galaxy
gesendet
Control: tag -1 pending
Hello,
Bug #1040360 in openal-soft 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
unblock 694320 by 694308
The fonts files in fonts-urw-core35 are not built by fontforge anymore.
- Fabian
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmMUfacACgkQy+qOlwzN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Samstag, dem 27.08.2022 um 19:40 +0200 schrieb Jonas Smedegaard:
> Yes, Ghostscript contains a script update-gsfonts which makes use of
> it.
I see, thank you . So, I'll keep the file.
Do you guys think I will have to post a heads-up to
/-/blob/master/debian/10fonts-urw-base35.conf
Am Samstag, dem 27.08.2022 um 14:12 +0200 schrieb Fabian Greffrath:
> Am Freitag, dem 26.08.2022 um 09:52 +0200 schrieb Roland Rosenfeld:
> > Just go for it.
>
> I have just uploaded fonts-urw-base35_20200910-2 to experimental
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Freitag, dem 26.08.2022 um 09:52 +0200 schrieb Roland Rosenfeld:
> Just go for it.
I have just uploaded fonts-urw-base35_20200910-2 to experimental which
takes over the gsfonts and gsfonts-x11 packages. So, if you guys could
check if the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 28 Jul 2022 10:21:17 +0200 Fabian Greffrath
wrote:
> > Maybe now is the time?
> Indeed my plan is to tackle this issue in about four weeks.
I currently despair of the format of the fonts.scale and fonts.alias
files that are
> Maybe now is the time?Indeed my plan is to tackle this issue in about four
> weeks. - Fabian Von meinem/meiner Galaxy gesendet
Ursprüngliche Nachricht Von: Chris Hofstaedtler
Datum: 28.07.22 01:02 (GMT+01:00) An: Fabian Greffrath
, 977...@bugs.debian.org Cc:
Control: tag -1 pending
Hello,
Bug #1008424 in flac 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:
Control: tag -1 pending
Hello,
Bug #1008424 in flac reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
Am 16.12.2021 11:22, schrieb G. Heine:
this version displays only letters a-z correctly thus making the system
hardly
usable, unless you change to a different font. The problem is best
shown with
the attached screen-shot.
this seems to be a duplicate of
Hi all,
Am 07.02.2021 22:51, schrieb Jonas Smedegaard:
Added now explicitly.
well, thanks. I can't wait to participate in this discussion.
My stance on this: In theory it should be technically possible to
replace the gsfonts (and gsfonts-x11) package with fonts-urw-base35 and
I believe
Hi Jonas,
Am Sonntag, den 20.12.2020, 14:10 +0100 schrieb Jonas Smedegaard:
> This package has been superseded by fonts-urw-base35, which contains
> the
> same fonts but a newer release and using policy-compliant package
> name.
indeed, I have prepared fonts-urw-base35 to take over both gsfonts
Am 2020-11-09 20:58, schrieb Paul Gevers:
# Failed test 'Testing stderr'
# at debian/tests/cfftot1.t line 24.
# got: 'cfftot1:
/usr/share/fonts/truetype/artemisia/GFSArtemisia.otf: No such file or
directory
This is looking for an opentype font in the truetype directory, which is
Control: tag -1 pending
Hello,
Bug #957394 in jumpnbump 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:
Control: tags -1 confirmed pending fixed-upstream
Control: forwarded -1
https://github.com/coelckers/prboom-plus/commit/29320630c9ae878e537f451f173dbf9007d6786b
Hi Adrian,
Am Samstag, den 23.05.2020, 15:39 +0300 schrieb Adrian Bunk:
> cd /<>/obj-s390x-linux-gnu/data && ./rdatawad -I [...]
> /<>/obj-s390x-linux-gnu/prboom-plus.wad
> Segmentation fault
> make[3]: *** [data/CMakeFiles/prboomwad.dir/build.make:257: prboom-
> plus.wad] Error 139
are these
Control: reopen -1
Control: found -1 1.98-1
Hi Sven,
Am 18.04.2020 07:50, schrieb Sven Joachim:
Since chocolate-doom was there first to ship the offending file, I
assume it should be removed from crispy-doom.
I'll take care of that with the next upload, thank you!
- Fabian
Control: tag -1 pending
Hello,
Bug #946474 in fluidsynth 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:
Control: tag -1 pending
Hello,
Bug #941559 in xvidcore reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi James,
Am 02.10.2019 01:45, schrieb James Cowgill:
Indeed readelf contains some non-executable program headers in
2:1.3.5-1+b1 which do not appear in 2:1.3.5-1 in buster. The
".rotext" section sounds suspicious.
indeed, the check_cpu_feature() function is defined in
Am Donnerstag, den 29.08.2019, 09:54 -0400 schrieb Hugo Lefeuvre:
> Ack, I'll NMU then. Good luck with the baby :)
Thank you! \o/
- Fabian
signature.asc
Description: This is a digitally signed message part
Dear Hugo,
Am Donnerstag, den 29.08.2019, 08:04 -0400 schrieb Hugo Lefeuvre:
> Fabian (faad2 maintainer and upstream), do you want to handle this?
> Otherwise I can NMU a second time with this patch.
please go ahead with a second NMU. I am a bit short on time currently
(home alone with the 10mo
Control: severity -1 normal
Hi Antonio,
thanks for the report, but I fail to see how a change in vertical
spacing could justify grave severity for a font package.
- Fabian
signature.asc
Description: This is a digitally signed message part
Control: severity -1 normal
Control: tags -1 +unreproducible
Am Donnerstag, den 20.12.2018, 21:38 +0200 schrieb Adrian Bunk:
> Warning: Option `-w G' is deprecated! Use option `-a qsq' instead
> postbuild_processing/tt-hinting/Hack-Regular-TA.txt:3:1: invalid
> glyph name (0x204)
> uni0023
Adrian Bunk wrote:
> Warning: Option `-w G' is deprecated! Use option `-a qsq' instead
> postbuild_processing/tt-hinting/Hack-Regular-TA.txt:3:1: invalid glyph
> name (0x204)
> uni0023 touch 0,1,2,3,18,19,20,21,22,23,24,25,26,27,28,31 x 0.25 @ 13
> ^
> Unable to execute ttfautohint on the
Hi,
Simon McVittie wrote:
> .PHONY: build
isn't the "clean" rule called before anything else? Couldn't we just
remove this directory in the "clean" rule?
- Fabian
Hi Klaumi,
Am Sonntag, den 22.10.2017, 15:24 +0200 schrieb Klaumi Klingsporn:
> Maybe it helps to upgrade libmp3lame0 to 3.100-2 as well?
> In this case lame should depend on this version (or above)
> of course!
the point is that in the lame 3.100-2 upload the library got a symbols
file that
control: tags -1 +unreproducible
Am Sonntag, den 22.10.2017, 14:01 +0100 schrieb Alex Dekker:
> Package: lame
> Version: 3.100-2
Hi Alex,
I cannot reproduce your issue.
> ii libmp3lame0 1:3.99.5-0.1
Ahem, please update the library package as well.
Thanks,
- Fabian
signature.asc
Am Freitag, den 29.09.2017, 14:08 + schrieb Holger Levsen:
> As you will have seen, I've done this now. :)
Cool, thanks! I have tagged what I uploaded as -4 yesterday in GIT, so
we should be clean again. ;)
Cheers,
- Fabian
signature.asc
Description: This is a digitally signed message
Holger Levsen wrote:
> I think you forgot a tag?
Oh, indeed. I'll push the "-4" tag when I am at home.
> ok, will do!
Thank you!
- Fabian
Am Freitag, den 29.09.2017, 00:05 + schrieb Holger Levsen:
> Sure, I'm happy to do that! Did you push everything to git?
Yes, I have pushed everything. The latest commit is my attempt to merge
both of our efforts, i.e. what *should* have become revision -4.
Please upload a new revision, I'll
Am Donnerstag, den 28.09.2017, 19:37 + schrieb Holger Levsen:
> just revert my changes and apply your changes… (and then I can
> cherry-pick
> those changes of mine which you didnt do…)
I have already merged our branches and also the changelog, so it would
probably be the cleanest solution to
Am Donnerstag, den 28.09.2017, 20:23 +0200 schrieb Fabian Greffrath:
> I am on this, about to upload!
Sorry, I have uploaded this before I could realize you already changed
the packaging in GIT. And then my upload was ACCEPTED before I could
send the dcut token to cancel it. Now we h
Am Donnerstag, den 28.09.2017, 16:22 + schrieb Holger Levsen:
> I've tried to simply set PYTHON=python3 in fonts-liberation2's
> upstream
> Makefile but that just caused a syntax error as the code aint ready
> for
> python3.
I am on this, about to upload!
- Fabian
signature.asc
Adrian Bunk wrote:
> python scripts/setisFixedPitch-fonttools.py src/LiberationMono-*.ttf
> /bin/sh: 1: python: not found
> Makefile:58: recipe for target 'ttf-dir' failed
> make[1]: *** [ttf-dir] Error 127
> make[1]: Leaving directory '/build/1st/fonts-liberation2-2.00.1'
> dh_auto_build: make
8d60f326aa15111f433ca194ee5b31883160d5fd
Author: Fabian Greffrath <fab...@debian.org>
Date: Wed Aug 2 20:47:26 2017 +0200
update debian/changelog
diff --git a/debian/changelog b/debian/changelog
index 7987cb6..9a589b3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+faad2 (2.8.1-2) unstable; u
control: tags -1 +patch
Am Donnerstag, den 29.06.2017, 12:04 +0100 schrieb James Cowgill:
> It looks to me like the game loop has no sleeps or other waiting in
> it.
> It has probably always consumed 100% CPU.
Good catch! I have simply added a usleep(10) call in the main loop,
effectively
Markus Koschany wrote:
> graphics are completely different. Yes, the level design of pixbros
> resembles those of the other non-free games but it is not a direct copy.
> Also the gameplay is much different. I am not aware of any design
> patents for those non-free games hence I am quite sure that
Control: severity -1 normal
Control: block -1 by 831425
Am Mittwoch, den 19.04.2017, 09:15 +0200 schrieb Lucas Nussbaum:
> E: Build killed with signal TERM after 150 minutes of inactivity
I fail to reproduce this on amd64, so I am sure this is due to the
known issue of fontforge exporting
Am Mittwoch, den 19.04.2017, 09:15 +0200 schrieb Lucas Nussbaum:
> [K [36mRMO[0mmsk-ocrb10efg.rmo
> > E: Build killed with signal TERM after 150 minutes of inactivity
This is the "remove overlaps" script called rmo.pe, which calls
fontforge with the following shebang line:
Guys, thanks for taking the time to discuss this issue with me.
Since I am the one who sponsored the 1.204-1 upload, I will also do the
next one. I will just re-upload the package with its section changed to
contrib/fonts. Is this sufficient or is there anything else needed?
Thanks for your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I admit it's a bit hard to argue against three, but I'll try anyway. ;)
Am Mittwoch, den 18.01.2017, 01:12 + schrieb Scott Kitterman:
> DFSG #2 requires that "The program must include source
> code". Preferred form of modification is the
t;r...@gnu.org>
To: Fabian Greffrath <fab...@greffrath.com>
Subject: Re: [ghostscript] opentypefont
These fonts, however, are supplied in a binary, though editable, format
called PFB. In our opinion this file format corresponds to object code
and is clearly not "t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Mittwoch, den 18.01.2017, 03:24 +1100 schrieb Ben Finney:
> Debian recipients should have equal access to make modifications to
> the work, build the work from modified source, and install the
> result.
All these modifications could be made to
Paul Wise wrote:
> The issue isn't that they currently use proprietary software to
> convert to OTF format. The issue is that there is no Free Software in
> Debian main that can build the OTF from source. This is a clear
> violation of Debian policy and that indicates the package needs to be
> in
Dear Ben,
thank you very much for your bug report. However, I believe you are wrong
with applying RC severity to this issue and I have added FTP-Masters to CC
in the hope for clarification.
Ben Finney wrote:
> I see now that this refers to a proprietary program named Glyphs, as a
> program used
It's just a wild guess, but this
Pietro Battiston wrote:
> Package: ardour
> Version: 1:5.4.0~dfsg-1
[...]
> ii ardour-data 1:4.2~dfsg-5
just doesn't seem corect to me!
- Fabian
Am Sonntag, den 17.07.2016, 16:24 +0100 schrieb James Cowgill:
> Woops I think that was my fault. It should be fixed in 2.0.3+dfsg1-2.
Thanks for taking care of this!
Is there a way to tell pbuilder to build arch:all and arch:any parts
separately, so bugs like this become apparent during a usual
Am Samstag, den 16.07.2016, 19:17 + schrieb Thorsten Glaser:
> I’ll compile and test it now (modulo time needed for cooking,
> eating, etc). and mail back.
Ah, whatever. It compiled fine and so I uploaded it. So users can
upgrade their sid systems. Everything else could be buffed out in a
Hi Thorsten,
I could do a team upload of the current state in GIT this evening.
Could you confirm this is fine for uploading as it is now?
- Fabian
Am Samstag, den 16.07.2016, 12:18 + schrieb Thorsten Glaser:
> Hi everyone,
>
> the version in the packaging repository allegedly fixes the
Am Sonntag, den 13.03.2016, 21:25 +0100 schrieb Sebastian Ramacher:
> Yes, dvdwizard would have to be RoQ-ed if we are going to remove
> transcode. But it's also dead upstream and orphaned.
Alright, let's go for it.
Anyway, since transcode is a command-line utility, it should be rather
Am Dienstag, den 08.03.2016, 23:39 +0100 schrieb Sebastian Ramacher:
> What do you think?
No objections, except for this:
$ apt-cache rdepends transcode
transcode
Reverse Depends:
transcode-doc
xjadeo
transcode-dbg
multimedia-video
python-mecavideo
dvdwizard
It appears that at least
Hi Chris,
Am Mittwoch, den 07.10.2015, 21:18 +0100 schrieb Chris Lamb:
> The full build log is attached [...]
that's 1.8 MB.
Please consider using gzip when transmitting files of this size. I am
reading mails over my phone on the train and incidently hitting a mail
like this may come out costy.
Am Donnerstag, den 08.10.2015, 09:07 +0100 schrieb Chris Lamb:
> Good grief, apologies. Let me know if you get dinged for this and
> I'll get you some BTC or somthing.
Never mind! By "costy" I meant "it drains off my high-speed volume". It
was not meant in the monetary sense, sorry for the
Control: severity -1 minor
Hi,
Am Samstag, den 26.09.2015, 21:49 -0430 schrieb PICCORO McKAY Lenz:
> Severity: grave
there is a policy regarding bug severities:
https://www.debian.org/Bugs/Developer#severities
This does not even remotely justify for a release-critical severity.
> debian
Am Dienstag, den 18.08.2015, 09:58 +0200 schrieb Fabian Greffrath:
> unfortunately, I had no luck convincing the SRM to accept my proposed e
> -d-s update in Jessie in #789429. I didn't even receive a singly reply
> after ~2 months. Maybe one of you wants to try his luck with it?
So, 8.2
Hi Jack,
Am Mittwoch, den 26.08.2015, 00:20 +0200 schrieb Jack Underwood:
> Any news on this bug? It looks like quite a simple fix, I would do it
> myself but I don't know how to use the debian git system (I have only
> ever used github before).
it should have made it to testing now.
Cheers,
Hi all,
Am Mittwoch, den 26.08.2015, 00:20 +0200 schrieb Jack Underwood:
Any news on this bug? It looks like quite a simple fix, I would do it
myself but I don't know how to use the debian git system (I have only
ever used github before).
would anyone object if I nmu, ne team-upload this?
Hi there,
Am Montag, den 15.06.2015, 10:46 +0200 schrieb Josselin Mouette:
I put 3.12.11 in unstable precisely so that it gets a little testing,
and I’d indeed like to see it in 8.2 if the diff is acceptable.
unfortunately, I had no luck convincing the SRM to accept my proposed e
-d-s update
Control: tags -1 + patch
Am Montag, den 08.06.2015, 09:07 +0200 schrieb Fabian Greffrath:
*((char *)buffer) = tmp;
Correction: You'll also need to dereference the tmp pointer, i.e.:
--- supertux-0.3.5a.orig/src/audio/wav_sound_file.cpp
+++ supertux-0.3.5a/src/audio/wav_sound_file.cpp
Am Donnerstag, den 13.08.2015, 20:05 +0200 schrieb Evgeni Golov:
-lSDL_image -lSDL_mixer
Is there anything special in your setup that would trigger this?
It seems to link against both SDL_image and SDL_mixer, but not against
SDL itself!
- Fabian
signature.asc
Description: This is a
Am Montag, den 15.06.2015, 10:56 +0200 schrieb Emilio Pozuelo Monfort:
OK. But beware of http://bugs.debian.org/787624 when trying to push
this to jessie.
So, there are two package revisions +deb8u{1,2} that are currently
missing from the jessie branch in SVN, right?
What is the gbp
Hi Emilio,
Am Freitag, den 12.06.2015, 19:54 +0200 schrieb Emilio Pozuelo Monfort:
There's already a branch in pkg-evolution/jessie/evolution-data
-server/. Use
that, build and test the packages in jessie, then open a p-u bug
against
release.debian.org with a debdiff from jessie attached.
Dear pkg-evolution,
this bug is present in the versions of e-d-s/libcamel currently in
unstable/testing and stable. It is really severe as it prevents mails
from being sent without evolution (and thus the user) taking any notice
of it. It thus may cause (and already has for me) silent data loss.
Hi Vincent,
Am Donnerstag, den 04.06.2015, 00:40 -0700 schrieb Vincent Cheng:
/«PKGBUILDDIR»/src/audio/wav_sound_file.cpp:162:4: error: 'void*' is not a
pointer-to-object type
*buffer = tmp;
^
make[3]: *** [CMakeFiles/supertux2.dir/src/audio/wav_sound_file.cpp.o] Error 1
Any help
Control: fixed -1 3.16.2-1
*sigh* will this work?
signature.asc
Description: This is a digitally signed message part
Package: evolution-data-server
Version: 3.12.9~git20141128.5242b0-2+deb8u2
Severity: critical
Tags: patch
Justification: causes serious data loss
Hi there,
there is a serious bug in libcamel 3.12.3. This bug is not fixed in
3.12.11 and since 3.12.11 is the last upstream release of that
branch,
Control: notfound -1 3.16.2-1
signature.asc
Description: This is a digitally signed message part
Control: found -1 3.12.9~git20141128.5242b0-2+deb8u2
Control: found -1 3.12.11-1
Control: notfound -1 3.16
Control: tags -1 +upstream +patch
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=749292
signature.asc
Description: This is a digitally signed message part
Hi there,
Am Samstag, den 30.05.2015, 18:46 +0200 schrieb Niklaas Baudet von
Gersdorff:
I already looked for a way to do so but remained unsuccessful. What is
the best way to achieve this once the packages have already been
installed from deb-multimedia.org ?
please follow the advice here
Control: severity -1 minor
Control: forwarded -1
https://github.com/chocolate-doom/chocolate-doom/issues/479
Control: tags -1 upstream pending
Control: retitle -1 accidental license upgrade to GPLv3+
Upstream also considers this a non-issue, thus downgrading severity:
Dear Jonathan,
Am Mittwoch, den 20.05.2015, 04:39 + schrieb Debian testing
autoremoval watch:
chocolate-doom 2.1.0-1 is marked for autoremoval from testing on 2015-06-10
It is affected by these RC bugs:
785122: chocolate-doom: includes licence-incompatible GPLv3 code
this is getting
Hi Jon,
Am Dienstag, den 12.05.2015, 14:17 +0100 schrieb Jonathan Dowland:
Chocolate-doom includes code taken from GnuPG, which is GPLv3, whereas
chocolate-doom is GPLv2 (or later). Upstream have fixed this by replacing
the AES implementation with one from the kernel. See
doesn't mixing
Hi all,
thanks for your replies!
Am Sonntag, den 26.04.2015, 01:10 +1000 schrieb Dmitry Smirnov:
.symbols seems not to be very useful for C++ and they come with high
maintenance cost. I'd probably just remove libflac++6.symbols...
Yes, that would probably be the easiest solution. And I am
Am Sonntag, den 26.04.2015, 19:01 +1000 schrieb Dmitry Smirnov:
No worries, I'll do that. :)
Cool, thank you very much for uploading!
- Fabian
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Control: tags -1 + help
Hi Sebastian,
Am Freitag, den 24.04.2015, 21:27 +0200 schrieb Sebastian Ramacher:
| - _ZN4FLAC7Decoder4File13read_callbackEPhPm@Base 1.3.0
| + _ZN4FLAC7Decoder4File13read_callbackEPhPj@Base 1.3.1-1
| +#MISSING: 1.3.1-1# _ZN4FLAC7Decoder4File13read_callbackEPhPm@Base
Control: reassign -1 doomsday
I once helped to get the package back up into shape in order to
provide another alternative engine (besides prboom-plus) that was able
to run freedoom. This was around the time when vavoom became unusable
and was eventually removed from Debian.
Meanwhile,
Source: deng
Version: 1.10.4-2
Severity: serious
Justification: Policy 5.6.3
Hi all,
I once helped to get the package back up into shape in order to
provide another alternative engine (besides prboom-plus) that was able
to run freedoom. This was around the time when vavoom became unusable
and
Am Dienstag, den 02.12.2014, 23:29 +0100 schrieb Bastien ROUCARIES:
And offencive (sexist) for 50% of the population the women...
Now it's getting really ridiculous. Gosh, it's a picture of a woman!
- Fabian
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject
Am Mittwoch, den 26.11.2014, 19:58 -0800 schrieb Erik de Castro Lopo:
One more patch to cherry pick:
Thank you very much!
I hope to be able to prepare updated packages by next week.
- Fabian
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
On Mon, 10 Nov 2014 21:44:58 +0100 Pino Toscano p...@debian.org wrote:
Please drop this NMU, since the approach chosen (bumping shlibs for
everybody) is not correct.
We once had a very similar issue in the ffmpeg, ne libav packaging,
where we had to declare much stricter dependencies among the
Hi Ondřej,
thanks for taking care of the libjpeg-turbo transition!
Am Samstag, den 18.10.2014, 15:48 +0200 schrieb Ondřej Surý:
Package: src:vavoom
Version: 1.33-5
Severity: serious
Justification: libjpeg-turbo transition
vavoom is currently only available in stable and experimental, and
Hi all,
Am Dienstag, den 23.09.2014, 00:53 -0700 schrieb Vincent Cheng:
jumpnbump-levels does not currently have any human uploaders. This is a
violation of a must directive in Policy 5.6.3 [1], hence it is a RC bug.
I have prepared a new package in
Package: brasero
Version: 3.10.0-1
Severity: critical
This happens when I try to start Brasero, the last line translates to
segmentation fault:
$ brasero
(brasero:32051): GLib-GObject-WARNING **: The property GtkMisc:xalign is
deprecated and shouldn't be used anymore. It will be removed in a
This is the backtrace (sorry, no additional debug symbols installed):
0x76334e86 in gtk_widget_size_allocate_with_baseline ()
from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
(gdb) bt
#0 0x76334e86 in gtk_widget_size_allocate_with_baseline ()
from
Hi Simon,
Am Dienstag, den 10.06.2014, 23:01 +0100 schrieb Simon McVittie:
Looks like a change in make(1) behaviour: a rule to build
build/24/quake.png used to take precedence over one for
build/%/quake.png (and the same for 3 other basenames), and now it doesn't.
This was more fragile
Am Samstag, den 10.05.2014, 21:27 -0700 schrieb Vincent Cheng:
Built, signed, and uploaded, thanks for your work!
Thank you so much for uploading the packages!
Best regards,
Fabian
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Am Montag, den 05.05.2014, 23:15 -0700 schrieb Vincent Cheng:
Don't forget that the Debian Games team
has a sponsorship queue [1] that you can use if you're looking for a
sponsor within the team; I aim to regularly check the queue for
packages to sponsor.
Alright, I have added my pending
Am Montag, den 05.05.2014, 23:15 -0700 schrieb Vincent Cheng:
Built, signed, and uploaded.
Thank you!
Don't forget that the Debian Games team
has a sponsorship queue [1] that you can use if you're looking for a
sponsor within the team; I aim to regularly check the queue for
packages to
Dear Andreas,
this bug is fixed in GIT since the day you reported it. However,
unfortunately my regular sponsor is short of time and has somwhow thrown
the towel for package uploads in the short term. Since I don't want to
keep this (otherwise perfectly fine) package from testing any longer and
Dear Olly,
Am Freitag, den 07.03.2014, 15:07 +1300 schrieb Olly Betts:
If I rebuild vavoom 1.33-4 with current unstable, then install it and
run vavoom, it fails to start. If I reinstall the package of 1.33-4
currently in the archive, vavoom starts OK, and seems to work - I played
a whole
Am Freitag, den 07.03.2014, 09:50 + schrieb Olly Betts:
http://www.vavoom-engine.com/ seems to work for me, and while it's
not as dead as some upstreams I've seen, the last release was over 3
years ago, and last SVN commit about 2.5 years ago:
severity 738811 important
thanks
Am Montag, den 03.03.2014, 08:16 -0500 schrieb Reinhard Tartler:
Thanks for the feedback. I'm reassigning this bug accordingly.
And I agree with Tony Mancill that this does not need to be
release-critical.
- Fabian
--
To UNSUBSCRIBE, email to
Am Dienstag, den 25.02.2014, 09:51 +0100 schrieb Jan Korous:
That's funny. I didn't notice this option. As soon as I unchecked the
box (and started using libdvdread) it works. So the problem was in
dvdnav actually (or at least according to the checker box label).
Let's hope new new releases
Am Donnerstag, den 13.02.2014, 08:37 +0100 schrieb Jan Korous:
I have tried 2 different DVDs which I was able to play at the same machine
without a glitch.
Could you please try again with the libdvdcss2 package installed?
- Fabian
--
To UNSUBSCRIBE, email to
Dear Andreas,
thank you very much for this bug report!
Am Donnerstag, den 06.02.2014, 02:36 +0100 schrieb Andreas Beckmann:
dh_auto_install --max-parallel=1 --
This will be fixed in the next upload. However, I have yet to understand
why overriding the documentation install directory
1 - 100 of 283 matches
Mail list logo
