Bug#794488: Re: Bug#794488: Piglit tests in Mesa crash, if radeonsi_dri.so is linked with libelf1 (libelfg0 works)
On Thu, Aug 06, 2015 at 05:14:25PM +0200, Kai Wasserbäch wrote:
Could you compile the following with:
gcc -g -lelf -o elfrel elfrel.c
this does not work for several reasons:
1. I certainly need -std=c99 for the inline initialisation of the
counter in the for() statement.
Ah, yes, this system has gcc 5.1 which defaults to gnu11.
2. *section (first used in »gelf_getshdr(section, section_header)«) isn't
defined/filled anywhere:
[...]
Long story short: did you paste the entire/correct code?
Drat, so sorry. I must have copy/pasted an earlier version, that didn't
even compile. Attached is a version I double checked, that includes one
extra check (the size of the .text section). It gives the following output
for me:
$ for i in 794488_elfs/libelf*/*; do ./elfrel $i; done
file: 794488_elfs/libelf1/dump.elf.EL5kJT
.text code size: 24
Nothing found
file: 794488_elfs/libelf1/dump.elf.J4EnbO
.text code size: 11c
symbols: 5
1: not global or undefined
2: not global or undefined
3: not global or undefined
4: not global or undefined
5: 0
relocations: 2
0: 10, SCRATCH_RSRC_DWORD1
1: 2c, SCRATCH_RSRC_DWORD0
file: 794488_elfs/libelfg0/dump.elf.7NnBvc
.text code size: 24
Nothing found
file: 794488_elfs/libelfg0/dump.elf.ahPsJJ
.text code size: 11c
symbols: 5
1: not global or undefined
2: not global or undefined
3: not global or undefined
4: not global or undefined
5: 0
relocations: 2
0: 10, SCRATCH_RSRC_DWORD1
1: 2c, SCRATCH_RSRC_DWORD0
file: 794488_elfs/libelfg0/dump.elf.DYTjdO
.text code size: 28
Nothing found
file: 794488_elfs/libelfg0/dump.elf.Lke6Xg
.text code size: 38
Nothing found
Could you run it against old/new libelf to see if anything is different.
If not, then I am looking for the bug in the wrong place.
Thanks,
Mark
#include gelf.h
#include stdio.h
#include string.h
#include inttypes.h
#include sys/types.h
#include sys/stat.h
#include fcntl.h
int
main (int argc, char **argv)
{
elf_version(EV_CURRENT);
printf (file: %s\n, argv[1]);
int fd = open (argv[1], O_RDONLY);
Elf *elf = elf_begin (fd, ELF_C_READ, NULL);
size_t section_str_index;
elf_getshdrstrndx(elf, section_str_index);
size_t reloc_count, symbol_sh_link, symbol_count;
Elf_Data *relocs, *symbols;
Elf_Scn *section = NULL;
while ((section = elf_nextscn(elf, section)))
{
const char *name;
GElf_Shdr section_header;
if (gelf_getshdr(section, section_header) != section_header)
{
fprintf(stderr, Failed to read ELF section header\n);
return -1;
}
name = elf_strptr(elf, section_str_index, section_header.sh_name);
if (strncmp(name, .symtab, 7) == 0)
{
symbols = elf_getdata(section, NULL);
symbol_sh_link = section_header.sh_link;
symbol_count = section_header.sh_size / section_header.sh_entsize;
}
else if (strcmp (name, .rel.text) == 0)
{
relocs = elf_getdata(section, NULL);
reloc_count = section_header.sh_size / section_header.sh_entsize;
}
else if (strcmp (name, .text) == 0)
{
Elf_Data *section_data = elf_getdata(section, NULL);
printf (.text code size: %zx\n, section_data-d_size);
}
}
if (!relocs || !symbols || !reloc_count)
{
printf(Nothing found\n);
return -1;
}
printf (symbols: %zd\n, symbol_count);
GElf_Sym symbol;
size_t i = 0;
while (gelf_getsym (symbols, i++, symbol))
{
if (GELF_ST_BIND(symbol.st_info) != STB_GLOBAL
|| symbol.st_shndx == 0)
{
printf (%zd: not global or undefined\n, i);
continue;
}
printf (%zd: % PRIx64 \n, i, symbol.st_value);
}
printf (relocations: %zd\n, reloc_count);
for (size_t i = 0; i reloc_count; i++)
{
GElf_Sym symbol;
GElf_Rel rel;
char *symbol_name;
gelf_getrel(relocs, i, rel);
gelf_getsym(symbols, GELF_R_SYM(rel.r_info), symbol);
symbol_name = elf_strptr(elf, symbol_sh_link, symbol.st_name);
printf (%zd: % PRIx64 , %s\n, i, rel.r_offset, symbol_name);
}
return 0;
}
Bug#794774: libstdc++6: Breaks: libboost-date-time1.55.0, but isn't that package fixed now?
On Sat, 2015-08-08 at 00:35 +0200, Matthias Klose wrote: this is unfortunate, however there never was and is any commitment of unstable getting security fixes. Sure, however reality is probably, that many people actually run unstable as their stable systems - I woudln't be surprised if this is also done by many DDs and if all of them are right now exposed to quite a number of critical security issues (e.g. the recent Firefox hole) we have a real problem, commitment or not :-( The issue is not fixed by any upload of boost1.55 built with GCC 4.9, and it won't build with GCC 5. An update to 1.57 or 1.58 is required. And it can't be fixed to build with v5? :-( Thanks, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#794911: bind9: bind9 update does not work, impossible to install
Package: bind9-host Version: 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 Severity: serious File: bind9 Tags: security Justification: fails to build from source (but built successfully in the past) Dear Maintainer, *** 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 lines *** -- System Information: Debian Release: 7.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: powerpc (ppc) Kernel: Linux 3.2.0-4-powerpc-smp (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bind9-host depends on: ii libbind9-80 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 ii libc6 2.13-38+deb7u8 ii libcap2 1:2.22-1.2 ii libdns88 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u3 ii libisc84 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 ii libisccfg82 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 ii liblwres801:9.8.4.dfsg.P1-6+nmu2+deb7u4 ii libssl1.0.0 1.0.1e-2+deb7u17 ii libxml2 2.8.0+dfsg1-7+wheezy4 bind9-host recommends no packages. bind9-host suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794234: developers-reference: quinn-diff is gone
Le Fri, Jul 31, 2015 at 03:42:26PM +0200, Jakub Wilk a écrit : Package: developers-reference Version: 3.4.15 §A.7.1 mentions the quinn-diff package, but this package was removed from the archive in 2011. Reference: bug #618820 Hi Jakub and everybody, I think that the mention of quinn-diff can be removed from the Developer's Reference. This can be done in two ways. - Remove §A.7.1 on quinn-diff. Then obviously §A.7.2 on dpkg-cross will become the new §A.7.1. - Replace §A.7.1 by a placeholder, such as: The systemitem role=packagequinn-diff/systemitem package was removed from Debian in 2011. This section is kept as a placeholder to prevent renumbering of the next section./para What do you think about this ? By the way, I could not find anymore the latest email describing who can commit what for the Developer's Reference. Can somebody refresh my memory ? Have a nice week-end, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794913: libphonenumber6: please use libboost-date-time 1.57 or 1.58 ASAP
Subject: libphonenumber6: please use libboost-date-time 1.57 or 1.58 ASAP Package: libphonenumber6 Version: 0.5.0-2 Severity: important Hi. libphonenumber6, depended upon by whole evolution, depends on libboost-date-time1.55.0 which itself is not compatible with the new libstdc++6 from GCC5. Apparently this won't be reseloved (see #793222 or #794774). That blocks upgrading to to current libstdc++6 (without removing a large number of packages) and thus also prevents other packages (that already depend on newer libstdc++6) with important security updates to be installed. Cheers, Chris smime.p7s Description: S/MIME cryptographic signature
Bug#794237: openconnect: Does not work with network-manager 1.0.4
Control: reassign -1 network-manager 1.0.4-1 Control: retitle -1 network-manager: sets VPN tunnel MTU incorrectly On Fri, Aug 07, 2015 at 22:31:44 +0300, Matti Koskimies wrote: On Fri, 2015-08-07 at 09:19 -0400, Mike Miller wrote: On Fri, Aug 7, 2015 at 13:53:49 +0100, David Woodhouse wrote: I blame NM. Fair enough. Matt already said that reverting to NM 1.0.2 was enough to restore his connection, but that was while running openconnect standalone. Matt, can you verify that going back to NM 1.0.2 and connecting to the VPN via NM now sets the proper MTU on tun0 and your connection works again? I can verify that going back to NM 1.0.2 and connecting to VPN via NM sets the proper MTU on vpn0 and my connection works. Ok, thanks, regression seems to be squarely on NM, reassigning again. -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794912: libcmis-0.5-5: please use libboost-date-time 1.57 or 1.58 ASAP
Package: libcmis-0.5-5 Version: 0.5.0-2 Severity: important Hi. libcmis-0.5-5, depended upon by whole libreoffice, depends on libboost-date-time1.55.0 which itself is not compatible with the new libstdc++6 from GCC5. Apparently this won't be reseloved (see #793222 or #794774). That blocks upgrading to to current libstdc++6 (without removing a large number of packages) and thus also prevents other packages (that already depend on newer libstdc++6) with important security updates to be installed. Cheers, Chris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794525: libnm-glib-vpn1: network-manager upgrade to 1.0.4-1 broke my OpenConnect VPN
On Tue, Aug 04, 2015 at 11:55:51 +0900, Michel Dänzer wrote: After upgrading network-manager packages from 1.0.2-2 to 1.0.4-1, my OpenConnect VPN connection stopped working reliably. Most TCP connections over the VPN hang and eventually fail with connection reset. Downgrading network-manager packages to 1.0.2-2 again works around the problem. I tried rebuilding network-manager-openconnect against network-manager 1.0.4-1, but it didn't help. Can you take a look at #794237, it sounds like you may be hitting the same regression. -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794914: libreoffice-core: please use libboost-date-time 1.57 or 1.58 ASAP
Subject: libreoffice-core: please use libboost-date-time 1.57 or 1.58 ASAP Package: libreoffice-core Version: 1:4.4.5-2 Severity: important Hi. libreoffice-core, depended upon by whole libreoffice, depends on libboost-date-time1.55.0 which itself is not compatible with the new libstdc++6 from GCC5. Apparently this won't be reseloved (see #793222 or #794774). That blocks upgrading to to current libstdc++6 (without removing a large number of packages) and thus also prevents other packages (that already depend on newer libstdc++6) with important security updates to be installed. Cheers, Chris smime.p7s Description: S/MIME cryptographic signature
Bug#794830: [Aptitude-devel] Bug#794830: aptitude: segfaults in memory allocation
Hi, Manuel A. Fernandez Montecelo wrote: 2015-08-07 14:11 GMT+01:00 Axel Beckert a...@debian.org: Matthijs van Duin wrote: I just noticed aptitude and libcwidget3v5 still depend on libsigc++-2.0-0c2a, shouldn't that be libsigc++-2.0-0v5 now? A cool, that has been fixed now, too! Yep, there is a libsigc++-2.0 transition upcoming: https://release.debian.org/transitions/html/auto-libsigc++-2.0.html Is this still a problem after being rebuilt after both cwidget and aptitude being rebuilt and depend on libsigc++-2.0-0v5? Nope. No more segfaults in my sid chroot (with incoming.debian.org's apt repo added, too). Yay! Matthijs: I'd close this bug with 0.7-1+b1 if you confirm. Matthias: Thanks for help and the BinNMUs for the libsigc++-2.0 transition. (I assume you triggered/ordered them.) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794862: [Aptitude-devel] Bug#794862: crashes randomly in libcwidget.so.3
Hi Yuri, Yuri D'Elia wrote: On 07/08/15 13:06, Axel Beckert wrote: Control: Yuri D'Elia wrote: After the update to 0.7-1, aptitude is very unstable. I can get segmentations faults just by moving the cursor around. That's either a duplicate of #794705 or #794830. Please choose. ;-) Though choice ;) In most of the crashes, the backtrace seems to be either in cwidget or in sigc, which is probably a signal that one of the two needs a rebuild due to the new ABI (I've just seen #794705 but nothing in libsigc++ yet). Yep, we're already discussing if #794705 should be reassigned to ligsigc++-2.0 (libsigc++ is no more in Debian for quite a while). The libsigc++2.0 transition also looks quite funny ;) The part which is relevant for aptitude is now done. Considering I've had to --force-depends a few packages to move my system through in the last two days or so.. [in that sense, I'd love aptitude to allow to proceed with --force-all if given 'g' enough times - it's a rare need, but heck, I do what I want(tm)]. Is your problem still present after both cwidget and aptitude being rebuilt and depend on libsigc++-2.0-0v5? Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794235: developers-reference: debian-maintainers is gone
Le Fri, Jul 31, 2015 at 03:42:39PM +0200, Jakub Wilk a écrit : Package: developers-reference Version: 3.4.15 §A.8.4 mentions the debian-maintainers package, but this package was removed from the archive in 2010. Hi all, how about the following, or a simpler version where the debian-maintainers section is completely removed ? I also removed mention of PGP since in my understanding the Debian keyring does not contain anymore old PGP keys. diff --git a/tools.dbk b/tools.dbk index ba8a846..59c1e5f 100644 --- a/tools.dbk +++ b/tools.dbk @@ -498,15 +498,17 @@ role=packagedebiandoc-sgml-doc/systemitem package. section id=debian-keyring titlesystemitem role=packagedebian-keyring/systemitem/title para -Contains the public GPG and PGP keys of Debian developers. See xref -linkend=key-maint/ and the package documentation for more information. +Contains the public GPG keys of Debian Developers and Maintainers. +See xref linkend=key-maint/ and the package documentation for more +information. /para /section section id=debian-maintainers titlesystemitem role=packagedebian-maintainers/systemitem/title para -Contains the public GPG keys of Debian Maintainers. +The public GPG keys of Debian Maintainers are now distributed in the +systemitem role=packagedebian-keyring/systemitem package. See ulink url=url-wiki-dm;/ulink for more information. /para /section Cheers, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794915: RFS: compute/0.4-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package compute * Package name: compute Version : 0.4-1 Upstream Author : Kyle Lutz kyle.r.l...@gmail.com * URL : https://github.com/boostorg/compute * License : Boost Software License 1.0 Section : science It builds those binary packages: libcompute-dev - cross-platform C++ library for GPU computing To access further information about this package, please visit the following URL: http://mentors.debian.net/package/compute Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/compute/compute_0.4-1.dsc Changes since the last upload: * Initial release. (Closes: #794649) Best regards, Ghislain Vaillant -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794236: developers-reference: debview is now part of debian-el
Le Fri, Jul 31, 2015 at 03:43:25PM +0200, Jakub Wilk a écrit : Package: developers-reference Version: 3.4.15 §A.8.5 mentions the debview package, but this package was removed from the archive in 2003. The debview code has been integrated into the debian-el package. Reference: bug #214311 Hi again, how about just replacing all occurences of debview by debian-el ? This would break URLs referencing to the current section ID (debview), but I believe that they should be very rare. Moreover, it only breaks the anchor, so this would not cause a HTTP error. On the other hand, debian-el has little relevance to the section on which it is presented (Documentation and information - The following packages provide information for maintainers or help with building documentation). Maybe it can be moved or removed ? Cheers, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794916: aptitude is uninstallable
Package: aptitude Version: 0.7-1 Severity: grave Justification: renders package unusable Hi. Aptitude 0.7-1 depends upon: libcwidget3v5 and libsigc++-2.0-0c2a (= 2.2.0) (amongst others): The former, however, depends on libsigc++-2.0-0v5 (= 2.2.0) which in turn conflicts libsigc++-2.0-0c2a, which aptitude depends upon. Thus installation of aptitude is impossible. Cheers, Chris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794830: [Aptitude-devel] Bug#794830: aptitude: segfaults in memory allocation
On 8 August 2015 at 01:18, Axel Beckert a...@debian.org wrote: Matthijs: I'd close this bug with 0.7-1+b1 if you confirm. The crashes are gone indeed. The... cosmetic... issue I mailed you about is still present. Should I file a new bug report on that? I'm still not quite sure how to phase it... (Another small detail that's not visible in the animated gif I sent you is that the grey blocks also have blinking black underlines) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794774: libstdc++6: Breaks: libboost-date-time1.55.0, but isn't that package fixed now?
Further searching has indeed suggested that boost 1.55 is still broken and will remain so (e.g. the bug #793222 discussion), and thus I can see that 1.57/1.58 is needed as you say. In fact 1.58 is available and it's actually just a couple of libreoffice dependencies specifically targeting 1.55 that are causing the hold up in upgrade installation currently (at least here on my systems). It is indeed unfortunate that packages for the gcc5 transition were pushed to unstable before libreoffice was made ready for it, and worse that this has resulted in security implications for Sid users. I must request that those responsible please tread more carefully in future (no disrespect intended, and do I really appreciate the free time and effort put into these projects). While there may sadly be no specific commitment for keeping unstable secure, it has been my impression that the record for pushing security fixes there is pretty strong. I am sure that many Debian users run Sid in order to have a much more up to date collection of application packages than you get from stable (testing does not seem suitable for normal use, since security updates are frequently delayed due to unstable-testing transitions). It would be very much appreciated if devs/maintainers would please keep this in mind in order to not cause problems like this for such users. On Sat, 2015-08-08 at 00:35 +0200, Matthias Klose wrote: Control: severity -1 important On 08/07/2015 09:11 PM, jnqnfe wrote: Control: severity -1 critical Control: tag -1 + security This dependency issue is now blocking installation of security updates on Sid (which many people use instead of stable, whether they should or not), specifically the emergency patch to iceweasel (CVE-2015-4495) in version 38.1.1esr-1. this is unfortunate, however there never was and is any commitment of unstable getting security fixes. The issue is not fixed by any upload of boost1.55 built with GCC 4.9, and it won't build with GCC 5. An update to 1.57 or 1.58 is required. If you need to have such an update in testing, then you should ask for an upload to testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794830: [Aptitude-devel] Bug#794830: Bug#794830: aptitude: segfaults in memory allocation
Hi Matthijs, Matthijs van Duin wrote: On 8 August 2015 at 01:18, Axel Beckert a...@debian.org wrote: Matthijs: I'd close this bug with 0.7-1+b1 if you confirm. The crashes are gone indeed. Yay! The... cosmetic... issue I mailed you about is still present. Should I file a new bug report on that? Yes, please. Please also include in which kind of terminal emulator you run aptitude as I can reproduce this with pbuilder login running inside an uxterm. You can also refer to my copy at https://people.debian.org/~abe/aptitude.gif if it still looks the same. (Another small detail that's not visible in the animated gif I sent you is that the grey blocks also have blinking black underlines) Hrm. If you want to make a new animgif, you can also attach it to the bug report instead of hosting it at your site. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794906: uhd 3.8 ftbfs on arm64, 3.7 built fine before on arm64
Package: uhd
Version: 3.8.5-1
Followup-For: Bug #794906
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch
In Ubuntu, the attached patch was applied to achieve the following:
* 0099-revert-neon-changes.patch: Revert the NEON changes from upstream
commit 1b149f561370687ad65e3aa644a402f00dbd16ea to fix build on arm64.
This is obviously not the ideal solution, one should probably fix the
NEON bits to work for both ARM architectures, but this revert doesn't
change any public symbols and seems to work on armhf and arm64, so it
was the path of least resistance while we're pushing through the g++5
transition.
... Adam
-- System Information:
Debian Release: jessie/sid
APT prefers wily-updates
APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.1.0-3-generic (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: systemd (via /run/systemd/system)
diff -Nru uhd-3.8.5/debian/patches/0099-revert-neon-changes.patch uhd-3.8.5/debian/patches/0099-revert-neon-changes.patch
--- uhd-3.8.5/debian/patches/0099-revert-neon-changes.patch 1969-12-31 17:00:00.0 -0700
+++ uhd-3.8.5/debian/patches/0099-revert-neon-changes.patch 2015-08-07 16:38:09.0 -0600
@@ -0,0 +1,113 @@
+Description: Revert the NEON changes from upstream commit
+ 1b149f561370687ad65e3aa644a402f00dbd16ea to fix arm64.
+Author: Adam Conrad adcon...@ubuntu.com
+Bug-Debian: https://bugs.debian.org/794906
+
+--- uhd-3.8.5.orig/host/lib/convert/CMakeLists.txt
uhd-3.8.5/host/lib/convert/CMakeLists.txt
+@@ -95,11 +95,8 @@ IF(CMAKE_COMPILER_IS_GNUCXX)
+ ENDIF(CMAKE_COMPILER_IS_GNUCXX)
+
+ IF(HAVE_ARM_NEON_H)
+-ENABLE_LANGUAGE(ASM)
+-
+ LIBUHD_APPEND_SOURCES(
+ ${CMAKE_CURRENT_SOURCE_DIR}/convert_with_neon.cpp
+-${CMAKE_CURRENT_SOURCE_DIR}/convert_neon.S
+ )
+ ENDIF()
+
+--- uhd-3.8.5.orig/host/lib/convert/convert_neon.S
/dev/null
+@@ -1,37 +0,0 @@
+-//
+-// Copyright 2014 Ettus Research LLC
+-//
+-// This program is free software: you can redistribute it and/or modify
+-// it under the terms of the GNU General Public License as published by
+-// the Free Software Foundation, either version 3 of the License, or
+-// (at your option) any later version.
+-//
+-// This program is distributed in the hope that it will be useful,
+-// but WITHOUT ANY WARRANTY; without even the implied warranty of
+-// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+-// GNU General Public License for more details.
+-//
+-// You should have received a copy of the GNU General Public License
+-// along with this program. If not, see http://www.gnu.org/licenses/.
+-//
+-
+- .arch armv7-a
+- .fpu neon
+- .syntax unified
+- .text
+- .align 2
+- .global neon_item32_sc16_swap_16n
+- .type neon_item32_sc16_swap_16n, %function
+-neon_item32_sc16_swap_16n:
+-.loop_swap:
+- vld2.16 {q0, q1}, [r0]!
+- vld2.16 {q2, q3}, [r0]!
+- vswp q0, q1
+- vswp q2, q3
+- vst2.16 {q0, q1}, [r1]!
+- vst2.16 {q2, q3}, [r1]!
+- subs r2, #1
+- bne .loop_swap
+- bx lr
+- .size neon_item32_sc16_swap_16n, .-neon_item32_sc16_swap_16n
+- .section .note.GNU-stack,,%progbits
+--- uhd-3.8.5.orig/host/lib/convert/convert_with_neon.cpp
uhd-3.8.5/host/lib/convert/convert_with_neon.cpp
+@@ -1,5 +1,5 @@
+ //
+-// Copyright 2011-2014 Ettus Research LLC
++// Copyright 2011-2012 Ettus Research LLC
+ //
+ // This program is free software: you can redistribute it and/or modify
+ // it under the terms of the GNU General Public License as published by
+@@ -19,12 +19,6 @@
+ #include uhd/utils/byteswap.hpp
+ #include arm_neon.h
+
+-extern C {
+-void neon_item32_sc16_swap_16n(void *, void *, int iter);
+-}
+-
+-static const int SIMD_WIDTH = 16;
+-
+ using namespace uhd::convert;
+
+ DECLARE_CONVERTER(fc32, 1, sc16_item32_le, 1, PRIORITY_SIMD){
+@@ -64,31 +58,3 @@ DECLARE_CONVERTER(sc16_item32_le, 1, fc3
+
+ item32_sc16_to_xxuhd::htowx(input+i, output+i, nsamps-i, scale_factor);
+ }
+-
+-DECLARE_CONVERTER(sc16, 1, sc16_item32_le, 1, PRIORITY_SIMD){
+-const sc16_t *input = reinterpret_castconst sc16_t *(inputs[0]);
+-item32_t *output = reinterpret_castitem32_t *(outputs[0]);
+-
+-size_t i = nsamps / SIMD_WIDTH;
+-
+-if (i)
+-neon_item32_sc16_swap_16n((void *) input, (void *) output, i);
+-
+-i *= SIMD_WIDTH;
+-
+-xx_to_item32_sc16uhd::htowx(input+i, output+i, nsamps-i, scale_factor);
+-}
+-
+-DECLARE_CONVERTER(sc16_item32_le, 1, sc16, 1, PRIORITY_SIMD){
+-const item32_t *input = reinterpret_castconst item32_t *(inputs[0]);
+-sc16_t *output = reinterpret_castsc16_t *(outputs[0]);
+-
+-size_t i = nsamps / SIMD_WIDTH;
+-
+-if (i)
+-neon_item32_sc16_swap_16n((void *) input, (void *) output, i);
+-
+-i *= SIMD_WIDTH;
+-
+-
Bug#794916: [Aptitude-devel] Bug#794916: aptitude is uninstallable
On Sat, 2015-08-08 at 02:06 +0200, Axel Beckert wrote: You are aware that Debian Unstable is in the midst of a huge transition (libstdc++6) with many followup transitions and that temporary uninstallabilities are very normal during such transitions? Sure... I just wasn't sure whether this may have happened accidentally (and thus unnoted), as you already switched to libcwidget3v5 but not to libsigc++ v5 version :-) Best wishes, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#794774: libstdc++6: Breaks: libboost-date-time1.55.0, but isn't that package fixed now?
On Sat, 2015-08-08 at 01:01 +0100, jnqnfe wrote: it's actually just a couple of libreoffice dependencies specifically targeting 1.55 that are causing the hold up in upgrade installation currently (at least here on my systems). No it seems to be much more... evolution (indirectly) depends on it, and via that most of gnome (at least gnome-shell, gnome-core, gdm) Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#794916: [Aptitude-devel] Bug#794916: Bug#794916: aptitude is uninstallable
Hi, Christoph Anton Mitterer wrote: On Sat, 2015-08-08 at 02:06 +0200, Axel Beckert wrote: You are aware that Debian Unstable is in the midst of a huge transition (libstdc++6) with many followup transitions and that temporary uninstallabilities are very normal during such transitions? Sure... I just wasn't sure whether this may have happened accidentally (and thus unnoted), as you already switched to libcwidget3v5 but not to libsigc++ v5 version :-) Well, the segfaults it fixes were happening accidentally. The transitions were on purpose. ;-) My current rule of thumb: Ignore any uninstallability which lasts less than two days during the next two weeks. And on desktop installations where apt or aptitude usually hold back hundreds of packages, I'd just wait until the whole bumpy ride is over. :-) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794581: /usr/bin/kwin_x11: crashes when starting first window
Ooops! Taked a deeper look on the Nvidia box: it turned out that for some reason breeze was still at -3. Then I tried to install -4 and... same as Intel: kwin_x11 crashed immediately at session start. Sorry for the noise. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794912: libcmis-0.5-5: please use libboost-date-time 1.57 or 1.58 ASAP
Control: severity -1 critical Control: tags -1 + security As described in the bug report, the libboost-date-time1.55.0 package is incompatible with GCC5 and will not be fixed, requiring a transition to 1.57 or 1.58. Unfortunately the GCC5 transition has already been taking place on Sid (with libstdc++6 specifying a break against libboost-date -time1.55.0), despite libreoffice and it's libphonenumber6 and libcmis -0.5-5 dependencies not being ready for a 1.57/1.58 transition. This has resulted in Sid users being unable to install a bunch of updates for the past few days, now including security updates (e.g. the CVE -2015-4495 emergency patch to iceweasel). Hence I'm taking the liberty of pushing up the severity on this. We need to get libreoffice and it's dependencies transitioned to a boost 1.57/1.58 ASAP. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794913: libphonenumber6: please use libboost-date-time 1.57 or 1.58 ASAP
Control: severity -1 critical Control: tags -1 + security As described in the bug report, the libboost-date-time1.55.0 package is incompatible with GCC5 and will not be fixed, requiring a transition to 1.57 or 1.58. Unfortunately the GCC5 transition has already been taking place on Sid (with libstdc++6 specifying a break against libboost-date -time1.55.0), despite libreoffice and it's libphonenumber6 and libcmis -0.5-5 dependencies not being ready for a 1.57/1.58 transition. This has resulted in Sid users being unable to install a bunch of updates for the past few days, now including security updates (e.g. the CVE -2015-4495 emergency patch to iceweasel). Hence I'm taking the liberty of pushing up the severity on this. We need to get libreoffice and it's dependencies transitioned to a boost 1.57/1.58 ASAP. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794916: [Aptitude-devel] Bug#794916: Bug#794916: aptitude is uninstallable
On Sat, 2015-08-08 at 02:21 +0200, Axel Beckert wrote: My current rule of thumb: Ignore any uninstallability which lasts less than two days during the next two weeks. Normally I'd do,... but right now we have several packages (already depending on v5 libstd++) with more or less critical security updates. So I wrote a number of tickets for those, and stumbled also over this issue here... and I forgot to look at incoming *sry* Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#794912: libcmis-0.5-5: please use libboost-date-time 1.57 or 1.58 ASAP
Hey. I appreciate that you try to push in that matter,... but strictly speaking, there is no security issue in this package, and also the severity wouldn't be justified. Some maintainers may not be too happy about that... Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#794913: libphonenumber6: please use libboost-date-time 1.57 or 1.58 ASAP
Hey. I appreciate that you try to push in that matter,... but strictly speaking, there is no security issue in this package, and also the severity wouldn't be justified. Some maintainers may not be too happy about that... Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#793152: pidgin: no pidgin window @ startup, no error, it just 'hangs'
The log from right after you moved ~/.purple is very confusing; it said it found your ~/.purple config files, and it's renaming legacy stuff from /gaim/. Do you also still have a ~/.gaim that you can remove?
Bug#794892: autogen: please make the build reproducible (cpu, locale, timestamps)
On 08/07/15 11:23, Valentin Lorentz wrote: Source: autogen Version: 1:5.18.6~pre3-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: cpu locale timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that autogen could not be built reproducibly. The attached patch fixes the following issues: * run time of ./configure affects a preprocessor constant This is necessary. Perhaps if you build on one platform and run on another, you might have issues, but the problem boils down to trying to understand when some template has wandered out into the weeds. I can pick an arbitrary Oh, I'm certain that doing thus-and-so will _never_ take longer than X. but that doesn't scale very well. So, I just take a rough measure based on configure time and then add in a factor of 10 on the theory that it's close enough and can be overridden anyway. So, proposal: allow a config flag that specifies the default timeout time. You specify that, you get reproducibility. Otherwise, it is speed-of-build- machine adaptable. * locale-dependant sort That should be fixed. I abhor and hate and despise locale-dependent sorting. It was a really stupid idea to foist that onto the computing world as a default. If you want to change the way things work, then invent new interfaces. Improving an older interfaces is amazingly stupid. * timezone-dependant date Unclear what part of the patch addresses this. Thank you! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794913: libphonenumber6: please use libboost-date-time 1.57 or 1.58 ASAP
Hey. Although there may not be security issues within this package itself, and while the descriptions of severity [1] may not perfectly cover this unfortunate scenario, an update to this package (and others) is urgently needed in order for Sid users to be able to install critical security patches (since rolling back the gcc5 transition temporarily I imagine isn't going to happen); and since this bug report is all about fixing this dependency breakage issue, I feel that it is perfectly appropriate to raise the severity as I have in order to help ensure that the maintainers take proper note of the urgency for which resolution of this issue is needed. Frankly I don't give a damn if the maintainer disagrees with the severity, they can ignore or change it, and at least it may have helped grab their attention. I think it's perfectly worth risking making them a little annoyed over a possibly inappropriately set severity level if it helps to make them aware of the security issues going on here. Regards :) [1] https://www.debian.org/Bugs/Developers#severities On Sat, 2015-08-08 at 02:47 +0200, Christoph Anton Mitterer wrote: Hey. I appreciate that you try to push in that matter,... but strictly speaking, there is no security issue in this package, and also the severity wouldn't be justified. Some maintainers may not be too happy about that... Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794912: libcmis-0.5-5: please use libboost-date-time 1.57 or 1.58 ASAP
Hey. Although there may not be security issues within this package itself, and while the descriptions of severity [1] may not perfectly cover this unfortunate scenario, an update to this package (and others) is urgently needed in order for Sid users to be able to install critical security patches (since rolling back the gcc5 transition temporarily I imagine isn't going to happen); and since this bug report is all about fixing this dependency breakage issue, I feel that it is perfectly appropriate to raise the severity as I have in order to help ensure that the maintainers take proper note of the urgency for which resolution of this issue is needed. Frankly I don't give a damn if the maintainer disagrees with the severity, they can ignore or change it, and at least it may have helped grab their attention. I think it's perfectly worth risking making them a little annoyed over a possibly inappropriately set severity level if it helps to make them aware of the security issues going on here. Regards :) [1] https://www.debian.org/Bugs/Developers#severities On Sat, 2015-08-08 at 02:46 +0200, Christoph Anton Mitterer wrote: Hey. I appreciate that you try to push in that matter,... but strictly speaking, there is no security issue in this package, and also the severity wouldn't be justified. Some maintainers may not be too happy about that... Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794868: Fix for writing unaligned iso images to DVD-R for growisofs
Hi Debian team! I applied the patches mentioned in the bug report by Thomas Schmitt and the DAO-burn with unaligned iso-images works OK now on Debian testing All the best EIke Patches added for clarity: --- Remedy for the wrong last WRITE transaction: --- --- growisofs_mmc-7.1-11.cpp2015-08-07 13:07:52.0 +0200 +++ growisofs_mmc.cpp 2015-08-07 14:06:31.375597960 +0200 @@ -540,7 +540,7 @@ ssize_t poor_mans_pwrite64 (int fd,const // own higher HZ value and disrespects the user-land one. // Sending them down as milliseconds is just safer... // - if (!(errcode=cmd.transport (WRITE,(void *)buff,size))) + if (!(errcode=cmd.transport (WRITE,(void *)buff,nbl*2048))) break; //--- WRITE failed ---// --- With the patch applied, the burn run succeeds, the medium is readable, and diff detects no alterations. I can confirm this. Remedy for the wrong error code display: --- transport-7.1-11.hxx2015-08-07 13:07:52.0 +0200 +++ transport.hxx 2015-08-07 13:43:02.759592641 +0200 @@ -70,7 +70,12 @@ inline long getmsecs() #ifndef FATAL_START #defineFATAL_START(er) (0x80|(er)) #endif -#define ERRCODE(s) s)[2]0x0F)16)|((s)[12]8)|((s)[13])) +#define ERRCODE_FIXED(s) s)[2]0x0F)16)|((s)[12]8)|((s)[13])) +#define ERRCODE_DESCR(s) s)[1]0x0F)16)|((s)[2]8)|((s)[3])) +#define ERRCODE(s) ((s)[0] == 0x70 || (s)[0] == 0x71 ? \ + ERRCODE_FIXED(s) : \ + ((s)[0] == 0x72 || (s)[0] == 0x73 ? \ + ERRCODE_DESCR(s) : 0)) #defineSK(errcode) (((errcode)16)0xF) #defineASC(errcode)(((errcode)8)0xFF) The error message on my Debian 8.1, burner LG GH24NSC0, SATA of mainboard ASUS P9D WS, is then correctly reported: :-[ WRITE@LBA=19c70h failed with SK=Bh/NO ADDITIONAL SENSE INFORMATION]: Input/output error Something which one could look up in e.g. https://en.wikipedia.org/wiki/Key_Code_Qualifier other than the fantasy error triple SK=0h/ASC=00h/ACQ=03h (Of course, i see the error only if the remedy for DAO is not applied.) --- Side note about dash (see also https://wiki.debian.org/DashAsBinSh): When manually running make after apt-get source dvd+rw-tools, i see the error message /bin/sh: 1: [: 1000: unexpected operator which stems from a bashism in Makefile.m4 minus_o:=$(shell [[ `id -u` == 0 ]] echo -o root) This fix works OK. -- Eike Lantzsch ZP6CGE Agencia Shopping del Sol Casilla de Correo 13005 1749 Asuncion / Paraguay -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794917: gqrx-sdr: URL in man page needs updating
Package: gqrx-sdr Version: 2.3.1-2 Severity: minor Dear Maintainer, URL given in man page (in SEE ALSO section) is http://www.oz9aec.net/index.php/gnu-radio/gqrx-sdr Project's home page has moved to http://gqrx.dk/ -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.4-khufu-0 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages gqrx-sdr depends on: ii libboost-program-options1.55.0 1.55.0+dfsg-4 ii libboost-system1.55.0 1.55.0+dfsg-4 ii libc6 2.19-19 ii libgcc1 1:5.1.1-14 ii libgnuradio-analog3.7.5 3.7.5-5 ii libgnuradio-blocks3.7.5 3.7.5-5 ii libgnuradio-fft3.7.53.7.5-5 ii libgnuradio-filter3.7.5 3.7.5-5 ii libgnuradio-osmosdr0.1.30.1.3-2 ii libgnuradio-pmt3.7.53.7.5-5 ii libgnuradio-runtime3.7.53.7.5-5 ii libpulse0 6.0-2 ii libqt4-network 4:4.8.7+dfsg-1 ii libqt4-svg 4:4.8.7+dfsg-1 ii libqtcore4 4:4.8.7+dfsg-1 ii libqtgui4 4:4.8.7+dfsg-1 ii libstdc++6 5.1.1-14 ii libvolk0.0.03.7.5-5 gqrx-sdr recommends no packages. gqrx-sdr suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792208: qt-at-spi: does not show up in KDE/Qt apps
forwarded 792208 https://bugreports.qt.io/browse/QTBUG-47677 thanks I'm afraid this is a hard one. As a team policy we do not patch qt except for patches ACKed by upstream. And that means pushed to upstream's gerrit. Moreover this one comes from a RH employee, and in my experience getting them to properly push the patches tends to be... complicated. So I did report the bug upstream and I'll try to track down the original coder of the patch. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#794918: cython is uninstallable in unstable
Package: cython Version: 0.22.1-1 Severity: serious As of today in a clean sid chroot: # apt install cython Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libfuse2 libpcre16-3 libpcre32-3 libsepol1-dev Use 'apt-get autoremove' to remove them. Suggested packages: cython-doc The following packages will be REMOVED: apt build-essential debfoster debhelper g++ g++-4.9 g++-5 gcc gcc-4.9 gcc-5 gettext gettext-base groff-base intltool-debian libapt-pkg4.12 libapt-pkg4.16 libasan1 libasan2 libasprintf0v5 libcc1-0 libcilkrts5 libcroco3 libfuse-dev libgc1c2 libgcc-4.9-dev libgcc-5-dev libicu52 liblsan0 libpcre3-dev libpcrecpp0v5 libselinux1-dev libstdc++-4.9-dev libstdc++-5-dev libstdc++6 libtsan0 libubsan0 libxml2 man-db po-debconf shared-mime-info The following NEW packages will be installed: cython WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! apt libapt-pkg4.16 (due to apt) libstdc++6 (due to apt) 0 upgraded, 1 newly installed, 40 to remove and 0 not upgraded. Need to get 1530 kB of archives. After this operation, 423 MB disk space will be freed. You are about to do something potentially harmful. To continue type in the phrase 'Yes, do as I say!' ?] ^C -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794919: libxcb1: Segmentation fault in libqxcb.so
Package: libxcb1 Version: 1.10-3+b1 Severity: important Dear Maintainer, Program received signal SIGSEGV, Segmentation fault. 0x7fffe1d18669 in ?? () from /usr/lib/x86_64-linux- gnu/qt5/plugins/platforms/libqxcb.so (gdb) bt #0 0x7fffe1d18669 in ?? () from /usr/lib/x86_64-linux- gnu/qt5/plugins/platforms/libqxcb.so #1 0x7fffe1d18bbb in ?? () from /usr/lib/x86_64-linux- gnu/qt5/plugins/platforms/libqxcb.so #2 0x7fffe1d05327 in ?? () from /usr/lib/x86_64-linux- gnu/qt5/plugins/platforms/libqxcb.so #3 0x7fffe1d0723e in ?? () from /usr/lib/x86_64-linux- gnu/qt5/plugins/platforms/libqxcb.so #4 0x7fffe1d18c6b in ?? () from /usr/lib/x86_64-linux- gnu/qt5/plugins/platforms/libqxcb.so #5 0x73d0da92 in QPlatformIntegrationFactory::create(QString const, QStringList const, int, char**, QString const) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #6 0x73d19636 in QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x73d1a29d in QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x737dcd38 in QCoreApplication::init() () from /usr/lib/x86_64 -linux-gnu/libQt5Core.so.5 #9 0x737dcda6 in QCoreApplication::QCoreApplication(QCoreApplicationPrivate) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x73d1c5f9 in QGuiApplication::QGuiApplication(QGuiApplicationPrivate) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7742e6cd in QApplication::QApplication(int, char**, int) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x00456141 in OBSApp (argv=optimized out, argc=@0x7fffe4cc: 1, this=0x7fffe500) at /root/tmp/obs-studio/obs/obs-app.cpp:460 #13 run_program (argv=optimized out, argc=1, logFile=...) at /root/tmp/obs- studio/obs/obs-app.cpp:870 #14 main (argc=1, argv=optimized out) at /root/tmp/obs-studio/obs/obs- app.cpp:1136 Found this thread on the Arch tracker: https://bugs.archlinux.org/task/37728 - but I'm not sure how relevant it is. -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (960, 'stable'), (900, 'oldstable'), (800, 'oldoldstable'), (500, 'oldstable-updates'), (500, 'oldoldstable-updates'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699754: grub core.img too large when using lvm+md
I have the same problem - a 95% full / Adam. On Sat, 08 Aug 2015 07:16:24 +1200, Markus Raab deb...@markus-raab.org wrote: Hello, On Thu, 5 Mar 2015 18:43:41 +0100 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= j...@inutil.org wrote: Is this still something which is relevant in jessie? Yes, I ran into this issue during a wheezy-jessie upgrade. The affected root file system is in a lvm. At the troublesome system the first parition starts at block 63. Then the post-installation script returns with an error. It does not print the error message. (Manual invocation of grub-install does) Basically, this problem can happen (and is noteworthy in the release notes) whenever core.img's size gets increased. Btw. with start=512 it works. It is easy to reproduce the error, e.g., with an 256mb flash disk cfdisk leaves per default too little space for the core.img. best regards, Markus -- Using Opera's mail client: http://www.opera.com/mail/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794920: docutils-common: rst.el doesn't indent description lists properly
Package: docutils-common Version: 0.12+dfsg-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Consider the following description list, from the rst docs. Place the cursor on the line containing Definition 1.. Press TAB any number of times; the only indentation offered is at the beginning of the line, which breaks the syntax of the list. term 1 Definition 1. term 2 Definition 2, paragraph 1. Definition 2, paragraph 2. - -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-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: systemd (via /run/systemd/system) Versions of packages docutils-common depends on: ii sgml-base 1.26+nmu4 ii xml-core 0.13+nmu2 Versions of packages docutils-common recommends: ii python-docutils 0.12+dfsg-1 ii python3-docutils 0.12+dfsg-1 docutils-common suggests no packages. - -- debconf-show failed -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCAAGBQJVxYkFAAoJEPIClx2kp54sIBYL/3r882d4y/YNSh1Qo+TTfxDU 298AL9qi3HmzlEfMp2CKk56u+NIg+GTfHIyY0/FPOppjBHOmd061KWtJl66T+9RT eIsXuD4PRxgnyd5m0ii4OtU+8g0LtdDzW3nrAzC8+QAtYWX3o9QnVYpFclqRdbWY TlOqNgrgDGKiBAbFYN/uJVFi6+jY9ipJNtv6E6PHmg2Y5tt97G2Os6ozHE9Jlwic y7o+JcwqUb+bb5grJyhtKtDkwO4lKmCAMqk44uFdnsOir+hzLpsporOoJ/5UGK23 N4Znp8hzHf3fK36ZCKXJ9jv8PwsSJLf3PNxwQwcAnzZuGlVMiyAac423RuqHWhJc 5euAZ3On1YyWxEF6IsIO8PFMCEnA3aIdiW8nmMgJeXChQVDI0Qon0smMkNH1Yi6t sY7HIhA8mx+nlxMUROy9B2Tie5dHeRRbtvqgsgVNNGQR2IpCvVSkoR2fXS/lerRv Nj3qzEGT3rsJZklERDhJLuYMD/J3kpvB7072mO3Iew== =YCNx -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793921: [syslinux] Bug#793921: tftpd-hpa: IPv6 address cannonization breaks IPv4
On Fri, Aug 07, 2015 at 11:52:49AM -0700, H. Peter Anvin wrote:
On Tue, Jul 28, 2015 at 03:45:30PM -0600, Jason Gunthorpe wrote:
Package: tftpd-hpa
Version: 5.2+20140608-3
Severity: important
This commit:
tftp: convert IPv6-mapped IPv4 addresses to IPv4
If we receive IPv4 addresses mapped to IPv6, convert them back to IPv4
so that mapping scripts which use \i behave sanely.
Signed-off-by: H. Peter Anvin h...@zytor.com
Totally breaks IPv4 support when tftpd is used with an IPv6 listening
socket
(eg when invoked from systemd)
The issue is that the tftpd caller assumes that 'from' and 'myaddr' have
the
same AF, however the above patch only cannonizes 'myaddr'. Ultimately this
results in the daemon attempting to use a socket with two address
families and
fails:
recvmsg(0, {msg_name(28)={sa_family=AF_INET6, sin6_port=htons(34500),
inet_pton(AF_INET6, :::10.0.0.192, sin6_addr), sin6_flowinfo=0,
sin6_scope_id=0}, msg_iov(1)=[{\0\1pxelinux.0\0netascii\0, 65468}],
msg_controllen=40, {cmsg_len=36, cmsg_level=SOL_IPV6, cmsg_type=, ...},
msg_flags=0}, 0) = 22
[..]
[pid 3757] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 0
[..]
[pid 3757] bind(0, {sa_family=AF_INET, sin_port=htons(0),
sin_addr=inet_addr(10.0.0.2)}, 16) = 0
[pid 3757] connect(0, {sa_family=AF_INET6, sin6_port=htons(34500),
inet_pton(AF_INET6, :::10.0.0.192, sin6_addr), sin6_flowinfo=0,
sin6_scope_id=0}, 28) = -1 EAFNOSUPPORT (Address family not supported by
protocol)
[pid 3757] sendto(3, 27Jul 28 15:32:20 tftpd[3757]: connect: Address
family not supported by protocol, 82, MSG_NOSIGNAL, NULL, 0) = 82
This makes the daemon utterly unusable.
Suggest this tested patch:
--- ../x/tftp-hpa-5.2+20140608/tftpd/recvfrom.c 2014-07-29
20:31:34.0 -0600
+++ tftpd/recvfrom.c 2015-07-28 15:42:12.533074001 -0600
@@ -24,6 +24,8 @@
#include machine/param.h /* Needed on some versions of FreeBSD */
#endif
+#include assert.h
+
#if defined(HAVE_RECVMSG) defined(HAVE_MSGHDR_MSG_CONTROL)
#include sys/uio.h
@@ -253,6 +255,8 @@
}
#endif
normalize_ip6_compat(myaddr);
+ normalize_ip6_compat((union sock_addr *)from);
+ assert(from-sa_family == myaddr-sa.sa_family);
}
#endif
}
I have applied the solution of canonicalizing all the addresses into git
for now. I would appreciate if someone could try to test it.
I ended up going for canonicalize everywhere because I found other
places in the code which probably would fail to operate correctly on
IPv6-mapped IPv4 addresses.
Thanks, that looks good to me by eye at least. I'll push it out to
unstable to get some broader testing on it.
Ron
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794921: bookmarks widget is missing in recent version(s)
Package: plasma-widgets-addons Version: 4:5.3.2-2 The bookmarks widget allows the nomination of a folder within the konqueror bookmarks to appear as an icon in the KDE panel, which can then provide multiple shortcuts to locations within the file system. It isn't the same as the Folder View widget, which just shows the contents of a nominated directory. On stretch/testing, the plasma-widgets-addons package does not include the plasma-applet-bookmarks widget. However it is definitely present in 4:4.14.2-1The format has changed with Plasma 5, of course -- from .desktop .so to .desktop .qml -- so I can't just copy the relevant files across. I also can't find a definitive reference to the state of this widget within Plasma 5, and appreciate it may not exist (yet). If it does exist, can we have it within this addons package please? Thanks!
Bug#794774: libstdc++6: Breaks: libboost-date-time1.55.0, but isn't that package fixed now?
On 08/08/2015 02:15 AM, Christoph Anton Mitterer wrote: On Sat, 2015-08-08 at 01:01 +0100, jnqnfe wrote: it's actually just a couple of libreoffice dependencies specifically targeting 1.55 that are causing the hold up in upgrade installation currently (at least here on my systems). No it seems to be much more... evolution (indirectly) depends on it, and via that most of gnome (at least gnome-shell, gnome-core, gdm) You may have missed https://lists.debian.org/debian-devel-announce/2015/07/msg0.html https://lists.debian.org/debian-devel-announce/2015/08/msg0.html https://lists.debian.org/debian-devel-announce/2015/08/msg2.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794891: iceweasel: 39.0.3-1 suddenly depends on libstdc++6 = 5.2 instead of = 4.9 as before
On Fri, 7 Aug 2015 21:31:04 +0200 Moritz Muehlenhoff j...@inutil.org wrote:
On Fri, Aug 07, 2015 at 08:10:54PM +0200, Thibaut Renaux wrote:
Package: iceweasel
Version: 39.0-1
Severity: grave
Justification: renders package unusable
I'm tracking stable for most of my packages but am using experimental
for
Iceweasel since it's the only way to get the latest version.
I'm currently running Iceweasel 39.0-1 and wanted to upgrade to
39.0.3-1,
mostly to get the fix for CVE-2015-4495.
However, when trying to upgrade it with aptitude, I get the following:
The following packages will be upgraded:
iceweasel{b}
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 38.9 MB of archives. After unpacking 824 kB will be freed.
The following packages have unmet dependencies:
iceweasel : Depends: libstdc++6 (= 5.2) but 4.9.2-10 is installed.
aptitude then proposes solutions ranging from ignoring the update,
downgrading
Iceweasel, or upgrading libstdc++6 which would then break dozens of
currently
installed packages.
I understand my setup is prone to this kind of issue, due to tracking
multiple
branches. However, I don't really understand why that dependency on a
newer
version of libstdc++6 suddenly appeared, especially considering this is
a minor
update.
Would it be possible to revert the dependency back to libstdc++6 = 4.9?
No, that's an ongoing transition:
https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
Would depending on libstdc++6 = 5.1 be an acceptable middle ground?
This would allow pulling in the testing tree rather than the risking
unstable.
David
Bug#532296: ♀come stai
come stai imac, gultar, prodotti samsung, orologio siamo in grado di offrire il trasporto gratuito per voi s it e: poazzlo .com
Bug#608116: ↑come stai
come stai imac, gultar, prodotti samsung, orologio siamo in grado di offrire il trasporto gratuito per voi s it e: poazzlo .com
Bug#791050: glibmm2.4: library transition may be needed when GCC 5 is the default
On 08/06/2015 05:14 PM, Michael Biebl wrote: Please let me know, when I can proceed with the upload to unstable. https://lists.debian.org/debian-devel-announce/2015/08/msg0.html Michael, you can directly upload to unstable, unless there not yet transitioned or not yet confirmed build dependencies. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733823: Adopting dxflib
Hi, I'm willing to step in as responsible uploader for dxflib, as it is now a dependency of a package I maintain, terralib. regards Alastair -- Alastair McKinstry, alast...@sceal.ie, mckins...@debian.org, https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663185: interested in (co-)maintaining midori
On Fri, 07 Aug 2015 15:39:54 -0400 Sergio Durigan Junior sergi...@sergiodj.net wrote: On Saturday, August 01 2015, Andres Salomon wrote: I'm interested in helping out with Midori packaging. I'm not sure who's still interested in the package at this point (I know Corsac isn't, so I didn't Cc him). I've created a git branch for the 0.5.10 release here: git://lunge.queued.net/git/midori http://lunge.queued.net/gitweb/?p=midori;a=shortlog;h=refs/heads/0.5.10 It builds (on sid and jessie) and runs (on jessie) for me, though it definitely needs more work tightening up deps, cleaning up lintian errors, etc. I'm happy to co-maintain the package, or take it over; whatever folks prefer. Please let me know what I should do, since it was never formally orphaned. I haven't heard anything regarding this, and it's been over a month. Should I just clean up my midori packages and upload? If I don't hear anything back and there's no activity with the package, that's my plan. Hi Andres, I saw your message only yesterday, sorry about that. As it turns out, I have also been working on getting Midori fixed. My intention is to maintain it; Thadeu Cascardo is going to help me take over the package. However, as you are also willing to co-maintain the package, maybe we could create a group on Alioth to work together? There's already a midori packaging group/git repo: http://anonscm.debian.org/cgit/collab-maint/midori.git/ My repo is based on this, and my plan was to get access permission from Corsac after uploading the package to sid. Then I could push my changes, maintaining history. That would be my preference. I also looked at your branch. What I am doing is basically a repackaging, from scratch, trying to figure out what's important and what's not. I'll publish my branch later today. Why from scratch? I'll take a look at your branch once it's published. So, any opinions on how to proceed? Thanks, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794912: libcmis-0.5-5: please use libboost-date-time 1.57 or 1.58 ASAP
severity 794912 serious close 794912 0.5.0-3 thanks Hi, On Sat, Aug 08, 2015 at 01:12:51AM +0200, Christoph Anton Mitterer wrote: libcmis-0.5-5, depended upon by whole libreoffice, depends on libboost-date-time1.55.0 which itself is not compatible with the new libstdc++6 from GCC5. Apparently this won't be reseloved (see #793222 or #794774). Already done. libcmis-0-5-5v5, though. libstdc++ transition. Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794915: RFS: compute/0.4-1 [ITP]
Hi Ghislain, I did a quick review of this package, and looks mostly good to me, but I have some nitpicks (some errors) for you: 1) you seem to produce a source only library, with no binaries: - why do you have an arch:any? 2) you seem to disable the testsuite during the build -DBOOST_COMPUTE_BUILD_BENCHMARKS=OFF \ -DBOOST_COMPUTE_BUILD_EXAMPLES=OFF \ -DBOOST_COMPUTE_BUILD_TESTS=OFF In my opinion you should run them, even if you do not install them, because they might be useful to understand if your library performs well (cfr websocketpp where I did exactly the same) 3) there is no need to specify the build system when there is no ambiguity (not a problem at all, just I want to let you aware of this) 4) the copyright file is good, but usually is better for the Debian packaging to choose the same license as upstream, to ease patch forwarding Actually expat seems more permissive of the upstream BSL-1.0, so its good For the copyright where the license is the same you can actually merge all the copyrights together (just list an * and the list of the copyright owners). What Debian really care is the License, the copyright of the single file is nice to have (so please leave it as is), but not strictly mandatory (please somebody correct me if I'm wrong) Files: * Copyright: list of all the copyright owners License: BSL-1.0 might have been good enough. Since you split all of them is is for sure better, so please leave it as is :) Let me know how do you want to proceed with the nitpicks, and I'll do another review. Cheers, Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699754: grub core.img too large when using lvm+md
Hello, On Thu, 5 Mar 2015 18:43:41 +0100 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= j...@inutil.org wrote: Is this still something which is relevant in jessie? Yes, I ran into this issue during a wheezy-jessie upgrade. The affected root file system is in a lvm. At the troublesome system the first parition starts at block 63. Then the post-installation script returns with an error. It does not print the error message. (Manual invocation of grub-install does) Basically, this problem can happen (and is noteworthy in the release notes) whenever core.img's size gets increased. Btw. with start=512 it works. It is easy to reproduce the error, e.g., with an 256mb flash disk cfdisk leaves per default too little space for the core.img. best regards, Markus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794901: Fixing tags
Control: -1 tag -pending Grrf. nmudiff is handy to send patches. but it just does a bit too much if you don't really NMU Regards Christoph -- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791328: new upstream version
Hi Jay, On Thu, Aug 6, 2015 at 5:26 PM, Jay Berkenbilt q...@debian.org wrote: I hope that the new maintainer will see if the new upstream version of vips includes a soname bump and, if so, will just upload that. As you know, it does include a soname bump. But there's an even newer version that is packaged for experimental; it's v8.0.2 at the moment. I consider packaging that and upload directly to Sid. That's what I would do if I were still maintaining this. What's your plan with the nip2 package? Would you package v8.0.x for me or is it up for adoption as well? Regards, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794830: [Aptitude-devel] Bug#794830: aptitude: segfaults in memory allocation
Hi, Matthijs van Duin wrote: I just noticed aptitude and libcwidget3v5 still depend on libsigc++-2.0-0c2a, shouldn't that be libsigc++-2.0-0v5 now? A cool, that has been fixed now, too! Yep, there is a libsigc++-2.0 transition upcoming: https://release.debian.org/transitions/html/auto-libsigc++-2.0.html Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794237: openconnect: Does not work with network-manager 1.0.4
On Fri, Aug 7, 2015 at 13:53:49 +0100, David Woodhouse wrote: On Fri, 2015-08-07 at 08:27 -0400, Mike Miller wrote: Thanks for the debugging guys, reassigned to NM-openconnect for now. Nah, that makes it my fault too! Pass the buck a bit further! Seriously, NM-openconnect doesn't really do much with the IP configuration at all. You can use dbus-monitor to watch what nm-openconnect-service-openconnect-helper hands back to NM, and I bet it *will* include the MTU. We haven't really touched that part for ages. I blame NM. Fair enough. Matt already said that reverting to NM 1.0.2 was enough to restore his connection, but that was while running openconnect standalone. Matt, can you verify that going back to NM 1.0.2 and connecting to the VPN via NM now sets the proper MTU on tun0 and your connection works again? -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794581: /usr/bin/kwin_x11: crashes when starting first window
On Friday, August 07, 2015 10:08:19 AM Maurizio Avogadro wrote: Hi I struggled with this bug an entire afternoon on my laptop (Intel Sandy Bridge HD Graphics 3000, xorg driver updated to latest git, Mesa 10.6.3-1): the users having the (default) Breeze theme configured, most of the times couldn't even reach the desktop at login; the rare times I could reach the desktop, kwin_x11 crashed as soon as I opened the first window. Systemsettings5 crashed everytime I tried to open the kwindecoration kcm; in the kwincompositing kcm I could set the rendering backend, but the OpenGL interface control was blank. By downgrading the packages all issues disappeared. But the most interesting thing is that another box with Nvidia graphics doesn't seem to be affected by this bug: kwin_x11 doesn't crash with Breeze theme and everything seems to work as expected, even with breeze 4:5.3.2-4. Thanks. Could this relate to this: https://bugs.kde.org/show_bug.cgi?id=349519 https://bugs.freedesktop.org/show_bug.cgi?id=86281 Scott K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794871: tuxtype: speaker muted but audio remains unmuted
Package: tuxtype
Version: 1.8.3-1
Severity: important
Turning off the speaker in the application, only turns off the menu music. All
other sounds - pop up sound on hovering over the menu item and the background
music in the games remain unmuted.
Patch for the same is attached.
Regards,
Prathibha
Senior Engineer
CDAC Chennai
---
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA Twitter: @cdacindia ]
This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
---
--- tuxtype-1.8.3-orig/src/titlescreen.c 2014-08-20 09:25:27.0 +0530
+++ tuxtype-1.8.3/src/titlescreen.c 2015-08-07 18:47:35.592817785 +0530
@@ -322,10 +322,12 @@
{
MusicUnload();
settings.menu_music = 0;
+ settings.sys_sound = 0;
}
else
{
settings.menu_music = 1;
+ settings.sys_sound = 1;
MusicLoad(tuxi.ogg, -1);
}
redraw = 1;
Bug#793517: [pkg-fgfs-crew] Bug#793517: fltk1.3-dev cmake interface now requires libcairo2-dev and fluid?
Rebecca N. Palmer rebecca_pal...@zoho.com writes: However, fgrun already bypasses cmake-data with find_package(FLTK REQUIRED NO_MODULE) Good point; I'd forgotten that recommendation, and have now noted my take on it in #793549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793549#10 -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794477: confirmation
I came across this same problem. I temporary solved it by installing packages mysql-server and libmysqlclient shared library-dev from sid. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794874: ITP: libdbicx-sugar-perl -- syntax sugar for DBIx::Class
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard d...@jones.dk -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: libdbicx-sugar-perl Version : 0.0001 Upstream Author : Naveed Massjouni nav...@vt.edu * URL : http://search.cpan.org/dist/DBICx-Sugar/ * License : Artistic or GPL-1+ Programming Lang: Perl Description : syntax sugar for DBIx::Class DBICx::Sugar provides some syntax sugar for your DBIx::Class applications. . DBIx::Class is an SQL to OO mapper with an object API inspired by Class::DBI and a resultset API that allows abstract encapsulation of database operations. Package is needed for recent releases of libdancer-plugin-dbic-perl. Package will be maintained in the Debian Perl team. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVxLlMAAoJECx8MUbBoAEh2HwP/jQdVRHG0RpfG4t7EH2fY2Zg g6zgm2AUOnWLefHzwLIJPQ4yupLfGDUo+cPtYIk4PdwkaS296M8btiJaO2piRhVw YyaF5zPDxaqFxadXIVKyImDR9xNJdckR3FBPtUhbTJREBOe/3Xy9Umagt0d7qQF+ ednPXqs7sh65IqJOJX5/kofRTJytKcE1R/dVRC7KuZdRhPyJtPvGdBN+ZqzUHBQQ yzUHd6qi7m74HSNdPNokgyrlR5Of4Hr1GFJmaAKLYZqkrfYW5pn7gGwpXMyVvIvo D+H0EggjRTEkmDMxdVYEISA3PETOga3JaHvcxV9knnv9NnOp5v/KtnZPCT/DH0MN odDM99iO+I3fgRxfKj5LgJo3moBMJ19qBxhOu1fw4i87icV86+3LaiCc2/DglDCX To3wRqFysUcUK0wzwcAzP8SMGze5mqMPVW9v0FRGDTfUe22N93EKl5LDH+fb6nz1 27QDSF4b6zdekE2uTjH2zlnghrk8HFSrYs4Ii8oMoc8FOTjZpc9gJx+tQInIOTaF J+FY9UABloVO0OSbAB7ZxpgOBKbjx50sADJ+1/dJJUZjChl9HMjVafHKnQIvc0WU jDt+lexOxxYhIJSNJ5YNaS1f29nKx57p2FWrv3F889wZDhSjwd7+s1owRYWHxOgZ P2BVFxl7KgaA3LoVkb7O =pbHb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732725: We intent to request the removal of libogre-perl (was: Re: Bug#732725: libogre-perl: Please upgrade OGRE dependency to 1.9 when upstream ready)
On Sat, May 23, 2015 at 03:14:31PM +, Damyan Ivanov wrote: -=| Axel Beckert, 23.05.2015 16:48:43 +0200 |=- Hi, the Debian Perl Team intents to file a removal bug for libogre-perl as * it no more builds against libogre 1.9 (#732725); * its upstream seems inactive since 2013, see https://rt.cpan.org/Public/Bug/Display.html?id=94066#txn-1344923; * it never had much popcon (maximum 26, current 22, vote maximum 7, vote current 1); and * it has no hard reverse dependencies. The only non-hard reverse dependencies are * games-perl-dev which Recommends it, and * libois-perl which Enhances it. Unless there are objections _and_ a fix, we'll soon file a removal bug report for libogre-perl soon. Cc to the submitter of #732725, the games-perl-dev maintainers and Dmitry E. Oboukhov who RFP'ed libogre-perl. (The maintainer of libois-perl is the Debian Perl Team itself, hence I'll remove that Enhances header there myself, soon, too.) dak sees no problems (e.g. broken build-dependencies) in the removal: dmn@coccia:~$ dak rm -n -R -s sid libogre-perl Will remove the following packages from sid: libogre-perl | 0.60-1 | source, ppc64el libogre-perl | 0.60-1+b2 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, sparc libogre-perl | 0.60-1+b4 | s390x Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org So this is good to go for removal, right? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791091: libbinio: library transition may be needed when GCC 5 is the default
clone 791091 -1 reassign 791091 src:libbinio found 791091 1.4+dfsg1-4 tags 791091 + pending thanks On Thu, Aug 06, 2015 at 02:53:54PM +0200, Julien Cristau wrote: On Wed, Aug 5, 2015 at 19:07:07 +0100, Iain Lane wrote: reassign 791091 release.debian.org [...] diff -Nru libbinio-1.4+dfsg1/debian/changelog libbinio-1.4+dfsg1/debian/changelog --- libbinio-1.4+dfsg1/debian/changelog 2014-08-23 12:59:32.0 +0100 +++ libbinio-1.4+dfsg1/debian/changelog 2015-08-05 19:05:05.0 +0100 @@ -1,3 +1,11 @@ +libbinio (1.4+dfsg1-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Rename library packages for g++5 ABI transition. (Closes: #791091) + * Update symbols file for g++5 ABI + + -- Iain Lane i...@orangesquash.org.uk Wed, 05 Aug 2015 18:42:13 +0100 + That upload shouldn't close a bug that's not assigned to the package. Ah, sorry - I guess these get manually closed when the transition is done? Maybe this wrangling will fix it up. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] signature.asc Description: Digital signature
Bug#794795: debiandoc-sgml-doc: please make the build reproducible
Control: tags -1 - patch
Hi,
I see this reproducible build effort is an respectable effort but ...
On Thu, Aug 06, 2015 at 07:19:13PM +0200, Dhole wrote:
Source: debiandoc-sgml-doc
Version: 1.1.23
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi,
While working on the reproducible builds effort [1], we have noticed
that debiandoc-sgml-doc could not be built reproducibly.
Because it includes the build date. This is intentional choice for this
document. There are too many OUTDATED documents on the web. For most
users, the date on the web page is the main source to see the age of
the information.
The attached patch removes timestamps from the documentation (I didn't
find a way to pass an external variable/date to the debiandoc tools to
replace the date tag). Once applied, debiandoc-sgml-doc can be built
reproducibly in our current experimental framework.
I noticed many people are fixing this issue in this way. That may fix
some itch for small group of highly technically minded people but does
disservice to many end-users.
We should better as DD than the one proposed.
- versiondate/version
That's very rough approach.
Let's promote to use the last changelog entry date for this kind of
BUILD_DATE for reproducible build.
I think something like the following to set it:
# short date of this Debian package (debian/changelog)
BUILD_DATE ?= $(shell { date +'%Y-%m-%d' -d`dpkg-parsechangelog -SDate` ||
date +'(No changelog) %Y-%m-%d' ; })
Patch should be more like
- versiondate/version
+ versionbuilddate;/version
Then set the date via entity.
Osamu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793549: cmake-data: Can't find fluid with FLTK 1.3.3
As Rebecca N. Palmer just reminded me at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793517#28 , FLTK's upstream README.CMake.txt recommends bypassing CMake's FindFLTK.cmake altogether by specifying NO_MODULE: https://sources.debian.net/src/fltk1.3/1.3.3-2/README.CMake.txt/#L235 As such, I'm contemplating having libfltk1.3-dev either override or simply divert FindFLTK.cmake for the time being. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780430: qtwebkit-opensource-src: port to m68k
Source: qtwebkit-opensource-src Version: 5.4.2+dfsg-2 Followup-For: Bug #780430 Hi Lisandro, please remember submitters don’t get bugmail… or ping them ;) Anyway, here you are: - We need the original author of the patches. The patches were written by myself. - We need the original author to either: - Publicly state that the patches are under a permisive license like BSD. Please feel free to choose any OSI-approved licence for them. Although they are probably trivial and thus not copyright-protected. Thanks for pushing it upstream and merging it! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794873: freedombox-setup: Tor startup times out on Raspberry Pi
Package: freedombox-setup Version: 0.5 Severity: normal On RaspberryPi, it looks like Tor startup is taking a long time. Meanwhile systemd decides that it is taking too long to start and is stuck. It then kills the process and Tor never starts. Perhaps one solution is to increase the systemd's startup timeout value. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages freedombox-setup depends on: ii apache22.4.12-2 ii augeas-tools 1.2.0-0.2 ii avahi-daemon 0.6.31-5 pn avahi-utilsnone ii bridge-utils 1.5-9 pn checkinstall none pn devio none ii dialog 1.2-20150528-1 pn dnsmasqnone ii dnsutils 1:9.9.5.dfsg-10 ii dosfstools 3.0.28-1 pn etckeeper none ii firewalld 0.3.13-1 pn havegednone ii hostname 3.15 ii htop 1.0.3-1 pn iftop none ii iptables 1.4.21-2+b1 ii iputils-ping 3:20121221-5+b2 ii isc-dhcp-client4.3.2-1 pn libnss-gw-name none ii libnss-mdns0.10-6 ii libnss-myhostname 222-1 ii libpython2.7-stdlib [python-argparse] 2.7.10-3 ii locales2.19-19 pn locales-allnone ii lsof 4.86+dfsg-1 pn lua-secnone pn macchanger none pn monkeysphere none ii net-tools 1.60-26+b1 ii ntp1:4.2.6.p5+dfsg-7 ii openssh-server 1:6.7p1-6 ii parted 3.2-7 pn plinth none ii psmisc 22.21-2 ii python-augeas 0.5.0-1 ii python-beautifulsoup 3.2.1-1 ii python-bjsonrpc0.2.0-1 ii python-docutils0.12+dfsg-1 ii python-lxml3.4.2-1 pn python:any none pn resolvconf none ii ssl-cert 1.0.36 ii sudo 1.8.12-1 ii tcpdump4.7.4-1 pn uaputl none ii vim-tiny 2:7.4.712-3 ii wget 1.16.3-3 pn zile none Versions of packages freedombox-setup recommends: pn batctl none pn pagekitenone pn rfkill none ii wireless-tools 30~pre9-8 freedombox-setup suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791240: pktools: symbols file update needed for GCC 5
Control: unblock 791240 by 790351 On Fri, 7 Aug 2015 21:20:57 +0100 Dimitri John Ledkov x...@debian.org wrote: Hello, The block on boost bug is incorrect. 1.55 will not support libstdc++6 c++11 abi. Instead one should build against boost 1.58, which is now the default in unstable, and uses the new abi. So transition to new boost is needed, but otherwise you should be good to go. Regards, Dimitri. Sorry - my mistake. So it should also be possible to install libdap now, as I discovered the bug had not been closed properly in the changelog (now closed manually). Cheers, Ross signature.asc Description: OpenPGP digital signature
Bug#794798: libnspr4-dev: pthread missing from pkg-config lib deps
Mike Hommey wrote: On Thu, Aug 06, 2015 at 04:37:06PM -0500, D. Jared Dominguez wrote: On Thu, Aug 06, 2015 at 03:46:39PM -0500, Mike Hommey wrote: On Thu, Aug 06, 2015 at 01:42:55PM -0500, Daniel Jared Dominguez wrote: Package: libnspr4-dev Version: 2:4.10.8-2 Severity: important pkg-config --libs nspr returns: -lplds4 -lplc4 -lnspr4 However, at least pthread is missing, which causes building with nspr4 and using pkg-config not to work right. You don't need to link against pthread to link against nspr. Well, it's what's causing this: http://paste.debian.net/289831/ Particularly, /usr/bin/gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wsign-compare -Wno-unused-result -Wno-unused-function -std=gnu11 -fshort-wchar -fPIC -flto -fno-strict-aliasing -fno-merge-constants -D_GNU_SOURCE -DCONFIG_x86_64 -I/«PKGBUILDDIR»/include -I/usr/include/efivar -I/usr/include/nss -I/usr/include/nspr -Wl,-z,relro-D_FORTIFY_SOURCE=2 -o pesigcheck pesigcheck.o pesigcheck_context.o certdb.o cms_common.o content_info.o oid.o password.o signed_data.o signer_info.o wincert.o ucs2.o /«PKGBUILDDIR»/libdpe/libdpe.a -lefivar -lnss3 -lnssutil3 -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4 -lpopt /usr/bin/ld: /tmp/ccSnL8H8.ltrans1.ltrans.o: undefined reference to symbol 'pthread_rwlock_wrlock@@GLIBC_2.2.5' //lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status I see that this is what Fedora is doing: http://pkgs.fedoraproject.org/cgit/nspr.git/tree/nspr-config-pc.patch Also, $ ldd /usr/lib/x86_64-linux-gnu/libnspr4.so | grep pthread libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f3111be4000) To me, that seems to be a pretty good indication that pthread is needed to link against nspr. To me, that seems to be a pretty good indication that one of those object files is using pthread_rwlock_wrlock. The only reference to pthread_rwlock_wrlock in the nspr code base is in a .c file, which means there is no way something #including nspr header can inadvertently have a dependency on that symbol. -lpthread -lrt -ldl (@OS_LIBS@) is certainly required for static linking (and there are static libraries in libnspr-dev). (However, I think the linked above fedora patch is also slightly wrong, @OS_LIBS@ should be in Libs.private, not in Libs). But I don't see -static in failed command above, so not sure why it fails and if this is a same problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794383: apache2: Upgrade to apache2-2.2.22-13+deb7u5 breaks CA certificate chain
Hi, On Sunday 02 August 2015 14:14:11, Felicitus wrote: [Sun Aug 02 13:19:52 2015] [error] Failed to configure CA certificate chain! Please try the version from https://people.debian.org/~sf/794383/ and check if it either fixes the problem or at least gives some more information in the error log. You may either replace all packages with dpkg or only the /usr/lib/apache2/modules/mod_ssl.so file by hand. The sha256 sums are below. Thanks in advance. Cheers, Stefan e9c380349cc6828e3eacc4cae61950bab89f85d39ccef7fd2930052014e917ec apache2_2.2.22-13+deb7u5+sf1_amd64.changes 5e6d002832a4d84bdcda5189acad7696b76a08505a1d2fb93e0531c0f78db435 apache2_2.2.22-13+deb7u5+sf1_amd64.deb b6c281ae8a89d94148e131493cca5db21a76734ca8801528d2e491a27e99e76c apache2_2.2.22-13+deb7u5+sf1.debian.tar.xz 2a2ff9d027749ecbc5fa7d0c113edc126c87c03e7ffe01f2a0a75672d986a93e apache2_2.2.22-13+deb7u5+sf1.dsc 74c1efe1a502339b004ad6488fbd858eb425a05968cd67c05695dbc0fe7c apache2_2.2.22.orig.tar.gz 2894f0f911db55cb39db46537020b17013c0f66a58a52d788699c65002ac58bd apache2.2-bin_2.2.22-13+deb7u5+sf1_amd64.deb 5ab19208f949bc5897c7b6e5f3115bae3083f2dc91d4149783e164de23ff13d1 apache2.2-common_2.2.22-13+deb7u5+sf1_amd64.deb ee019865f50f5b39db85da152316aa8a3f636321f52b01b66b4b99ff3508e510 apache2-dbg_2.2.22-13+deb7u5+sf1_amd64.deb 1aacf94ba56b86484dc1eb593ba3425880555e83448ed9f2a6e6a0568c8424f2 apache2-doc_2.2.22-13+deb7u5+sf1_all.deb 2de2b0ac2cd21b98b13703cacdd6ed44bb7758aeeecf7d6194e0197fc717c3ac apache2-mpm-event_2.2.22-13+deb7u5+sf1_amd64.deb e26b9a4bffebe7151535da515691a141b6930a2672b8fe5d640f6d0988ee7218 apache2-mpm-itk_2.2.22-13+deb7u5+sf1_amd64.deb fd8216542a06af4461ae42c58736c2a97dc9f211b91477da12d196c64a0854a6 apache2-mpm-prefork_2.2.22-13+deb7u5+sf1_amd64.deb ad986acc97024990ee5a2d70a5fb7fb421682499d553b9bd18836edfdf8ed8b0 apache2-mpm-worker_2.2.22-13+deb7u5+sf1_amd64.deb d0e01faaa22614bc4a794568531036a53af77128ddc7063576560a3fb0ddbaf6 apache2-prefork-dev_2.2.22-13+deb7u5+sf1_amd64.deb 9c023cd686801ed9d5c53008514fd6a29188a5adb182faeaa07362aac5e7172f apache2-suexec_2.2.22-13+deb7u5+sf1_amd64.deb e9b1994182a6fe07ae975757875281a7278bcf272eeff98eaa3138cb0207a7b7 apache2-suexec-custom_2.2.22-13+deb7u5+sf1_amd64.deb 5feb8f4fcd5c923a4c89467d22483403eb341f46c15fa090ad5c428978c554e6 apache2-threaded-dev_2.2.22-13+deb7u5+sf1_amd64.deb d8b5d69947a2f3ac7a38400dd9b6418b0adf64d6bf91b23f7c379a919fc93418 apache2-utils_2.2.22-13+deb7u5+sf1_amd64.deb ff52cfb9f762ef33b8a7831b61070b08b7140a784be6950ab73561237419007d mod_ssl.so signature.asc Description: This is a digitally signed message part.
Bug#791077: imagemagick: library transition may be needed when GCC 5 is the default
On Fri, Aug 7, 2015 at 11:28 PM, Matthias Klose d...@debian.org wrote: Control: tags -1 + confirmed patch Control: severity -1 serious Control: retitle -1 imagemagick: library transition is needed when GCC 5 is the default On 08/07/2015 07:42 PM, Andreas Metzler wrote: I have just tried rebuilding imagemagick_6.8.9.9-5 on sid (g++ 5.2.1-14), as expected it fails at dpkg-gensymbols. Iam attaching both the full error message attached and the newly generated symbol file debian/libmagick++-6.q16-5/DEBIAN/symbols. Since we find e.g. - (c++)Magick::Blob::base64()@Base + _ZN6Magick4Blob6base64B5cxx11Ev@Base I assume imagemagick needs a transition. confirmed, attaching a patch. however first ilmbase needs a transition, and then openexr, before you can start this one. Feel free to do a NMU or push experimental version to unstable (experimental version has libmagick++-6). At your choice. My usual sponsor is on VAC Bastien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794909: libcolpack0v5: missing Breaks/Replaces against libcolpack0
Package: libcolpack0v5 Version: 1.0.9-3.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libcolpack0v5:amd64. Preparing to unpack .../libcolpack0v5_1.0.9-3.1_amd64.deb ... Unpacking libcolpack0v5:amd64 (1.0.9-3.1) ... dpkg: error processing archive /var/cache/apt/archives/libcolpack0v5_1.0.9-3.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libColPack.so.0.0.0', which is also in package libcolpack0:amd64 1.0.9-3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libcolpack0v5_1.0.9-3.1_amd64.deb cheers, Andreas libcolpack0=1.0.9-3_libcolpack0v5=1.0.9-3.1.log.gz Description: application/gzip
Bug#793215: antlr: change of type in system_error might break with GCC-5
Hey. Anything new here? That blocks upgrading to to current libstdc++6 (without removing a large number of packages) and thus also prevents other packages (that already depend on newer libstdc++6) with important security updates to be installed. Shouldn't the severity been raised, as the package is unistallable? Cheers, Chris smime.p7s Description: S/MIME cryptographic signature
Bug#777833: digikam: ftbfs with GCC-5
Hey. Anything new here? That blocks upgrading to to current libstdc++6 (without removing a large number of packages) and thus also prevents other packages (that already depend on newer libstdc++6) with important security updates to be installed. Cheers, Chris smime.p7s Description: S/MIME cryptographic signature
Bug#791240: pktools: symbols file update needed for GCC 5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07-08-15 22:51, Ross Gammon wrote: On Fri, 7 Aug 2015 21:20:57 +0100 Dimitri John Ledkov wrote: So it should also be possible to install libdap now, as I discovered the bug had not been closed properly in the changelog (now closed manually). As long as the libdap transition (#791114) has not started libstdc++6 breaks the version in unstable: The following packages have unmet dependencies: libstdc++6 : Breaks: libdap17 (= 3.14.0-2) but 3.14.0-2 is to be installed. Breaks: libdapclient6 (= 3.14.0-2) but 3.14.0-2 is to be installed. Breaks: libdapserver7 (= 3.14.0-2) but 3.14.0-2 is to be installed. We need to wait to for the Release Team to give the go-ahead to start the libdap transition before the fixed version of libdap should arive in unstable. Kind Regards, Bas - -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVxSE2AAoJEGdQ8QrojUrxWcAP/jMmhipGAuj6GoLdZUMGy1o/ hooxDTkYGS6srKdiMvDGPngibxzLdeGZhvjfPN3rmdvwPT49zmWLTCZu7B6XfVq3 75brPbr/0n2CfJ9Nkqw4kt1zptmcUetqx5t6EwG6EwekrZZ02Fdvfa5avGi8+wtf AQxadsTGAjCZkGN1QLkkyT4BG7f0u7Mr/K9GHTqM4iq/fnByw7HSJZ33EOssvXGb EhZcJPuVukQ5/dM5mbmW1MyVAq1KDNn7H7mpbXQA1w7fzwmnW4KbCKoI/+wHsi5T Ojuw2kzByJZTzFNgr0PnW4Jm7VvJpxDqmImmyohdPbTOJ7PHroLtiLRxSWzahU5m 1ImeU0Nl3zaXAl3f3J5Vb1WCFQBnH9qRqSl6qZazUrP5ficgFfkb8EAJJdTbU7jX 4CE5VNfVn5qu9m2pYqrdbIDze3s+0+rK51wCaUZGTOecwK6zzdgwCu9l2ep+DI95 IjPghfSHt0xBdWahW97sUUtLx9n9mwVIFnO7L0dZYQRDufBCZgGvAsEYQYmAj7S7 uB9j9iiFKk6drYliadHe6hiZ3b/g688Tu1pUumeKInyBz0V+y+ImZaPM9NDEBpse lvb9ui42mxcdTS9MX6ALV/cHjpxFLqepDQ9P7NvY2esMcpkldx0yN/D5PZPJ46g+ QbMaPXwk+1JqcwnZl8Ym =GPxG -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794905: llvm-3.7-dev: Incorrect install prefix in installed LLVMConfig.cmake
Package: llvm-3.7-dev
Version: 1:3.7~+rc2-2
Severity: normal
Tags: patch
Dear Maintainer,
The LLVM_INSTALL_PREFIX variable set by LLVMConfig.cmake wrongly
assumes that the installed CMake configuration files are in a
subdirectory of the actual LLVM installation. The Debian package moves
the CMake configuration files to /usr/share/llvm-VERSION/, so this
assumption is not correct.
The way that the LLVM_INSTALL_PREFIX variable is determined has
changed in LLVM 3.7, and this issue for Debian was pointed out (along
with a proposed fix) by Brad King, here:
http://thread.gmane.org/gmane.comp.compilers.llvm.cvs/255502/focus=25574
The attached patch resolves this by essentially using the same
mechanism to determine LLVM_INSTALL_PREFIX as was used in LLVM
3.6. The resulting changes to the generated LLVMConfig.cmake match the
changes proposed by Brad above.
Many thanks,
James
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.1.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages llvm-3.7-dev depends on:
ii libc6 2.19-19
ii libedit2 3.1-20150325-1
ii libffi-dev 3.2.1-3
ii libffi63.2.1-3
ii libgcc11:5.2.1-14
ii libjsoncpp0v5 0.10.5-1
ii libllvm3.7 1:3.7~+rc2-2
ii libstdc++6 5.2.1-14
ii libtinfo-dev 5.9+20150516-2
ii libtinfo5 5.9+20150516-2
ii llvm-3.7 1:3.7~+rc2-2
ii zlib1g 1:1.2.8.dfsg-2+b1
llvm-3.7-dev recommends no packages.
llvm-3.7-dev suggests no packages.
-- no debconf information
--- a/cmake/modules/Makefile
+++ b/cmake/modules/Makefile
@@ -62,17 +62,9 @@
LLVM_CONFIG_CODE := \
\# Compute the CMake directory from the LLVMConfig.cmake file location.\n\
-get_filename_component(_LLVM_CMAKE_DIR $${CMAKE_CURRENT_LIST_FILE} PATH)\n\
-\# Compute the installation prefix from the LLVMConfig.cmake file location.\n\
-get_filename_component(LLVM_INSTALL_PREFIX $${CMAKE_CURRENT_LIST_FILE} PATH)\n
+get_filename_component(_LLVM_CMAKE_DIR $${CMAKE_CURRENT_LIST_FILE} PATH)\n
-# Compute number of levels (typically 3 - ``share/llvm/cmake/``) to PROJ_prefix
-# from PROJ_cmake, then emit the appropriate number of calls to
-# get_filename_components(). Note this assumes there are no spaces in the
-# cmake_path_suffix variable.
-cmake_path_suffix := $(subst $(PROJ_prefix),,$(subst $(DESTDIR),,$(PROJ_cmake)))
-cmake_path_dirs := $(subst /, ,$(cmake_path_suffix))
-LLVM_CONFIG_CODE += $(foreach __not_used,$(cmake_path_dirs),get_filename_component(LLVM_INSTALL_PREFIX $${LLVM_INSTALL_PREFIX} PATH)\n)
+LLVM_CONFIG_CODE += set(LLVM_INSTALL_PREFIX $(subst /,\/,$(PROJ_prefix)))\n
LLVM_CONFIG_CODE += set(_LLVM_LIBRARY_DIR $${LLVM_INSTALL_PREFIX}\/lib)
Bug#794906: uhd 3.8 ftbfs on arm64, 3.7 built fine before on arm64
Package: src:uhd Version: 3.8.5-1 Severity: serious Tags: sid stretch see https://buildd.debian.org/status/fetch.php?pkg=uhdarch=arm64ver=3.8.5-1stamp=1438910044 [ 19%] Building C object lib/CMakeFiles/uhd.dir/convert/convert_orc.c.o cd /«PKGBUILDDIR»/build/lib /usr/bin/cc -DHAVE_CONFIG_H -DUHD_DLL_EXPORTS -DUHD_IMAGES_DIR=OFF -DUHD_VERSION=30805 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -I/«PKGBUILDDIR»/build/include -I/«PKGBUILDDIR»/host/include -I/«PKGBUILDDIR»/build/lib/ic_reg_maps -I/usr/include/orc-0.4 -I/«PKGBUILDDIR»/host/lib/convert -I/«PKGBUILDDIR»/build/lib/convert -I/«PKGBUILDDIR»/build/lib/transport/nirio/lvbitx -I/usr/include/libusb-1.0 -I/«PKGBUILDDIR»/host/lib/usrp/cores -I/«PKGBUILDDIR»/host/../firmware/fx2/common -I/«PKGBUILDDIR»/host/lib/usrp/common -I/«PKGBUILDDIR»/host/lib/usrp/common/ad9361_driver-Wall -Wextra -Wsign-compare -o CMakeFiles/uhd.dir/convert/convert_orc.c.o -c /«PKGBUILDDIR»/build/lib/convert/convert_orc.c /«PKGBUILDDIR»/build/lib/convert/convert_orc.c: In function '_backup__convert_fc32_1_to_item32_1_nswap_orc': /«PKGBUILDDIR»/build/lib/convert/convert_orc.c:254:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (tmp == 0x8000 !(var38.x2[0]0x8000)) tmp = 0x7fff; ^ /«PKGBUILDDIR»/build/lib/convert/convert_orc.c:260:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (tmp == 0x8000 !(var38.x2[1]0x8000)) tmp = 0x7fff; ^ /«PKGBUILDDIR»/build/lib/convert/convert_orc.c: In function '_backup__convert_fc32_1_to_item32_1_bswap_orc': /«PKGBUILDDIR»/build/lib/convert/convert_orc.c:460:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (tmp == 0x8000 !(var38.x2[0]0x8000)) tmp = 0x7fff; ^ /«PKGBUILDDIR»/build/lib/convert/convert_orc.c:466:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (tmp == 0x8000 !(var38.x2[1]0x8000)) tmp = 0x7fff; ^ /«PKGBUILDDIR»/build/lib/convert/convert_orc.c: In function '_backup__convert_fc32_1_to_sc8_1_nswap_orc': /«PKGBUILDDIR»/build/lib/convert/convert_orc.c:1371:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (tmp == 0x8000 !(var37.x2[0]0x8000)) tmp = 0x7fff; ^ /«PKGBUILDDIR»/build/lib/convert/convert_orc.c:1377:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (tmp == 0x8000 !(var37.x2[1]0x8000)) tmp = 0x7fff; ^ /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/build/CMakeFiles -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794908: RFS: node-convert-source-map/1.1.1-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package node-convert-source-map * Package name: node-convert-source-map Version : 1.1.1-1 Upstream Author : Thorsten Lorenz thlor...@gmx.de * URL : https://github.com/thlorenz/convert-source-map/ * License : Expat Section : web It builds this binary package: node-convert-source-map - Converts a source-map from/to between formats To access further information about this package, please visit the following URL: http://mentors.debian.net/package/node-convert-source-map Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/node-convert-source-map /node-convert-source-map_1.1.1-1.dsc The packaging can be found here: http://anonscm.debian.org/cgit/pkg-javascript/node-convert-source-map.git Changes since the last upload: * New upstream release * Drop testsuite stanza as no longer required * Fix New Issues URL in metadata Regards, Ross Gammon -- System Information: Debian Release: jessie/sid APT prefers vivid-updates APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), (100, 'vivid-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-25-generic (SMP w/4 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) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794907: Please consider updating to version 5
Package: chronicle Version: 4.6-2 Severity: minor Hi! chronicle version 5 has been released a while ago and it seems to have quite some improvements! Would be great if the package could be updated! Christoph -- System Information: Debian Release: 8.0 APT prefers stable-kfreebsd APT policy: (990, 'stable-kfreebsd'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 10.1-0-amd64 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 chronicle depends on: ii libhtml-template-perl 2.95-1 ii libtimedate-perl 2.3000-2 ii perl 5.20.2-3 ii perl-modules 5.20.2-3 chronicle recommends no packages. Versions of packages chronicle suggests: ii libsoap-lite-perl 1.11-1 ii libtext-markdown-perl 1.0.26-1 pn libtext-textile-perl none ii libtext-vimcolor-perl 0.11-2 pn memcached none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644019: reglookup: Please package latest upstream (1.0.1)
On Mon, 08 Jun 2015, Raphael Hertzog wrote: we just tried the trunk. It's better but there are still multiple problems: - LDFLAGS is not used when you link the executables (it's only used when you link libregfi) - the default value for LDFLAGS is wrong, -z relro is an option for ld but when you pass it through gcc you need -Wl,-z,relro - I saw you tried to hack up some code to setup the SONAME... it does set the SONAME on the library but the library is still installed under the wrong name (libregfi.so instead of the name set in the SONAME) - the SONAME must not encode the full version... it's only a simple counter of API/ABI compatibility. Please use libregfi.so.0 as the first SONAME (and then bump to libregfi.so.1 when you break the ABI/API, etc.) (and 99.99.99.X looks really wrong as a version number :)) Tim, I hope you can fix those issues quickly now that we have identified how to properly handle versioned libraries and that you can make a new release. Hi Raphael, I finally had a chance to take another crack at this. I've attempted to address all of the items listed above. I integrated your guys' soname patch and tweaked it a bit to use a partial reglookup version number as the ABI version. The way it behaves right now is to assign 1.0.1 as the version when working from trunk. When working from a release version, it will use just the first two portions of the version (e.g. 1.0). The reason for this is that I don't change my API in minor point releases, but I typically do when the upper version numbers change. I did not integrate the other patch that strips python installs, since users need that if they compile from source. Can you simply run these two targest to achieve the same result? scons install_bin scons install_lib I fixed the two LDFLAGS issues you pointed out as well. Let me know if you think it is up to snuff now. Best, tim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794383: apache2: Upgrade to apache2-2.2.22-13+deb7u5 breaks CA certificate chain
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please try the version from https://people.debian.org/~sf/794383/ and check if it either fixes the problem or at least gives some more information in the error log. You may either replace all packages with dpkg or only the /usr/lib/apache2/modules/mod_ssl.so file by hand. I will try that after my holiday. Note that there were _no_ additional log entries. cheers Felicitus -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVxTBhAAoJEFfhxMvO1P2NcKsIAI9RwTQT3wwLmKq+fL5ehRn6 UwACgbHq042QyclbULj/u1NmH2RtZ60+HOstE1Cbh5Znox7JhW4ZJMGETHnYxyc8 SkNwFhH9nXHaXoQ2J8r5c20TYUHYtHvJ0T0u4iL7alDmkxdmlhnwHvwMnIBzRdwJ Cew3Z3W3ZR+oLDBtO39PhIv3yHt8VEqIfTtF/WWja4sd5223aa97TrRWirs1pWKA 8xXFsy60KCjO4eRpsoaOTnc8j/70avGJU+x6VxI2KGujGEX2UBlNGKKBlTaITW6P g67emr6MQ9b1lt4/i5Gvx5FX9+DhIAk6bYp6aZXuf3OKoIIoZ2AFj3GZnkt7g3s= =YOiJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793275: powertop: change of type in system_error might break with GCC-5
Hey. Anything new here? That blocks upgrading to to current libstdc++6 (without removing a large number of packages) and thus also prevents other packages (that already depend on newer libstdc++6) with important security updates to be installed. Shouldn't the severity been raised, as the package is uninstallable? Cheers, Chris smime.p7s Description: S/MIME cryptographic signature
Bug#789298: htmlcxx: FTBFS with glibc-2.21 and gcc-5
Control: tag -1 + patch On Fri, Jun 19, 2015 at 08:42:19AM -0700, Daniel Schepler wrote: From my pbuilder build log, using a setup preferring glibc and gcc-defaults packages from experimental: The patch provided for #791070 fixes this, but it involves a transition. Regards, Stephen signature.asc Description: Digital signature
Bug#794802: new version 0.4.5 pre release
Ciao, Am 07.08.2015 um 21:54 schrieb Davide Prina: On 07/08/2015 21:04, Markus Koschany wrote: On Thu, 06 Aug 2015 21:13:06 +0200 Davide Prina wrote: I'm aware of the new pre-release but I'm waiting for upstream to address some of my concerns [1] which will most likely happen soon. [1] https://github.com/freeorion/freeorion/issues/265 but the actual Debian version has a bug: [...] and Dilvish say he have solved it... I have played only 2-3 games and I found that bug only in the last one. I don't know I can ask in freeorion forum (this is a old debianized version) and also open a bug in Debian for a old version... If I find more time I will download the 4.5-pre-release source and try to check if this bug is solved. Feel free to report this as a separate bug report. But if Dilvish says it is fixed, this is probably the case. They intend to release the final 0.4.5 during the next weeks. I only wait for a new pre-release that fixes the issues which I have already reported upstream. If your problem persists with this version, please report back. Markus signature.asc Description: OpenPGP digital signature
Bug#663185: interested in (co-)maintaining midori
On Saturday, August 01 2015, Andres Salomon wrote: I'm interested in helping out with Midori packaging. I'm not sure who's still interested in the package at this point (I know Corsac isn't, so I didn't Cc him). I've created a git branch for the 0.5.10 release here: git://lunge.queued.net/git/midori http://lunge.queued.net/gitweb/?p=midori;a=shortlog;h=refs/heads/0.5.10 It builds (on sid and jessie) and runs (on jessie) for me, though it definitely needs more work tightening up deps, cleaning up lintian errors, etc. I'm happy to co-maintain the package, or take it over; whatever folks prefer. Please let me know what I should do, since it was never formally orphaned. I haven't heard anything regarding this, and it's been over a month. Should I just clean up my midori packages and upload? If I don't hear anything back and there's no activity with the package, that's my plan. Hi Andres, I saw your message only yesterday, sorry about that. As it turns out, I have also been working on getting Midori fixed. My intention is to maintain it; Thadeu Cascardo is going to help me take over the package. However, as you are also willing to co-maintain the package, maybe we could create a group on Alioth to work together? I also looked at your branch. What I am doing is basically a repackaging, from scratch, trying to figure out what's important and what's not. I'll publish my branch later today. So, any opinions on how to proceed? Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794830: [Aptitude-devel] Bug#794830: aptitude: segfaults in memory allocation
2015-08-07 14:11 GMT+01:00 Axel Beckert a...@debian.org: Hi, Matthijs van Duin wrote: I just noticed aptitude and libcwidget3v5 still depend on libsigc++-2.0-0c2a, shouldn't that be libsigc++-2.0-0v5 now? A cool, that has been fixed now, too! Yep, there is a libsigc++-2.0 transition upcoming: https://release.debian.org/transitions/html/auto-libsigc++-2.0.html Is this still a problem after being rebuilt after both cwidget and aptitude being rebuilt and depend on libsigc++-2.0-0v5? Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781165: ITP: prospector -- Python code analysis tool
Prospector is very close. The situation on the packages: A NMU for the pep8 update is in deferred uploads, pylint-celery is in NEW. Pylint 1.4 is in unstable (thanks very much!), and that would be it for the depends. Coming back to the recommends, Vulture is RFS [1], Frosted hangs in unstable waiting for python-pies [2], and no life sign on the ITP of Pyroma for now [3]. Prospector just exists telling that an extra isn't available if tried to run with, however, the tests like shipped want to work with them. I'll get into how they could be run without the extras becoming available whenever, that's not so important to have them all right now. Working on the package I've seen that the Sphinx docs use sphinx-argparse, which isn't available right now [4]. Plainbox has the proper plainbox.vendor.sphinxarg.ext, but only in a Python 3 package. However, not crucial. DS [1] https://bugs.debian.org/789699 RFS: vulture/0.6-1 [ITP,PAPT] [2] https://packages.qa.debian.org/f/frosted.html [3] https://bugs.debian.org/734121 ITP: pyroma -- tool to test Python project's packaging friendliness [4] https://bugs.debian.org/794776 ITP: sphinx-argparse -- Sphinx extension that documents argparse arguments and options -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794902: debian-policy: obsolete footnote about liblockfile1 dependency
Le Fri, Aug 07, 2015 at 10:38:15PM +0200, Jakub Wilk a écrit : A footnote in §11.6 reads: “You will need to depend on `liblockfile1 (1.01)' to use these [maillock and mailunlock] functions.” This seems to suggest hardcoding shared library dependency in debian/control, which is a bad idea. Anyway, liblockfile 1.01 was released in 1999, so no version constraint is necessary. Let's remove this footnote. Hi Jakub, good point, I agree. I think that this footnote is obsolete and can be removed. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793517: Fwd: fltk1.3_1.3.3-3_amd64.changes ACCEPTED into unstable
I've worked around both of these problems on my side for now for the sake of the GCC 5 transition, but may want to revisit them once that's settled down. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ---BeginMessage--- Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 07 Aug 2015 18:12:49 -0400 Source: fltk1.3 Binary: fluid libfltk1.3-dev libfltk1.3-compat-headers libfltk1.3 libfltk-cairo1.3 libfltk-forms1.3 libfltk-gl1.3 libfltk-images1.3 libfltk1.3-dbg fltk1.3-doc fltk1.3-games Architecture: source all amd64 Version: 1.3.3-3 Distribution: unstable Urgency: medium Maintainer: Aaron M. Ucko u...@debian.org Changed-By: Aaron M. Ucko u...@debian.org Description: fltk1.3-doc - Fast Light Toolkit - documentation fltk1.3-games - Fast Light Toolkit - example games: checkers, sudoku fluid - Fast Light Toolkit - user interface designer libfltk-cairo1.3 - Fast Light Toolkit - Cairo rendering layer support libfltk-forms1.3 - Fast Light Toolkit - Forms compatibility layer support libfltk-gl1.3 - Fast Light Toolkit - OpenGL rendering support libfltk-images1.3 - Fast Light Toolkit - image loading support libfltk1.3 - Fast Light Toolkit - main shared library libfltk1.3-compat-headers - Fast Light Toolkit - compatibility header symlinks libfltk1.3-dbg - Fast Light Toolkit - shared libraries with debugging symbols libfltk1.3-dev - Fast Light Toolkit - development files Changes: fltk1.3 (1.3.3-3) unstable; urgency=medium . * CMake/FLTKConfig.cmake.in: Include UseFLTK.cmake, which is responsible for defining FLTK_FLUID_EXECUTABLE. (Works around cmake-data bug #793549.) * debian/control (libfltk1.3-dev): Temporarily upgrade all recommendations and suggestions other than fltk1.3-doc to full dependencies, because cmake may well try to link against all of them. (See fgrun bug #793517.) Checksums-Sha1: b44053d3f4d5d84259e10bbdc6b9a726b5e5d51d 2744 fltk1.3_1.3.3-3.dsc 1714cfd7f484c4334bebad1716df1466ac6c228b 41400 fltk1.3_1.3.3-3.debian.tar.xz 9784ab84b279ce8fbb0cde86924645016a34fd61 8151496 fltk1.3-doc_1.3.3-3_all.deb 66474100b5db5c1d5004740dd75c49b8af7582a5 372766 fltk1.3-games_1.3.3-3_amd64.deb 6cdb3c5873e71f84bd5e638baa38ec0c10c51d21 199176 fluid_1.3.3-3_amd64.deb 91b9d3d72a12d7cc91047b171262e897b5a240e3 33822 libfltk-cairo1.3_1.3.3-3_amd64.deb 03e962f8c764ad24d4c913876ce9528bf1693f95 40300 libfltk-forms1.3_1.3.3-3_amd64.deb a8b3cea56ebad3182dbf1181845083caad2176f1 65154 libfltk-gl1.3_1.3.3-3_amd64.deb a971bdc987bbb1ed4149c58406f18cb12218fef5 52324 libfltk-images1.3_1.3.3-3_amd64.deb 6f6510a272deeeb1fca9e5b186caa7a85c436c9a 33278 libfltk1.3-compat-headers_1.3.3-3_all.deb 5a981001bef69ee1125c87e763ea572f3f265ab1 4325786 libfltk1.3-dbg_1.3.3-3_amd64.deb e50f20b0a2eac87e82f4b7c07f761fd16bb80815 818372 libfltk1.3-dev_1.3.3-3_amd64.deb 92818b953f6d9826c66a410e3695c67b93c1bff7 528292 libfltk1.3_1.3.3-3_amd64.deb Checksums-Sha256: 0823e86bc4b50dd910bc9bd8435b4181d97a453644c8ed7b1d7720263203c3af 2744 fltk1.3_1.3.3-3.dsc bcbbf78ff3245b990e99022c72d2dd8c6da75bb2c12b985f11b4445fdb4484a4 41400 fltk1.3_1.3.3-3.debian.tar.xz 2c22a3c701c800e4638d340ed03efcf91fa0b92918e6b9622ac80e47ddbb525b 8151496 fltk1.3-doc_1.3.3-3_all.deb 8d48fc792ce369eecffed484d6c6018675705ba94c4b8b6c1e4cba706ecff5bc 372766 fltk1.3-games_1.3.3-3_amd64.deb 506977e609b2aa8bdc6f1741f4c2ac4e413c887711a83991dfb5db31890da426 199176 fluid_1.3.3-3_amd64.deb be0f4f8b401a7d8fbe4df2ef3ff654c2da4775b0f9afa12eaf21055da50b0301 33822 libfltk-cairo1.3_1.3.3-3_amd64.deb e262211a99cfb8178e0ab8d08d3ab9825cd4f32c2fb7c0c69ce636d13f0af16c 40300 libfltk-forms1.3_1.3.3-3_amd64.deb c74cb736757620303c97442932828fe17355c9542d94d491b6c43df68663372c 65154 libfltk-gl1.3_1.3.3-3_amd64.deb db6abefd3c8931a2cdc2c82d4166982817b7ff7bdb389c2a17480dfc31de6e67 52324 libfltk-images1.3_1.3.3-3_amd64.deb c408fbc0bee054077898f77ef790c294c114ca81f9847a9959239fb5a6e0d6d5 33278 libfltk1.3-compat-headers_1.3.3-3_all.deb 68ac33a0f54e732be98a698561a3fe30ae4a3377b2422047973a0a45d8c4a7ee 4325786 libfltk1.3-dbg_1.3.3-3_amd64.deb 04d32329e752e89737d3f79a3eacb73ffd338bdfb14abac366cbf108b476cd2f 818372 libfltk1.3-dev_1.3.3-3_amd64.deb 92756a88fdf99b111eca89eab29c5ee9e6518893a3a3166f9b0cc5a8cf33ebf0 528292 libfltk1.3_1.3.3-3_amd64.deb Files: 6a6fce4ac7d51ae22e2059301b000628 2744 libs optional fltk1.3_1.3.3-3.dsc 8cc3258eeb5f304597b979a56a80b2f2 41400 libs optional fltk1.3_1.3.3-3.debian.tar.xz 42c457e140e8f1b784b33b997529e6b5 8151496 doc optional fltk1.3-doc_1.3.3-3_all.deb ab0731c151ac1907fbe9107bb78a1191 372766 games optional fltk1.3-games_1.3.3-3_amd64.deb cfd503921b8ba65866dacd8fb483d267 199176 devel optional fluid_1.3.3-3_amd64.deb 6f2ab4e3659f32db6f2d4917b106edb9 33822 libs optional libfltk-cairo1.3_1.3.3-3_amd64.deb 5d027c892c5948adc336632a215c6559 40300 libs optional
Bug#794581: /usr/bin/kwin_x11: crashes when starting first window
On Friday 07 August 2015 16:43:49 Diederik de Haas wrote: On Friday 07 August 2015 16:36:10 Maurizio Avogadro wrote: And I'm still wondering how could the small changes in breeze between -3 and -4 cause such issues... Updated build daemon with gcc-5 (I think) It is. It got caught by the gcc5 transition. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#794774: libstdc++6: Breaks: libboost-date-time1.55.0, but isn't that package fixed now?
Control: severity -1 important On 08/07/2015 09:11 PM, jnqnfe wrote: Control: severity -1 critical Control: tag -1 + security This dependency issue is now blocking installation of security updates on Sid (which many people use instead of stable, whether they should or not), specifically the emergency patch to iceweasel (CVE-2015-4495) in version 38.1.1esr-1. this is unfortunate, however there never was and is any commitment of unstable getting security fixes. The issue is not fixed by any upload of boost1.55 built with GCC 4.9, and it won't build with GCC 5. An update to 1.57 or 1.58 is required. If you need to have such an update in testing, then you should ask for an upload to testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794910: libmovit2v5: missing Breaks/Replaces against libmovit2
Package: libmovit2v5 Version: 1.1.3-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libmovit2v5:amd64. Preparing to unpack .../libmovit2v5_1.1.3-2_amd64.deb ... Unpacking libmovit2v5:amd64 (1.1.3-2) ... dpkg: error processing archive /var/cache/apt/archives/libmovit2v5_1.1.3-2_amd64.deb (--unpack): trying to overwrite '/usr/share/movit/header.130.frag', which is also in package libmovit2:amd64 1.1.3-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libmovit2v5_1.1.3-2_amd64.deb cheers, Andreas libmovit2=1.1.3-1_libmovit2v5=1.1.3-2.log.gz Description: application/gzip
Bug#792200: closed by Vincent Cheng vch...@debian.org (Re: Bug#792200: RFS: roxterm/3.0.2-1)
Hi Tony, On Thu, Aug 6, 2015 at 5:11 AM, Tony Houghton h...@realh.co.uk wrote: Hi, I got emails saying that roxterm 3.0.1-1 and then 3.0.2-1 were uploaded and the RFS bugs closed (the latter on 13 July), but the latest version showing up in the archives is still 2.9.5-1. Has something gone wrong with the upload? roxterm 3.0.1-1 and 3.0.2-1 introduced new binary packages, so they have to go through the NEW queue [1] and be manually approved by ftpmasters. Regards, Vincent [1] https://ftp-master.debian.org/new.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794237: openconnect: Does not work with network-manager 1.0.4
On Thu, 2015-08-06 at 12:29 +0100, David Woodhouse wrote: On Thu, 2015-08-06 at 14:18 +0300, Matti Koskimies wrote: Pinging doesn't work, but I don't expect it to in our network. Oh? Your network is infested by idiot admins who like to block ICMP? That's almost certainly relevant. Instead, I used netcat for port pinging the ssh port: $ nc -znvw1 172.24.38.144 22 Connection to 172.24.38.144 22 port [tcp/*] succeeded! $ Despite this, the ssh command just hangs. This is a typical symptom of the above-mentioned 'idiot admin' problem. If you do a packet capture, do you find that the connection hangs the moment the SSH server wants to send you a full-sized packet? Which presumably doesn't fit through the VPN, so the VPN server sends back an ICMP packet to the server telling it to send a smaller one... and the VPN server never receives it because of the aforementioned idiot admins. So the SSH server just keeps sending the too-large packets. which never get through. You normally get away with this when you are connecting directly from the VPN client host (as opposed to a virtual machine running thereon). Because the TCP connection setup will indicate an MSS value which *will* fit in the MTU for the immediately local connection. Can you show that packet capture? And try *reducing* your MTU on the VPN interface (tun0) and see if that works? And go and punch one of the idiots for me. :) I just might do that... The MTU value of the tun0 device created when using openconnect on the command line was 1200. It was 1500 for the vpn0 device created using network-manager-openconnect. So I reduced the mtu value to 1200 and voilà, everything works fine! Can I somehow make this setting permanent? -- Matti K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794704: viva: FTBFS
On Thu, Aug 06, 2015 at 12:38:41PM +0200, Tobias Frost wrote: Hi Martin, Thanks for the reply! can you check if the workaround would solve this; Maybe a quick fix would help to get the libconfig transition forward faster, as a new upstream version takes lots more time... I will need to wait for tomorrow night as I have no good connexion here. I'm not even sure of when this mail will get out of my box :( Sorry, Mt -- You have a problem and decide to use floats. Now you have 2.0001 problems. -- Old Computer Engineers saying signature.asc Description: Digital signature
Bug#794836: python3-sphinxcontrib.youtube: Fails to run because dict.iteritems() does not exist in Python 3
Package: python3-sphinxcontrib.youtube Version: 1.0-1 Severity: important Tags: patch Dear Maintainer, Using the python3 version of sphinxcontrib.youtube fails with the following error when building the sphinx project: Exception occurred: File /usr/lib/python3/dist-packages/sphinxcontrib/youtube.py, line 22, in css return ; .join(sorted(%s: %s % kv for kv in d.iteritems())) AttributeError: 'dict' object has no attribute 'iteritems' iteritems() was removed in Python 3 and is to be replaced with items() The following change in /usr/lib/python3/dist-packages/sphinxcontrib/youtube.py fixes the problem: 22c22 return ; .join(sorted(%s: %s % kv for kv in d.iteritems())) --- return ; .join(sorted(%s: %s % kv for kv in d.items())) Torsti -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-sphinxcontrib.youtube depends on: ii python3-sphinx 1.2.3+dfsg-1 pn python3:any none python3-sphinxcontrib.youtube recommends no packages. python3-sphinxcontrib.youtube suggests no packages. 22c22 return ; .join(sorted(%s: %s % kv for kv in d.iteritems())) --- return ; .join(sorted(%s: %s % kv for kv in d.items()))
Bug#794562: 0ad: Test 0ad with new version of nvidia-texture-tools
I went through all the added patches and removed all those which were already included in upstream. That left me with mostly debian related patches[0] which he doesn't want applied upstream. issue188 - still have that one clang-cpp11 - doesn't really apply to debian but I will probably include it anyhow to avoid any future bugs. or report it upstream to get it added to a release rpath - don't think that applies to dynamic libraries and therefore this package cmake-dev* - those patches basically just add some switches to look for certain libraries. i think we can work with upstream here as we only built with a dfsg setup on debian which means no cuda or cg anyway. I'll try to get upstream to release a new version of nvtt so I can get a clean release for the new package. [0]http://anonscm.debian.org/cgit/collab-maint/nvidia-texture-tools.git/tree/debian/patches On 2015-08-07 03:16, Vincent Cheng wrote: On Thu, Aug 6, 2015 at 6:06 PM, Vincent Cheng vch...@debian.org wrote: Here's some feedback from upstream (freenode #0ad-dev): s/freenode/quakenet/ of course -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790655: python3-pygithub, remove the package?
Hi Dmitry, cd /home/users/kaction-guest/repository/mini-dinstall/incoming/ -bash: cd: /home/users/kaction-guest/repository/mini-dinstall/incoming/: Permission denied cd /var/lib/gforge/chroot/home/users/kaction-guest/repository/mini-dinstall/incoming/ -bash: cd: /var/lib/gforge/chroot/home/users/kaction-guest/repository/mini-dinstall/incoming/: Permission denied I guess I have no enough permissions to see the file :) (it is fine to append the debian directory.tar.xz to a mail, with the bug in cc if you want :) ) cheers, G. Il Giovedì 6 Agosto 2015 19:09, Dmitry Bogatov kact...@gnu.org ha scritto: * Gianfranco Costamagna costamagnagianfra...@yahoo.it [2015-08-06 08:59:21+] Okay. mentors gives me 500 error, probably it dislikes Tor. I will investigate, but now to keep things fast you can git clone git://anonscm.debian.org/users/kaction-guest/pygithub.git and NMU it. Also, I can violate nettiqette *hard* and email packaging to you. thanks a lot, but I leave the decision to you. I found new solution: please get package from alioth (~kaction-guest/repository/mini-dinstall), review (changes are trivial, but still) and upload it. If I am correct, it will avoid NMU. -- Accept: text/plain, text/x-diff Accept-Language: eo,en,ru X-Keep-In-CC: yes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794817: Should mplayer2 be removed from unstable?
Quoting Sebastian Ramacher (2015-08-07 03:19:29) On 2015-08-06 23:05:58, Andreas Cadhalpun wrote: I think mplayer2 should be removed because: * It is dead upstream (even the homepage is gone). * mplayer is back in Debian, which can replace mplayer2. … and one copy of mplayer is surely enough. Alessio, Jonas, Reinhard: What is your opinion on that? Suggestion sounds sensible, but my opinion shouldn't carry much weight, as I don't follow those packages in particular: I've moved to mpv as my favored media player. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#791829: new upstream
Hi Harald, I'll try to upload it this evening or tomorrow. Thanks, Alberto On Thu, Aug 06, 2015 at 09:26:51PM +0200, Harald Dunkel wrote: 2.3.8 came out, fixing the askpass option. Please mail if I can help to verify a new package. Regards Harri -- Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico mailto/sip: a...@inittab.org | en GNU/Linux y software libre Encrypted mail preferred| http://inittab.com Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D 4BF2 009B 3375 6B9A AA55 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794833: /usr/bin/xflock4: xflock4 sometimes calls slock after wakeup despite xscreensaver running
Package: xfce4-session Version: 4.10.1-10 Severity: normal File: /usr/bin/xflock4 Dear Maintainer, Sometimes, after my system wakes up from suspend/hibernate, xscreensaver locks the screen, then, after I unlock it (too fast?) slock runs and locks the screen again. I failed to obtain any error messages from xscreensaver (there are none in ~/.xsession-errors after the event), sorry for that. Feel free to reassign to xscreensaver if you think the problem is its fault, not xflock4's. Best regards, Ivan -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-session depends on: ii libatk1.0-02.14.0-1 ii libc6 2.19-18 ii libcairo2 1.14.0-2.1 ii libdbus-1-31.8.18-0+deb8u1 ii libdbus-glib-1-2 0.102-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-3 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-02.24.25-3 ii libice62:1.0.9-1+b1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpolkit-gobject-1-0 0.105-8 ii libsm6 2:1.2.2-1+b1 ii libwnck22 2.30.7-2 ii libx11-6 2:1.6.2-3 ii libxfce4ui-1-0 4.10.0-6 ii libxfce4util6 4.10.1-2 ii libxfconf-0-2 4.10.0-3 ii multiarch-support 2.19-18 ii xfce4-settings 4.10.1-2 ii xfconf 4.10.0-3 Versions of packages xfce4-session recommends: ii dbus-x11 1.8.18-0+deb8u1 ii libpam-systemd 215-17+deb8u1 ii systemd-shim 9-1 ii systemd-sysv 215-17+deb8u1 ii upower 0.99.1-3.2 ii x11-xserver-utils 7.7+3+b1 ii xfdesktop4 4.10.2-3 ii xfwm4 4.10.1-3 ii xscreensaver 5.30-1+b1 Versions of packages xfce4-session suggests: pn fortunes-mod none ii sudo 1.8.10p3-1+deb8u2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
