Bug#636003: libvigraimpex: FTBFS with libpng 1.5
Hi Ralf,
you could apply the upstream patch instead:
https://github.com/ukoethe/vigra/commit/7f7b24
That uses #ifdef to build with both 1.2 and 1.5 png versions.
Best regards
Joachim
commit 7f7b24e78ff56d66239e4a34ca66a85bdd2f44fb
Author: Ullrich Koethe ullrich.koe...@iwr.uni-heidelberg.de
Date: Fri Mar 11 14:55:42 2011 +0100
update for libpng 1.5 (fix by Mark Brand, mingw-cross-env)
diff --git a/src/impex/png.cxx b/src/impex/png.cxx
index e525fc6..5b7e84a 100644
--- a/src/impex/png.cxx
+++ b/src/impex/png.cxx
@@ -320,7 +320,11 @@ namespace vigra {
#if (PNG_LIBPNG_VER 10008) defined(PNG_READ_iCCP_SUPPORTED)
char * dummyName;
int dummyCompType;
+#if (PNG_LIBPNG_VER 10500)
char * profilePtr;
+#else
+png_byte * profilePtr;
+#endif
png_uint_32 profileLen;
if (png_get_valid( png, info, PNG_INFO_iCCP )) {
png_get_iCCP(png, info, dummyName, dummyCompType, profilePtr, profileLen) ;
@@ -593,7 +597,11 @@ namespace vigra {
// set icc profile
if (iccProfile.size() 0) {
png_set_iCCP(png, info, (png_charp)(icc), 0,
+#if (PNG_LIBPNG_VER 10500)
(png_charp)iccProfile.begin(), (png_uint_32)iccProfile.size());
+#else
+ (png_byte*)iccProfile.begin(), (png_uint_32)iccProfile.size());
+#endif
}
#endif
Bug#609722: is still there
Hello Rainer, you're right: If the rest of the installation works well with netboot from USB-Stick, grub-install should do his job, too. And this image should *then* be a valid alternative. But I am unsure, if that can be fixed before the release so it's perhaps something for the errata - state that netboot can't be used on usb sticks. Ben Armstrong said, the mini.iso is not suitable: http://lists.debian.org/debian-boot/2011/01/msg00899.html (and follow-ups) so please use a netinst.iso To test the installer from a usb-Stick I used hd-media/boot.img.gz (yes you can also use initrd.gz and linux separately) together with the ISO debian-testing-i386-netinst.iso from http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/ Or you could try the hybrid CD alternative and dd the netinst.iso directly to the stick. By the way: You can find the new installation manual at: http://www.debian.org/releases/testing/i386/index.html.en In my eyes the documentation concerning USB-Installs is still very confusing or even inconsistent! Best Regards Joachim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609722: is still there
Hello Reiner, Am 23.01.2011 18:55, schrieb Rainer Dorsch: The installation files from http://http.us.debian.org/debian/dists/squeeze/main/installer- i386/current/images/netboot/ I used are from Jan-17. In your first report there is no hd-media image mounted. Did you boot 'netboot' images from a usb-Stick? The link you provide points to the images for a network installation. As far as I understand those files should not be used for usb-stick installations. Best Regards Joachim Am 21.01.2011 17:34, schrieb Ben Armstrong: On 01/21/2011 11:35 AM, Christophe Schockaert wrote: So, I followed what's here for a network install: http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html Please don't confuse netboot with netinst. The former boots an image from a properly configured server (usually located on your LAN). The latter boots an image from media attached to the machine which includes a base system that then fetches remaining packages from a Debian archive over the network. You are attempting a netinst and should ignore doc that deals with netboot. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609722: installation-reports: USB Memory Stick Booting wrote Bootsector on USB Stick
reassign 609722 grub-installer 1.58 severity 609722 serious merge 568529 609722 thanks Another report of installing grub to usb stick instead of hard-drive. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568529 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603942: Grub installed to wrong disk
found 603942 1.57 merge 568529 603942 thanks Hello Christian Perrier, I found this bug still beeing present in beta2 installer using grub-installer 1.57 (See #605562). Bug 603942 seems to be another duplicate of #568529, so I merge them. Best Regards Joachim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605562: installation-report: Installation from usb stick lead, to unbootable system (und unbootable usb stick)
severity 568529 serious tags 568529 - moreinfo thanks Hello, now we have five different people reporting that bug. Most of them set a severity of serious or above. Therefore I increased the severity: Makes package unfit for release in my opinion. Some more additional information from the installer environment; I ran a shell before installing grub (Expert install; another empty hard-drive as in the report above): ash BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ # mount rootfs on / type rootfs (rw) none on /proc type proc (rw,relatime) none on /sys type sysfs (rw,relatime) tmpfs on /dev type tmpfs (rw,relatime,mode=755) none on /dev/prs type devpts (rw,relatim,gid=5,mode=620,ptmxmode=000) /dev/sda1 on /hd-media type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shotname=mixed,errors=remount-ro) /dev/loop0 on /cdrom type iso9660 (ro,relatime) /dev/sdb1 on /target type ext3 (rw,relatime,errors=remount-ro,data=ordered) /dev/sdb6 on /target/home type ext3 (rw, relatime,errors=continue,data=ordered) /dev/sdb1 on /dev/.static/dev type ext3 (rw,relatime,errors=remount-ro,data=ordered) tmpfs on /target/dev/ type tmpfs (rw,relatime,mode=755) /dev/loop0 on /target/media/cdrom0 type iso9660 (ro,relatime) ~ # chroot /target grub-mkdevicemap --no-floppy -m - (hd0) /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_20053349610A41A2F01B-0:0 (hd1) /dev/disk/by-id/ata-FUJITSU_M1623TAU_08316741 ~ # readlink -f $(chroot /target grub-mkdevicemap --no-floppy -m - | head -n1 | cut -f2) /dev/sda ash Do you need addional information? My interpretation (grub-installer Line 538-570): grub-installer uses the first device and double-checks that this is not /cdrom. But that check is false, because /cdrom is /dev/loop0. We should additionally check the device-to-disk() of /hd-media in the same manner as /cdrom. That would install grub on the right device. Is it a problem when after reboot at an update the usb-stick is no longer present and the hard drive is named /dev/sda then? What do you think? Best Regards Joachim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
