Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)
Hi, adrian15 wrote: > It seems you are proposing to add like three tags: Medium?, Firmware?, > Architecture? but I don't get how that would transform into options that the > final user can use. For now i only state that this is a model by which one can describe the purpose of boot loaders in an ISO filesystem. > And, well, how would you go into enabling or not a given bootloader given a > Medium?, Firmware?, Architecture? combination. I am pondering a better language for describing the boot equipment to xorriso. It would have to be less tricky than the zoo of inherited and self-invented mkisofs options. Not easy. > I'm not sure I understand why we need this. Mainly take care not to create a terminology which contradicts the correct model. (As far as it is identified yet.) > Your proposal begins to make sense although I'm not 100% convinced ;). I am not convinced either. The model matches the facts, so far. But its straightforward implementation is not yet clear to me. There is a fourth dimension to be expressed: Bootloader. Then there is the dimension of ISO filesystem objects. A user wish would contain at least ISO-Object, Bootloader, Medium, Firmware, Architecture E.g. Appended Partition, with GRUB2 content, for CDROM and HDD, via EFI, on i386 ISO Data File, with SYSLINUX content, for HDD, via BIOS, on i386 and amd64 I am not sure whether this list of more or less combinable dimensions is complete yet. Further one will want to express whether the gaps between partitions should be filled, which kinds of partition tables shall emerge, ... These properties are global to the ISO, not specific to a single boot image. Some are combinable, some are mutally exclusive. (Maybe it is time to break out an UML editor.) > > [SYSLINUX] > > Did you try whether it boots via EFI if no BIOS boot equipment > > is in the ISO ? > Well, I tried: kvm -bios /usr/share/ovmf/OVMF.fd -boot d -cdrom file.iso . More we cannot expect. :) The fact that there is a minimal operating system in the EFI System Partition explains why it works. > > debian-cd has an MBR partition 0xef and a GPT > > partition which point to that EFI boot image. (The GPT is to be > > ignored by all sane EFI implementations.) > Ok. Did you mean "NOT to be ignored"? No. The GPT is surplus, according to UEFI 2.4 specs. Either you have an MBR partition 0xef or you have GPT. Not both. But Matthew Garrett had reason to produce it. Re-reading his blog http://mjg59.dreamwidth.org/11285.html i get the suspicion, that he first tried GPT alone, then added MBR partition 0xef, and so invalidated his original GPT approach. > Maybe that's why the syslinux-efi does not boot. I could give it a try > changing the partition type and see what happens. Rather not. The presence of MBR partition 0xef should cause EFI to simply not look for GPT partitions. > > I recently tested on my Sid VM with various combinations of grub-pc, > > grub-efi-ia32-bin, and grub-efi-amd64-bin. All together, pair-wise, alone. > > They all booted with qemu via its default BIOS and via OVMF (as EFI). > Did you try to boot them either as a cdrom or as a hard disk? I think that > EFI + hard disk was the one failed for me. Hopefully i tested all reasonable combinations. (But i begin to doubt that i tried an i386 VM. Will have to check.) > That's interesting. So we have Fedora, debian-cd, grub-mkimage ways of > dealing with UEFI. Probably Ubuntu has also its own way of handling it too. Fedora, Debian, Ubuntu use the Matthew Garrett layout. Debian and Ubuntu omit the HFS+ aspect of that layout, though. OpenSuSE is different. They have a mountable ISO partition after the EFI System Partition. For that stunt they cut off the head of a first ISO and prepend it to a second, reproducibly built ISO, which lacks the EFI partition data file. (In american length units, Frankenstein castle is not very far from Nuremberg.) grub-mkrescue layout is rarely used for distro ISOs. I blame this on the existing SYSLINUX based production software for distro ISOs. In principle, a pure GRUB2 or a pure SYSLINUX equipment appears to be the more reasonable choice. > So you don't like the primary or secondary terms. > How does xorriso name them? They have no partitcular name in the docs. Joerg Schilling obviously considered them "alternative" when he invented option name -eltorito-alt-boot. We should not put too much weight on that options naming tradition. It grew slowly and in part cluelessly. (Joerg's and mine alike.) > Maybe we can just name them as: > "Main bootloader" > and > "Alternate bootloader". The model does not imply any ranking. "First", "Second", "Third" could be justified, because there are lists in El Torito and partition tables where the boot entries have to line up in sequence. For my taste, "Main" or "Primary" too much implies a rank. > So that we can force a given bootloader to be used only as a "Main eltorito entry" ? Currently this would be done by mentionin
Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)
Hi, after checking El Torito specs, i have to correct my statements about ranking of El Torito boot images. The first entry in the boot catalog not only has the title "Initial" but "Initial/Default". "4.4 Boot Entry Selection If the CD has several boot entries, a default entry which boots a election program may be provided as the Default/Initial catalog entry. This image will usually be a floppy image which loads a program that selects the proper boot image by examining the system configuration or questioning the user." Insofar, the first boot image in the catalog is something special. It is to be preferred over the other boot images with the same Platform Id. (Nevertheless, it is not obliged to really offer booting of the others of the same Platform Id.) I would plan for only one El Torito boot image per platform: 0 = 80x86 BIOS , 0xef = EFI. But if there is a use case for offering BIOS boot images from GRUB2 and ISOLINUX in the same El Torito catalog, then the sequence matters if one of them occupies the first entry in the catalog. If you put the EFI boot image first, then both BIOS boot images get equal rank. In the light of this, it seems wise to stay with the sequence that is tested since a few years: First the BIOS boot image, then the EFI boot image, no further BIOS boot images. This makes it clear to the firmware: BIOS will hop on the first entry, because it has the right Platform Id and is Default. BIOS will most probably not enforce that the first boot image is a floppy image, because there is no other BIOS boot image. (You always have to expect that the BIOS programmers read the specs with tired eyes.) EFI will not hop on the Default entry, because the Platform Id does not match. The MBR x86 BIOS code, too, would have to decide on which BIOS boot image binary to hop. If there is only one, the decision is easy. Have a nice day :) Thomas
Bug#812422: vlock: 'vlock -n' fails to load plugin 'new': No such file or directory
Package: vlock Version: 2.2.2-5 Severity: normal Dear Maintainer, Attempting to run 'vlock -n' fails with the following error message: vlock: loading plugin 'new failed: No such file or directory I suspect this to be due to the fact that there is no 'new' module installed to /usr/lib/vlock/modules. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages vlock depends on: ii adduser 3.113+nmu3 ii libc6 2.21-6 ii libpam-modules 1.1.8-3.2 ii libpam0g1.1.8-3.2 vlock recommends no packages. vlock suggests no packages. -- no debconf information
Processing of abiword_3.0.1-5_source.changes
abiword_3.0.1-5_source.changes uploaded successfully to localhost along with the files: abiword_3.0.1-5.dsc abiword_3.0.1-5.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)
abiword_3.0.1-5_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Jan 2016 21:21:21 +0100 Source: abiword Binary: abiword-common abiword abiword-plugin-grammar libabiword-3.0 libabiword-3.0-dev gir1.2-abiword-3.0 abiword-dbg Architecture: source Version: 3.0.1-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski Description: abiword- efficient, featureful word processor with collaboration abiword-common - efficient, featureful word processor with collaboration -- common abiword-dbg - debugging symbols for abiword word processor abiword-plugin-grammar - grammar checking plugin for AbiWord gir1.2-abiword-3.0 - GObject introspection data for libabiword libabiword-3.0 - efficient, featureful word processor with collaboration -- shared libabiword-3.0-dev - efficient, featureful word processor with collaboration -- develo Closes: 809882 811381 Changes: abiword (3.0.1-5) unstable; urgency=medium . * QA upload. * Fix FTBFS with libpng16 (closes: #809882) * Use default gnutls cipher/kx priorities, fixes FTBFS with gnutls30. * Fix FTBFS with gcc-6 (closes: #811381) Checksums-Sha1: 8054c2ca3cd31ae0f563fc463d4db12d4727595e 2625 abiword_3.0.1-5.dsc c85f6cc99f1e53c06c4ef74d27cea3f4ac095618 50520 abiword_3.0.1-5.debian.tar.xz Checksums-Sha256: b9a7e557298afb3e7d184ba8a36d398aaa9f9911b756047a8d4a68551605bed1 2625 abiword_3.0.1-5.dsc b26c2c12ebb1f578010578a1aa663fab539bb524b9b63b3eb51743db9bb31900 50520 abiword_3.0.1-5.debian.tar.xz Files: 321d12652bf169b047e62420a69e462c 2625 gnome optional abiword_3.0.1-5.dsc b7f152cdd20b6778748323b96dcddc59 50520 gnome optional abiword_3.0.1-5.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJWo+UnAAoJECw7Q2/qxoEBhx0IAJMFJ/NgylbrDjOC+MUbhksk ZjPyI8PFdWIh25FglExIttCGMCDL+K/DHHPpXwUm2qCbGVnGGNLIuspf3nxoNsGn vMi8TfnkYXzqwbsdOfUij8fcSDFcnZJKLVhA6vFPWsiZmH0dnGtVKB37to97B0UE 2eCWprPcTdu2Fyurk2ZHKue6Rra9U/m1oTyokLpIZJN1l4YMSn5Pn1lXATpbsTt1 RAEgrOzlmhqdlLG63rnFA4OLimVz9Xnrw7YvTRRXI4vMLT0lngqUXAKRKPrkw+1N CkT4SYBcBFVVF/5QqaeCKKjjvE5uolJUQqlKtGS13udbQBtFpvzu2QlF790x7GY= =g/09 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processed: wicd-daemon: Can't connect to WEP networks anymore
Processing control commands: > forwarded -1 https://bugs.launchpad.net/wicd/+bug/1419464 Bug #812427 [wicd,wicd-daemon] wicd-daemon: Can't connect to WEP networks anymore Set Bug forwarded-to-address to 'https://bugs.launchpad.net/wicd/+bug/1419464'. -- 812427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#812427: wicd-daemon: Can't connect to WEP networks anymore
Package: wicd,wicd-daemon Version: 1.7.3-2 Severity: important Tags: upstream Control: forwarded -1 https://bugs.launchpad.net/wicd/+bug/1419464 Since wicd 1.7.3, wicd can't connect to WEP based wireless networks anymore. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (900, 'testing'), (899, 'testing-proposed-updates'), (600, 'stable'), (500, 'proposed-updates'), (201, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.4.0-rc8-686-pae (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages wicd-daemon depends on: ii adduser 3.113+nmu3 ii dbus 1.10.6-1 ii debconf 1.5.58 ii ethtool 1:4.2-1 ii iproute2 4.3.0-1 ii iputils-ping 3:20121221-5+b2 ii isc-dhcp-client 4.3.3-5 ii lsb-base 9.20160110 ii net-tools1.60+git20150829.73cef8a-2 ii psmisc 22.21-2.1 ii python-dbus 1.2.0-3 ii python-gobject 3.18.2-2 ii python-wicd 1.7.3-3 pn python:any ii wireless-tools 30~pre9-8 ii wpasupplicant2.3-2.3 Versions of packages wicd-daemon recommends: ii rfkill 0.5-1 ii wicd-cli [wicd-client] 1.7.3-2 ii wicd-curses [wicd-client] 1.7.3-2 ii wicd-gtk [wicd-client] 1.7.3-2 Versions of packages wicd-daemon suggests: ii pm-utils 1.4.1-15 Versions of packages wicd depends on: ii wicd-cli [wicd-client] 1.7.3-2 ii wicd-curses [wicd-client] 1.7.3-2 ii wicd-gtk [wicd-client] 1.7.3-2 Versions of packages wicd-cli depends on: pn python:any Versions of packages wicd-cli recommends: ii sudo 1.8.15-1.1 Versions of packages wicd-gtk depends on: ii python-glade2 2.24.0-4 ii python-gtk22.24.0-4 pn python:any Versions of packages wicd-gtk recommends: ii gksu 2.0.2-9 ii python-notify 0.1.1-4 Versions of packages wicd-curses depends on: ii python-urwid 1.3.1-2 pn python:any Versions of packages wicd-curses recommends: ii sudo 1.8.15-1.1 Versions of packages python-wicd depends on: pn python:any -- debconf information: * wicd/users:
Bug#812224: IndexError: list index out of range
Control: tag -1 - help + pending Hi again, Axel Beckert wrote: > I'll contact the new upstream about this issue. Actually the bug has been reported 4 times upstream. A few of these bug reports had patches. Took the one from ArchLinux, where someone thanked for the patch and confirmed that it's working. Will upload a new package soon. I though fear there are more such issues in here... Any help is appreciated. Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: Re: Bug#812224: IndexError: list index out of range
Processing control commands: > tag -1 + help upstream Bug #812224 [wicd-curses] IndexError: list index out of range Added tag(s) help and upstream. -- 812224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#812224: IndexError: list index out of range
Control: tag -1 + help upstream Hi, Axel Beckert wrote: > Jens Kubieziel wrote: > > * Axel Beckert schrieb am 2016-01-22 um 13:23 Uhr: > > > The connection you've chosen, is that a wireless or a wired one? I > > > suspect a wireless one. > > > > Your suspicion is right. It's wireless. > > Thanks. Will have a look at it. Seems as if I checked changing > properties of wireless networks (which resulted in the patch > https://anonscm.debian.org/cgit/collab-maint/wicd.git/tree/debian/patches/35-fix_ValueError_None_is_not_in_list.patch) > but not actually connecting to one as I prefer wired connections at > home for better backup performance. Sorry for missing that. Hrm, I actually can't connect to my wireless network at home with wicd anymore, but I couldn't find a solution to either issue. :-/ I'll contact the new upstream about this issue. If neither the new upstream nor the anyone else reading this comes up with a fix, I'm considering uploading 1.7.2.4 again to unstable, either with an epoch added or with a "+really1.7.2.4" suffix to the upstream version. Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: retitle 812224 to wicd-curses: IndexError: list index out of range
Processing commands for cont...@bugs.debian.org: > retitle 812224 wicd-curses: IndexError: list index out of range Bug #812224 [wicd-curses] IndexError: list index out of range Changed Bug title to 'wicd-curses: IndexError: list index out of range' from 'IndexError: list index out of range' > thanks Stopping processing here. Please contact me if you need assistance. -- 812224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#812224: IndexError: list index out of range
Processing control commands: > tag -1 - help + pending Bug #812224 [wicd-curses] IndexError: list index out of range Ignoring request to alter tags of bug #812224 to the same tags previously set Bug #812224 [wicd-curses] IndexError: list index out of range Added tag(s) pending. -- 812224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)
El 23/01/16 a las 09:21, Thomas Schmitt escribió:
There is a fourth dimension to be expressed: Bootloader.
Then there is the dimension of ISO filesystem objects.
A user wish would contain at least
ISO-Object, Bootloader, Medium, Firmware, Architecture
E.g.
Appended Partition, with GRUB2 content, for CDROM and HDD, via EFI, on i386
ISO Data File, with SYSLINUX content, for HDD, via BIOS, on i386 and amd64
I am not sure whether this list of more or less combinable
dimensions is complete yet.
Further one will want to express whether the gaps between partitions
should be filled, which kinds of partition tables shall emerge, ...
These properties are global to the ISO, not specific to a single
boot image. Some are combinable, some are mutally exclusive.
(Maybe it is time to break out an UML editor.)
I propose you to send these concerns to live-wrapper project which has
just begun and it's advertised as highly modular by Iain. It would be
quite nice if all these concerns were properly addressed by Iain's tool.
I am not saying that they are not welcomed to live-build but, right
now, I think we should focus on making UEFI to boot and not re-thinking
all the bootloader handling.
grub-mkrescue layout is rarely used for distro ISOs.
I blame this on the existing SYSLINUX based production software
for distro ISOs. In principle, a pure GRUB2 or a pure SYSLINUX
equipment appears to be the more reasonable choice.
I once asked in a Debconf why the people were so stubborn to use
syslinux instead of using grub2 (which seems technically superior to
me). It would seem that the same people that maintain syslinux happen to
maintain the kernel boot stack (or whatever it is called, I mean what
happens just after the bootloader handling the execution to the kernel).
So, that means, it's far easier to them to debug why the kernel is
refusing to boot.
I am personally in a favour of GRUB2-only Live CDs so that it's much
easier to have native Super Grub2 Disk in them :) .
Maybe we can just name them as:
"Main bootloader"
and
"Alternate bootloader".
The model does not imply any ranking. "First", "Second", "Third"
could be justified, because there are lists in El Torito and
partition tables where the boot entries have to line up in sequence.
For my taste, "Main" or "Primary" too much implies a rank.
So... what about using:
FIRST_BOOTLOADER
and
SECOND_BOOTLOADER
instead of my current:
PRIMARY_BOOTLOADER
and
SECONDARY_BOOTLOADER
?
I could even add a third bootloader if needed. And, well, I have some
ideas on how to add some special functions to binary_bootloader files so
that we have some sort of Object-Oriented / Hook programming when
defining what goes into the mkisofs options.
If you check current: binary_iso file it just relies on existing
binary_bootloaders without having an agnostic bootloader approach.
Here it's what I'm talking about:
https://github.com/adrian15/live-build/blob/5eba3dff5a16a34c3c1eb5d54e3767339654e2d0/scripts/build/binary_iso#L111-L145
case "${LB_PRIMARY_BOOTLOADER}" in
grub)
(...)
grub-pc)
(...)
esac
We could just invent the:
grub-pc-xorriso-options()
or
syslinux-xorriso-options()
functions which would be defined in:
binary_grub-pc
or
binary_syslinux
files
and handle all of these with only 3 or 4 lines of code.
E.g. binary_iso would add '-eltorito-alt-boot' just before a second
bootloader so that the bootloader only needs to take care of their own
boot options.
Is there anyone opposed to such a big change on live-build handling of
bootloaders?
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
Bug#812443: mknbi: not compatable with linux 2.6 or newer
Package: mknbi Version: 1.4.4-11 Severity: normal Tags: upstream from http://etherboot.org/wiki/doc NBI, Etherboot and Linux 2.6 Unfortunately, mknbi cannot be used to make a NBI of a Linux 2.6 (or newer) kernel image. If you are tied to Etherboot but need to boot a Linux 2.6 or newer kernel, wraplinux must be used to create a working NBI. This appears be the only issue in an otherwise stable package, and given a upstream recommended alternative, I recommend adding a note to the man page, and since wraplinux is packaged for debian that it be recommended to minimize frustration. -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.2.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages mknbi depends on: ii perl 5.22.1-4 mknbi recommends no packages. mknbi suggests no packages. -- no debconf information
Processed: tagging 812427
Processing commands for cont...@bugs.debian.org: > tags 812427 + pending Bug #812427 [wicd,wicd-daemon] wicd-daemon: Can't connect to WEP networks anymore Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 812427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809882: marked as done (abiword: FTBFS with libpng16)
Your message dated Sat, 23 Jan 2016 21:49:40 + with message-id and subject line Bug#809882: fixed in abiword 3.0.1-5 has caused the Debian Bug report #809882, regarding abiword: FTBFS with libpng16 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: abiword Severity: important User: lib...@packages.debian.org Usertags: libpng16-transition Dear abiword maintainer, Currently we are preparing the transistion of libpng1.2 to libpng1.6. The transistion bug is #650601. A rebuilt of all packages depending on libpng-dev and libpng12-dev has been done. The result with buildlogs can be found here: https://libpng.sviech.de/ abiword FTBFS during this rebuild. The buildlog is available at https://libpng.sviech.de/abiword.build The Titanpad at https://titanpad.com/libpng16-transistion might give you clues about what went wrong as well as some recipes/pointers how to fix them. Please feel free to amend the information on the pad as you might see fit. A plain-text, non java-script version is here: https://titanpad.com/ep/pad/export/libpng16-transistion/latest Please try to make abiword compatible with libpng16 and then make sure to B-D on libpng-dev only, if the fix makes it possible to compile it against libdev12 and libdev16. If you can only make in a non-backward compatible way, please B-D on libpng16-dev. This bug will become RC as soon as the transistion starts. Best regards, -- tobi --- End Message --- --- Begin Message --- Source: abiword Source-Version: 3.0.1-5 We believe that the bug you reported is fixed in the latest version of abiword, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam Borowski (supplier of updated abiword package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Jan 2016 21:21:21 +0100 Source: abiword Binary: abiword-common abiword abiword-plugin-grammar libabiword-3.0 libabiword-3.0-dev gir1.2-abiword-3.0 abiword-dbg Architecture: source Version: 3.0.1-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski Description: abiword- efficient, featureful word processor with collaboration abiword-common - efficient, featureful word processor with collaboration -- common abiword-dbg - debugging symbols for abiword word processor abiword-plugin-grammar - grammar checking plugin for AbiWord gir1.2-abiword-3.0 - GObject introspection data for libabiword libabiword-3.0 - efficient, featureful word processor with collaboration -- shared libabiword-3.0-dev - efficient, featureful word processor with collaboration -- develo Closes: 809882 811381 Changes: abiword (3.0.1-5) unstable; urgency=medium . * QA upload. * Fix FTBFS with libpng16 (closes: #809882) * Use default gnutls cipher/kx priorities, fixes FTBFS with gnutls30. * Fix FTBFS with gcc-6 (closes: #811381) Checksums-Sha1: 8054c2ca3cd31ae0f563fc463d4db12d4727595e 2625 abiword_3.0.1-5.dsc c85f6cc99f1e53c06c4ef74d27cea3f4ac095618 50520 abiword_3.0.1-5.debian.tar.xz Checksums-Sha256: b9a7e557298afb3e7d184ba8a36d398aaa9f9911b756047a8d4a68551605bed1 2625 abiword_3.0.1-5.dsc b26c2c12ebb1f578010578a1aa663fab539bb524b9b63b3eb51743db9bb31900 50520 abiword_3.0.1-5.debian.tar.xz Files: 321d12652bf169b047e62420a69e462c 2625 gnome optional abiword_3.0.1-5.dsc b7f152cdd20b6778748323b96dcddc59 50520 gnome optional abiword_3.0.1-5.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJWo+UnAAoJECw7Q2/qxoEBhx0IAJMFJ/NgylbrDjOC+MUbhksk ZjPyI8PFdWIh25FglExIttCGMCDL+K/DHHPpXwUm2qCbGVnGGNLIuspf3nxoNsGn vMi8TfnkYXzqwbsdOfUij8fcSDFcnZJKLVhA6vFPWsiZmH0dnGtVKB37to97B0UE 2eCWprPcTdu2Fyurk2ZHKue6Rra9U/m1oTyokLpIZJN1l4YMSn5Pn1lXATpbsTt1 RAEgrOzlmhqdlLG63rnFA4OLimVz9Xnrw7YvTRRXI4vMLT0lngqUXAKRKPrkw+1N CkT4SYBcBFVVF/5QqaeCKKjjvE5uolJUQqlKtGS13udbQBtFpvzu2QlF790x7GY= =g/09 -END PGP SIGNATURE End Message ---
Bug#811381: marked as done (abiword: ftbfs with GCC-6)
Your message dated Sat, 23 Jan 2016 21:49:40 +
with message-id
and subject line Bug#811381: fixed in abiword 3.0.1-5
has caused the Debian Bug report #811381,
regarding abiword: ftbfs with GCC-6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
811381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: abiword
Severity: normal
Tags: upstream patch
Usertags: ftbfs-gcc-6
Dear Maintainer,
abiword fails to build with gcc-6. This appears to be because g++ uses
C++ 11 by default which introduces several errors. They include brace
initializers that use negative numbers to initialize unsigned variables,
"blah"foo not being valid because of operator "", and errors about
implicitly converting to bool. The attached patch fixes enough of these
issues to get the package to compile, but it may not always be the best
way to resolve the issue.
-- System Information:
Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- abiword-3.0.1.orig/plugins/collab/backends/service/xp/RealmProtocol.cpp
+++ abiword-3.0.1/plugins/collab/backends/service/xp/RealmProtocol.cpp
@@ -6,8 +6,8 @@ namespace protocolv1 {
#define MAX_PACKET_DATA_SIZE 64*1024*1024
-#define RPV1_PACKET_NONEXISTENT -2
-#define RPV1_PACKET_VARIABLE -1
+#define RPV1_PACKET_NONEXISTENT uint32_t(-2)
+#define RPV1_PACKET_VARIABLE uint32_t(-1)
static uint32_t body_size[6] = {
RPV1_PACKET_NONEXISTENT, /* 0: reserved */
--- abiword-3.0.1.orig/plugins/collab/backends/service/xp/soa_soup.cpp
+++ abiword-3.0.1/plugins/collab/backends/service/xp/soa_soup.cpp
@@ -163,7 +163,7 @@ namespace soup_soa {
static bool _invoke(const std::string& /*url*/, const soa::method_invocation& /*mi*/, SoaSoupSession& sess, std::string& result) {
if (!sess.m_session || !sess.m_msg )
- return soa::GenericPtr();
+ return false;
guint status = soup_session_send_message (sess.m_session, sess.m_msg);
if (!(SOUP_STATUS_IS_SUCCESSFUL (status) ||
--- abiword-3.0.1.orig/plugins/latex/xp/ie_exp_LaTeX.cpp
+++ abiword-3.0.1/plugins/latex/xp/ie_exp_LaTeX.cpp
@@ -1329,7 +1329,7 @@ void s_LaTeX_Listener::_outputData(const
m_pie->write(sBuf.c_str(),sBuf.size());
}
-#define SUB(a,who) case a: subst = "\\(\\"who"\\)"; return true;
+#define SUB(a,who) case a: subst = "\\(\\" who"\\)"; return true;
#define SUBd(a,who) case a: subst = who; return true;
static bool _convertLettersToSymbols(char c, const char *& subst)
{
--- abiword-3.0.1.orig/plugins/xslfo/xp/ie_exp_XSL-FO.cpp
+++ abiword-3.0.1/plugins/xslfo/xp/ie_exp_XSL-FO.cpp
@@ -1451,7 +1451,7 @@ void s_XSL_FO_Listener::_openSection(PT_
{ \
UT_UTF8String esc = szValue; \
esc.escapeXML(); \
- buf += " "x"=\""; \
+ buf += " " x"=\""; \
buf += esc.utf8_str(); \
buf += "\""; \
}
--- End Message ---
--- Begin Message ---
Source: abiword
Source-Version: 3.0.1-5
We believe that the bug you reported is fixed in the latest version of
abiword, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adam Borowski (supplier of updated abiword package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 23 Jan 2016 21:21:21 +0100
Source: abiword
Binary: abiword-common abiword abiword-plugin-grammar libabiword-3.0
libabiword-3.0-dev gir1.2-abiword-3.0 abiword-dbg
Architecture: source
Version: 3.0.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Adam Borowski
Description:
abiword- efficient, featureful word processor with collaboration
abiword-common - efficient, featureful word processor with collaboration --
common
abiword-dbg - debugging symbols for abiword word processor
abiword-plugin-grammar - grammar checking plugin for AbiWord
gir1.2-abiword-3.0 - GObject introspection data for libabiwor
Processing of wicd_1.7.3-3_i386.changes
wicd_1.7.3-3_i386.changes uploaded successfully to localhost along with the files: wicd_1.7.3-3.dsc wicd_1.7.3-3.debian.tar.xz python-wicd_1.7.3-3_all.deb wicd-cli_1.7.3-3_all.deb wicd-curses_1.7.3-3_all.deb wicd-daemon_1.7.3-3_all.deb wicd-gtk_1.7.3-3_all.deb wicd_1.7.3-3_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)
Processed: tagging 812224
Processing commands for cont...@bugs.debian.org: > tags 812224 - help Bug #812224 [wicd-curses] wicd-curses: IndexError: list index out of range Removed tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 812224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of nield_0.6.1-1_source.changes
nield_0.6.1-1_source.changes uploaded successfully to localhost along with the files: nield_0.6.1-1.dsc nield_0.6.1.orig.tar.gz nield_0.6.1-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)
Bug#812224: marked as done (wicd-curses: IndexError: list index out of range)
Your message dated Sun, 24 Jan 2016 04:22:47 + with message-id and subject line Bug#812224: fixed in wicd 1.7.3-3 has caused the Debian Bug report #812224, regarding wicd-curses: IndexError: list index out of range to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 812224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wicd-curses Version: 1.7.3-2 Severity: grave Justification: renders package unusable Dear Maintainer, the new version of wicd is rather crashy. > ERROR:dbus.connection:Exception in handler for D-Bus signal: > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 230, in > maybe_handle_message > self._handler(*args, **kwargs) > File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper > return func(*args, **kargs) > File "/usr/share/wicd/curses/wicd-curses.py", line 850, in update_netlist > self.wiredCB.get_body().set_list(wiredL) > File "/usr/share/wicd/curses/wicd-curses.py", line 469, in set_list > wired.ReadWiredNetworkProfile(self.get_selected_profile()) > File "/usr/share/wicd/curses/wicd-curses.py", line 535, in > get_selected_profile > return self.theList[loc] > IndexError: list index out of range This happens every time, without doing anything at all. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0f (SMP w/4 CPU cores; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wicd-curses depends on: ii python-urwid 1.3.1-2 pn python:any ii wicd-daemon 1.7.3-2 Versions of packages wicd-curses recommends: ii sudo 1.8.15-1.1 wicd-curses suggests no packages. Versions of packages wicd-daemon depends on: ii adduser 3.113+nmu3 ii dbus 1.10.6-1 ii debconf 1.5.58 ii ethtool 1:4.2-1 ii iproute2 4.3.0-1 ii iputils-ping 3:20121221-5+b2 ii isc-dhcp-client 4.3.3-5 ii lsb-base 9.20160110 ii net-tools1.60+git20150829.73cef8a-2 ii psmisc 22.21-2.1+b1 ii python-dbus 1.2.0-3 ii python-gobject 3.18.2-2 ii python-wicd 1.7.3-2 pn python:any ii wireless-tools 30~pre9-8 ii wpasupplicant2.3-2.3 Versions of packages wicd-daemon recommends: ii rfkill 0.5-1 Versions of packages wicd-daemon suggests: pn pm-utils Versions of packages python-wicd depends on: pn python:any -- debconf information excluded --- End Message --- --- Begin Message --- Source: wicd Source-Version: 1.7.3-3 We believe that the bug you reported is fixed in the latest version of wicd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 812...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated wicd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 24 Jan 2016 02:35:17 +0100 Source: wicd Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd Architecture: source all Version: 1.7.3-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Axel Beckert Description: python-wicd - wired and wireless network manager - Python module wicd - wired and wireless network manager - metapackage wicd-cli - wired and wireless network manager - scriptable console client wicd-curses - wired and wireless network manager - Curses client wicd-daemon - wired and wireless network manager - daemon wicd-gtk - wired and wireless network manager - GTK+ client Closes: 812224 812427 Changes: wicd (1.7.3-3) unstable; urgency=low . * QA upload * Add patch from upstream bug report to fix "IndexError: list index out of range" in wicd-curses. (Closes: #812224) * Add patch to fix the parsing and writing of wep-hex configurations and hence fix connecting to WEP based networks. (Cl
Bug#812427: marked as done (wicd-daemon: Can't connect to WEP networks anymore)
Your message dated Sun, 24 Jan 2016 04:22:47 + with message-id and subject line Bug#812427: fixed in wicd 1.7.3-3 has caused the Debian Bug report #812427, regarding wicd-daemon: Can't connect to WEP networks anymore to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 812427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wicd,wicd-daemon Version: 1.7.3-2 Severity: important Tags: upstream Control: forwarded -1 https://bugs.launchpad.net/wicd/+bug/1419464 Since wicd 1.7.3, wicd can't connect to WEP based wireless networks anymore. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (900, 'testing'), (899, 'testing-proposed-updates'), (600, 'stable'), (500, 'proposed-updates'), (201, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.4.0-rc8-686-pae (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages wicd-daemon depends on: ii adduser 3.113+nmu3 ii dbus 1.10.6-1 ii debconf 1.5.58 ii ethtool 1:4.2-1 ii iproute2 4.3.0-1 ii iputils-ping 3:20121221-5+b2 ii isc-dhcp-client 4.3.3-5 ii lsb-base 9.20160110 ii net-tools1.60+git20150829.73cef8a-2 ii psmisc 22.21-2.1 ii python-dbus 1.2.0-3 ii python-gobject 3.18.2-2 ii python-wicd 1.7.3-3 pn python:any ii wireless-tools 30~pre9-8 ii wpasupplicant2.3-2.3 Versions of packages wicd-daemon recommends: ii rfkill 0.5-1 ii wicd-cli [wicd-client] 1.7.3-2 ii wicd-curses [wicd-client] 1.7.3-2 ii wicd-gtk [wicd-client] 1.7.3-2 Versions of packages wicd-daemon suggests: ii pm-utils 1.4.1-15 Versions of packages wicd depends on: ii wicd-cli [wicd-client] 1.7.3-2 ii wicd-curses [wicd-client] 1.7.3-2 ii wicd-gtk [wicd-client] 1.7.3-2 Versions of packages wicd-cli depends on: pn python:any Versions of packages wicd-cli recommends: ii sudo 1.8.15-1.1 Versions of packages wicd-gtk depends on: ii python-glade2 2.24.0-4 ii python-gtk22.24.0-4 pn python:any Versions of packages wicd-gtk recommends: ii gksu 2.0.2-9 ii python-notify 0.1.1-4 Versions of packages wicd-curses depends on: ii python-urwid 1.3.1-2 pn python:any Versions of packages wicd-curses recommends: ii sudo 1.8.15-1.1 Versions of packages python-wicd depends on: pn python:any -- debconf information: * wicd/users: --- End Message --- --- Begin Message --- Source: wicd Source-Version: 1.7.3-3 We believe that the bug you reported is fixed in the latest version of wicd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 812...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated wicd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 24 Jan 2016 02:35:17 +0100 Source: wicd Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd Architecture: source all Version: 1.7.3-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Axel Beckert Description: python-wicd - wired and wireless network manager - Python module wicd - wired and wireless network manager - metapackage wicd-cli - wired and wireless network manager - scriptable console client wicd-curses - wired and wireless network manager - Curses client wicd-daemon - wired and wireless network manager - daemon wicd-gtk - wired and wireless network manager - GTK+ client Closes: 812224 812427 Changes: wicd (1.7.3-3) unstable; urgency=low . * QA upload * Add patch from upstream bug report to fix "IndexError: list index out of range" in wicd-curses. (Closes: #812224) * Add patch to fix the parsing and writing of wep-hex configurations and hence fix connecting to WEP based networks. (Closes: #812427) Checksums-Sha1: e8dcb24337ef6ef7b7eb3ac50dda7694fcedbcb5 2120 wicd_1.7.3-3.dsc 8a08d102b19c41f6a6a24a58f
wicd_1.7.3-3_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 24 Jan 2016 02:35:17 +0100 Source: wicd Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd Architecture: source all Version: 1.7.3-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Axel Beckert Description: python-wicd - wired and wireless network manager - Python module wicd - wired and wireless network manager - metapackage wicd-cli - wired and wireless network manager - scriptable console client wicd-curses - wired and wireless network manager - Curses client wicd-daemon - wired and wireless network manager - daemon wicd-gtk - wired and wireless network manager - GTK+ client Closes: 812224 812427 Changes: wicd (1.7.3-3) unstable; urgency=low . * QA upload * Add patch from upstream bug report to fix "IndexError: list index out of range" in wicd-curses. (Closes: #812224) * Add patch to fix the parsing and writing of wep-hex configurations and hence fix connecting to WEP based networks. (Closes: #812427) Checksums-Sha1: e8dcb24337ef6ef7b7eb3ac50dda7694fcedbcb5 2120 wicd_1.7.3-3.dsc 8a08d102b19c41f6a6a24a58fb145d6a7f228df3 25176 wicd_1.7.3-3.debian.tar.xz e274da916f009e0a2189f28a723361143e62dba8 52402 python-wicd_1.7.3-3_all.deb 3e02442fe0d3108eec8704aa2b2f5654d4b2ae37 25370 wicd-cli_1.7.3-3_all.deb 84be7cbd7fbb9dc629a81e10eb2298bbd7043fad 49764 wicd-curses_1.7.3-3_all.deb 79f3cf636c493f04f30e610b48ea6f5d02214d76 159332 wicd-daemon_1.7.3-3_all.deb 46d11bcc660d2c8ce17fcb76d0d3e95478be6591 152554 wicd-gtk_1.7.3-3_all.deb aae53d6258783904e58314692da037efc1d38f52 21710 wicd_1.7.3-3_all.deb Checksums-Sha256: 81f1b334f14d0c1c87611b776670c38bb585c4ecfea57679e640a735eeecc41a 2120 wicd_1.7.3-3.dsc 753ddf6bf82217f42eaaa697668d82d92081e2470db00c8ab5de51c2af8ea09c 25176 wicd_1.7.3-3.debian.tar.xz 7ce51e475e02831b374bb4d167b1445a41a504c6bf93d53749daa5d76d2c9496 52402 python-wicd_1.7.3-3_all.deb f6e77107c20f4b8329d5cecba1f0cbc772a20cb12bbd23479458078a90954231 25370 wicd-cli_1.7.3-3_all.deb 3ad6aaa87826bb188051dd9ce0e57d157d42dd24ce8d10ed4421a3adcce5188e 49764 wicd-curses_1.7.3-3_all.deb 71535edb40ffe6aba7f90b8a25c774d66f8a1723a2a3955d63487cd6eb1a71c1 159332 wicd-daemon_1.7.3-3_all.deb f43c741f0643d1c6c679c16fb5fb36476806accb4a723ca768a6129c09b970c3 152554 wicd-gtk_1.7.3-3_all.deb 8f1c30109f5b82395126f5cab492fb8ab26d9a1be69ddb637703d73b1dea1a7f 21710 wicd_1.7.3-3_all.deb Files: 00515f0661102893d94639dc34f00f12 2120 net optional wicd_1.7.3-3.dsc 013f39c6bfcd015a09198527aa4c2ee5 25176 net optional wicd_1.7.3-3.debian.tar.xz 53291ea1cd8d8f2db5271536393ef511 52402 python optional python-wicd_1.7.3-3_all.deb 442581026aa6cc150bdf13ca683866b6 25370 net optional wicd-cli_1.7.3-3_all.deb 872a9cfcc4553f2dd3b054044893ec18 49764 net optional wicd-curses_1.7.3-3_all.deb 718a8730994292be6f0045781015e6b6 159332 net optional wicd-daemon_1.7.3-3_all.deb fa4d8d2c3c6ddba32800e640e0458918 152554 net optional wicd-gtk_1.7.3-3_all.deb 7870b9bd2d2f5f3a0c0de2b81e7bd8b4 21710 net optional wicd_1.7.3-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWpCvIAAoJEGvmY8daNcl1A0EQALWcy0c70VOyBKuFmGOUmiWW zzmSJhgDsrzIvR2ENk/HhmFarLr81w5bgO01TEcM93srjHNXLFmYgW1omxDxbZNU t2PVecTMBJqMTBHvo/S5fcX8MJDETQeNj68dQiIK3ayERW7KsCjF1v53dZYsEw3H M9y9Crx8eeWUIgPZ+uLOvdW6eBR5QSEWrd/mibqzUG7bT0EHtiiB440eoSQjSyD1 nobk+L34jwoZAa3mvbFK+5itSpeo1I9KMgJ8py3Uupzk92WpfxVAgRCZ+4o0p4Sb MHvUbAsAr9/x+MJJekH9BtOz2RYlrLWFrKs342GI+G+HSc1kc338KkL7QM5zKOG2 zsEnPrqUJYz4nvK+sgPRZxRtY3BWLpTXX7yo237sVd0AROr5pqra3vKFi2SyhuZ0 V6e8kbb/f+HfdeAKnszJIZRl/WWWcW4+DrzLNUnzNs1dUmDs2DKNDv46NhxHsnPz 9gQ2YTWk+A6+DLh5D89GdS/tgUGSnPpB16vS/lhL7V0YobPkwkOdmBn7ueAzH3nL ZLl3DUEtoB9uxuq3nfvOLyA5Kb1MzHVeP34CQPJCt6LrbhC9EN50lLbIWN1uEt56 TXDoPctH9Up1YkZPu0D9oZnRsCFjL/osvxfSGYjK8llEGvkFfYCHO7ifVGimFufd +/oUp3UgSTQqUa8/h+SE =0qOU -END PGP SIGNATURE- Thank you for your contribution to Debian.
glfer is marked for autoremoval from testing
glfer 0.4.2-2 is marked for autoremoval from testing on 2016-03-01 It (build-)depends on packages with these RC bugs: 811223: fftw: FTBFS: perl texi2html: Can't use 'defined(@array)'
gramofile is marked for autoremoval from testing
gramofile 1.6-10 is marked for autoremoval from testing on 2016-03-01 It (build-)depends on packages with these RC bugs: 811223: fftw: FTBFS: perl texi2html: Can't use 'defined(@array)'
