From: Johannes Schauer Marin Rodrigues
Date: Tue, 10 Sep 2024 19:26:28 +0200
> In an upstream github issue that Keith responded to a week or more ago he did
> say he couldn't do anything immediately as he was "off flying rockets" - I
> took that to mean he is likely enjoying a vacation but may be
Scott Talbert writes:
> On Wed, 30 Nov 2022, Keith Packard wrote:
>
>> Scott Talbert writes:
>>
>>> @Keith, do you have time to upload this patch? Unfortunately, this is
>>> blocking a large number of packages from migrating to testing.
>>> Alternat
Scott Talbert writes:
> @Keith, do you have time to upload this patch? Unfortunately, this is
> blocking a large number of packages from migrating to testing.
> Alternatively, any objections to an NMU?
Thanks for the NMU! Did you happen to create a git repo with this
change? I just noticed th
Scott Talbert writes:
> @Keith, do you have time to upload this patch? Unfortunately, this is
> blocking a large number of packages from migrating to testing.
> Alternatively, any objections to an NMU?
I didn't get to this today, and might not until thursday or
friday. Happy for your to NMU i
I looked for exactly this bug as I fixed the same issue in
binutils-riscv-unknown-elf today, but somehow I missed it.
This should be fixed in version 18 by using dpkg-query instead of
hand-hacked shell bits:
upstream_version := $(shell dpkg-query -W -f="\$${source:Upstream-Version}\n"
binutils-
Matthias Klose writes:
> This blocks migration of gcc-defaults, there is no aarch64 cross
> target on armhf.
Suggestions on how to work around this welcome; I really don't know what
to do. I want to continue providing the generated binaries on all
architectures, but we appear to need to restrict
Adrian Bunk writes:
> I am just a normal user enjoying the game, and looking at the number of
> uploads in the past decade two maintainers might be sufficient to handle
> the load. ;-)
I've uploaded 'kgames' to the new queue :-)
Thanks for playing.
--
-keith
signature.asc
Description: PGP
Paul Gevers writes:
> Your package is only blocked because the arch:all binary package(s)
> aren't built on a buildd. Unfortunately the Debian infrastructure
> doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
> shortly do a no-changes source-only upload to DELAYED/15, closi
Steven Robbins writes:
> On Saturday, December 26, 2020 12:50:58 A.M. CST Keith Packard wrote:
>
>> I've tagged version '1.0' of this repository and created some (not
>> finished) debian packaging for it. This version has imported the mille
>> sources
Keith Packard writes:
> This package includes a bunch of games using a shared widget library,
> including a raft of solitaire, another (not terribly good) reversi
> implementation and even a version of dominoes. Having this build only
> xmille would be fairly easy. If that
Adrian Bunk writes:
> On Mon, Dec 07, 2020 at 09:12:23AM -0800, Keith Packard wrote:
>> Adrian Bunk writes:
>> >
>> > Keith, do you remember the copyright history of this code?
>>
>> I may have copied the underlying mille sources *before* copyrights wer
Ryan Armstrong writes:
> I just did a bit of digging, since I previously had a 2.11 BSD VM set up
> in SIMH (fun!). It looks like the version of mille in that release was
> indeed from about the 1985/1986 time frame, and the copyright headers
> were not yet added. So that makes much more sense
Adrian Bunk writes:
> On Sun, Nov 08, 2020 at 07:06:52PM -0500, Ryan Armstrong wrote:
>>...
>> I have been researching old terminal and X games recently, and realized
>> that much of the code from 'xmille' orignated from the terminal game
>> 'mille', which is part of bsdgames.
>>
>> Specifically
Lucas Nussbaum writes:
> There was a texlive update in the meantime. Here are the versions of
> packages that differ.
I explored this a bit today -- there's something quite amiss with the
docbook toolchain. I'm seeing a lot of this error:
! Undefined control sequence.
\close@pdf
Adrian Bunk writes:
> Source: libnewlib-nano
> Version: 2.11.2-1
> Severity: serious
> Tags: ftbfs bullseye sid
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libnewlib-nano.html
The correct fix is to get picolibc out of the new queue so I can finish
removing this package
Pirate Praveen writes:
> On Mon, 09 Mar 2020 12:41:41 -0700 kei...@keithp.com ("Keith Packard") wrote:
>>
>> Source: ruby-asciidoctor-pdf
>> Version: 1.5.3-1
>>
>> Updated gemspec dependency on concurrent-ruby to ~> 1.1.0 which matches
Ralf Treinen writes:
> snek build-depends on picolibc-arm-none-eabi which does not exist (yet)
> in sid.
Yup. It's been stuck in the 'new' queue for several months now.
--
-keith
signature.asc
Description: PGP signature
Ivo De Decker writes:
> I added a removal hint to get it out of testing.
I saw that after I uploaded 2.0-1... I'd been meaning to get back to
calypso for quite a while but got stuck because the various Python2
dependencies were no longer supported and yet some were not yet
available for Python3.
Raphael Hertzog writes:
> (Keith, I would really like if you could step in, fontconfig
> is at its fifth NMU in a row and the sources are not even in
> a git packaging repo... I find it highly demotivating to contribute
> without any reaction from the package maintainer when I know that
> he's no
Salvatore Bonaccorso writes:
> Control: tags 833570 + pending
>
> Hi Keith,
>
> I've prepared an NMU for fontconfig (versioned as 2.11.0-6.5) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
Also, thanks for doing this upload!
--
-keith
signature.asc
Salvatore Bonaccorso writes:
> Control: tags 833570 + pending
>
> Hi Keith,
>
> I've prepared an NMU for fontconfig (versioned as 2.11.0-6.5) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
Looks like that patch is already in fontconfig 2.12.1; thanks f
Raphael Hertzog writes:
> Hello dear maintainer(s),
>
> the Debian LTS team would like to fix the security issues which are
> currently open in the Squeeze version of your package:
> https://security-tracker.debian.org/tracker/source-package/freetype
>
> Would you like to take care of this yourse
Keith Packard writes:
> Ivo De Decker writes:
>
>> Hi Keith,
>>
>> On Sun, Feb 23, 2014 at 08:09:41PM -0800, Keith Packard wrote:
>>> I've uploaded 2.11.0-5 which just provides the pre-built documentation
>>> as a debian patch for now.
>>
Ivo De Decker writes:
> Hi Keith,
>
> On Sun, Feb 23, 2014 at 08:09:41PM -0800, Keith Packard wrote:
>> I've uploaded 2.11.0-5 which just provides the pre-built documentation
>> as a debian patch for now.
>>
>> I think I'll probably eliminate the font
"Rebecca N. Palmer" writes:
>> , as this bug makes ~all GUI packages
>> BD-Uninstallable on non-amd64.
> Sorry...it looks like this is being fixed by forcing builds against
> 2.11.0-2 (https://buildd.debian.org/status/package.php?p=fontconfig), so
> fixing this bug is no longer so urgent.
I've
peter green writes:
>>
>> I've resolved this by including pre-built documentation and not
>> regenerating that at package build time. This fix requires a new
>> .orig.tar.gz file, and that needs help from ftp-masters to replace the
>> existing file.
>>
> I've just confirmed with the FTP team t
Andreas Beckmann writes:
> Package: fontconfig-config
> Version: 2.11.0-3
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package failed to purge.
>
>>From the attached log (scroll to the bottom...):
>
> Removing
"Rebecca N. Palmer" writes:
> fontconfig recently added a build-dependency on docbook-utils, and hence
> an indirect build-dependency on itself. As the arch:any libfontconfig1
> has an exact version dependency on the arch:all fontconfig-config, this
> causes the build to fail on all architect
Helmut Grohne writes:
> Package: fontconfig-config
> Version: 2.11.0-2
> Severity: serious
> Justification: fails to upgrade
>
> Hi Keith,
>
> I noticed the following apt output while upgrading fontconfig-config
> from 2.11.0-2 to 2.11.0-3 with fontconfig 2.11.0-3 already installed.
I uploaded -
Felix Braun writes:
> Package: calypso
> Version: 1.1
> Severity: serious
> Justification: Policy 3.5
>
> Dear Maintainer,
>
> as calypso uses git as its storage backend, it needs git installed for
> proper operation. I've checked version 1.2 which doesn't list the
> dependency either.
Thanks fo
Alan Coopersmith writes:
> Reviewed-by: Alan Coopersmith
Merged.
6a49f88..fe7463b master -> master
--
keith.pack...@intel.com
pgpYmmpZTo9YP.pgp
Description: PGP signature
On Tue, 1 May 2012 17:19:43 +0200, gregor herrmann wrote:
> I've prepared an NMU for cairo-5c (versioned as 1.6+nmu1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
I've uploaded version 1.7 that fixes this bug.
--
keith.pack...@intel.com
pgpfqA0oy
Package: fop
Version: 1:1.0.dfsg2-1
Severity: grave
Tags: sid
Justification: renders package unusable
Fop wasn't generating any output for any input and was exiting with
error code 1. There's a fedora bug that looks identical to me.
https://bugzilla.redhat.com/show_bug.cgi?id=689930
This
On Mon, 11 Jan 2010 08:38:26 +0100, Andreas Barth wrote:
> Could you please bump the dependency on defoma to >= 0.11.10-4 with
> the next upload, as we still have "badly built" packages in the
> archive?
I'll set a build dependency on 0.11.10-4 but leave the suggests at 0.7.0
as this is strictly
On Thu, 31 Dec 2009 18:44:18 +0100, Cyril Brulebois wrote:
> In the meanwhile, defoma was uploaded with the debhelper-like syntax
> (as quoted above). In my previous mail[1], you can scratch “until new
> defoma is installed on all architectures” since it's arch: all. ;)
Ok, I've adopted the same
On Thu, 31 Dec 2009 09:10:49 +0100, Cyril Brulebois wrote:
> Still, losing Riku's band-aid wasn't nice. Anyway, now that the root
> issue's being addressed, the band-aid shouldn't be necessary for too
> much time.
Right, I didn't realize there was a bug in defoma as well which was
causing this p
On Thu, 31 Dec 2009 09:03:59 +0100, Cyril Brulebois wrote:
> Keith Packard (30/12/2009):
> > > I'm about to QA-upload defoma with this change in the various
> > > debhelper-files/* files, but I wanted to open this bugreport for
> > > reference.
>
> F
o open this bugreport for
> reference.
>
> Cc'ing defoma folks and buildd folks, since they might be interested in
> knowing about this.
>
> Mraw,
> KiBi.
Here's a patch which I've used to build new fontconfig packages which
should survive the absence of defoma.
On Thu, 31 Dec 2009 00:09:42 +0100, Cyril Brulebois wrote:
> 1. reply to RC bugs filed against your packages;
I haven't received any mail about RC bugs today, and can't find any
through the bugs.debian.org web interface.
> 2. optionally fix them;
I'm trying, but it looks like dh_installdefom
On Sat, 2009-02-28 at 18:36 -0700, Bdale Garbee wrote:
> I gather this is a transition problem in the move from ps to pdf that foomatic
> isn't quite ready for yet? In any case, it's a pretty horrific bug that
> really must get resolved before squeeze releases, so I'm increasing the
> severity
On Wed, 2007-11-14 at 07:51 +0100, Sven Luther wrote:
> Hi Keith, ...
>
> The bug was supposed to be an etch bug, so i wonder how a fontconfig
> upload to uunstable could have fixed it. Or does this mean that since
> etch is stable, this bug cannot be fixed, and thus you are closing the
> bug ?
This bug should be fixed by 2.4.91; if someone can check and make sure
it works for them now, I'll go ahead and mark it closed when I upload
2.4.92.
--
[EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
On Thu, 2007-01-25 at 00:07 +1100, Angus Lees wrote:
>
> I can do so, but the symlinking seems simpler. defoma tracks fonts by
> filename, so its possible for fonts to be scattered anywhere in the
> filesystem.How does the fontconfig searching/caching mechanism
> scale? For example, a naive
On Mon, 2007-01-22 at 00:55 -0800, Steve Langasek wrote:
> tags 402014 etch-ignore
> thanks
>
> I'm going to go out on a limb here and tag this bug as non-RC for etch. The
> only case where this has been a concrete problem so far was for a particular
> font package which had a broken version uplo
On Sun, 2007-01-21 at 23:08 +1100, Angus Lees wrote:
> hrm. you're right - we need to run fc-cache on the directories we
> didn't need to symlink to ..
Would it be better to add the new font directories to the fontconfig
configuration instead of symlinking the files to /var?
Oh, and we need to u
On Tue, 2007-01-16 at 17:39 +1100, Angus Lees wrote:
> Keith, here's the patch written during your talk at LCA ;)
>
> It fixes bug 402014, by simply adding '-f' to the fc-cache run, hence
> me filing it under this bug number. Really though, this patch avoids
> creating symlinks for fonts that are
On Mon, 2006-12-18 at 11:22 +0100, Leszek Koltunski wrote:
> CFLAGS=-g or CFLAGS='' does not make any difference.
Ah, but not setting CFLAGS is different from setting it to the empty
string. When unset, automake picks some defaults (-O -g) which turns on
optimization.
> But here's another clue: n
On Mon, 2006-12-18 at 10:07 +0100, Leszek Koltunski wrote:
> after
>
> apt-get source fontconfig
> dpkg-source -x fontconfig_2.4.2-1.dsc
>
> I already can see a directory named 'fontconfig-2.4.2' . This is the
> source with all Debian patches applied, right? If I compile that the
> './configure
On Mon, 2006-12-18 at 08:49 +0100, Leszek Koltunski wrote:
> If you helped me out with compilation of the package, I think I could
> gather some more info.
Ok, let's try building just the raw upstream package; trust me, there
aren't any significant debian changes outside of the configuration
stuf
On Mon, 2006-12-18 at 04:59 +0100, Leszek Koltunski wrote:
> #0 0xf7e8306c in ?? () from /usr/lib/libfontconfig.so.1
> #1 0xf7e84fc4 in FcDirCacheOpenFile (cache_file=,
> file_stat=0xffa541e4) at /usr/include/sys/stat.h:380
Ok, I'm mystified. The stack trace (even with -O) appears clean, and
t
On Sat, 2006-12-16 at 16:22 +0100, Leszek Koltunski wrote:
> Package: fontconfig
> Version: 2.4.2-1
> Severity: grave
> Justification: renders package unusable
>
> I've got an AMD64 system with a i386 chroot where I install 386-only
> applictions ( Firefox for the
> flashplugin, Skype etc ). I am
On Tue, 2006-12-05 at 21:46 +0100, Loïc Minier wrote:
> On Tue, Dec 05, 2006, Josselin Mouette wrote:
> > The fix is to have these packages register their fonts to defoma. This
> > will automatically run fc-cache -f in the defoma directory.
>
> Either defoma is borken, or dh_installdefoma doesn't
On Tue, 2006-12-05 at 20:53 +0100, Loïc Minier wrote:
> On Tue, Dec 05, 2006, Keith Packard wrote:
> > I think I could fix upstream fontconfig to do a more careful check when
> > fc-cache is run and finds font files newer than the cache for their
> > directory. I don
On Tue, 2006-12-05 at 20:08 +0100, Loïc Minier wrote:
> On Tue, Dec 05, 2006, Keith Packard wrote:
> > Right, the current DejaVu font package has a broken version of condensed
> > which does not correctly report the setwidth value in the OS/2 header of
> > the file. I thin
On Tue, 2006-12-05 at 15:29 +0100, Loïc Minier wrote:
> I don't see how this relates to my analysis. I upgraded fontconfig,
> and the fonts were ugly. I removed DejaVu Condensed, and the fonts
> were nice again, and the result of fc-match changed as well; certainly
> you can explain what par
On Mon, 2006-12-04 at 22:17 +0100, Eugeniy Meshcheryakov wrote:
> 3 грудня 2006 о 23:50 +0100 eugen написав(-ла):
> > > fontconfig would also use the 'width' information from the OS/2 table,
> > > but DejaVu Condensed has that set incorrectly.
> > Yes, that was bug in DejaVu, and that is allready f
On Sat, 2006-10-28 at 07:27 +0200, Andreas Mohr wrote:
> Preparing to replace fontconfig 2.3.2-7 (using
> .../fontconfig_2.4.1-2_i386.deb) ...
> Cleaning up font configuration of fontconfig...
> Cleaning up category cid..
> Cleaning up category truetype..
> Cleaning up category type1..
> "/var/li
On Mon, 2006-10-09 at 19:43 +0200, Andreas Barth wrote:
> If fonts.conf is changed, the user is asked via debconf if the file can
> be overwritten. So, the only issue is if (the file is changed) and (the
> user denies overwritting it).
Note that there was a transient bug in one of the 2.4.0 versi
On Mon, 2006-09-18 at 10:51 +0800, Haifeng Chen wrote:
> While upgrading to version 2.4.1-1, it seems fontconfig-config automatically
> restore the setting back to default. I have to use dpkg-reconfigure to set it
> again.
Oops. Fontconfig wasn't looking for a new-style configuration during
upgra
On Sun, 2006-09-17 at 17:23 +0300, David Baron wrote:
> Package: fontconfig
> Version: 2.4.1-1
> Severity: grave
> Justification: renders package unusable
>
> Recent Sid versions cannot write font caches.
> Will report scanning of # directories, # fonts in log or using -v option,
> but will not wr
On Wed, 2006-09-13 at 18:30 -0700, Steve Langasek wrote:
> Package: fontconfig
> Version: 2.4.0-4
> Severity: serious
>
> Hi Keith,
>
> fontconfig is failing to build on mipsel with the following error:
HA. Fixed it before you reported the bug.
2.4.0-5 has been uploaded about 30 seconds ago.
A
On Mon, 2006-06-05 at 12:09 -0700, Steve Langasek wrote:
> On Mon, Jun 05, 2006 at 11:41:01AM -0700, Keith Packard wrote:
> > That patch is horrific and won't be accepted upstream...
>
> Ok, but the freetype website also claims that fontconfig 2.3.93 doesn't need
> p
On Mon, 2006-06-05 at 12:09 -0700, Steve Langasek wrote:
> On Mon, Jun 05, 2006 at 11:41:01AM -0700, Keith Packard wrote:
> > That patch is horrific and won't be accepted upstream...
>
> Ok, but the freetype website also claims that fontconfig 2.3.93 doesn't need
> p
That patch is horrific and won't be accepted upstream...
--
[EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
On Mon, 2006-06-05 at 18:58 +0200, Josselin Mouette wrote:
> Le lundi 05 juin 2006 à 13:38 +0200, Julien Danjou a écrit :
> > > fcfreetype.c:53:10: error: #include expects "FILENAME" or
> > > fcfreetype.c:58:10: error: #include expects "FILENAME" or
> > > fcfreetype.c:59:10: error: #include expec
strace shows bzflag attempting to open files starting with "${prefix}".
I suspect that's because the new version was built with newer autoconf
which requires an updated AC_DEFINE_DIR. Same thing happened to me today
with a local build of the X server. Here's the newer version of
AC_DEFINE_DIR (note
66 matches
Mail list logo
