Bug#600306: ttf-oldstandard: diff for NMU version 2.2-2.1
tags 600306 + patch tags 600306 + pending thanks Dear maintainer, I've prepared an NMU for ttf-oldstandard (versioned as 2.2-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru ttf-oldstandard-2.2/debian/build.py ttf-oldstandard-2.2/debian/build.py --- ttf-oldstandard-2.2/debian/build.py 2009-11-14 17:27:09.0 +0100 +++ ttf-oldstandard-2.2/debian/build.py 2010-10-25 20:11:42.0 +0200 @@ -15,7 +15,8 @@ print ( ); print (Building ) + font.fullname + ( from font source: ) + font.fontname + (.sfd...); print (Done.); - font.generate(fontname,); + # layer=TTF from ost-generate.py + font.generate(fontname,,layer=TTF); font.close(); i += 1; diff -Nru ttf-oldstandard-2.2/debian/changelog ttf-oldstandard-2.2/debian/changelog --- ttf-oldstandard-2.2/debian/changelog2010-02-07 12:46:41.0 +0100 +++ ttf-oldstandard-2.2/debian/changelog2010-10-25 20:16:48.0 +0200 @@ -1,3 +1,10 @@ +ttf-oldstandard (2.2-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Use TTF layer to fix rendering problems. Closes: #600306 + + -- Jan Lübbe jlue...@debian.org Mon, 25 Oct 2010 20:16:45 +0200 + ttf-oldstandard (2.2-2) unstable; urgency=low * Drop fontforge from Recommends. Closes: #568662 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599200:
I've also tried it on a lenny live-cd and it works fine, too... Which versions did you use? Jan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599200:
Hi, i'm the maintainer of the qemu-kvm package and have now tried serveral combinations: Host with 64-bit CPU and 32bit squeeze kernel/userspace and 32bit lenny or squeeze netinst as guest: lm in the host's /proc/cpuinfo but *not* in the guest's Host with 64-bit CPU and 64bit sid kernel/userspace and 32bit lenny netinst as guest: lm in *both* host's and guest's /proc/cpuinfo Host with 64-bit CPU and 64bit sid kernel/userspace and 64bit lenny netinst as guest: lm in *both* host's and guest's /proc/cpuinfo Host with 32-bit CPU and 32bit squeeze kernel/userspace and 32bit lenny netinst as guest: lm in *neither* host's nor guest's /proc/cpuinfo Each of those cases is what I'd expect. Petter Reinholdtsen wrote he was using Lenny's kvm: QEMU Virtual CPU version 0.10.0 That verion is rather old and if it is indeed broken, i don't think we could get the cpuid fixed soon. I'll setup a lenny machine and try it there, too. Jan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559971: [Pkg-mozext-maintainers] Bug#559971: itsalltext: Source package does not contain corresponding source for work
On Tue, 2009-12-08 at 12:17 +1100, Ben Finney wrote: Package: itsalltext Version: 1.3.1-1 Severity: serious Justification: Policy 2.3 The source package for ‘itsalltext’ is not the corresponding source for the work. Instead, it is a bundling of the binary ‘*.jar’ libraries. The jar 'libraries' are just zip archives of the source code. This violates the license terms of the work (GPLv3 §6) and as such means the package is currently illegal to distribute by the Debian project. The GPLv3 defines the “corresponding source” as: The Corresponding Source for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. The work is not shipped in 'object code' as i understand it, just compressed original .js and .xul files. The jar files have been obtained by extracting upstream's .xpi file. So, fixing this bug involves changing the source package to consist of the corresponding source for the work plus the Debian packaging, all licensed appropriately. For the next upstream version, i will change it to the recommended pkg-mozext style where the the jars are extracted. For this package, the source package needs to include all the files from the VCS repository (currently a Git repository located at ‘git://gerf.org/itsalltext.git’). The Debian packaging then should use the ‘Makefile’ to build the binary package from source. I've had not seen this git repo before and have now compared the source files in my package to those in git. They seem to be identical. The package's build system uses the third-party packages ‘jslint’ URL:http://bugs.debian.org/559969 and (for the documentation) ‘jsdoc-toolkit’ URL:http://bugs.debian.org/559963. Building without those tools also works, and produces the same as upstreams .xpi. What do you think we would gain by using the git repo as upstream? Best regards, Jan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551620: DOS on the LAN when starting kvm with 2 network devices and bridging
Hi! On Mon, 2009-10-19 at 16:23 +0200, Goswin von Brederlow wrote: sudo kvm -m 256 -drive file=/scratch/ramdisk/build/build/hda.img,if=ide,boot=on -drive file=/scratch/ramdisk/build/build/hdb.img,if=ide,boot=off -net nic,model=e1000,macaddr=54:52:00:00:42:12 -net tap -net nic,model=e1000,macaddr=54:52:00:00:42:13 -net tap -smp 1 -kernel /scratch/ramdisk/build/build/chroot-amd64/boot/vmlinuz-2.6.27.34-1-ql-beowulf -append root=/dev/ram0 rw ramdisk_size=97872 console=ttyS0,115200 quiet --initrd /scratch/ramdisk/build/build/image-beobox-amd64-7.0.0-0.gz -nographic and the /etc/kvm/kvm-ifup script adds both devices to a bridge: The is an effect of how qemu's internal networking is designed. You defined 2 nics and *2 tap devices* on the same qemu-internal vlan. Bridging these devices together creates a loop. If you just want two devices in the same physical lan use '-net tap' only once. This will connect the two nics to the same tap device. You only need explicit vlans if you want to connect them to different bridges on the host. I don't think this is RC, maybe qemu should warn if more than one tap device is used on the same internal vlan. Jan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#467260: kvm-source: FTBFS on 2.6.24 persists w/ 65+fdsg-2
On Sat, 2008-04-12 at 09:04 -0400, Ian MacDonald wrote: Version: 65+dfsg-2 Experiencing the same build errors as Mike Hommey, even after m-a clean; m-a a-i kvm-source This is strange, i thought they were caused by leftover files from previous source packages. Are you sure it is the exact same error? Could you verify that /usr/src/modules/kvm does not exist before running m-a build kvm-source? Are you building against the current debian kernel? If not, please send me your .config and exact kernel version. Does the error occour when you don't use module-assistant (i use make-kpkg modules-image for my own kernels)? Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472343: Acknowledgement (gitosis: Creates a user called git without checking for it first)
This problem only occoured because i created the git user manually. When it is a system user, adduser only warns about it. Maybe this should be documented for people upgrading from older packages? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469125: kvm: Building on amd64 fails because of dependency to etherboot which does only exist on i386
On Mon, 2008-03-03 at 10:08 +0100, Thomas Besser wrote: Package: kvm Version: 62+dfsg-2 Severity: serious Justification: no longer builds from source I've noticed that as well, my next upload will split the firmware into an arch-independent package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467260: kvm-source: FTBFS with 2.6.24 kernel
Hi! On Sun, 2008-02-24 at 10:20 +0100, Mike Hommey wrote: Package: kvm-source Version: 61+dfsg-1 Severity: serious Justification: FTBFS Can't build kvm-source 61 with 2.6.24 kernel: *snip build errors* -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores) Are you building kvm-source against this kernel? Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash I just tried to build for amd64 with make-kpkg against the kernel.org tree i usually use and with module-assistant against the debian amd64 kernel with: module-assistant -k /usr/src/linux-headers-2.6.24-1-amd64/ build kvm-source Both tries produced usable packages. I'll send you the ones for 2.6.24-1-amd64 in a seperate mail. What did you do differently? Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453934: severity of 453934 is important
# Automatically generated email from bts, devscripts version 2.10.13 # occours only for some users with win2k severity 453934 important -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453934:
Could you try to reproduce this bug again with kvm-60? It is probably fixed by now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453934: kvm-source: emulation failed (pagetable)
On Sun, 2007-12-02 at 13:50 +0100, Bastian Scholz wrote: After updating kvm-source from kvm-28 to kvm-54 kvm only shows a black screen, even the virtual BIOS is not shown (but I can enter the kvm-monitor and can type commands). If I load the old kvm-28 module or disable kvm with -no-kvm the system would start. dmesg shows [..] loaded kvm module (kvm-54) emulation failed (pagetable) rip fff0 00 00 00 00 Which commandline do you use to run kvm? Which guest OS are you using? Jan Lübbe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453934: kvm-source: emulation failed (pagetable)
On Sun, 2007-12-02 at 17:50 +0100, Bastian Scholz wrote: Which commandline do you use to run kvm? kvm -hda win2k-c.img -m 192M (-no-kvm) I try it with -no-acpi and -no-kvm-irqchip, too. All the same. Which guest OS are you using? Win-2000 Pro, but not relevant I think. The problem occurs with an empty hdd-image, too. I think it is a pre-OS failure and somewhere in the virtual BIOS initialization. I can't repoduce the problem here. Windows XP and Linux guests work ok. What are the details of your host system? CPU (/proc/cpuinfo), kernel, Mainboard/BIOS? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
