Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)
El 18/01/16 a las 07:31, Michal Suchanek escribió: Hello, thanks for working on this. On 18 January 2016 at 05:24, adrian15 wrote: In my last message I forgot to CC many people who are involved in this bug so I'm going to refer to my former message, CC some people and finally point you to my repo/branches where you might find interesting commits. 1) My original message with attached patches (which you can download to your email program and reply from there) can be found at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731709#153 2) Repo / Branches: * efi_support_based_on_debian_cd ( https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd ) : Original dirty branch where I worked in both syslinux-efi and grub-efi bootloaders at the same time * efi_support_based_on_debian_cd_rebased ( https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd_rebased ) : The same branch rebased to have minimal useful commits. syslinux-efi was removed from it because it did not boot. I have checked what EFI platforms I have and it seems neither would be bootable with this. 1) a Windows tablet that needs signed bootloader - signed grub is available as non-free package (because it cannot be modified to not break the signature) and presumably allows booting on such systems without going through the unlocking stuff which may break your windows installation. Yeah, that's the Microsoft Secure Boot. debian-cd people are working on bringing it into official Debian CDs. There is not a fixed date for that but everything points that it will be finished within 2016. Once they manage to do so I'll see how easy it is to port into this work. You can always try virtual systems. This is how I currently test this: kdesudo "kvm -bios /usr/share/ovmf/OVMF.fd -cdrom rescatux-0.40b3.iso -boot d -m 512" . 2) a mac mini which probably needs a GPT and the bootloader stored on a HFS+ volume or something. Also the bootloader needs to be 'blessed'. Command for that exists in grub and crashes. Never got this working on an USB stick. Well, I have not mentioned that this implementation (based on debian-cd team work) also would support intel based mac systems because it has an additional HFS+ volume. I also have a mac book pro myself and the 'hybrid' version of Super Grub2 Disk 2.02s3 works for me (when using ALT key at boot). I don't remember having blessed it so... I'm unsure about the need (or not) to bless it. So, the 'hybrid' Super Grub2 Disk 2.02s3 also has an additional HFS+ partition (as our current implementation here in these patches) put in place for mac book compatibility so I guess that this build will also boot in my system but I still need to test it. As to the primary and secondary bootloader - how is the efi bootloader secondary? It boots the same as the legacy bootloader. You probably want a concept of compatible bootloaders - that is pairs of bootloaders that can be installed alongside on the same medium. * What is it a secondary bootloader? It's what happens when you request mkisofs that your bootloader to be boot in second place or as a second partition. I don't know how it actually works. So in grub-efi we just add to the xorriso options: -eltorito-alt-boot \ -e boot/grub/efi.img \ -no-emul-boot \ -isohybrid-gpt-basdat \ -isohybrid-apm-hfsplus And in syslinux-efi (currently) we add: -eltorito-alt-boot \ --efi-boot boot/efi.img \ -append_partition 2 0x01 \ binary/boot/efi.img . So, I guess the -eltorito-alt-boot does the magic but I'm not sure. Maybe someone else can explain it better than me. * About current compatible bootloaders. The technology is there. I mean. This is what it's currently available: binary_grub-efi : Secondary bootloader binary_grub-legacy : Primary bootloader binary_grub-pc : Primary bootloader binary_syslinux : Primary bootloader binary_syslinux-efi : Secondary bootloader so that means, in theory you can request one of these 9 combinations: grub-legacy grub-pc syslinux grub-legacy,grub-efi grub-pc,grub-efi syslinux,grub-efi grub-legacy,syslinux-efi grub-pc,syslinux-efi syslinux,syslinux-efi Why can't you request: grub-efi or grub-efi,syslinux-efi ? Because nobody has coded grub-efi installed as a primary bootloader yet. But the 'framework' is there. You either need to improve binary_grub-efi or create another script file that does its job when ' Is_Primary_Bootloader "grub-efi" ' is true. Unless the user requests two bootloaders that are incompatible the medium can be created. Ignoring bootloaders is not a good idea. If the user requested something that is not possible the build should report an error and stop. Yeah, that it's hard to implement from the perspective of a single bootloader script. So I decided not to implement it. You could add an additional script or function named: check_compatible_bootable_pairs (as you propose) but then you need to maintain that fictional database each
Bug#811364: wicd-gtk: status's icons -Status of wireless network- doesnt show in the interface of Wicd
Package: wicd-gtk Version: 1.7.3-1 Severity: minor Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.3.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: systemd (via /run/systemd/system) Versions of packages wicd-gtk depends on: ii python-glade2 2.24.0-4 ii python-gtk22.24.0-4 pn python:any ii wicd-daemon1.7.3-1 Versions of packages wicd-gtk recommends: ii gksu 2.0.2-9 ii python-notify 0.1.1-4 wicd-gtk suggests no packages. Versions of packages wicd depends on: ii wicd-daemon 1.7.3-1 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-2+b4 ii python-gobject 3.18.2-2 ii python-wicd 1.7.3-1 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: * wicd/users:
Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)
On 18 January 2016 at 10:43, adrian15 wrote: > El 18/01/16 a las 07:31, Michal Suchanek escribió: >> >> Hello, >> >> thanks for working on this. >> > >> As to the primary and secondary bootloader - how is the efi bootloader >> secondary? It boots the same as the legacy bootloader. You probably >> want a concept of compatible bootloaders - that is pairs of >> bootloaders that can be installed alongside on the same medium. > > * What is it a secondary bootloader? > > It's what happens when you request mkisofs that your bootloader to be boot > in second place or as a second partition. I don't know how it actually > works. > > So in grub-efi we just add to the xorriso options: > > -eltorito-alt-boot \ > -e boot/grub/efi.img \ > -no-emul-boot \ > -isohybrid-gpt-basdat \ > -isohybrid-apm-hfsplus > > And in syslinux-efi (currently) we add: > > -eltorito-alt-boot \ > --efi-boot boot/efi.img \ > -append_partition 2 0x01 \ > binary/boot/efi.img -eltorito-alt-boot is not documented option of xorriso. For genisoimage -eltorito-alt-boot denotes start of new bootloader parameters. So any bootloader is made primary by leaving out -eltorito-alt-boot. > > . > > So, I guess the -eltorito-alt-boot does the magic but I'm not sure. Maybe > someone else can explain it better than me. > > > * About current compatible bootloaders. > The technology is there. I mean. This is what it's currently available: > > binary_grub-efi : Secondary bootloader > binary_grub-legacy : Primary bootloader > binary_grub-pc : Primary bootloader > binary_syslinux : Primary bootloader > binary_syslinux-efi : Secondary bootloader > > so that means, in theory you can request one of these 9 combinations: > > grub-legacy > grub-pc > syslinux > > grub-legacy,grub-efi > grub-pc,grub-efi > syslinux,grub-efi > > grub-legacy,syslinux-efi > grub-pc,syslinux-efi > syslinux,syslinux-efi You can probably use only one legacy bootloader but syslinux-efi and grub-efi use different files so it should be possible to install both. I am not sure how selecting one or the other would work, though. > >> Unless >> the user requests two bootloaders that are incompatible the medium can >> be created. >> >> Ignoring bootloaders is not a good idea. If the user requested >> something that is not possible the build should report an error and >> stop. > > Yeah, that it's hard to implement from the perspective of a single > bootloader script. So I decided not to implement it. > > You could add an additional script or function named: > check_compatible_bootable_pairs (as you propose) but then you need to > maintain that fictional database each time a new bootloader gets in. > > That's why I decide to avoid it using it. > > What it's straight-forward to implement is one of the only-secondary > bootloaders finding themselves as a primary bootloader and outputting a > warning message. But, I'm not sure what to put there as a warning. Any > suggestion? Unsupported bootloader combination or whatever. It should not be a warning however. The script should avoid making unbootable medium. Thanks Michal
Bug#805799: kst: Fails to build with GSL 2
tags 805799 +patch thanks Ubuntu have a fix for this. https://patches.ubuntu.com/k/kst/kst_2.0.3-4ubuntu3.patch I cleaned up the changelog and removed ubuntus maintainer changes and uploaded to raspbian. Debdiff of that at. http://debdiffs.raspbian.org/main/k/kst/kst_2.0.3-4%2brpi1.debdiff
Processed: re: kst: Fails to build with GSL 2
Processing commands for cont...@bugs.debian.org: > tags 805799 +patch Bug #805799 [src:kst] kst: Fails to build with GSL 2 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 805799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)
Hi, adrian15 wrote: > * What is it a secondary bootloader? > It's what happens when you request mkisofs that your bootloader to be > boot in second place or as a second partition. I don't know how it > actually works. An ISO may contain several lures for boot firmware. If it is booted from CD/DVD/BD, then the lures are in the El Torito boot catalog. In case of debian-cd it contains two entries which point to boot images. One entry is marked as suitable for BIOS and one marked as suitable for EFI. The boot firmware then picks what it deems right and starts it, or offers it to the user for starting. If the ISO is presented on USB stick or alike, then BIOS looks for the magic number of an MBR and if so, mindlessly executes the x86 machine code that starts at byte 0 of the ISO. This code then hops onto the same boot code that is advertised by El Torito (because xorriso or isohybrid patched its block address into the MBR code). EFI looks on USB stick for an MBR partition of type 0xef or for a single partition of type 0xee. In the latter case it assumes the presence of GPT and looks for a GPT partition with type GUID 28732ac11ff8d211ba4b00a0c93ec93b. Inside the found partition it expects a FAT filesystem and particular binaries for each supported processor archictecture. E.g. \EFI\BOOT\BOOTX64.EFI The El Torito EFI boot image has the same content specification as the EFI System Partition. Therefore both boot paths can share the same data. My cheat sheet is at http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/view/head:/doc/boot_sectors.txt - > So, I guess the -eltorito-alt-boot does the magic but I'm not sure. > Maybe someone else can explain it better than me. -eltorito-alt-boot is simply a separator between the options of El Torito boot images. I assume your first boot image is announced by -b and gets the usual options -no-emul-boot -boot-load-size 4 -boot-info-table Before the announcement of the EFI boot image begins, option -eltorito-alt-boot is needed to protect your -b and its helpers from being overwritten. > So in grub-efi we just add to the xorriso options: > -eltorito-alt-boot \ > -e boot/grub/efi.img \ > -no-emul-boot \ > -isohybrid-gpt-basdat \ > -isohybrid-apm-hfsplus Here a second boot image gets announced by -e and the next three options apply to it. > And in syslinux-efi (currently) we add: > -eltorito-alt-boot \ > --efi-boot boot/efi.img \ Option --efi-boot is a shortcut for -eltorito-alt-boot -e ... -no-emul-boot -eltorito-alt-boot normally used by grub-mkrescue. The SYSLINUX community prefers -e. > -append_partition 2 0x01 \ > binary/boot/efi.img I wonder what EFI firmware would hop on an MBR partition of type 0x01. An EFI System Partition in MBR should have type 0xef to be recognized. It looks like this variant will not get GPT. That's fully compliant to UEFI 2.4. Just the MBR partition type should be 0xef. (Does "syslinux-efi" mean that you can boot from ISO via EFI and SYSLINUX stuff to an operating system ? That would be new.) --- Above options do not produce HFS+ with blessing. Option -isohybrid-apm-hfsplus causes an Apple Partition Map entry which points to the data content of boot/grub/efi.img. There are two ways known to me how to get a boot path via HFS+: Fedora Live CD as of Matthew Garrett or grub-mkrescue as of Vladimir Serbinenko. --- Fedora Live, e.g. Fedora-Live-Xfce-x86_64-rawhide-20150704.iso is the ancestor of debian-cd's layout. It contains a small HFS+ filesystem image as ISO data file /isolinux/macboot.img debian-cd does not have such an HFS+ image file. Image content and production is out of my scope. xorriso would only bond it to El Torito, MBR, GPT, and APM. I understand that APM leads some Macs to that HFS+ filesystem. Whether there are customers for GPT is unclear. The lures in El Torito and MBR are probably unused. The essential xorriso -as mkisofs options are a superset of those of debian-cd for amd64: -isohybrid-mbr /path/to/isohdpfx.bin -apm-block-size 2048 -c '/isolinux/boot.cat' -b '/isolinux/isolinux.bin' -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e '/isolinux/efiboot.img' -no-emul-boot -isohybrid-gpt-basdat -isohybrid-apm-hfsplus -eltorito-alt-boot -e '/isolinux/macboot.img' -no-emul-boot -isohybrid-gpt-hfsplus -isohybrid-apm-hfsplus (Options picked out of proposal of xorriso -hfsplus on \ -indev Fedora-Live-Xfce-x86_64-rawhide-20150704.iso \ -report_el_torito as_mkisofs ) No UEFI compliant firmware should use the GPT in there, because the MBR partition table contains a partition of type other than 0x00 and 0xee. EFI firmware should rather follow the MBR partition of type 0xef if the ISO is presented on USB st
Processed: tagging 811364
Processing commands for cont...@bugs.debian.org: > tags 811364 + confirmed Bug #811364 [wicd-gtk] wicd-gtk: status's icons -Status of wireless network- doesnt show in the interface of Wicd Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 811364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)
Hi, Michal Suchanek wrote: > -eltorito-alt-boot is not documented option of xorriso. You need to look into man xorrisofs for the options of the -as mkisofs emulation. -eltorito-alt-boot Finalize the current El Torito boot catalog entry and begin a new one. A boot image file and all its necessary options shall be specified before option -eltorito-alt-boot. All further El Torito boot options apply to the new catalog entry. Up to 32 catalog entries are possible. > So any bootloader is made primary by leaving out -eltorito-alt-boot. There is no "primary" or "secondary" on the level of boot images and loaders. (Of course you may call them this way in your project.) There are first, second, third ... El Torito boot images or MBR, GPT, APM partition entries. The sequence is just needed because not all can be first in the list. The boot firmware inspects the medium for its known lures, picks a tasty one, and follows it to the boot loader or kernel. > You can probably use only one legacy bootloader but syslinux-efi and > grub-efi use different files so it should be possible to install both. > I am not sure how selecting one or the other would work, though. You can offer several EL Torito boot images for BIOS, indeed. It will depend on your BIOS what it does in this case. There can be only one MBR, though. So you would have to hop by MBR x86 code to a standalone program which chooses among the BIOS suitable El Torito boot images. With EFI it makes few sense to offer more than one El Torito boot image or EFI System Partition. UEFI 2.4 rather prescribes to handle all alternatives inside the FAT filesystem. The firmware will start the \EFI\BOOT\BOOT*.EFI binary which it deems suitable for its processor type. This binary is quite free in its further proceedings. Have a nice day :) Thomas
Bug#811381: abiword: ftbfs with GCC-6
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 += "\""; \
}
Bug#811385: adplay: ftbfs with gcc-6
Package: adplay
Severity: normal
Tags: upstream
Usertags: ftbfs-gcc-6
Dear Maintainer,
adplay fails to build with gcc 6 because adplay.cc:92 tries to
initialize cfg.subsong which is an unsigned int with -1 which is invalid
in C++11.
The error from gcc is:
adplay.cc:98:1: error: narrowing conversion of '-1' from 'int' to
'unsigned int' inside { } [-Wnarrowing]
};
^
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 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)
Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)
A quick update on my grub-efi work: 1) I have noticed I have missed to give execution permissions to many files when I rebased. These are: scripts/build/binary_grub-efi scripts/build/binary_syslinux-efi scripts/build/efi-image scripts/build/grub-cpmodules You can find additional commits to fix this situation on: https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd_rebased and https://github.com/adrian15/live-build/commits/syslinux-efi-2016 . (I will probably do another rebase in another branch in the future with other of your suggestions and these fixes.) 2) I have released Rescatux 0.40 beta 5 based on: https://github.com/adrian15/live-build/tree/rescatux-0.40b5 (The patches you have already seen + execution permissions fixed) . It is built by using: --bootloaders="syslinux,grub-efi" . You can find more information about it and download links on: http://www.supergrubdisk.org/2016/01/18/rescatux-0-40-beta-5-released/ Remember that if you want to test it into a USB drive you need to do the 'dd' if you want it to work ok and that means DESTROYING your data in the USB drive. adrian15 -- Support free software. Donate to Super Grub Disk. Apoya el software libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
Processing of dwb_20150419git-2_amd64.changes
dwb_20150419git-2_amd64.changes uploaded successfully to localhost along with the files: dwb_20150419git-2.dsc dwb_20150419git-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)
dwb_20150419git-2_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Jan 2016 17:39:03 +0100 Source: dwb Binary: dwb Architecture: source Version: 20150419git-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sebastian Ramacher Description: dwb- lightweight WebKit browser Closes: 809569 Changes: dwb (20150419git-2) unstable; urgency=medium . * QA upload. * debian/control: Orphan package. * debian/patches/no-Werror.patch: Do not build with -Werror. (Closes: #809569) * debian/menu: Removed since dwb includes a desktop file. Checksums-Sha1: e1727706f70cf795a5c81162c8c729ae6de927a1 1807 dwb_20150419git-2.dsc d20f49455883ee3da0081830c4cc4148bef83a3f 5508 dwb_20150419git-2.debian.tar.xz Checksums-Sha256: 927f9121cc105f2507240a14e05f9cff7cc5b7ce3875709d1cc4a940c015565b 1807 dwb_20150419git-2.dsc 3bb8f9d4c46839a0262280fa35e4a13068c2cc0f9dcc023ee4f59620e73d3b70 5508 dwb_20150419git-2.debian.tar.xz Files: c08dc9e3b53ba532013b935420951189 1807 web extra dwb_20150419git-2.dsc 951fd1558e5152d9a77f37f07852f448 5508 web extra dwb_20150419git-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWnRVfAAoJEGny/FFupxmT2fUQAIGl8yhy0oJUKM8KDnIGEn+d 9HXiFXCbn5q27HL120CJi/oXTCe6NXD6FkHlEKUEZLuZcN/v089rkFLMG1BzQqhk bixGHYtblzlz3RCC66v4WhZLTXmdeoyGcmcQqkavE5WjCKS2lMAAX3olOwqGuXty VZkJFDhWoQzL1EP9dqC4LloaY8QsEua+Iq1IdX2rIgG5WNb3irzkZVStfKt+euxe 1/RULzvLSUvejFjwBPsyWhZEDsmc9PGnGsNuh7T4yc0PJocQmkK/Hh+ubis3pXJK 4YdIjasuC/qopqZTtG6ROEV62eTM0SjAk6/KbvOtAE3TQI21r0SSePkOB7tIIW81 M3xfryzQUbonwwMLxi28CdFqAxM+gBbopFQ9BWakgjKQzwih+Z+dQr2kAnX/EzFG NijJbPYeFPbqSjC/QU5TpuYJMgnUFLh1bioIF4qGs8kHvAqa/uTkqzmlgUmNzjaZ PcYWNN9sUAEu8B/znAwkJV22es3ilSyZSv5oJXUGfaguDVMKixmpN116HNzSJujG m6dGHUSYd1aY+ouwSKTUPXhH3CoUFYB/TS0RkODwHwuIPb5i4DVYcKmQTNOHbo/q uCrnGkq42zvSjqsaZNUTxnrqTdCCEDPEmS760RHDrOFBTcQvLIRB9rWndJ8T9GuG 4eJ+PG4EuA2GcOOoCBns =jxUF -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#811364: wicd-gtk: status's icons -Status of wireless network- doesnt show in the interface of Wicd
Control: severity -1 normal
Control: retitle -1 wicd-gtk: pixmaps missing in package
Since the last upload, wicd-gtk unfortunately misses pixmaps
used in the application (systray icon, signal strength indicators, etc.)
See the debdiff below.
$ debdiff wicd-gtk_1.7.2.4-5_all.deb wicd-gtk_1.7.3-1_all.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in second .deb but not in first
-
-rw-r--r-- root/root /usr/share/icons/hicolor/192x192/apps/wicd-gtk.png
-rw-r--r-- root/root /usr/share/icons/hicolor/24x24/apps/wicd-gtk.png
-rw-r--r-- root/root /usr/share/icons/hicolor/36x36/apps/wicd-gtk.png
-rw-r--r-- root/root /usr/share/icons/hicolor/72x72/apps/wicd-gtk.png
Files in first .deb but not in second
-
-rw-r--r-- root/root /usr/share/pixmaps/wicd/bad-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/bad-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/both-bad-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/both-bad-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/both-good-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/both-good-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/both-high-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/both-high-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/both-low-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/both-low-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/good-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/good-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/high-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/high-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/idle-bad-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/idle-bad-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/idle-good-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/idle-good-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/idle-high-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/idle-high-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/idle-low-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/idle-low-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/low-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/low-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/no-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/receiving-bad-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/receiving-bad-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/receiving-good-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/receiving-good-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/receiving-high-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/receiving-high-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/receiving-low-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/receiving-low-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/signal-100.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/signal-25.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/signal-50.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/signal-75.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/transmitting-bad-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/transmitting-bad-signal.png
-rw-r--r-- root/root
/usr/share/pixmaps/wicd/transmitting-good-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/transmitting-good-signal.png
-rw-r--r-- root/root
/usr/share/pixmaps/wicd/transmitting-high-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/transmitting-high-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/transmitting-low-signal-lock.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/transmitting-low-signal.png
-rw-r--r-- root/root /usr/share/pixmaps/wicd/wired-gui.svg
-rw-r--r-- root/root /usr/share/pixmaps/wicd/wired.png
Control files: lines which differ (wdiff format)
Depends: [-python:any (>= 2.6.6-7~), python-gtk2,-] python-glade2,
{+python-gtk2,+} wicd-daemon (= [-1.7.2.4-5)-] {+1.7.3-1), python:any (>=
2.7.5-5~)+}
Homepage: [-http://wicd.sourceforge.net/-] {+https://launchpad.net/wicd+}
Installed-Size: [-475-] {+404+}
Version: [-1.7.2.4-5-] {+1.7.3-1+}
signature.asc
Description: Digital signature
Processed: Re: wicd-gtk: status's icons -Status of wireless network- doesnt show in the interface of Wicd
Processing control commands: > severity -1 normal Bug #811364 [wicd-gtk] wicd-gtk: status's icons -Status of wireless network- doesnt show in the interface of Wicd Severity set to 'normal' from 'minor' > retitle -1 wicd-gtk: pixmaps missing in package Bug #811364 [wicd-gtk] wicd-gtk: status's icons -Status of wireless network- doesnt show in the interface of Wicd Changed Bug title to 'wicd-gtk: pixmaps missing in package' from 'wicd-gtk: status's icons -Status of wireless network- doesnt show in the interface of Wicd' -- 811364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#811364: wicd-gtk: status's icons -Status of wireless network- doesnt show in the interface of Wicd
Hi Reiner, Reiner Herrmann wrote: > Since the last upload, wicd-gtk unfortunately misses pixmaps > used in the application (systray icon, signal strength indicators, etc.) Thanks for the analysis! Will have a look at why this is missing later this evening. 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
Processing of hashalot_0.3-8_source.changes
hashalot_0.3-8_source.changes uploaded successfully to localhost along with the files: hashalot_0.3-8.dsc hashalot_0.3-8.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)
hashalot_0.3-8_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 Jan 2016 13:30:46 -0200 Source: hashalot Binary: hashalot Architecture: source Version: 0.3-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Joao Eriberto Mota Filho Description: hashalot - Read and hash a passphrase Changes: hashalot (0.3-8) unstable; urgency=medium . * QA upload. * Set Debian QA Group as maintainer. (see #809257) * Migrations: - DebSrc to 3.0 format. - Using autoreconf now. * debian/control: - Added the Homepage field. - Removed the decimal part (zeroes) from debhelper in Build-Depends field. * debian/copyright: - Moved a license name from GPL to GPL-1. - Moved the initial comment put in GPL-1 text to a 'Comment' field. - Updated the full text of the GPL-2. - Updated and reorganized data about the upstream copyright. - Updated the copyright data about the packaging. * debian/lintian-overrides/: - Moved the debian/lintian-overrides/hashalot to debian/ and renamed to lintian-overrides. - Updated to use the current lintian message. * debian/patches/10_avoid_direct_changes.patch: created to avoid direct changes in upstream source code. * debian/rules: added the DEB_BUILD_MAINT_OPTIONS variable to improve the GCC hardening. * debian/watch: improved. Checksums-Sha1: 40991b0d7c19845d5bf905ec60a09ed3162d0cbc 1808 hashalot_0.3-8.dsc c59d5fb1f1cf9fa959e63404cfc75854463ac35e 5448 hashalot_0.3-8.debian.tar.xz Checksums-Sha256: 56ba8afd74982806ff4a4d516ce630df372b2e2d0244cc38909e916199ab0afa 1808 hashalot_0.3-8.dsc c9bafb4a56c9badcbab4c1836fb017ab6b221ef9d2a0b9fb4a3daf86166beb91 5448 hashalot_0.3-8.debian.tar.xz Files: c956a781044b28e9beb7169eb5224219 1808 utils optional hashalot_0.3-8.dsc 02bd32baf01856ccd39e77435496b86f 5448 utils optional hashalot_0.3-8.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJWnT8OAAoJEN5juccE6+nvbJQP/RHERIZ2UmS8ehL/ATf8dmMt hJHMUh+39GezY3tlbACFFKK4k/cCFbBQV44a1Rr6OdqR8ztsFSgolUNTm5qMNpDX i/NpNH4f6uSaIO5lR9Q4vZBYSvaCKTNGCeTP/Kh4l6tW+5n5ue+a+Tkmbp3Zcx0W 1CBcUqHx+OUj2LGHtJruHih9VJJBR1lI+UbPO7ydayyjF9svOSC9wXTxWto98GqR P9kTmnpxHDMPpbN6unzMHhv7MQCTENq+0lKPHjyDyGIFXzH7a8AuzQF6/V+my65c t4uyubNRn+Sb4LRBjsRHt2OwSie95ZhBJPoaj6SQApZ83qJKM3IqjzRJr/v+9qxv verSGbV3IZby2AuvgnEPid37Us0OU8GlAPkTLTFI+aePe1pY2K39ZsB+DrW02BgN uI75OzbhWKguxTyldODRj99PaB0y6W1enX7jEU1FKMQiDwFPKFPCq3UAYXYLYenY 0Dvi7qblyeN88P5wUivdcFdhisunbWLoXZhJLO9xJr15E1HyRdyf7Cs0PPkUcwBX +vGuPhj2fm7ufFSPtFyyvBF9hzpDzxt1yPKjwZn/04hdAoIwUKPhbkyTkZzjjiRL GEGfu6o52Y9uuusWE2y7gzpl0LOJpuRg8pg+TQ0a/GAVRc5ABetzv4o83UnYbprl 464pRVUnUrBsFsLidohN =Zzfz -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processed: tagging 811364
Processing commands for cont...@bugs.debian.org: > tags 811364 + pending Bug #811364 [wicd-gtk] wicd-gtk: pixmaps missing in package Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 811364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of wicd_1.7.3-2_i386.changes
wicd_1.7.3-2_i386.changes uploaded successfully to localhost along with the files: wicd_1.7.3-2.dsc wicd_1.7.3-2.debian.tar.xz python-wicd_1.7.3-2_all.deb wicd-cli_1.7.3-2_all.deb wicd-curses_1.7.3-2_all.deb wicd-daemon_1.7.3-2_all.deb wicd-gtk_1.7.3-2_all.deb wicd_1.7.3-2_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)
Bug#811364: marked as done (wicd-gtk: pixmaps missing in package)
Your message dated Mon, 18 Jan 2016 23:24:08 + with message-id and subject line Bug#811364: fixed in wicd 1.7.3-2 has caused the Debian Bug report #811364, regarding wicd-gtk: pixmaps missing in package 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.) -- 811364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wicd-gtk Version: 1.7.3-1 Severity: minor Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.3.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: systemd (via /run/systemd/system) Versions of packages wicd-gtk depends on: ii python-glade2 2.24.0-4 ii python-gtk22.24.0-4 pn python:any ii wicd-daemon1.7.3-1 Versions of packages wicd-gtk recommends: ii gksu 2.0.2-9 ii python-notify 0.1.1-4 wicd-gtk suggests no packages. Versions of packages wicd depends on: ii wicd-daemon 1.7.3-1 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-2+b4 ii python-gobject 3.18.2-2 ii python-wicd 1.7.3-1 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: * wicd/users: --- End Message --- --- Begin Message --- Source: wicd Source-Version: 1.7.3-2 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 811...@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: Mon, 18 Jan 2016 23:28:27 +0100 Source: wicd Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd Architecture: source all Version: 1.7.3-2 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: 811364 Changes: wicd (1.7.3-2) unstable; urgency=low . * QA upload * Add new /usr/share/wicd/icons/ directory to debian/wicd-gtk.install. Fixes regression with missing status icons in wicd-gtk. (Closes: #811364) Thanks to Reiner Herrmann for the right hint! Checksums-Sha1: c7c3ee93cb1eb4dd116280c692c208cf6776d607 2120 wicd_1.7.3-2.dsc fa1d4f29a68c6c8e4b386fd9577d75b10f09fbaa 24408 wicd_1.7.3-2.debian.tar.xz 0536905b51bde3ef004d6826329e0afccd7d3426 52262 python-wicd_1.7.3-2_all.deb 2d60d674ed42ebc28dfa58a1282dbe25a7e7bea5 25250 wicd-cli_1.7.3-2_all.deb 0c34b30e444bae99176c4b8931b24a3c69259464 49642 wicd-curses_1.7.3-2_all.deb dcd5fe7f4713385b55ae1d9647a876d3522ee554 159316 wicd-daemon_1.7.3-2_all.deb d0848ff74c641e8fe80ef5a60558dbfad2e0b372 15249
wicd_1.7.3-2_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Jan 2016 23:28:27 +0100 Source: wicd Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd Architecture: source all Version: 1.7.3-2 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: 811364 Changes: wicd (1.7.3-2) unstable; urgency=low . * QA upload * Add new /usr/share/wicd/icons/ directory to debian/wicd-gtk.install. Fixes regression with missing status icons in wicd-gtk. (Closes: #811364) Thanks to Reiner Herrmann for the right hint! Checksums-Sha1: c7c3ee93cb1eb4dd116280c692c208cf6776d607 2120 wicd_1.7.3-2.dsc fa1d4f29a68c6c8e4b386fd9577d75b10f09fbaa 24408 wicd_1.7.3-2.debian.tar.xz 0536905b51bde3ef004d6826329e0afccd7d3426 52262 python-wicd_1.7.3-2_all.deb 2d60d674ed42ebc28dfa58a1282dbe25a7e7bea5 25250 wicd-cli_1.7.3-2_all.deb 0c34b30e444bae99176c4b8931b24a3c69259464 49642 wicd-curses_1.7.3-2_all.deb dcd5fe7f4713385b55ae1d9647a876d3522ee554 159316 wicd-daemon_1.7.3-2_all.deb d0848ff74c641e8fe80ef5a60558dbfad2e0b372 152498 wicd-gtk_1.7.3-2_all.deb 9778a81e1788bf41c809f3ff65c157621b7b7a53 21608 wicd_1.7.3-2_all.deb Checksums-Sha256: 55f5749e8b177f9e3d504317c5cbe201273a415cf62f84506ff5a5cbf7b7e520 2120 wicd_1.7.3-2.dsc 1983fd350ecb7cb2d09b579bfc3d7ca9f4fd7f867f32d890b2086a6070045b47 24408 wicd_1.7.3-2.debian.tar.xz daac8164882e48be6b3b7129221309adcafcfa6d8711c61e86fc72b1bd9e3813 52262 python-wicd_1.7.3-2_all.deb ed827169aa153f5ee7f4a5ab7d1bac9ec16e50800e39b967fe66c8abb7adf74c 25250 wicd-cli_1.7.3-2_all.deb 27a128ddacf8e70f1914ff073575d532152b003676cd0f103d0dc5140eff4d5b 49642 wicd-curses_1.7.3-2_all.deb 7734552e0f8cff09c6774d82414f8387f2905025174ab125e4a9cc4c4f87f42f 159316 wicd-daemon_1.7.3-2_all.deb 7cf9482b731765426f71724a65cc105482f92e85a5ff0fc2866062ee743be07b 152498 wicd-gtk_1.7.3-2_all.deb 1d352190abc8b4fa55e59f3672af7cd59cc872b5057228b4f501acece5bbbdc0 21608 wicd_1.7.3-2_all.deb Files: 6759e933daee2ed80b105ee656e83f05 2120 net optional wicd_1.7.3-2.dsc a2bd881bc102810e1a0a05a2002fb12f 24408 net optional wicd_1.7.3-2.debian.tar.xz e5e7f9670281861d88b3dc9c72e9ce11 52262 python optional python-wicd_1.7.3-2_all.deb 06ca5375b5ef97ef434a5fca57d12b30 25250 net optional wicd-cli_1.7.3-2_all.deb 448e030a57aca0a72780e5ad28e3e665 49642 net optional wicd-curses_1.7.3-2_all.deb 4c76d816f54cb4b3baaeebf80109f2fe 159316 net optional wicd-daemon_1.7.3-2_all.deb 59df70b52fa1ec3b2172db322112810f 152498 net optional wicd-gtk_1.7.3-2_all.deb ac68a38f3cba4f4326a664616590be13 21608 net optional wicd_1.7.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWnW4zAAoJEGvmY8daNcl1DEYP/AtKf2/62I4wNfGPbtOoHrVD KHNXmIXik/eRBZrXf8VcyEQePOs6IHXcJOVlOa7WyIMDvqjB1vGdDucM4neeN4lR KzHrlUgYmlKD3kTV4o69dwcQ8Vu+Ypcic8O3SLHJVOh3o6jvaXS0tTfqs5wDudSq 9L2OvXRvm9w8SxMwpW+4SFMi/U8wEdzmdjcX7ZModBF+qyDoYUgijJHh26JhhCHx u4YCCODmy7WbpR7Xik3EFySJdvR5h2x09dQ7FwRQrYqIRqDh/M0VADxdU++cLygI Cxfyc4Ydbcypdfa+RHp6U6/3fnkRrAIpTdClrqMFxzZ4Vl8hI/ac6bdNuELQS7+7 pWT/lSCv+RbDANxCzO3WHwnjW8vhPN4Bz5haUnL9DF8HYPpB+/ZxTS8Peu/zrmbU tDU2LOoDOD9/R3eC8sIhJlLhy1OeahylaCK+vCohneh81qgVmQOPl6pk8XDoeZPG c/6SKn0w4XFjaxltGmUfimIb2G4WLK+BhiqJ3rxTK1zSdsiQBg413Q3t+pWUxhX+ jDaBnMXYiKfYhnVogxc+qqQ2XyI2ckjeanF1ietSjqvY7+2dPSWNny9297L9lqzG qCsF3S8jobkyqTForsexgTl2jpEbN8geLzXxmGB2ZtZ5k8bIM81b2pQBsx2sNY9s eTu91/4iZY7CZdLREAIE =xi5d -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of ifrit_4.1.2-2_source.changes
ifrit_4.1.2-2_source.changes uploaded successfully to localhost along with the files: ifrit_4.1.2-2.dsc ifrit_4.1.2-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)
ifrit_4.1.2-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 17 Jan 2016 16:17:19 +0100 Source: ifrit Binary: ifrit Architecture: source Version: 4.1.2-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski Description: ifrit - powerful tool for visualizing 3-dimensional data sets Changes: ifrit (4.1.2-2) unstable; urgency=medium . * QA upload. * Drop hardcoded dependency on tcl-vtk. Checksums-Sha1: 64dd4bc3639b962413e96b9416fb1ef6350d 1552 ifrit_4.1.2-2.dsc d4640ab075e759e2e24b2d414ce5b99ef19835fc 6000 ifrit_4.1.2-2.debian.tar.xz Checksums-Sha256: 30afc6cd80bd76b74813a5145a1e5da4b2b0e79a5686da72839255a1a8b137f4 1552 ifrit_4.1.2-2.dsc ff40ce446aee4a6333dca8469254d80f3a3b7428928d203ab032789e50e76c4d 6000 ifrit_4.1.2-2.debian.tar.xz Files: ffca65f3b3955ca344596418fe1720c2 1552 science optional ifrit_4.1.2-2.dsc 740cd403d0b534a0054f53eae15ba638 6000 science optional ifrit_4.1.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJWm7CiAAoJECw7Q2/qxoEBxsUIAJiRsQ/ogAXK9yqPdWtmUmwt objvwBh8SvQbt521ohuRKVGu/ewuiLFPP0pCLIai1MpcmxtCVFl3KcPbq/fE2GA1 b0lmR9sYHwvB9DNsqUo2MQTtBBwtAiXNTJvOUKDdCRaPdA1eS58ASfA9NDMDHeau ba1Czh8uYeqRt0RsmG9GpegzONDs5y8bpG5GP99dIiRDywIH0kMG8CtDCXDmpawE 8D2LbwDyhdApz6rr84sLU05sq8L9myPAyFjfKqpu0ghL04sTfA1I3T242mVvUDwF jBCl1TBPXyy9fQ2FUXmPuz4foIgBOQpvvNAqhp5d/yLPk6okJ1c9SbUX8JxoTdI= =Ul55 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of acheck-rules_0.3.2_source.changes
acheck-rules_0.3.2_source.changes uploaded successfully to localhost along with the files: acheck-rules_0.3.2.dsc acheck-rules_0.3.2.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)
acheck-rules_0.3.2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 Jan 2016 23:26:29 -0200 Source: acheck-rules Binary: acheck-rules Architecture: source Version: 0.3.2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Joao Eriberto Mota Filho Description: acheck-rules - Basic rules for acheck Closes: 530336 692859 723775 800296 Changes: acheck-rules (0.3.2) unstable; urgency=medium . * QA upload. * Set Debian QA Group as maintainer. (see #710152) * Ack to NMU by Bill Allombert. (Closes: #530336, #692859, #723775) * Migrations: - debian/rules to new (reduced) format. - DebSrc to 3.0 format. - DH level to 9. (Closes: #800296) * debian/clean: added to remove some files from upstream place before build. * debian/control: - Bumped Standards-Version to 3.9.6. - Improved the long description. * debian/install: added to install some files. * debian/manpages: added to install the manpages. Checksums-Sha1: a97c049a96b010096bc360d46f67cc26afe5c8bc 1410 acheck-rules_0.3.2.dsc 2b919f7fd3fe93bd83197662f6ca2decacebd2b9 8552 acheck-rules_0.3.2.tar.xz Checksums-Sha256: 9a81aa347b5644a0a32324c880b716b3cc0d2ccb5ee58776f7547f0b4cd13675 1410 acheck-rules_0.3.2.dsc 522270bd832c7018bde28424b6b5390ce00477123b361e6b2a2618e318828b58 8552 acheck-rules_0.3.2.tar.xz Files: 069efe3392426937a13fa2fa15b32538 1410 text optional acheck-rules_0.3.2.dsc b212cec66c2cdfa3b204164907428636 8552 text optional acheck-rules_0.3.2.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJWnZtXAAoJEN5juccE6+nvTrEQAJnoInF++BOeATbRt+kr44vi 3QZ9AfyDdG/2vxjqzmWQbt86eaG/EMUfxCjiM65YeLN97NRTBSMvEmdTGHnLTxDy i2lzCz7qmz5tRaiEdt+EvEpt8wV+qeAF0W4q1XOVWQNWzPhUui+j/kzhfWdOpw+6 wyxLJtX6ltUL7tp90+aL/c7UWACl5w4U2DlrKaTi6Y7BGfdToW8bJbH5O5f0ll6t 2U+UF1hlFBOQZOnGkr8opHTEttzNJmDVBdvgu5iRJ4yKy/z22FLMDNNrhVHPxtbw yl3VAQamhaZjjgb2PG2u7e4BgQi2P6q9RBlMxL3Bqurl0txYv1LRmaMNYY07aD04 2eL0IJWc98w2V3U80CCmvHEvG/NfZS7tnN3yGMVruiysO0zDsk2MP5qMuAQgPqqf zxzUd0t/EOnrvd4Dtsqhp0/hfoB7VeiPXaAjNoqNNxOyJBcPA6vmhVHbS1ZzAGYJ 8ZQ6jsqMPIK6hvA5cMhDbD4yMVfQchRxjO3ESVSNGR1GVLGDln++PEdHe8COO80S R++w19n4tEKLioP8U2/zO7ezABQwgHi361LdLsxnY9+nYx6Pj2Xrmryq5jsbu7Lf 8DOmp53vPJJj07p0J3HGbUTiiTsZ9TSEpGBgdBpLvJjxtl4ur2c60EIfGzPXTO0f chugyXhM2R6qLGq/+VRd =qFqH -END PGP SIGNATURE- Thank you for your contribution to Debian.
pyro is marked for autoremoval from testing
pyro 1:3.14-4 is marked for autoremoval from testing on 2016-02-02 It is affected by these RC bugs: 790352: pyro: remove version 3 in stretch?
dpkg-www is marked for autoremoval from testing
dpkg-www 2.56 is marked for autoremoval from testing on 2016-02-18
It (build-)depends on packages with these RC bugs:
790273: publib: FTBFS with glibc 2.21 and gcc-5
807349: publib: dwww: FTBFS: error: expected identifier or '(' before
'__extension__'
