Bug#745347: ITP: releases -- A Sphinx extension for changelog manipulation
I'll gladly rename the package and try again. Since I got no official rejection AFAIR from any ftp-master, should I just do the rename and seek another sponsorship upload? Thanks ZK On Wed, Jun 11, 2014 at 12:42 PM, Guillem Jover guil...@debian.org wrote: Hi! On Mon, 2014-04-21 at 15:19:38 +0100, Steve Cotton wrote: On Mon, Apr 21, 2014 at 14:05 +0200, Zygmunt Krynicki wrote: I saw the package being uploaded to NEW just a moment ago. I could rename it to python-releases (I don't think there's a standard naming scheme for sphinx extensions yet). What do you think? I find python-releases confusing in the same way. If I saw Bug #xx is in stable python-releases but fixed in unstable python-releases. then I'd understand that it was a bug in the python2.7 python3.2 packages, not a bug in a package called python-releases. I prefer a name that doesn't look like the name of another package followed by the word releases. Maybe python-releaseslog. Or python-sphinx-releases, python-sphinx.releases or something like that, there's few precedents for the former on the archive already. I think it would be nice to discuss this on the debian-python list to try to come to an agreement on the namespace, because simply using the non-namespaced upstream module name is really not good for the overall distribution. Please make sure to rename both binary and *source* packages. Note: I'm not a DD, if no DD is complaining then maybe it's not confusing. I just saw it in NEW and I've to agree it is very confusing. I think people might usually notice when it's already in the archive which implies going through NEW again, package removal requests, possibly transitional packages, etc, which might deter them from mentioning it or filing bug reports. IMO the ftp-masters are not rejecting enough packages when it comes to namespace problems. Thanks, Guillem
Bug#751241: amule: Please update to use wxwidgets3.0
Source: amule Version: 2.3.1-11 Severity: important Tags: sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wx3.0 Control: block 748169 by -1 Dear maintainer, We're aiming to migrate the archive to using wxwidgets3.0 instead of wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released. I've attempted to rebuild amule by updating the BD to libwxgtk3.0-dev and wx3.0-i18n, but the build fails. It looks like the major issue is that it's not possible to include a wx header to get class wxExecuteData defined. I've reported that to wx upstream: http://trac.wxwidgets.org/ticket/16325 If upstream don't come up with a fix quickly, we can probably just install the required private header in the wx headers directory to work around the problem. I ran the build with debian/rules patched to use make -k, so as to show all the compilation errors, and the only one not related to wxExecuteData seems to be: ../../src/amuled.cpp:656:15: error: variable 'wxFFile ff' has initializer but incomplete type That sounds like it's just missing including the right header. While building without errors doesn't necessarily mean it will work, this seems quite promising, aside from the wxExecuteData issue. Do you know what plans amule upstream have for wx3.0 support? I've tried to check their website, but it just gives a page saying the site is down due to server migration, with a link to the downloads page, and another to a forum which is 404. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748383: ITP: bash8 -- bash script style guide checker
Hi!
On Sat, 2014-05-17 at 09:49:04 -0400, Thomas Goirand wrote:
On Sat May 17 2014 07:46:16 AM EDT, Ben Finney b...@benfinney.id.au wrote:
Certainly ‘bash8’ carries no reliable connotation of “style checker for
Bash code”.
This is a reference to pep8 in the Python.
In the Python community, “PEP 8” carries strong connotation of “code
style conventions for Python code”. It is *only* because of that
existing connotation that a package named ‘pep8’ implies what the
package installs.
The same is not true for the name ‘bash8’. It is unreasonable to expect
the average Bash user looking at package names to get a reference to
Python conventions.
IMO, the package (source and binary) name should more explicitly carry
an implication of what the package installs. Perhaps
‘bash8-style-checker’ or the like.
It's ok, since the resulting binaries will be
python{3,}-bash8. Our users don't get exposed
much to source package names, so I think it's ok
for me to choose bash8 as name to follow the one
upstream, though if you want I can use python-bash8.
I've to agree with the other people complaining, the name is very
confusing and as it is, it's a namespace grab. Prefixing it with
«python-» only clarifies slightly, but at least it stops somewhat
being a namespace grab, but it is still quite confusing. Please try
to convince upstream to rename it, and do so in Debian regardless.
Something like python-bash-pep8-style-checker would seem acceptable
to me, there's probably better, shorter names that could be used
though, maybe python-pep8-style-bash, or simply python-pep8-bash.
With the «python3?-» prefix being a distribution specific thing.
Also just following upstream when it comes to naming be it for source
or binary packages is not wise in many cases. Lots of upstreams create
packages or language modules in language silos, where those names are
implicitly namespaced by being part of that language community/portal
for example. Having Http be a perl module is fine, the same for a
python or ruby module, not so much when it comes to integrating it
in a general purpose distribution. Why should the http source package
name be the perl implementation? Even if that source provided modules
for many languages, why should it take over the canonical protocol
name for its source package? Also the source package name is really
pretty visible in many places in the distribution.
The current practice of many python modules to just use the upstream
name as the source package name is a namespace grab, wrong and unfair
to the rest of the distribution, some quick examples to illustrate:
appdirs argvalidate audioread distlib
I wish other language teams in Debian followed the perl lead here.
Thanks,
Guillem
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729134: (no subject)
hello! after yesterday's update (haven't updated for some time before, though) i've faced not working reboot/shutdown buttons if xfce too. reading some discussions here, i've tried to play with libpam-systemd disabling and removal. and what i found: - disabling libpam-systemd thru pam-auth-update or commenting it out doesn't help - removing libpam-systemd and policykit-1 along with it solves the problem - installing libpam-systemd alone breaks nothing! - installing policykit-1 is what breaks the things! i tried commenting out the whole /etc/pam.d/polkitd and killing polkitd. but that didn't help. i also don't understand who run polkitd, pstree raise it straight to init(1). policykit-1 package has nothing intersting in postinst triggers, so the problem is in one of it's files (smth like /var/lib/polkit-1/blah-blah-blah or whatever) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751242: libpetsc3.4.2-dbg: please recompile with new default gfortran version, to get mod file versions right
Package: libpetsc3.4.2-dbg Version: 3.4.2.dfsg1-8 Severity: important Dear Maintainer, with version 1.128 of gcc-defaults, gfortran now defaults to 4.9, which has a different mod file version. Since libpetsc3.4.2-dbg installs the file /usr/lib/petscdir/3.4.2/linux-gnu-c-debug/include/petscdmdadef.mod, it has to be recompiled with the gcc suite 4.9 to make it compatible with the version of gfortran which is now the default. Fixing This should involve no changes, just a plain rebuild of the package, therefore relatively painless for you. Thanks in advance, bye Giacomo Mulas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705618: Found in 3.2.57-3+deb7u2
Control: found -1 linux/3.2.57-3+deb7u2 Apparently I started hitting this bug after upgrading to the latest security update. I haven't seen this before, so this has a slight regressiony odor. This seems to be triggered somewhat differently from the original report, there is NFSD: failed to write recovery record (err -17); please check that /var/lib/nfs/v4recovery exists and is writeable just before the stall warning (/var/lib/nfs/v4recovery does exist and is writeable). Backtrace attached. Jun 11 10:59:46 debian kernel: [ 110.779247] NFSD: failed to write recovery record (err -17); please check that /var/lib/nfs/v4recovery exists and is writeable Jun 11 10:59:46 debian kernel: [174423.780044] INFO: rcu_bh detected stall on CPU 6 (t=0 jiffies) Jun 11 10:59:46 debian kernel: [174423.780157] sending NMI to all CPUs: Jun 11 10:59:46 debian kernel: [174423.780168] NMI backtrace for cpu 0 Jun 11 10:59:46 debian kernel: [174423.780171] CPU 0 Jun 11 10:59:46 debian kernel: [174423.780173] Modules linked in: cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave sha1_generic hmac cryptd aes_x86_64 aes_generic cbc cts rpcsec_gss_krb5 nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc ext2 mbcache loop radeon ttm drm_kms_helper drm power_supply i2c_algo_bit nv_tco snd_pcm snd_page_alloc snd_timer snd soundcore k10temp i2c_nforce2 evdev psmouse amd64_edac_mod pcspkr shpchp i2c_core edac_mce_amd edac_core powernow_k8 serio_raw mperf processor button thermal_sys xfs raid1 md_mod sg sr_mod cdrom sd_mod crc_t10dif ata_generic ohci_hcd pata_amd sata_nv ehci_hcd forcedeth usbcore libata scsi_mod usb_common [last unloaded: scsi_wait_scan] Jun 11 10:59:46 debian kernel: [174423.780221] Jun 11 10:59:46 debian kernel: [174423.780225] Pid: 1450, comm: apache2 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.57-3+deb7u2 Supermicro H8DMR-82/H8DMR-82 Jun 11 10:59:46 debian kernel: [174423.780229] RIP: 0033:[7ff938106e45] [7ff938106e45] 0x7ff938106e44 Jun 11 10:59:46 debian kernel: [174423.780237] RSP: 002b:7fff5ef6d4c8 EFLAGS: 0202 Jun 11 10:59:46 debian kernel: [174423.780239] RAX: 7ff93d32bd70 RBX: 7ff93d31eed0 RCX: 00545345 Jun 11 10:59:46 debian kernel: [174423.780241] RDX: RSI: 7ff93d31e9e0 RDI: 7ff93d31eed0 Jun 11 10:59:46 debian kernel: [174423.780243] RBP: 7ff93d31e9e0 R08: 7ff93d32b9e0 R09: 544c4790 Jun 11 10:59:46 debian kernel: [174423.780245] R10: 0075 R11: 7ff93d31ea60 R12: 539810b8 Jun 11 10:59:46 debian kernel: [174423.780247] R13: R14: 7ff93d32bd70 R15: 7ff93cf1c430 Jun 11 10:59:46 debian kernel: [174423.780250] FS: 7ff93c377740() GS:88011fc0() knlGS: Jun 11 10:59:46 debian kernel: [174423.780252] CS: 0010 DS: ES: CR0: 80050033 Jun 11 10:59:46 debian kernel: [174423.780254] CR2: 7ff93d380bc0 CR3: 000107449000 CR4: 06f0 Jun 11 10:59:46 debian kernel: [174423.780256] DR0: DR1: DR2: Jun 11 10:59:46 debian kernel: [174423.780258] DR3: DR6: 0ff0 DR7: 0400 Jun 11 10:59:46 debian kernel: [174423.780261] Process apache2 (pid: 1450, threadinfo 880103b68000, task 88011ab57740) Jun 11 10:59:46 debian kernel: [174423.780263] Jun 11 10:59:46 debian kernel: [174423.780264] Call Trace: Jun 11 10:59:46 debian kernel: [174423.780268] NMI backtrace for cpu 6 Jun 11 10:59:46 debian kernel: [174423.780273] CPU 6 Jun 11 10:59:46 debian kernel: [174423.780277] Modules linked in: cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave sha1_generic hmac cryptd aes_x86_64 aes_generic cbc cts rpcsec_gss_krb5 nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc ext2 mbcache loop radeon ttm drm_kms_helper drm power_supply i2c_algo_bit nv_tco snd_pcm snd_page_alloc snd_timer snd soundcore k10temp i2c_nforce2 evdev psmouse amd64_edac_mod pcspkr shpchp i2c_core edac_mce_amd edac_core powernow_k8 serio_raw mperf processor button thermal_sys xfs raid1 md_mod sg sr_mod cdrom sd_mod crc_t10dif ata_generic ohci_hcd pata_amd sata_nv ehci_hcd forcedeth usbcore libata scsi_mod usb_common [last unloaded: scsi_wait_scan] Jun 11 10:59:46 debian kernel: [174423.780393] Jun 11 10:59:46 debian kernel: [174423.780401] Pid: 0, comm: swapper/6 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.57-3+deb7u2 Supermicro H8DMR-82/H8DMR-82 Jun 11 10:59:46 debian kernel: [174423.780413] RIP: 0010:[811b57ca] [811b57ca] __bitmap_empty+0xa/0x52 Jun 11 10:59:46 debian kernel: [174423.780434] RSP: 0018:88021fd03e20 EFLAGS: 0012 Jun 11 10:59:46 debian kernel: [174423.780440] RAX: 0008 RBX: 2710 RCX: 0040 Jun 11 10:59:46 debian kernel: [174423.780446] RDX: RSI: 0200 RDI: 8168eb40 Jun 11 10:59:46 debian kernel: [174423.780452]
Bug#729134: (no subject)
On mer., 2014-06-11 at 15:53 +0400, dimas wrote: hello! after yesterday's update (haven't updated for some time before, though) i've faced not working reboot/shutdown buttons if xfce too. reading some discussions here, i've tried to play with libpam-systemd disabling and removal. and what i found: - disabling libpam-systemd thru pam-auth-update or commenting it out doesn't help - removing libpam-systemd and policykit-1 along with it solves the problem - installing libpam-systemd alone breaks nothing! - installing policykit-1 is what breaks the things! i tried commenting out the whole /etc/pam.d/polkitd and killing polkitd. but that didn't help. i also don't understand who run polkitd, pstree raise it straight to init(1). policykit-1 package has nothing intersting in postinst triggers, so the problem is in one of it's files (smth like /var/lib/polkit-1/blah-blah-blah or whatever) Try to install systemd-shim or systemd-sysv (which will make systemd your init system). Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#751241: amule: Please update to use wxwidgets3.0
On Wed, Jun 11, 2014 at 11:46:49PM +1200, Olly Betts wrote: Do you know what plans amule upstream have for wx3.0 support? I've tried to check their website, but it just gives a page saying the site is down due to server migration, with a link to the downloads page, and another to a forum which is 404. I had a look in the wayback machine, and it's been like that since September 2012! https://web.archive.org/web/20120919013043/http://www.amule.org/ And the last release looks like it was made 2011-11-11 - the two together make me wonder if amule is in fact dead upstream. If so, is it worth trying to keep it in Debian? To do so, you're essentially going to need to take over the work upstream would normally do... Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751243: libetsf-io-dev: wrong module version for new default gfortran (4.9)
Package: libetsf-io-dev Version: 1.0.3-4+b1 Severity: important Dear Maintainer, with version 1.128 of gcc-defaults, gfortran now defaults to 4.9, which has a different mod file version. Since libetsf-io-dev installs the file /usr/include/etsf_io_file.mod, it has to be recompiled with the gcc suite 4.9 to make it compatible with the version of gfortran which is now the default. Fixing This should involve no changes, just a plain rebuild of the package. Thanks in advance, bye Giacomo Mulas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749648: +1
The impact this has from my POV is that once you could just install the source package and the sources and javadocs for your JDK then show up automatically in Eclipse which presumes that src.zip is in the same folder. Now you require an extra step to get this useful resource (I make a softlink as suggested). Not sure if this counts as an Ubuntu problem in my case : the amd64 package is not available in the repository. But source code isn't really an architecture-dependent artefact and the previous packaging seems to make more sense in this regard.
Bug#751244: syncbbdb: Reverse depends libpda-pilot-perl FTBFS. Help is needed.
Package: syncbbdb Severity: important Hello, I am the Debian maintainer of pilot-link. syncbbdb depends on libpda-pilot-perl from pilot-link. I am not unable to build libpda-pilot-perl from source because of a new error: cc -c -I../../include -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fstack-protector -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\0.12.5\ -DXS_VERSION=\0.12.5\ -fPIC -I/usr/lib/perl/5.18/CORE -DPERL_POLLUTE Pilot.c In file included from /usr/include/string.h:631:0, from /usr/lib/perl/5.18/CORE/perl.h:1045, from Pilot.xs:22: Pilot.xs: In function ‘doPackCategory’: Pilot.xs:579:60: error: ‘na’ undeclared (first use in this function) strncpy(c-name[i], (s=av_fetch(av, i, 0)) ? SvPV(*s,na) : , 16); ^ It looks like the internals of Perl have changed :-( The pilot-link project is dead upstream since a few years now. The project web site http://www.pilot-link.org/ is no more available. I do not use the libpda-pilot-perl package myself. I do not use pilot-link other packages any more. So I will not invest energy to fix this bug. Alternatives: 1- you adopt pilot-link and maintain it and fix it 2- You help me to fix the FTBFS bug so I can upload a version of pilot-link 3- You do not help me and I upload a new of pilot-link without the libpda-pilot-perl package and syncbbdb will become unusable and removed from Debian I see you adopted syncbbdb in April 2014 so you are active on this package. Regards, -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751245: libslepc3.4.2-dbg: fortran mod file incompatible with new default gfortran (4.9)
Package: libslepc3.4.2-dbg Version: 3.4.2.dfsg-2 Severity: important Dear Maintainer, with version 1.128 of gcc-defaults, gfortran now defaults to 4.9, which has a different mod file version. Since libslepc3.4.2-dbg installs the file /usr/lib/slepcdir/3.4.2/linux-gnu-c-debug/include/slepcipdef.mod, it has to be recompiled with the gcc suite 4.9 to make it compatible with the version of gfortran which is now the default. Fixing This should involve no changes, just a plain rebuild of the package, therefore relatively painless for you. Thanks in advance, bye Giacomo Mulas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743543: gnome-shell fails to start : Unable to initialize Clutter
Control: block -1 by 722161 On Sat, Apr 05, 2014 at 12:59:43AM +0200, Emilio Pozuelo Monfort wrote: Do you have ATI graphics with the fglrx driver? If so this is a known problem with them not implementing libEGL. It's very likely that this is #722161, AFAIU. Hope this helps. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751247: please build a gccgo-doc package
Package: src:gcc-doc-defaults Version: 5:8 please build a gccgo-doc package (and a gccgo-4.9-doc package). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751246: libhdf5-openmpi-dev: please recompile with new default version of gfortran to get mod version right
Package: libhdf5-openmpi-dev Version: 1.8.12+docs-1.1 Severity: important Dear Maintainer, with version 1.128 of gcc-defaults, gfortran now defaults to 4.9, which has a different mod file version. Since libhdf5-openmpi-dev installs the file /usr/include/h5f.mod, it has to be recompiled with the gcc suite 4.9 to make it compatible with the version of gfortran which is now the default. Fixing This should involve no changes, just a plain rebuild of the package, therefore relatively painless for you. Thanks in advance, bye Giacomo Mulas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711139: gnuplot-qt: the grid doesn't work with the 'qt' terminal in -persist state
Control: forcemerge 711139 711141
I'm merging these two bugs because they basically cover the same issue.
However each covers 3 different issues: a documentation one, an UI one,
and a feature one (see below).
On 2014-06-10 19:04:42 -0700, sfeam wrote:
Then if I type quit to get the prompt back, the window
persists as required, but grid button no longer works.
You are trying to use persist for something beyond what
it was intended for.
I was mainly surprised that qt didn't behave like wxt. But this is
partly due to incomplete documentation (partly solved, but the man
page should be updated too) and poor UI: when a feature provided by
a button is not available, the button is normally greyed out; this is
not the case here. Alternatively, an error message could be displayed
when a non-working button (show grid or zoom) is clicked.
Now it is true that some terminal types are smart enough
to toggle the grid on/off even in persistent mode after
the main program has exiting. It would be possible to
make qt do that also, but only if the original plot already
contained a grid. And that is only possible because it
isn't really necessary to regenerate the whole plot just
to make the grid lines [in]visible. It doesn't change
the basic limitation.If toggling the grid is important
to you by itself, could you please file a feature request
for uniform support to toggle it off in terminals that
support a persistent mode? It would be easy in qt, but
I'd have to think about the other terminals.
Well, toggling the grid and zooming may be important in some cases.
When gnuplot is used in a script, there should be a way to use these
features (I'm not saying to use persist, it could be something
like pause mouse keypress + some other code but it seems to badly
interact with the buttons) and make the gnuplot processes terminate
when the terminal is closed by the user ('q', 'Ctrl-q', via the
window manager, or whatever). See
https://sourceforge.net/p/gnuplot/bugs/1418/#645d
and my reply.
--
Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/
100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751249: vtk6 is not installable (tcl-vtk conflict)
Package: vtk6 Version: 6.1.0+dfsg-5 Severity: important Dear Maintainer, vtk6 is not installable (and thus libvtk6-dev as well). Problem is, that vtk6 contains a conflict against tcl-vtk because both of them contain /usr/bin/vtk. Starting with 6.1.0+dfsg-4 libvtk6.1 depends on libxdmf2, which depends on tcl-vtk. As vtk6 depends on libvtk6.1, it's not installable. I guess we either have to remove /usr/bin/vtk from the package or revert the dependency on libxdmf2. Cheers Jochen -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/12 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 vtk6 depends on: ii libc6 2.19-1 ii libgcc1 1:4.9.0-6 ii libstdc++6 4.9.0-6 ii libtcl8.6 8.6.1-6 ii libtk8.68.6.1-5 pn libvtk6 none vtk6 recommends no packages. Versions of packages vtk6 suggests: pn vtk6-doc none pn vtk6-examples none -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751248: libadios-dev: please recompile with new default version of gfortran to get mod version right
Package: libadios-dev Version: 1.6.0-7+b1 Severity: important Dear Maintainer, with version 1.128 of gcc-defaults, gfortran now defaults to 4.9, which has a different mod file version. Since libadios-dev installs the file /usr/include/adios_defs_mod.mod, it has to be recompiled with the gcc suite 4.9 to make it compatible with the version of gfortran which is now the default. Fixing This should involve no changes, just a plain rebuild of the package, therefore relatively painless for you. Thanks in advance, bye Giacomo Mulas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706284: apt-file: multiple options and spaces in options in source.list mishandled
On Sat, Apr 27, 2013 at 07:22:51PM +0100, Josh Berdine wrote: Package: apt-file Version: 2.5.1 Severity: normal Dear Maintainer, * What led up to the situation? I added the entry deb [arch=i386 trusted=yes] http://download.skype.com/linux/repos/debian/ stable non-free #skype to /etc/sources.list . * What exactly did you do (or not do) that was effective (or ineffective)? Executed $ apt-file search /lib/x86_64-linux-gnu/libc.so.6 * What was the outcome of this action? The following output was produced: Use of uninitialized value $scheme in string at /usr/bin/apt-file line 185, SOURCE line 15. Use of uninitialized value $scheme in concatenation (.) or string at /usr/bin/apt-file line 186, SOURCE line 15. W: Don't know how to handle Use of uninitialized value $scheme in string at /usr/bin/apt-file line 185, SOURCE line 15. Use of uninitialized value $scheme in concatenation (.) or string at /usr/bin/apt-file line 186, SOURCE line 15. W: Don't know how to handle libc6: /lib/x86_64-linux-gnu/libc.so.6 * What outcome did you expect instead? libc6: /lib/x86_64-linux-gnu/libc.so.6 If the sources.list entry is modified to deb [arch=i386] http://download.skype.com/linux/repos/debian/ stable non-free #skype or deb [trusted=yes] http://download.skype.com/linux/repos/debian/ stable non-free #skype then no errors are reported. I experience the exact same errors when spaces are present between the square brackets of the option lists. E.g. each of these lines will trigger the same error: deb [ arch=amd64,i386 ] http://ftp.nl.debian.org/debian/ jessie main deb [ arch=amd64 ] http://www.emdebian.org/debian/ jessie main deb [ arch=armhf ] http://archive.raspbian.org/raspbian/ wheezy main Remove the spaces to get the following and the errors disappear: deb [arch=amd64,i386] http://ftp.nl.debian.org/debian/ jessie main deb [arch=amd64] http://www.emdebian.org/debian/ jessie main deb [arch=armhf] http://archive.raspbian.org/raspbian/ wheezy main -- Met vriendelijke groet, With kind regards, Giel van Schijndel -- A clever person solves a problem. A wise person avoids it. -- Albert Einstein signature.asc Description: Digital signature
Bug#751250: libnetcdf-dev: please rebuild with new default version of gfortran (4.9) to get mod version right
Package: libnetcdf-dev Version: 1:4.1.3-7 Severity: important Dear Maintainer, with version 1.128 of gcc-defaults, gfortran now defaults to 4.9, which has a different mod file version. Since libnetcdf-dev installs the file /usr/include/typesizes.mod, it has to be recompiled with the gcc suite 4.9 to make it compatible with the version of gfortran which is now the default. Fixing this should involve no changes, just a plain rebuild of the package, therefore relatively painless for you. Thanks in advance, bye Giacomo Mulas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747031: fixed in python-debian 0.1.22
Hi John, * python_support: Avoid hashlib dependency, using the built-in _sha or _sha1 module (depending on Python version) instead. That way we don't link in OpenSSL, which has an incompatible license. (Closes: 747031) We should be careful that this particular change is not backwards compatible with wheezy's python: $ PYTHONPATH=. python -c 'import debian.debian_support; debian.debian_support.new_sha1()' Traceback (most recent call last): File string, line 1, in module File debian/debian_support.py, line 50, in new_sha1 Built-in sha1 implementation not found; cannot use hashlib NotImplementedError: Built-in sha1 implementation not found; cannot use hashlib implementation because it depends on OpenSSL, which may not be linked with this library due to license incompatibilities (the test suite does fail which would alert a backporter) Fiddling around with an internal interface like _sha feels quite wrong too. I think it's likely to bring pain back to us in the future. I'm quite unconvinced by the argument that a GPL'd script can't import hashlib; I think GPLv3 is quite clear that hashlib is a Standard Interface of the Python programming language and that making use of it is fine; the language is less precise for GPLv2 but I still don't think there's a problem there. There are plenty of other GPL'd things in Debian that import hashlib and I don't think anyone's interested in working on this. I've taken this particular issue out of the too-hard-basket and put it back in several times already... thanks for taking a crack at it. cheers Stuart -- Stuart Prescott Senior Lecturer in Chemical Engineering Rm 706 Chemical Sciences Building UNSW AUSTRALIA UNSW SYDNEY NSW 2052 AUSTRALIA T: +61 2 9385 2641 F: +61 2 9385 5966 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751251: gfortran: please file a bunch of heads-up bugs to library packages installing mod files
Package: gfortran Version: 4:4.9.0-3 Severity: wishlist Dear Maintainer, with version 1.128 of gcc-defaults, gfortran now defaults to 4.9, which has a different mod file version. Library packages with fortran 90 interfaces will all need to be recompiled for their mod files to be compatible with the (now default) 4.9 version of gfortran. I just searched by hand all such mod files on my sid system and filed bug reports for their packages, but this could (should?) be made automatic whenever a new version of gfortran is made the default. Thanks in advance, bye Giacomo Mulas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751241: [Pkg-amule-devel] Bug#751241: amule: Please update to use wxwidgets3.0
Hello Olly, On Wed, Jun 11, 2014 at 2:06 PM, Olly Betts o...@survex.com wrote: On Wed, Jun 11, 2014 at 11:46:49PM +1200, Olly Betts wrote: Do you know what plans amule upstream have for wx3.0 support? I've tried to check their website, but it just gives a page saying the site is down due to server migration, with a link to the downloads page, and another to a forum which is 404. I had a look in the wayback machine, and it's been like that since September 2012! https://web.archive.org/web/20120919013043/http://www.amule.org/ yeah I know, they simply suggest to go to a forum website to talk about amule. I already made a lot of complains about that, even proposed to migrate to Google Code volunteering for the migration - but they just simply refuse any such help and ignore any complains about a missing website for such a long time :( And the last release looks like it was made 2011-11-11 - the two together make me wonder if amule is in fact dead upstream. well they are available thru such forum, but they don't seem to do much development work there. If so, is it worth trying to keep it in Debian? To do so, you're essentially going to need to take over the work upstream would normally do... Amule - as is in Debian - works without any problem: it connects to KAD and emule servers network, downloads/uploads correctly and so on, so even if upstream is not present at teh moment the project per see has still a lot of usefulness in Debian; but I don't plan to do any development work on it, I'll just keep packaging it and maintain such package - that's all. ah sure patches are welcome :D Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751252: caff: doesn't send email found no signed uids
Package: signing-party Version: 1.1.7-1 Severity: normal Dear Maintainer, caff can sign every key but when it's the moment to mail the signatures of certain keys with cert-level=1 caff ends with: gpg save [INFO] key 1234567890 done. [INFO] found no signed uids for 1234123412341234567890 and no email is sent. Then if I reopen caff it correctly prints fooman foo...@valid-email.com was already signed by key 43214321 Nothing to sign with key 43214321 Ok, then if I retype save it repeats found no signed uids So caff can sign but then doesn't send emails. I use exim4 and the command mail works via smarthost. I tried also with caff version 0.0.0.634 from pgp-tools svn but with no difference. With every key it works well using cert-level = 0, 2 or 3. With very few keys it works also with cert-level = 1, and sends the emails. In .caff/gnupghome/gpg.conf I have ask-cert-level Examples: Key1 pub 4096R expires usage: C sub 4096R expires usage: S sub 4096R expires usage: E sub 4096R expires usage: A cert-level 0: ok cert-level 1: problem cert-level 2: ok cert-level 3: ok Key2 pub 1024D doesn't expire usage: SC sub 4096g doesn't expire usage: E cert-level 0: ok cert-level 1: ok cert-level 2: ok cert-level 3: ok Key3 pub 4096R expires usage: SC sub 4096R expires usage: E cert-level 0: ok cert-level 1: problem cert-level 2: ok cert-level 3: ok Key4 pub 1024D expires usage: SC sub 4096g expires usage: E cert-level 0: ok cert-level 1: problem cert-level 2: ok cert-level 3: ok Key5 pub 2048R expires usage: SCA sub 2048R expires usage: E cert-level 0: ok cert-level 1: problem cert-level 2: ok cert-level 3: ok Key6 pub 1024D doesn't expire usage: SC sub 4096g doesn't expire usage: E sub 4096g doesn't expire usage: E sub 4096g doesn't expire usage: E sub 4096g doesn't expire usage: E sub 4096g doesn't expire usage: E cert-level 0: ok cert-level 1: problem cert-level 2: ok cert-level 3: ok Key7 pub 8192R doesn't expire usage: SCE sub 8192R doesn't expire usage: E cert-level 0: ok cert-level 1: problem cert-level 2: ok cert-level 3: ok Key8 pub 16384R doesn't expire usage: SCEA cert-level 0: ok cert-level 1: problem cert-level 2: ok cert-level 3: ok I can't find any other example of keys without this problem. Thanks, Ilario Gelmetti -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages signing-party depends on: ii gnupg 1.4.16-1.1 ii libc6 2.18-7 ii libclass-methodmaker-perl 2.21-1 ii libgnupg-interface-perl0.50-2 ii libmailtools-perl 2.12-1 ii libmime-tools-perl 5.505-1 ii libnet-idn-encode-perl 2.100-2 ii libterm-readkey-perl 2.32-1 ii libtext-template-perl 1.46-1 ii perl 5.18.2-4 pn python:any none ii qprint 1.0.dfsg.2-2 Versions of packages signing-party recommends: ii dialog 1.2-20140219-1 ii exim4-daemon-light [mail-transport-agent] 4.82.1-1 ii libgd-gd2-noxpm-perl 1:2.46-2.1+b1 ii libintl-perl 1.23-1 ii libpaper-utils 1.1.24+nmu3 ii libtext-iconv-perl 1.7-5+b1 ii whiptail 0.52.15-3+b1 Versions of packages signing-party suggests: pn fonts-droidnone ii imagemagick8:6.7.7.10+dfsg-3 ii mutt 1.5.23-1 pn texlive-latex-recommended none pn texlive-xetex none pn wipe 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#750996: eglibc FTBFS on Alpha: malloc/malloc.os build failure and testsuite failures.
On Wed, Jun 11, 2014 at 08:55:42PM +1200, Michael Cree wrote: Aurelien: I guess I should file bugs against gcc-4.8 and gcc-4.9 to get that fix into Debian's gcc as the commit does not seem to have been backported into the upstream 4.8 and 4.9 branches. I have just backported the fix into the gcc-4.8 and gcc-4.9 packages. It will be available with the next upload, but I don't know exactly when it will happen. Have you been able to look at the other issue, concerning __ASSUME_FUTEX_CLOCK_REALTIME? -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751253: RFP: rhc -- command line client for Red Hat OpenShift
Package: wnpp Severity: wishlist * Package name: rhc Version : 1.26.2 Upstream Author : Red Hat * URL : https://github.com/openshift/rhc * License : Apache License 2.0 Programming Lang: Ruby Description : command line client for Red Hat OpenShift The OpenShift command line tools allow you to manage your OpenShift applications from the command line. --- Useful to access OpenShift from the command line. It's Ruby and it's on Github, so not the best upstream for packaging, but it looks like they make release numbers, and do some packaging for Fedora. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751254: sleepd: Integer overflow while calculating battery percentage
Package: sleepd
Version: 2.05
Severity: normal
Tags: patch
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
My laptop got suspended immediately when the AC power off.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I find the problem: Integer overflow while calculating battery percentage.
* What was the outcome of this action?
* What outcome did you expect instead?
Here is a concrete description: http://kdr2.com/tech/linux/1406-sleepd-
bug-batt-cap.html , and there's a patch in the attachement.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10.27 (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
Versions of packages sleepd depends on:
ii libc62.19-1
ii libglib2.0-0 2.40.0-3
ii libupower-glib1 0.9.23-2+b2
ii lsb-base 4.1+Debian13
Versions of packages sleepd recommends:
ii pm-utils 1.4.1-14
ii upower0.9.23-2+b2
sleepd suggests no packages.
-- Configuration Files:
/etc/default/sleepd changed [not included]
From 5eef101c0b5360a6da4219c94d2086008373520b Mon Sep 17 00:00:00 2001
From: KDr2 killy.d...@gmail.com
Date: Wed, 11 Jun 2014 18:35:29 +0800
Subject: [PATCH] use int64_t for battery capacity to avoid integer overflow
---
acpi.c | 14 +++---
acpi.h | 6 +++---
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/acpi.c b/acpi.c
index 38bf820..417ce67 100644
--- a/acpi.c
+++ b/acpi.c
@@ -27,7 +27,7 @@ char acpi_batt_info[ACPI_MAXITEM][128];
/* Filenames of the battery status files for each system battery. */
char acpi_batt_status[ACPI_MAXITEM][128];
/* Stores battery capacity, or 0 if the battery is absent. */
-int acpi_batt_capacity[ACPI_MAXITEM];
+int64_t acpi_batt_capacity[ACPI_MAXITEM];
int acpi_ac_count = 0;
char acpi_ac_adapter_info[ACPI_MAXITEM][128];
@@ -86,15 +86,15 @@ int strmcmp(const char *s1, const char *s2)
/* Given a buffer holding an acpi file, searches for the given key in it,
* and returns the numeric value. 0 is returned on failure. */
-inline int scan_acpi_num (const char *buf, const char *key) {
+inline int64_t scan_acpi_num (const char *buf, const char *key) {
char *ptr;
- int ret = 0;
+ int64_t ret = 0;
do {
ptr = strchr(buf, '\n');
if (!strmcmp(buf, key)) {
if ((ptr = strchr(buf, '='))) {
-sscanf(ptr + 1, %d, ret);
+sscanf(ptr + 1, %ld, ret);
return ret;
} else {
return 0;
@@ -145,14 +145,14 @@ char *get_acpi_value (const char *file, const char *key) {
/* Returns the last full charge capacity of a battery.
*/
-int get_acpi_batt_capacity(int battery) {
+int64_t get_acpi_batt_capacity(int battery) {
char *s;
s = get_acpi_value(acpi_batt_info[battery], acpi_labels[label_last_full_capacity]);
if (s == NULL) {
return 0;
} else {
- return atoi(s);
+ return atoll(s);
}
}
@@ -327,7 +327,7 @@ int acpi_read (int battery, apm_info *info) {
/* Work out if the battery is present, and what percentage of full
* it is and how much time is left. */
if (strcmp(scan_acpi_value(buf, acpi_labels[label_present]), 1) == 0) {
- int pcap = scan_acpi_num(buf, acpi_labels[label_remaining_capacity]);
+ int64_t pcap = scan_acpi_num(buf, acpi_labels[label_remaining_capacity]);
state = scan_acpi_value(buf, acpi_labels[label_charging_state]);
if (state) {
if (state[0] == 'D') { /* discharging */
diff --git a/acpi.h b/acpi.h
index f82cba7..f7c77cc 100644
--- a/acpi.h
+++ b/acpi.h
@@ -20,10 +20,10 @@ int acpi_supported (void);
int acpi_read (int battery, apm_info *info);
#endif
char *get_acpi_file (const char *file);
-int scan_acpi_num (const char *buf, const char *key);
+int64_t scan_acpi_num (const char *buf, const char *key);
char *scan_acpi_value (const char *buf, const char *key);
char *get_acpi_value (const char *file, const char *key);
-int get_acpi_batt_capacity(int battery);
+int64_t get_acpi_batt_capacity(int battery);
extern int acpi_batt_count;
/* Filenames of the battery info files for each system battery. */
@@ -31,7 +31,7 @@ extern char acpi_batt_info[ACPI_MAXITEM][128];
/* Filenames of the battery status files for each system battery. */
extern char acpi_batt_status[ACPI_MAXITEM][128];
/* Stores battery capacity, or 0 if the battery is absent. */
-extern int acpi_batt_capacity[ACPI_MAXITEM];
+extern int64_t acpi_batt_capacity[ACPI_MAXITEM];
extern int acpi_ac_count;
extern char acpi_ac_adapter_info[ACPI_MAXITEM][128];
--
2.0.0
Bug#751245: libslepc3.4.2-dev package is also affected
Package: libslepc3.4.2-dev Version: 3.4.2.dfsg-2 Followup-For: Bug #751245 Dear Maintainer, libslepc3.4.2-dev also ships the file /usr/lib/slepcdir/3.4.2/linux-gnu-c-opt/include/slepcstdef.mod therefore it incures the same problem and is fixed in one go with the same remedy. bye Giacomo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751244: syncbbdb: Reverse depends libpda-pilot-perl FTBFS. Help is needed.
Yeah. I don't think anyone is using PalmOS anymore. I've even stopped, and I'm a pretty retro-computing guy. It seems to me that we should just have both packages removed from Debian. I only adopted syncbbdb because I was pushing bbdb3 into debian and wanted to make sure related packages were healthy. But there really isn't any serious reason to keep them around. Cheers, --Barak. -- Barak A. Pearlmutter Hamilton Institute Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland http://www.bcl.hamilton.ie/~barak/ pgpTmHdMxuXRu.pgp Description: PGP signature
Bug#711142: gnuplot-qt: zooming with the 'qt' and 'wxt' terminals yields blank contents
Control: retitle 711142 gnuplot-qt: zooming with the 'wxt' terminal doesn't work with -persist Only the retitle wasn't taken into account. Changed it again (and fixed it). -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733974: Partial diagnosis.
WOOT! thanks a lot! your analysis is incredibly useful. It makes perfectly sense. I feel bad about using the embeeded version of the lib, and I'd love if you could find some time to investigate further. I'm rather underwater right now, unfortunately. Thanks, Mt. On Wed, Jun 11, 2014 at 04:29:46AM -0700, ERIIX Blaike wrote: I can't say I'm entirely happy with my result so far, but I have figured out the general thrust of this bug. Minetest seems incompatible with the libjsoncpp in Debian. Solving this issue properly may be a mess, but the proof for the location of the problem also suggests a temporary workaround. If you have the Minetest source available (Upstream source -- git://github.com/minetest/minetest), it contains src/json/. From within, you can simply g++ -shared jsoncpp.cpp -o libjsoncpp.so.0 and use LD_LIBRARY_PATH to force the current Debian package to load that preferentially to the system-wide version. Suddenly, the server list and online mod repo work as they do upstream. An obvious temporary solution is to keep the bundled libjsoncpp, but a long-term solution will require figuring out why the system libjsoncpp fails and either making it work correctly or making Minetest use it correctly, dependent on which is behaving improperly. I haven't looked too deeply into which is responsible, though I'd suspect Minetest. I'll look into it later, but it is quite late right now, so I figured I'd send in what I have and get to bed. -- Je préfère glisser ma peau sous les draps pour le plaisir des sens que la risquer sous les drapeaux pour le prix de l'essence. signature.asc Description: Digital signature
Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]
On Wed, Jun 11, 2014 at 01:56:59PM +0200, Yoann Gauthier wrote: Hello, Hei, Okay, I will fix missing-license-paragraph-in-dep5-copyright gpl-3 during this week. To generate debian package you use : git-buildpackage ? And what is the complete lintian command ? Yes. git-buildpackage makes it easy to build a package. It also has some nice features like re-creating the upstream tarballs and much more. For lintian i run 'lintian -EvIL +pedantic'. I am not sure how mentors.debian.net does it. Thanks, Yoann 2014-06-10 23:04 GMT+02:00 Alexander Alemayhu alexan...@bitraf.no: On Tue, Jun 10, 2014 at 09:15:49PM +0200, Yoann Gauthier wrote: Hello, Hei, I updated the changelog file as asked. Thanks for the push access, it's easier for me to make changes now :). My changelog needs a review I think, because I am not familiar with changeLog conventions. It looks good IMO :) If you have new task to delegate, I am available. After running lintian today a new warning appears: W: postr source: missing-license-paragraph-in-dep5-copyright gpl-3 (paragraph at line 3) The warning does appear on earlier commits aswell. Maybe something has changed in lintian, could you look into it? I talked with a DD and was recommended to fix the autotools warnings reported by lintian. He also proposed to handle the python bytecode generation in a more correct way. I will be looking at using dh-autoreconf to make the package free of the autools warnings. It might take a couple of days... Regards, Yoann 2014-06-10 7:57 GMT+02:00 Alexander Alemayhu alexan...@bitraf.no: On Mon, Jun 09, 2014 at 08:29:51PM +0200, Yoann Gauthier wrote: Hello, Hei. I fixed the desktop-entry-lacks-keywords-entry as asked. Find attached the patch. I used quilt to create my patch : 04-fix_desktop_keywords.patch and then git format to create patch file. Good. You should also update the debian/changelog to include an entry which mentions the patch. Please take a close look at the existing lines to get an idea of what to write. Regards, PS : have access (push request) to your repository will be easier for me. Full access granted. You should now be able to push directly. Yoann 2014-06-03 22:50 GMT+02:00 Alexander Alemayhu alexan...@bitraf.no: On Tue, Jun 03, 2014 at 11:45:27AM +0200, Yoann Gauthier wrote: Hi Alexander, What are the next tasks I can do to help for the packaging ? You could look at the desktop-entry-lacks-keywords-entry[0] lintian tag and try to fix it. I was planning on fixing it but wanted to prioritize the autotools warnings. Hopefully we can get some advice from David. It looks like you would need to create a debian patch file to modify data/postr.desktop.in.in. If you are unfamiliar with quilt, take a look at this introduction[1]. PS: Remember to fetch the latest changes, before making new changes. It might help in avoiding merge conflicts. PPS: desktop-entry-lacks-keywords-entry only occurs when using `lintian -EvIL +pedantic` on my machine. [0]: http://lintian.debian.org/tags/desktop-entry-lacks-keywords-entry.html [1]: http://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/ Regards, Yoann 2014-06-02 21:26 GMT+02:00 Alexander Alemayhu alexan...@bitraf.no: On Mon, Jun 02, 2014 at 10:30:40AM +0200, Yoann Gauthier wrote: Hi, For man page license, I propose to distribute it under GNU GLP (v3). Do you agree ? I am no license expert, but I think it is okay assuming you mean GNU GPL. Okay for the maintener part, I will set the maintainer to Python Applications Packaging Team. Regards, Yoann 2014-06-01 18:26 GMT+02:00 Alexander Alemayhu alexan...@bitraf.no: On Sun, Jun 01, 2014 at 03:50:27PM +0200, Yoann Gauthier wrote: Le 31 mai 2014 20:00, Alexander Alemayhu alexan...@bitraf.no a écrit : On Sat, May 31, 2014 at 03:29:16PM +0200, Yoann Gauthier wrote: Hello, Hei, I wrote the man page (attachment). I have no access to the repository today, I will upload the page to repository tomorrow. Nice. I decided to use github as the Vcs-* since collab-maint seems to be for
Bug#724576: libgl1-mesa-glx:libGL error:failed to load driver:nouveau
Dear Maintainer, This problem persists with libgl1-mesa version 10.1.4-1 on iMac G4 powerpc (NV34 graphics card). Testing with an Asymptote example: $ asy -V cube.asy the command produces the 'failed to load driver' message but no graphical output. Downgrading the libgl1-mesa-dri package (to 9.1.7-1) works around the problem, as mentioned in message #30. However, even with the downgraded package there is still a problem with large graphical output. FreeCAD, for example, causes the GPU to lockup in full-screen mode. This could be the same problem reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744387 . Cheers, Paul. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683338: CVE-2013-7273 fix on next Wheezy point release.
Hello, Since this bug is tagged as path and security, Is there a chance that the problem will be corrected on the next Wheezy point release ? Since this bug is forwarded, do I need tho send my patch to the upstream gdm maintainers ? Cheers, Baptiste -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751169: libc6: Segmentation fault during libc upgrade, leaving system very unstable
Hi, On 10/06/14 05:50 PM, Aurelien Jarno wrote: Hi, On Tue, Jun 10, 2014 at 04:49:34PM -0400, Christian Weeks wrote: Package: libc6 Severity: important Dear Maintainer, Whenever I upgrade either elibc or gcc, my system enters a state where almost all software segmentation faults, including the upgrade itself. This happens repeatably on any upgrade of either of those packages, and has done for some time. I finally managed to capture a trace of the upgrade in progress which is why I am filing this report now. I have attached the output of both the upgrade output and my subsequent repair. There are 3 phases: the original upgrade, the first pass at repair (using dpkg), and finally the second pass at repair, which is exactly the same command as the first pass, but works completely. If I run dpkg -i with the list of packages seen (libc6:amd64, libc6:i386,libgcc:amd64,libgcc:i386) then the system becomes usable again. In this case, and very often when I do this repair, I have to run it twice to actually get the repair to stick. It appears the problem is when libc is deconfigured for upgrade. libgcc stops functioning (it depends on libc, obviously) and the segmentation fault means dpkg is unable to recover (I guess one of the configure scripts is failing). The segmentation fault is likely due to some incompatible libc version being mixed, one being the unpacked version, one being on the filesystem at a different location. I suspect the problem is somehow related to multi-arch, since it seems that multiarch is causing one side to deconfigure, breaking that side and then creating a dependency conflict situation. Indeed, we also suspect it is related to that. I am only filing this as important because obviously it breaks my system but it is recoverable. The non-existence of others reporting this makes me wonder if there isn't something weird, however, I have two machines and both exhibit the same symptoms. We already have one bug similar to yours (#741031) although it concerns the previous upgrade from 2.17 to 2.18. Unfortunately we are not able to understand the bug, as we have not been able to get a status of the system *before* any repair action is taken. Do you by chance still have a system in the broken state? If so, could you please send us the output of: dpkg -l libc* ls -l /lib /lib32 /lib64 /lib/i386-linux-gnu/ /lib/x86_64-linux-gnu/ Sadly, I don't have a broken state right now. I just tried on another machine, as jessie just got libc6 2.19 - however this issue did not occur there, and I noticed that libgcc did not update in jessie simultaneously. I wonder if you have to update both at once to cause the problem to occur. I've only noticed it when libgcc and libc have simultaneously updated previously, though this could be selective memory on my part. Next time gcc and libc update simultaneously, I'll capture pre-break and post-break state for your perusal, before fixing it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751000: Hardware-Information for virtual environment in Virtualbox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 see attachments [dmsg.txt.xz] and [hw-rep.txt.xz]. I chose the ICH9-chipset there and ICH6 for storage and enabled bridged networking in order to be able to export the information using NFS. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlOYV18ACgkQ5+rBHyUt5ws1AwCeJRHjqrykAK1iauMDF0IMyJ17 j3QAn1B72wPewPeS7pAcP639cJxYTvAY =nvgm -END PGP SIGNATURE- dmsg.txt.xz Description: application/xz hw-rep.txt.xz Description: application/xz
Bug#751255: treeviewx: Please update to use wxwidgets3.0
Package: treeviewx
Version: 0.5.1+20100823-2
Severity: important
Tags: patch sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wx3.0
Control: block 748169 by -1
Dear maintainer,
We're aiming to migrate the archive to using wxwidgets3.0 instead of
wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released.
I've rebuilt your package using the attached patch. I haven't tried
to run it though - a specialist package like this is much better tested
by someone who actually uses it (I don't have any suitable data, and
I'd have little idea what to do with it even if I did!)
One thing I should probably explain about the patch as my change may
seem odd otherwise - upstream's configure.in says USE_SVG=0 but the
generated configure says USE_SVG=1, so I've simply updated
configure.in to match what it must have said when configure was
generated.
I'm happy to NMU this change if you wish me to - just let me know.
Cheers,
Olly
diff -Nru treeviewx-0.5.1+20100823/debian/changelog treeviewx-0.5.1+20100823/debian/changelog
--- treeviewx-0.5.1+20100823/debian/changelog 2012-08-03 00:43:20.0 +1200
+++ treeviewx-0.5.1+20100823/debian/changelog 2014-06-12 01:03:38.0 +1200
@@ -1,3 +1,10 @@
+treeviewx (0.5.1+20100823-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Update to use wxWidgets 3.0 (new patch: wx3.0-compat.patch).
+
+ -- Olly Betts o...@survex.com Thu, 12 Jun 2014 01:03:35 +1200
+
treeviewx (0.5.1+20100823-2) unstable; urgency=low
* debian/watch: Fixed after Google code redirector stopped working
diff -Nru treeviewx-0.5.1+20100823/debian/control treeviewx-0.5.1+20100823/debian/control
--- treeviewx-0.5.1+20100823/debian/control 2012-08-03 00:43:05.0 +1200
+++ treeviewx-0.5.1+20100823/debian/control 2014-06-12 00:57:14.0 +1200
@@ -5,7 +5,7 @@
DM-Upload-Allowed: yes
Uploaders: Charles Plessy ple...@debian.org,
Andreas Tille ti...@debian.org
-Build-Depends: debhelper (= 9), libwxgtk2.8-dev
+Build-Depends: debhelper (= 9), libwxgtk3.0-dev, dh-autoreconf
Standards-Version: 3.9.3
Vcs-Browser: http://svn.debian.org/wsvn/debian-med/trunk/packages/treeviewx/trunk/
Vcs-Svn: svn://svn.debian.org/debian-med/trunk/packages/treeviewx/trunk/
diff -Nru treeviewx-0.5.1+20100823/debian/patches/series treeviewx-0.5.1+20100823/debian/patches/series
--- treeviewx-0.5.1+20100823/debian/patches/series 2012-08-03 00:16:12.0 +1200
+++ treeviewx-0.5.1+20100823/debian/patches/series 2014-06-12 00:30:12.0 +1200
@@ -1,3 +1,4 @@
60_LGPLtoGPL.patch
70_choose_tree.patch
fix_loading_crash.patch
+wx3.0-compat.patch
diff -Nru treeviewx-0.5.1+20100823/debian/patches/wx3.0-compat.patch treeviewx-0.5.1+20100823/debian/patches/wx3.0-compat.patch
--- treeviewx-0.5.1+20100823/debian/patches/wx3.0-compat.patch 1970-01-01 12:00:00.0 +1200
+++ treeviewx-0.5.1+20100823/debian/patches/wx3.0-compat.patch 2014-06-12 01:11:54.0 +1200
@@ -0,0 +1,97 @@
+--- a/configure.in
b/configure.in
+@@ -54,7 +54,7 @@
+ # The reason for this is wxGTK RPMs from wxWidgets.org
+ # do not have the required SVG library (which is a contribution)
+ AC_MSG_CHECKING(whether we will use SVG)
+-USE_SVG=0
++USE_SVG=1
+ WX_SVG_LIB=
+ if test $USE_SVG = 0 ; then
+AC_MSG_RESULT(no)
+@@ -66,7 +66,9 @@
+ case $wx_version in
+ 2.4.*) WX_SVG_LIB=[`$WX_CONFIG --basename`_dcsvg-`echo ${wx_version} | sed -e s:\.[0-9]\{1,\}$::`]
+;;
+- *)WX_SVG_LIB=[`$WX_CONFIG --basename`_svg-`echo ${wx_version} | sed -e s:\.[0-9]\{1,\}$::`]
++ 2.*) WX_SVG_LIB=[`$WX_CONFIG --basename`_svg-`echo ${wx_version} | sed -e s:\.[0-9]\{1,\}$::`]
++ ;;
++ *) WX_SVG_LIB=
+;;
+ esac
+
+@@ -76,7 +78,7 @@
+
+ if test $USE_SVG = 1 ; then
+CXXFLAGS=$CXXFLAGS -DUSE_SVG
+- LIBS=$LIBS -l$WX_SVG_LIB
++ test -n $WX_SVG_LIB LIBS=$LIBS -l$WX_SVG_LIB
+ fi
+
+ AC_OUTPUT(Makefile ncl-2.0/Makefile ncl-2.0/src/Makefile TreeLib/Makefile tv.spec)
+--- a/tv.cpp
b/tv.cpp
+@@ -162,9 +162,9 @@
+ {
+ // Optional command line argument is name of file to open
+ #if wxUSE_UNICODE
+- wchar_t *InputFile = NULL;
++ const wchar_t *InputFile = NULL;
+ #else
+- char *InputFile = NULL;
++ const char *InputFile = NULL;
+ #endif
+ // Read input/output files
+ if (argc 1)
+--- a/tview.cpp
b/tview.cpp
+@@ -63,9 +63,13 @@
+ #ifdef __WXMSW__
+ #else
+ #ifdef USE_SVG
++#if wxMAJOR_VERSION = 3
++ #include wx/dcsvg.h
++#else
+ #include wx/svg/dcsvg.h
+ #endif
+ #endif
++#endif
+
+ // GUI interface
+ #include tv.h
+@@ -187,7 +191,7 @@
+ wxFrame *f = GetMainFrame();
+ wxFileDialog dialog((wxWindow *)f, wxT(Save Picture as), wxT(), pictureFileName,
+ wxT(Enhanced metafile (*.emf)|*.emf),
+-wxSAVE|wxOVERWRITE_PROMPT);
++wxFD_SAVE|wxFD_OVERWRITE_PROMPT);
+
+ if (dialog.ShowModal() == wxID_OK)
+ {
+@@ -207,7 +211,7 @@
+ #endif
+ wxFileDialog dialog((wxWindow *)f, wxT(Save Picture as), wxT(),
Bug#751133: crash on startup
Hello, the Yubikey neo doesn't seem to be detected: #pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader... This message stays forever- Though 'dmesg' says: [1171616.043090] usb 5-6.3.3: USB disconnect, device number 49 [1171622.388457] usb 5-6.3.3: new full-speed USB device number 50 using ehci-pci [1171622.482191] usb 5-6.3.3: New USB device found, idVendor=1050, idProduct=0110 [1171622.482198] usb 5-6.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1171622.482202] usb 5-6.3.3: Product: Yubikey NEO OTP [1171622.482206] usb 5-6.3.3: Manufacturer: Yubico [1171622.485176] input: Yubico Yubikey NEO OTP as /devices/pci:00/:00:1d.7/usb5/5-6/5-6.3/5-6.3.3/5-6.3.3:1.0/input/input24 [1171622.485428] hid-generic 0003:1050:0110.0011: input,hidraw4: USB HID v1.10 Keyboard [Yubico Yubikey NEO OTP] on usb-:00:1d.7-6.3.3/input0 I am using stock Debian testing with libccid 1.4.16-1 package with running pcscd on a i386 machine. Best regards, Werner -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751256: lz4: support ppc64el architecture.
Source: lz4 Version: 0.0~r117-1 Severity: normal Tags: patch User: debian-powe...@lists.debian.org Usertags: ppc64el Dear Maintainer, Currently lz4 package does not built on ppc64el due to that ppc64el is identified as a big endian and 32 bit architecture, thus the tests fail. I am providing a patch that fixes the problem. It is based on the William Grant's patches entitled 'Fix __GLIBC__ endianness check to include stdlib.h' plus changes to add the platform as 64 bits. With the following patch, the tests run fine with the following result: compression ratio: 48.824% HC compression ratio: 38.515% This patch was also sent upstream at https://code.google.com/p/lz4/issues/detail?id=131q=label%3APriority-minor Thanks Breno -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (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 Index: lz4-0.0~r117/lz4.c === --- lz4-0.0~r117.orig/lz4.c 2014-06-11 12:46:02.0 + +++ lz4-0.0~r117/lz4.c 2014-06-11 12:48:00.0 + @@ -56,7 +56,9 @@ **/ /* 32 or 64 bits ? */ #if (defined(__x86_64__) || defined(_M_X64) || defined(_WIN64) \ - || defined(__powerpc64__) || defined(__ppc64__) || defined(__PPC64__) \ + || defined(__powerpc64__) || defined(__powerpc64le__) \ + || defined(__ppc64__) || defined(__ppc64le__) \ + || defined(__PPC64__) || defined(__PPC64LE__) \ || defined(__64BIT__) || defined(_LP64) || defined(__LP64__) \ || defined(__ia64) || defined(__itanium__) || defined(_M_IA64) ) /* Detects 64 bits mode */ # define LZ4_ARCH64 1 @@ -68,6 +70,7 @@ * Little Endian or Big Endian ? * Overwrite the #define below if you know your architecture endianess */ +#include stdlib.h #if defined (__GLIBC__) # include endian.h # if (__BYTE_ORDER == __BIG_ENDIAN) Index: lz4-0.0~r117/lz4hc.c === --- lz4-0.0~r117.orig/lz4hc.c 2014-06-11 12:46:02.0 + +++ lz4-0.0~r117/lz4hc.c 2014-06-11 12:48:26.0 + @@ -54,7 +54,9 @@ **/ /* 32 or 64 bits ? */ #if (defined(__x86_64__) || defined(_M_X64) || defined(_WIN64) \ - || defined(__powerpc64__) || defined(__ppc64__) || defined(__PPC64__) \ + || defined(__powerpc64__) || defined(__powerpc64le__) \ + || defined(__ppc64__) || defined(__ppc64le__) \ + || defined(__PPC64__) || defined(__PPC64LE__) \ || defined(__64BIT__) || defined(_LP64) || defined(__LP64__) \ || defined(__ia64) || defined(__itanium__) || defined(_M_IA64) ) /* Detects 64 bits mode */ # define LZ4_ARCH64 1 @@ -66,6 +68,7 @@ * Little Endian or Big Endian ? * Overwrite the #define below if you know your architecture endianess */ +#include stdlib.h #if defined (__GLIBC__) # include endian.h # if (__BYTE_ORDER == __BIG_ENDIAN)
Bug#748291: lxc-start: failed creating cgroups
tag 748291 -confirmed tag 748291 -help retitle 748291 Please mount cgroup automatically reassign 748291 initscripts forcemerge 748291 601757 thanks imho it's not a proper solution to invent an extra packaging just for mounting cgroupsfs, unworthy for debian as a workaround for sysvinit not merging a patch. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751257: [python-beautifulsoup] Please package the latest Beautiful Soup - 4.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: python-beautifulsoup Version: 3.2.1-1 Severity: normal Beautiful Soup 4.2 is available now, along with a Python 3 module. Thanks - --- System information. --- Architecture: amd64 Kernel: Linux 3.14-1-amd64 Debian Release: jessie/sid 990 testing security.debian.org 990 testing ftp.uk.debian.org 500 unstableftp.uk.debian.org 500 stable ftp.uk.debian.org 500 quodlibet-unstable www.student.tugraz.at 1 experimentalftp.uk.debian.org - --- Package information. --- Depends (Version) | Installed ===-+-== python2.7 | 2.7.7-2 OR python2.6 | 2.6.8-2 python(= 2.6.6-7~) | 2.7.6-2 python ( 2.8) | 2.7.6-2 Recommends (Version) | Installed =-+-=== python-chardet| 2.2.1-2 Package's Suggests field is empty. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBAgAGBQJTmF04AAoJEBfSPH39wvOPW84QAIjj5HbU9YxKqWITNabwfbQs D+dSf7XiOiZrM3No2bzzq1aICf3A2pByPNRWBbrTcazpCZ+BMRN69dYqDaEPitn0 Ad4WjIMZMcGbjtf4h7T71mXRDs4aWqaVxXR18RCXJFUdScJs2y9/TnIMl59B4ykH /S+oNTjRBJgKhRRD54gelSeIZSuPcOVCK1qediIVuXii96h59U1QlXyPNDVbOm5l SEPHWJCRiSD+dgEYqagDmqB6L8f/ZIrSZoCFuaGsWyCYfx88RSaKET+e3/J7bOqE 5fAVz1s+Or8Tb6GPuBiaWUF7eyZgglZWQ4XYIZ+g0ZKTX8P77CCH5abls5VSEHt0 spliMsGaUVP9y8dC8TYU9aY60/Ro6M0C6tZ9hdapIOLRNNG0y9Hd0nwUaAPAK9XL niRXxYrn55eGUUrX8nROTIPcHOcYgq2u8eir9d00mnM/Q4fxS7HyC0uhqaLrWA5l TuH1Eb1WMlDM8BeGJ7d9CDHAA2QkAci/sQwAzabclyZAzBCsb7UoU3vS2GRWu7lH SwEX2+G7G1PfbUt+PrYVknRqSiYhi0sUBIC3XntE8C3o0qtSCn730/czp7gRC0Lt +rEBpHZWuGHkYNZVHq0h0VVyRykwQHunX7HaKsNfhRnUEC5OTlhTPmqDFCwmby29 z3iGxC3QTAIz0iRalXoZ =WUfW -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#750651: xymon-client: clientupdate fails
Am 07.06.2014 20:05, schrieb Christoph Berg: In FHS-compliant installations, updating files spread all over the filesystem is a pretty scary idea. Axel was satisfied with /var/lib/xymon... /var/lib/xymon is also $HOME for xymon user. Would both be happy with /var/run/xymon? If you really want to use the client-pulls-new-binaries-from-server thing, why are you using prepackaged .debs anyway? To me, it sounds like you should rather use a one-time make install (possibly packaged as a tarball that you ship to clients), and go from there. I have always been doing so. Now the version in debian testing is newer than one in my repository. I hope with stable jessie, I no longer have to make own packages. Moreover, clientupdate is a brillant feature of xymon that should someday work for all. This is not to say there's no way to integrate this in the package, but it needs careful thinking about which parts should be overridable, and I guess none of that should be enabled by default. Clientupdate is never enabled by default! As long as no clientversion: are defined in the file client-local.cfg on xymon server, clientupdate makes nothing. Accepted? Best Regards, Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751241: amule: Please update to use wxwidgets3.0
Am Donnerstag, 12. Juni 2014, 00:06:27 schrieben Sie: And the last release looks like it was made 2011-11-11 - the two together make me wonder if amule is in fact dead upstream. Dead is not the correct word. There is still a project-leader that claims to be working on the new site. The forums at forumer are there for support with the existing release. There are just no new features to do, that would need a new release and for now it's more a state of waiting. Everything the original emule can do, is supported, so the goal of the project is reached. If emule decides for a way, how they can support IPv6, this will also go into amule, otherwise both projects will die. If so, is it worth trying to keep it in Debian? To do so, you're essentially going to need to take over the work upstream would normally do... I want to try wx-3.0 for several weeks now. Maybe in one or two, I find the time. -- MfG usw. Werner Mahr
Bug#751241: amule: Please update to use wxwidgets3.0
Hi there, Just to comment that the forum is accessible at http://amule.forumer.com/ . The URL at amule.org points to an index.php file, which is what gives the 404. Access the root address without that PHP file and you'll get there. :-) Regards, Pitxyoki -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750515: deets: Updates for new libdpkg 1.17.10 API changes
On Wed, Jun 04, 2014 at 03:13:20AM +0200, Guillem Jover wrote: Here's a patch series with some fixes and an update for the upcoming changes in the libdpkg 1.17.10 API. Some enum value names have changed, but the switch to the pkg_status_name() function will shield the code from that now and in the future, and will reduce code duplication. Applied and pushed, thanks! I'm a bit too busy to make a release right now but I'll try to get to it soon. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751258: nmu: stk_4.4.4-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Needs librtaudio-dev = 4.1.1~ds0-2 nmu stk_4.4.4-5 . ALL . -m Rebuild against new rtaudio and rtmidi -- System Information: Debian Release: jessie/sid APT prefers stable APT policy: (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737921: [TLS1.2] gnutls only likes SHA1 and SHA256 certificates
Hi, this is getting a real issue for us now. We need new gnutls versions for Wheezy and at least Squeeze - We still have a lot of internal infrastructure running on Debian/Squeeze and we are facing certificate expiration issues now. Our internal LDAP infrastructure is giving us a lot of headache as we are not able to use the CACert renewals with openldap replications. We also expect SMTP/TLS getting a real issue soon as more and more newer systems will start using SHA512 certificates. Flo -- Florian Lohoff f...@zz.de signature.asc Description: Digital signature
Bug#751259: webkitgtk FTBFS on armel/armhf
Package: webkitgtk Version: 2.4.3-2 Severity: serious Justification: FTBFS Hi, It seems libgl1-mesa-dev will be pulled in regardless: dd-schroot-cmd -c sid_armhf-dchroot-7101d185-7aa9-42e0-a68c-0bbf3271b410 apt-get build-dep webkitgtk ... libgirepository-1.0-1 libgirepository1.0-dev libgl1-mesa-dev libgl1-mesa-glx libglapi-mesa libgles2-mesa libgles2-mesa-dev libglib2.0-0 libglib2.0-bin ... So a build-conflicts: libgl1-mesa-dev [armel armhf] would be needed, or the sources need to accomodate the possibility of both installed. Since with freeadreno and nouveau drivers coming to arm, there are also full opengl drivers for arm, this kind of arch based detection is a bit frowned upon. If armel/armhf go gles, please check that all packages building upon webkitgkt still work on arm after the change. See http://people.debian.org/~public_html/webkitgtk_armhf.log for build log: In file included from ../Source/WebCore/platform/graphics/egl/GLContextEGL.cpp:32:0: ../Source/ThirdParty/ANGLE/include/GLES2/gl2.h:39:26: error: 'GLsizeiptr' has a previous declaration as 'typedef khronos_ssize_t GLsizeiptr' typedef khronos_ssize_t GLsizeiptr; ^ In file included from /usr/include/GL/gl.h:2059:0, from /usr/include/GL/glx.h:32, from /usr/include/cairo/cairo-gl.h:96, from ../Source/WebCore/platform/graphics/egl/GLContextEGL.cpp:39: /usr/include/GL/glext.h:469:19: error: conflicting declaration 'typedef ptrdiff_t GLintptr' typedef ptrdiff_t GLintptr; ^ In file included from ../Source/WebCore/platform/graphics/egl/GLContextEGL.cpp:32:0: ../Source/ThirdParty/ANGLE/include/GLES2/gl2.h:38:26: error: 'GLintptr' has a previous declaration as 'typedef khronos_intptr_t GLintptr' typedef khronos_intptr_t GLintptr; ^ GNUmakefile:64748: recipe for target 'Source/WebCore/platform/graphics/egl/libWebCoreGtk_la-GLContextEGL.lo' failed make[2]: *** [Source/WebCore/platform/graphics/egl/libWebCoreGtk_la-GLContextEGL.lo] Error 1 make[2]: *** Waiting for unfinished jobs mv -f Source/WebCore/plugins/gtk/.deps/libWebCoreGtk_la-PluginViewGtk.Tpo Source/WebCore/plugins/gtk/.deps/libWebCoreGtk_la-PluginViewGtk.Plo make[2]: Leaving directory '/home/riku/webkitgtk-2.4.3/build-2.0' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750106: bts
retitle 750107 syntax errors in apparmor severity 750107 normal tag 750107 pending retitle 750106 please complete apparmor support severity 750106 wishlist tag 750106 upstream tag 750106 help thanks #748291 got cloned as bugs #750106 and #750107. #748291 was about cgroupfs not mounted by the user (and is solved), and has nothing to do with the clones (they were ment about to be submitted regarding apparmor support by the bug submitter). there are two bugs about apparmor, one is a syntax error, and the other one is that the general integration of apparmor support is incomplete. in an attempt of cleaning up the cloning mess, i'm now retiteling them accordingly now. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749681: [diskscan] doesn't causes in extended description
2014-06-10 22:11 GMT-03:00 Filipus Klutiero chea...@gmail.com: On 2014-06-10 15:18, Eriberto wrote: 2014-06-10 12:16 GMT-03:00 Filipus Klutiero chea...@gmail.com: hi! diskscan is intended to find sectors of a storage medium (hard disk, flash drive (pendrive), etc.) which are bad or I used or and I avoided a comma before the etc. Sorry for this.You are right. In Brazilian Portuguese we don't put a comma before an etc because etc. = et cetera = and other choices. We don't use a comma before an and. Two examples: Comprei batata, tomate e cebola. Comprei batata, tomate, cebola etc. But, after your comment, I searched in Internet and I learned that we must to use a comma before etc. when writting in English. Thanks! Even though that may be illogical, etc is usually preceded by a comma. There are two problems: 1. The repetition of the word medium. I do not see this as a problem. 2. The nonexistence of the word media. It is bad when search a package via apt-cache. I believe it's unlikely that people looking for diskscan will search for media, but if you want to keep media, I suggest to do it via the short description: scan storage media for bad or near failure sectors This would be at the same time more complete and more grammatically correct. Ok. Done. I believe that we can use this text. Description: scan HDD/SSD for bad or near failure sectors diskscan is intended to find sectors of a storage medium (hard disk, flash drive or pendrive etc.) which are bad or in the process of going bad. . The operation is entirely read-only and does not cause damage to the data on filesystems. As the program reads block device sectors, it will work whether there is a filesystem or not. . diskscan reads the entire block device and notes the time it took to read a block. When there is an error it is immediately noted and also when there is a higher latency to read a block. A histogram of the block latency times is also given to assess the health of the media. . diskscan also can be used to test the speed and quality of the media. diskscan can also would be a little better. Done! :D All sectors of a perfect medium could be read at the same speed. Thanks to you -- Filipus Klutiero http://www.philippecloutier.com Thanks a lot Filipus. You helped to improve this package. My native language is Brazilian Portuguese and your help was very good. I will upload a new revision now and it will close this bug. Have a nice day! Cheers, Eriberto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751260: devscripts: wrap-and-sort does not handle comments in Build-Depends properly
Package: devscripts Version: 2.14.1 Severity: normal Dear Maintainer, Running wrap-and-sort on a control file of a package that had the first build dep commented out completely deletes the build-deps of the package. Testcase : Snippet from a control file - Build-Depends: # kde-sc-dev-latest (= 4:4.10.2), cmake, debhelper (= 7.3.16), pkg-kde-tools (= 0.12), Running wrap-and-sort on a control file with such a snippet will delete everything from the Build Depends -- Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- DEBSIGN_KEYID=F2672094 -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty-proposed'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.0-30-generic (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 Versions of packages devscripts depends on: ii dpkg-dev 1.17.5ubuntu5.3 ii libc62.19-0ubuntu6 ii perl 5.18.2-2ubuntu1 ii python3 3.4.0-0ubuntu2 pn python3:any none Versions of packages devscripts recommends: ii at3.1.14-1ubuntu1 ii curl 7.35.0-1ubuntu2 ii dctrl-tools 2.23ubuntu1 ii dput 0.9.6.4ubuntu1 ii fakeroot 1.20-3ubuntu2 ii gnupg 1.4.16-1ubuntu2 ii libdistro-info-perl 0.12 ii libencode-locale-perl 1.03-1 ii libjson-perl 2.61-1 ii libparse-debcontrol-perl 2.005-4 ii liburi-perl 1.60-1 ii libwww-perl 6.05-2 ii lintian 2.5.22ubuntu1 ii man-db2.6.7.1-1 ii patch 2.7.1-4ubuntu1 ii patchutils0.3.2-3 ii python3-debian0.1.21+nmu2ubuntu2 ii python3-magic 1:5.14-2ubuntu3 ii sensible-utils0.0.9 ii strace4.8-1ubuntu5 ii unzip 6.0-9ubuntu1 ii wdiff 1.2.1-2 ii wget 1.15-1ubuntu1 ii xz-utils 5.1.1alpha+20120614-2ubuntu2 Versions of packages devscripts suggests: pn bsd-mailx | mailxnone ii build-essential 11.6ubuntu6 pn cvs-buildpackage none ii debian-keyring 2014.03.03 pn devscripts-elnone pn equivs none pn gnuplot none ii gpgv 1.4.16-1ubuntu2 ii libauthen-sasl-perl 2.1500-1 ii libfile-desktopentry-perl0.07-1 ii liblwp-protocol-https-perl 6.04-2 ii libnet-smtp-ssl-perl 1.01-3 pn libsoap-lite-perlnone pn libterm-size-perlnone ii libtimedate-perl 2.3000-1 pn libyaml-syck-perlnone pn mutt none ii openssh-client [ssh-client] 1:6.6p1-2ubuntu2 pn svn-buildpackage none pn w3m 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#751252: caff: doesn't send email found no signed uids
Control: severity -1 important Hi Ilario, First off, thanks for this thorough report :-) This seems to be due to gpg ignoring signatures under the cutoff certification level (2 by default) when exporting with the ‘export-clean’ option. Compare the output of the following two lines: gpg --min-cert-level=1 --export-options export-clean --export $keyID | gpg --list-packets | grep -B1 -A3 'sigclass 0x11$' gpg --min-cert-level=2 --export-options export-clean --export $keyID | gpg --list-packets | grep -B1 -A3 'sigclass 0x11$' If that behavior isn't consistent, that's a bug in gpg. (And if I got the manpage right, the cutoff certification level is only relevant when building the trustdb, hence should be irrelevant when exporting.) I'd be happy to reassign it myself, but I couldn't a find a key for which export-clean works as expected. Would you mind asking the owner of Key2 if they would like their key to be listed in a bug report and/or a unit test? In the mean time, adding ‘min-cert-level 1’ to caff's gnupghome should help. Cheers, -- Guilhem. signature.asc Description: Digital signature
Bug#751029: Please split kpartx off from multipath-tools
On 6/11/2014 12:29 AM, Ritesh Raj Sarraf wrote:
Thank you Phillip and Guido for this conversation and concluding it.
Please feel free to submit the reworked patch. So we are just splitting
to a new kpartx package.
Ok, here you go... now it just splits the kpartx binary into its own udeb.
=== modified file 'debian/changelog'
--- debian/changelog2014-03-09 16:52:09 +
+++ debian/changelog2014-06-11 14:05:33 +
@@ -1,3 +1,9 @@
+multipath-tools (0.5.0-2) unstable; urgency=low
+
+ * Split kpartx out of multipth-tools-udeb into kpartx-udeb
+
+ -- Phillip Susi ps...@ubuntu.com Mon, 09 Jun 2014 11:45:08 -0400
+
multipath-tools (0.5.0-1) unstable; urgency=low
* [955018b] Imported Upstream version 0.5.0
=== modified file 'debian/control'
--- debian/control 2014-03-09 16:52:09 +
+++ debian/control 2014-06-11 14:04:34 +
@@ -63,7 +63,7 @@
Package: multipath-udeb
Package-Type: udeb
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, multipath-modules
+Depends: ${shlibs:Depends}, ${misc:Depends}, multipath-modules, kpartx-udeb
Section: debian-installer
Description: maintain multipath block device access - udeb package
This is a udeb, or a microdeb, for the debian-installer.
@@ -71,3 +71,14 @@
These tools are in charge of maintaining the disk multipath device maps and
react to path and map events.
+Package: kpartx-udeb
+Package-Type: udeb
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Section: debian-installer
+Description: create device mappings for partitions - udeb package
+ This is a udeb, or a microdeb, for the debian-installer.
+ .
+Kpartx can be used to set up device mappings for the partitions of any
+partitioned block device. It is part of the Linux multipath-tools.
+
=== added file 'debian/kpartx-udeb.install'
--- debian/kpartx-udeb.install 1970-01-01 00:00:00 +
+++ debian/kpartx-udeb.install 2014-06-09 17:07:15 +
@@ -0,0 +1,1 @@
+/sbin/kpartx
=== modified file 'debian/multipath-udeb.install'
--- debian/multipath-udeb.install 2010-01-23 00:14:04 +
+++ debian/multipath-udeb.install 2014-06-09 17:07:25 +
@@ -1,4 +1,3 @@
/sbin/multipath
/lib/multipath/
/lib/libmultipath.so.*
-/sbin/kpartx
signature.asc
Description: OpenPGP digital signature
Bug#751261: iputils-arping: -D option in manpage needs clarification
Package: iputils-arping Version: 3:20121221-5 Severity: minor arping manpage says: -D Duplicate address detection mode (DAD). See RFC2131, 4.4.1. Returns 0, if DAD succeeded i.e. no replies are received But there is no explanation about what DAD succeeded means, basically if a zero return status means there are duplicated IP address on the network or not. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (700, 'testing'), (650, 'stable'), (500, 'stable-updates'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages iputils-arping depends on: ii libc62.18-5 ii libcap2 1:2.22-1.2 Versions of packages iputils-arping recommends: ii libcap2-bin 1:2.22-1.2 iputils-arping suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751237: claws-mail: SEGV when trying to get IMAP mail
Control: tags -1 moreinfo Hi Shane, On Wed, Jun 11, 2014 at 12:07:37PM +0200, Shane Kerr wrote: Package: claws-mail Version: 3.9.3-2+b3 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I have happily been using claws-mail on this machine, but today when I tried using it, it crashed when I tried to click on the first mail folder after startup. I tried retrieving new mail, and this also crashed. I tried uninstalling and re-installing the claws-mail package, but this made no difference (which is good I suppose). I went ahead and installed gdb and used ulimit -c unlimited to allow a core to be generated, and had a look. I get this: Reading symbols from /usr/bin/claws-mail...(no debugging symbols found)...done. You can install claws-mail-dbg package to have debug symbols. That way backtraces are more meaningful. Can you reproduce it that way and post the new backtrace? Be sure to use ‘thread apply all bt’ within gdb (claws-mail is multi-threaded). Thanks in advance, -- Ricardo Mones ~ Don't take the name of root in vain. /usr/src/linux/README signature.asc Description: Digital signature
Bug#751259: webkitgtk FTBFS on armel/armhf
Control: tags -1 upstream Control: forwarded -1 https://bugs.webkit.org/show_bug.cgi?id=133550 On Wed, Jun 11, 2014 at 04:57:42PM +0300, Riku Voipio wrote: It seems libgl1-mesa-dev will be pulled in regardless: Yes, we know this problem, it's already reported upstream: https://bugs.webkit.org/show_bug.cgi?id=133550 Thanks, Berto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751262: barry: Please update to use wxwidgets3.0
Package: barry
Version: 0.18.5-1
Severity: important
Tags: patch sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wx3.0
Control: block 748169 by -1
Dear maintainer,
We're aiming to migrate the archive to using wxwidgets3.0 instead of
wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released.
I've tried to rebuild barry with wxwidgets3.0, and just updating the
build-dependencies isn't enough - some changes are needed to the
upstream source. I fixed a few, but hit this - I'm not confident I
know what's going on with this code:
bsyncjail.cc: In member function 'virtual void
BarrySyncJail::HandleConflict(OpenSync::SyncConflict)':
bsyncjail.cc:221:59: error: invalid conversion from 'const void*' to 'wxChar*
{aka wchar_t*}' [-fpermissive]
buf = m_conflict_con-Request(CONFLICT_ITEM_ANSWER, size);
I've attached a patch with the fixes I made to get this far, which I
hope will be of use. You may also find wx upstream's overview of
changes since wx2.8 useful:
http://docs.wxwidgets.org/3.0/overview_changes_since28.html
One particular thing to be aware of is that wx3.0 turns on WXDEBUG
mode by default, and as a result at run-time some applications throw up
a lot of assertion failed dialogs due to using the wx API in invalid
ways. If you compile your package with -DNDEBUG then such assertions
aren't checked, and the same fallbacks which were quietly used in wx2.8
are used instead.
If you hit any problems with getting things working with wxwidgets3.0
which you can't overcome, let me know and I'll try to help.
Cheers,
Olly
diff -Nru barry-0.18.5/debian/changelog barry-0.18.5/debian/changelog
--- barry-0.18.5/debian/changelog 2013-11-19 07:32:59.0 +1300
+++ barry-0.18.5/debian/changelog 2014-06-12 00:38:56.0 +1200
@@ -1,3 +1,10 @@
+barry (0.18.5-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Update to build with wxWidgets 3.0 (new patch: wx3.0-compat.patch).
+
+ -- Olly Betts o...@survex.com Thu, 12 Jun 2014 00:38:30 +1200
+
barry (0.18.5-1) unstable; urgency=low
* New upstream version 0.18.5
diff -Nru barry-0.18.5/debian/control barry-0.18.5/debian/control
--- barry-0.18.5/debian/control 2013-11-19 07:32:59.0 +1300
+++ barry-0.18.5/debian/control 2014-03-14 14:48:15.0 +1300
@@ -32,7 +32,7 @@
Section: misc
Priority: optional
Maintainer: Chris Frey cdf...@foursquare.net
-Build-Depends: debhelper (= 7.0.0), g++ (= 4.1), cdbs, autoconf, autoconf-archive, automake, libtool, pkg-config, libusb-dev, libboost-serialization-dev, libxml++2.6-dev, libfuse-dev (= 2.5), zlib1g-dev, libtar-dev, libglibmm-2.4-dev, libgtkmm-2.4-dev, libglademm-2.4-dev, autopoint | gettext ( 0.18), libgcal-dev, wx-common, libwxgtk2.8-dev, libsdl-dev, php5-cli
+Build-Depends: debhelper (= 7.0.0), g++ (= 4.1), cdbs, autoconf, autoconf-archive, automake, libtool, pkg-config, libusb-dev, libboost-serialization-dev, libxml++2.6-dev, libfuse-dev (= 2.5), zlib1g-dev, libtar-dev, libglibmm-2.4-dev, libgtkmm-2.4-dev, libglademm-2.4-dev, autopoint | gettext ( 0.18), libgcal-dev, wx-common, libwxgtk3.0-dev, libsdl-dev, php5-cli
Standards-Version: 3.9.4
Homepage: http://netdirect.ca/barry
Vcs-Git: git://repo.or.cz/barry.git -b v0.18.x
diff -Nru barry-0.18.5/debian/patches/series barry-0.18.5/debian/patches/series
--- barry-0.18.5/debian/patches/series 1970-01-01 12:00:00.0 +1200
+++ barry-0.18.5/debian/patches/series 2014-03-14 14:59:07.0 +1300
@@ -0,0 +1 @@
+wx3.0-compat.patch
diff -Nru barry-0.18.5/debian/patches/wx3.0-compat.patch barry-0.18.5/debian/patches/wx3.0-compat.patch
--- barry-0.18.5/debian/patches/wx3.0-compat.patch 1970-01-01 12:00:00.0 +1200
+++ barry-0.18.5/debian/patches/wx3.0-compat.patch 2014-06-12 01:13:55.0 +1200
@@ -0,0 +1,37 @@
+Description: Fix to build with wxWidgets 3.0
+ Should be compatible with wx2.8 too.
+Author: Olly Betts o...@survex.com
+Last-Update: 2013-03-14
+
+--- a/desktop/src/Mode.h
b/desktop/src/Mode.h
+@@ -23,6 +23,7 @@
+ #define __BARRYDESKTOP_MODE_H__
+
+ #include wx/wx.h
++#include wx/listctrl.h
+
+ class Mode
+ {
+--- a/desktop/src/bsyncjail.cc
b/desktop/src/bsyncjail.cc
+@@ -177,7 +177,7 @@
+ void BarrySyncJail::HandleConflict(OpenSync::SyncConflict conflict)
+ {
+ OpenSync::SyncConflict::iterator i;
+- int size = 0;
++ size_t size = 0;
+ wxChar *buf = 0;
+
+ // start with a new sequence ID
+--- a/desktop/src/MigrateDlg.cc
b/desktop/src/MigrateDlg.cc
+@@ -81,7 +81,7 @@ bool EventDesktopConnector::PasswordProm
+ wxCommandEvent event(MET_PROMPT_PASSWORD, wxID_ANY);
+ event.SetEventObject(m_dlg);
+ event.SetInt(bp.remaining_tries());
+- m_dlg-AddPendingEvent(event);
++ m_dlg-GetEventHandler()-ProcessEvent(event);
+ m_dlg-WaitForEvent();
+
+ password_result = m_dlg-GetPassword().utf8_str();
Bug#748918: postgrey fails to start
Control: tag -1 + fixed-upstream Hi, Geoff Crompton wrote on 22 May 2014: A fresh install of postgrey on two Wheezy machines fails to start. Much like was the case in debian bug #722136, starting the postgrey daemon on the command line reveals the same failure mode: $ sudo postgrey --inet 10023 2014/05/22-19:09:07 postgrey (type Net::Server::Multiplex) starting! pid(15633) Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 Binding to TCP port 10023 on host 127.0.0.1 with IPv4 Insecure dependency in bind while running with -T switch at /usr/lib/perl/5.14/IO/Socket.pm line 202. Applying the same patch, https://github.com/yasuhirokimura/postgrey/commit/9673b54064691a5b9c295ffea340d8a1f9ee1cb8, fixes this problem for me. Despite not being mentioned in the upstream changelog[1], that patch has been applied[2] upstream and is part of the recent 1.35 upstream release[3]. [1] http://postgrey.schweikert.ch/pub/Changes [2] https://github.com/schweikert/postgrey/commits/master [3] http://postgrey.schweikert.ch/pub/postgrey-1.35.tar.gz So packaging the new upstream release should fix the issue in Sid and Jessie. Maybe a stable-update with only that patch would be a good idea, too. Antonio and Jon: Do you need help in maintaining postgrey in Debian? I'm a long-time postgrey user at work as well as at home, and occassionally contribute to upstream's default whitelist. I also know postgrey's upstream developer from maintaining fping in Debian which has the same upstream developer. I could join you as co-maintainer. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751264: awscli: Unconditionally crashes at startup
Package: awscli Version: 1.2.9-2 Severity: grave Justification: renders package unusable Any attempt to run 'aws' crashes with the following traceback: ~$ aws --version Traceback (most recent call last): File /usr/bin/aws, line 23, in module sys.exit(main()) File /usr/bin/aws, line 19, in main return awscli.clidriver.main() File /usr/share/awscli/awscli/clidriver.py, line 44, in main driver = create_clidriver() File /usr/share/awscli/awscli/clidriver.py, line 53, in create_clidriver event_hooks=emitter) File /usr/share/awscli/awscli/plugin.py, line 49, in load_plugins plugin.awscli_initialize(event_hooks) File /usr/share/awscli/awscli/handlers.py, line 73, in awscli_initialize register_removals(event_handlers) File /usr/share/awscli/awscli/customizations/removals.py, line 32, in register_removals 'verify-email-address']) File /usr/share/awscli/awscli/customizations/removals.py, line 45, in remove self._create_remover(remove_commands)) File /usr/lib/python3/dist-packages/botocore/hooks.py, line 64, in register self._verify_accept_kwargs(handler) File /usr/lib/python3/dist-packages/botocore/hooks.py, line 84, in _verify_accept_kwargs argspec = inspect.getargspec(func) File /usr/lib/python3.4/inspect.py, line 930, in getargspec raise ValueError(Function has keyword-only arguments or annotations ValueError: Function has keyword-only arguments or annotations, use getfullargspec() API which can support them -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (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 Versions of packages awscli depends on: ii python3 3.4.1~rc1-1 ii python3-bcdoc 0.12.0-2 ii python3-botocore 0.29.0+repack-2 ii python3-colorama 0.2.5-0.2 ii python3-docutils 0.11-3 ii python3-rsa 3.1.2-1 ii python3-six 1.6.1-2 pn python3:any none awscli recommends no packages. awscli 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#751263: ppp: default pap-secrets file contains wrong example and does not work
Package: ppp Version: 2.4.6-2 Severity: normal Hi Marco, I stumbled upon the issue, that the example for a client configuration in pap- secrets is wrong. It seems that, at least on my system, the example cannot work because it is a) syntactically wrong and b) a template substitution does not work correctly. The Variable HOST is empty, thus the placeholder -HOSTNAME- is replaced with the empty string. I think one can get rid of the template completely and just include a static example (see below), also for the following other 'issues': It seems, that a newly created file will not contain the line #GENERATED-BY- DEBIAN-INSTALLER# - such that an update will not regenerate the file - at least the version installed on my system does not, as the source file does not contain that tag. Furthermore it seems strange to me, that the postinstall script is creating temporary files with a fixed name in /etc/ppp without checking first if they already exist. Then, finally, I found that the format should be something like that: # Secrets for authentication using PAP # clientserver secret acceptable local IP addresses fred* flintstone and not as the example text in the pap-secrets file suggests: # Here you should add your userid password to connect to your providers via # PAP. The * means that the password is to be used for ANY host you connect # to. Thus you do not have to worry about the foreign machine name. Just # replace password with your password. # If you have different providers with different passwords then you better # remove the following line. #-HOSTNAME- * password So -HOSTNAME- -- the variable not being replaced - should really by the username, right? I suggest something along this, note that it does not include the last line: # Here you should add your userid password to connect to your providers via # PAP. The * means that the password is to be used for ANY host you connect # to. Thus you do not have to worry about the foreign machine name you probably # do not know. Just replace password with your password and login # with the login at your ISP. # Secrets for authentication using PAP # clientserver secret login * password cheers, Florian -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ppp depends on: ii init-system-helpers 1.18 ii libc62.18-7 ii libpam-modules 1.1.8-3 ii libpam-runtime 1.1.8-3 ii libpam0g 1.1.8-3 ii libpcap0.8 1.5.3-2 ii procps 1:3.3.9-2 ppp recommends no packages. ppp 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#751133: crash on startup
Hi, Your NEO is in the OTP-only mode, so it is not a smartcard at all. You need to put the NEO in OTP/CCID or CCID-only mode, see at the bottom of the man page: TROBLESHOOTING The error No device found can be because a number of reasons. The simplest, of course, is that the device really is not connected to the machine (USB or NFC). Another reason may be that it is in a mode where ykneomgr cannot talk to it. This can happen if the device is in OTP‐ only mode (mode 0), where you must use the ykpersonalize tool to mode switch it from the OTP‐only mode. It can also happen if the device is in a MODE_FLAG_EJECT mode (i.e., 81 or 82). If that is the case, you must touch the button in order to insert the virtual smartcard before you can invoke ykneomgr. So run 'ykpersonalize -m82' or similar to change it from OTP-only mode. /Simon You wrote: Hello, the Yubikey neo doesn't seem to be detected: #pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader... This message stays forever- Though 'dmesg' says: [1171616.043090] usb 5-6.3.3: USB disconnect, device number 49 [1171622.388457] usb 5-6.3.3: new full-speed USB device number 50 using ehci-pci [1171622.482191] usb 5-6.3.3: New USB device found, idVendor=1050, idProduct=0110 [1171622.482198] usb 5-6.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1171622.482202] usb 5-6.3.3: Product: Yubikey NEO OTP [1171622.482206] usb 5-6.3.3: Manufacturer: Yubico [1171622.485176] input: Yubico Yubikey NEO OTP as /devices/pci:00/:00:1d.7/usb5/5-6/5-6.3/5-6.3.3/5-6.3.3:1.0/input/input24 [1171622.485428] hid-generic 0003:1050:0110.0011: input,hidraw4: USB HID v1.10 Keyboard [Yubico Yubikey NEO OTP] on usb-:00:1d.7-6.3.3/input0 I am using stock Debian testing with libccid 1.4.16-1 package with running pcscd on a i386 machine. Best regards, Werner -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750106: bts
retitle 750106 AppArmor ineffective for LXC reassign 750106 apparmor thanks upstream said[0] that this is not a bug in lxc, but in apparmor or the kernel, thus reassigning to apparmor. [0] https://github.com/lxc/lxc/issues/235 -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748941: mediawiki-classes: fails to install, trying to overwrite other packages files
notfound 748941 1:1.19.15+dfsg-2 found 748941 1:1.19.15+dfsg-0+deb7u1 thanks Dixi quod… is in unstable. Does this work if you first recompile the wheezy package with… http://anonscm.debian.org/viewvc/pkg-mediawiki?view=revisionrevision=544 …applied, then upgrade from it to jessie/sid? Yes it does. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722611: mutt: segfaults when sending with SMTP
On Mon, 10 Mar 2014 12:15:07 -0400, Matteo Cypriani m...@lm7.fr wrote: On Sat, 8 Mar 2014 23:11:30 +0100, Evgeni Golov evg...@golov.de wrote: That's interesting, but looks more like an libsasl issue to me. Can you reproduce the bug with the latest libsasl and mutt from unstable? Now mutt doesn't segfault any more, but right after sending the message I can see this (incomplete) message on top of the mutt display: double free or corruption (!prev): 0x0225f070 *** *** Error in `mutt': double free or corruption (!prev): 0x02260130 *** Not sure this is the same bug, but it's still related to sending an email. Please let me know if I can do anything. Cheers, Matteo Package versions: libsasl2-2 2.1.26.dfsg1-9 mutt1.5.22-1 I hadn't really used it since last time, but I just had mutt crash again after sending a mail: Envoi du message... 0K/9,6K (0%) *** Error in `mutt': double free or corruption (!prev): 0x02868280 *** zsh: abort mutt Package versions: mutt1.5.23-1 libsasl2-2 2.1.26.dfsg1-9 Cheers, Matteo pgpygkbn39wb9.pgp Description: PGP signature
Bug#751249: vtk6 is not installable (tcl-vtk conflict)
severity 751249 serious thanks Anton 2014-06-11 14:24 GMT+02:00 Jochen Sprickerhof debian-...@jochen.sprickerhof.de: Package: vtk6 Version: 6.1.0+dfsg-5 Severity: important Dear Maintainer, vtk6 is not installable (and thus libvtk6-dev as well). Problem is, that vtk6 contains a conflict against tcl-vtk because both of them contain /usr/bin/vtk. Starting with 6.1.0+dfsg-4 libvtk6.1 depends on libxdmf2, which depends on tcl-vtk. As vtk6 depends on libvtk6.1, it's not installable. I guess we either have to remove /usr/bin/vtk from the package or revert the dependency on libxdmf2. Cheers Jochen -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/12 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 vtk6 depends on: ii libc6 2.19-1 ii libgcc1 1:4.9.0-6 ii libstdc++6 4.9.0-6 ii libtcl8.6 8.6.1-6 ii libtk8.68.6.1-5 pn libvtk6 none vtk6 recommends no packages. Versions of packages vtk6 suggests: pn vtk6-doc none pn vtk6-examples none -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750029: bts
tag 750029 - help tag 750029 - moreinfo tag 750029 - unreproducible tag 750029 pending thanks given the answer from upstream in [0], i think there's nothing we can do here anymore (except having a reference to it in README.Debian). [0] https://github.com/lxc/lxc/issues/236 -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748150: again...
On 06/11/2014 09:08 AM, Ryan Kavanagh wrote: Hi Lorenzo, On Tue, Jun 10, 2014 at 10:01:13PM +0200, Lorenzo wrote: otherwise I guess this should be reported upstream. Thanks for putting in the legwork and bringing this back to my attention. The same problem exists in OpenSSH (from which the compatibility layer for opensmtpd was taken), except that the Debian OpenSSH maintainers simply patched out the entire check[0] (SONAME is sufficient nowadays for us). Upstream rewrote the broken check last night[1]. In order to minimise the delta between upstream opensmtpd and Debian, I intend to apply their fixed check later on today or tomorrow at the latest instead of simply cutting out the check as was done for OpenSSH. Best wishes, Ryan [0] http://anonscm.debian.org/gitweb/?p=pkg-ssh/openssh.git;a=blob;f=debian/patches/no-openssl-version-check.patch;h=56fa46aac080a3566941ac006c9324c0b8aa55ba;hb=HEAD [1] https://github.com/poolpOrg/OpenSMTPD/commit/452d687 So if I understand correctly the idea was to check that we aren't running on a system with an openssl library older than what opensmtpd was linked against? Hey, it makes sense finally XD -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737128: gpg exits with a fatal error about missing trustdb despite successfully having imported a key
Control: notfound -1 1.4.16-1.1 Contol: merge -1 735363 This seems to be working now: gpg --export $keyID | gpg --homedir $(mktemp -d --tmpdir gpg.XX) --trust-model=always --import -- Guilhem. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (800, 'testing'), (700, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnupg depends on: ii gpgv 1.4.16-1.1 ii libbz2-1.01.0.6-5 ii libc6 2.19-1 ii libreadline6 6.3-6 ii libusb-0.1-4 2:0.1.12-23.3 ii zlib1g1:1.2.8.dfsg-1 Versions of packages gnupg recommends: ii gnupg-curl 1.4.16-1.1 ii libldap-2.4-2 2.4.39-1 Versions of packages gnupg suggests: pn gnupg-doc none ii imagemagick 8:6.7.7.10+dfsg-3 ii libpcsclite1 1.8.11-3 -- no debconf information signature.asc Description: Digital signature
Bug#628845: notification-daemon: window manager crashes with large notification text
Intrigeri, I appreciate your reaching out to solve this bug. I am no longer running a Debian system anymore. While I appreciate the effort to fix this bug, it's too little far too late. This bug doesn't even seem to have been noticed by any developers, let alone fixed, and I filed it in 2011, almost 3 years ago to the day. I doubt it even effects anybody anymore. -- -Ed On Sat, Jun 7, 2014 at 11:38 AM, intrigeri intrig...@debian.org wrote: Hi, (Stumbling upon this bug report while looking for an issue similar to what I'm experiencing.) Ed wrote (01 Jun 2011 19:58:06 GMT) : Use a simple app like notify-send to create a notification window. Use so much text in the body of the notification that the notification does not fit vertically in the resolution. This will cause metacity to crash and restart or compiz to crash and metacity to replace it. This bug report was filed from a Squeeze system, and this version of Debian is not supported anymore. Ed, can you still reproduce it with current Debian stable (Wheezy) or newer? Also, if the window manager crashes, even if the crash is triggered by a GTK widget created by notification-daemon, I think the bug is in the window manager itself, so perhaps this bug should be reassigned. My guess is that the maintainers of that window manager will then find out that it's actually a bug in GTK, but who knows :) Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
Bug#751265: xpath missing -e option
Package: libguestfs-tools Version: 1:1.18.1-1+deb7u3 There is a typo in the man page of virt-resize: # virsh dumpxml guestname | xpath /domain/devices/disk/source should read: # virsh dumpxml guestname | xpath -e /domain/devices/disk/source See man page for xpath (libxml-xpath-perl). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750648: qpdfview: Search does not work
Hi Yoric, thank you for taking the time to report and investigate this problem. If you could answer the following questions, it would probably help tracking down its cause: 1. Does the search not work in all of your russian PDFs? 2. In those PDFs where search does not work, can you copy text from the PDF and paste it to a text file? (If this does not work, the text may actually be part of an image and not properly embedded as text in the PDF.) 3. Could you provide an example file, for which the problem occurs? Best wishes, Benjamin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751266: gnupg2: Fatal error/non-zero exit code returned when --trust-model=always used
Package: gnupg2 Version: 2.0.23-1 Severity: important Dear Maintainer, gnupg2 is also affected by #735363 (and #737128). $ gpg --export $keyID | gpg2 --homedir $(mktemp -d) --trust-model=always --import gpg: keyring `/tmp/tmp.CgvawKyhkU/secring.gpg' created gpg: keyring `/tmp/tmp.CgvawKyhkU/pubring.gpg' created gpg: Fatal: can't open `/tmp/tmp.CgvawKyhkU/trustdb.gpg': No such file or directory $ echo $? 2 (Other operation that modify the trust database if existing, such as key generation or edition, fail in a similar way.) While the issues have been dealt with in gnupg, gnupg2 is still affected. Cheers, -- Guilhem. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (800, 'testing'), (700, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnupg2 depends on: ii dpkg 1.17.10 ii gnupg-agent 2.0.23-1 ii install-info 5.2.0.dfsg.1-4 ii libassuan0 2.1.1-1 ii libbz2-1.0 1.0.6-5 ii libc62.19-1 ii libcurl3-gnutls 7.37.0-1+b1 ii libgcrypt11 1.5.3-4 ii libgpg-error01.12-0.2 ii libksba8 1.3.0-3 ii libreadline6 6.3-6 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages gnupg2 recommends: ii libldap-2.4-2 2.4.39-1 Versions of packages gnupg2 suggests: pn gnupg-doc none pn xloadimage none -- no debconf information signature.asc Description: Digital signature
Bug#751267: pu: package pydap/2.2.6.7-1.1
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu python-dap in stable is affected by #709376, which causes spurious warnings from python in unrelated scripts. Proposed debdiff: diff -Nru pydap-2.2.6.7/debian/changelog pydap-2.2.6.7/debian/changelog --- pydap-2.2.6.7/debian/changelog 2011-09-01 21:34:24.0 +0200 +++ pydap-2.2.6.7/debian/changelog 2014-06-11 16:00:07.0 +0200 @@ -1,3 +1,10 @@ +pydap (2.2.6.7-1.1) wheezy; urgency=low + + * Non-maintainer upload. + * Add dap to namespace_packages in setup.py (Closes: #709376) + + -- Julien Cristau julien.cris...@logilab.fr Wed, 11 Jun 2014 16:00:05 +0200 + pydap (2.2.6.7-1) unstable; urgency=low * Initial release (Closes: #640037) diff -Nru pydap-2.2.6.7/debian/patches/namespace.diff pydap-2.2.6.7/debian/patches/namespace.diff --- pydap-2.2.6.7/debian/patches/namespace.diff 1970-01-01 01:00:00.0 +0100 +++ pydap-2.2.6.7/debian/patches/namespace.diff 2014-06-11 15:59:38.0 +0200 @@ -0,0 +1,13 @@ +Index: pydap-2.2.6.7/setup.py +=== +--- pydap-2.2.6.7.orig/setup.py pydap-2.2.6.7/setup.py +@@ -59,7 +59,7 @@ The latest version is available in a `Su + url='http://pydap.org/', + license='MIT', + packages=find_packages(exclude=['ez_setup', 'examples', 'tests']), +- namespace_packages=['dap.plugins', 'dap.responses'], ++ namespace_packages=['dap', 'dap.plugins', 'dap.responses'], + include_package_data=True, + zip_safe=False, + install_requires=[ diff -Nru pydap-2.2.6.7/debian/patches/series pydap-2.2.6.7/debian/patches/series --- pydap-2.2.6.7/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ pydap-2.2.6.7/debian/patches/series 2014-06-11 15:59:19.0 +0200 @@ -0,0 +1 @@ +namespace.diff -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/16 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Julien Cristau julien.cris...@logilab.fr Logilab http://www.logilab.fr/ Informatique scientifique gestion de connaissances -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689962: linux-image-3.2.0-4-amd64: Compile with CONFIG_VIRTIO_CONSOLE=y
On Sat, 13 Oct 2012, Vincent Bernat wrote: In fact, as of 3.6, it is not possible to use virtconsole as an initial console. I don't know if this will be fixed later but this makes the bug It’s fixed. I just installed Ubuntu’s 3.15 on Debian wheezy and booted with “console=hvc0” and it worked. So +1 please set this =y even in Debian. Thanks, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749560: transition: miniupnpc
On 11/06/14 11:53, Thomas Goirand wrote: Hi Emilio, Thanks a lot for your help and the advices. I hope to learn and know well how to manage transitions after this one (as I did a poor job with them before). :) On 06/10/2014 02:13 AM, Emilio Pozuelo Monfort wrote: In the meantime, please upload to experimental so that it goes through NEW. This was done. Good. I see there are build failures on kfreebsd. After I pinged upstream it was fixed in the last version, which I just uploaded. Cool. Though there's FTBFS issues seemingly related to the new version of miniupnpc with these: - 0ad: see [1] below - megaglest: see [2] below - warzone2100: see [3] below Open bugs with severity important. Bonus points if you provide patches (that will greatly help get this transition started (and finished)). Bugs open with patches (with help from upstream of MiniUPnPc): 0ad: #751224 megaglest: #751225 warzone2100: #751229 I have checked the build with newer MiniUPnP client, and no issues as far as I can tell. Great! And then these seem to have unrelated FTBFS in Sid: - eiskaltdcpp: FTBFS (in eiskaltdcpp-qt/src/ChatEdit.cpp which doesn't have UPNP stuff) - litecoin: FTBFS (but package not in Testing anyway) Try to reproduce in a clean sid environment and report bugs with severity serious. I have no time to do that right now, will try to do so later on. OK. once we know if those fail to build, and if so, once they are fixed or at least fixes are available (especially for eiskaltdcpp which is in testing) then we should be able to proceed. Open those bugs and make them block this one. If you provide patches, at least for the ones caused by miniupnpc, we could start the transition and then ask for the patches to be applied, NMU-ing if that doesn't happen. What's the reasonable amount of time after which we can NMU (to the delayed queue?) for such a transition? After miniupnpc hits unstable, the bugs become RC as the packages fail to build, and IMHO direct uploads to DELAYED/2 would be fine. Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751268: iceweasel-dev: Re-add pkg-config files
Package: iceweasel-dev Version: 30.0-1 Hi Mike On 2014-06-11 11:47:17, Mike Hommey wrote: I just uploaded iceweasel 30 to unstable, which is the first version not to provide xulrunner-dev. Instead, there is an iceweasel-dev package, and it most certainly has things missing. Read: I *know* there are things missing. I just don't know what specifically reverse build deps would need. This is where I need your assistance: could you try building your packages against iceweasel-dev and see what they are bugging about? Please file bugs against iceweasel-dev for anything missing you'd encounter. The gecko-mediaplayer package uses the pkg-config files provided by xulrunner-dev to obtain the location of the SDK. There doesn't seem to be a pkg-config file present in iceweasel-dev that allows to obtain the information. Please add it back. (If the use of the pkg-config is outdated, please let me know what's the current recommended way to get the the location of SDK.) Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#751269: libetpan-dev: Please switch dependency from libgnutls-dev to libgnutls28-dev
Source: libetpan-dev Version: 1.4.1-1 Severity: important Hi, Please switch the libetpan-dev against libgnutls-dev to libgnutls28-dev The library itself is built against libgnutls28-dev so I guess the -dev package should be adjusted too. Cheers, Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735946: ITP: shc -- Generic shell script compiler
Hi Tong! How are you? I checked your package again and I saw you are using two patch to override a Makefile self change. The correct action is say to DH to ignore changes in file. You can use this patch: --- shc-3.8.9.orig/debian/source/options1969-12-31 21:00:00.0 -0300 +++ shc-3.8.9/debian/source/options 2014-06-11 12:46:12.878450159 -0300 @@ -0,0 +1 @@ +extend-diff-ignore = ^Makefile$ So, you can remove the Makefile patches. A good news for you: I am in last step to become a DD. I think that I need wait a month or less. So, I will can upload your package. Have a nice day! Cheers, Eriberto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751270: bitlbee: Twitter broken in Stable's Bitlbee (Please Backport?)
Package: bitlbee Version: 3.0.5-1.2 Severity: wishlist Dear Maintainer, It is currently impossible to use a Twitter account through the Bitlbee in Stable. According to the Bitlbee Version Reference [0], the version currently in Testing should be able to perform this task. However, it is not possible to install the Testing version of Bitlbee onto Stable currently (requires newer libc). Could we have the Testing version of Bitlbee available through wheezy-backports? Thanks! [0]: http://wiki.bitlbee.org/VersionReference -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (800, 'stable-updates'), (800, 'stable'), (600, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (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 Versions of packages bitlbee depends on: ii bitlbee-common 3.0.5-1.2 ii debianutils 4.3.2 ii libc6 2.13-38+deb7u1 ii libevent-2.0-5 2.0.19-stable-3 ii libgcrypt11 1.5.0-5+deb7u1 ii libglib2.0-02.33.12+really2.32.4-5 ii libgnutls26 2.12.20-8+deb7u2 bitlbee recommends no packages. bitlbee 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#735946: ITP: shc -- Generic shell script compiler
Thanks Eriberto for your tip and your good news. That's really good timing, I was planning to revisit/repack shc within a month. Cheers On Wed, Jun 11, 2014 at 11:50 AM, Eriberto eribe...@eriberto.pro.br wrote: Hi Tong! How are you? I checked your package again and I saw you are using two patch to override a Makefile self change. The correct action is say to DH to ignore changes in file. You can use this patch: --- shc-3.8.9.orig/debian/source/options1969-12-31 21:00:00.0 -0300 +++ shc-3.8.9/debian/source/options 2014-06-11 12:46:12.878450159 -0300 @@ -0,0 +1 @@ +extend-diff-ignore = ^Makefile$ So, you can remove the Makefile patches. A good news for you: I am in last step to become a DD. I think that I need wait a month or less. So, I will can upload your package. Have a nice day! Cheers, Eriberto
Bug#750708: RFS: audiotools/2.21-3 [ITP] -- Collection of audio handling programs for the command line
On Sat, Jun 7, 2014 at 2:23 PM, Eriberto Mota eribe...@eriberto.pro.br wrote: Hi Eric, If it is an ITP, the package no exist in Debian yet. So, you musn't report revisions. Please, remove all entries about the -2 and -3 revisions in d/changelog. I suggest you put the upstream e-mail address in d/copyright. Searching in Google: b...@biosci.umn.edu and tu...@users.sourceforge.net. Yes, added upstream e-mail address, cleaned up (removed) revisions: http://mentors.debian.net/debian/pool/main/a/audiotools/audiotools_2.21-1.dsc Note that I am not able to upload your package. But I want to say that your package appears very good. Regards, Eriberto Thanks! Who can sponsor this package, should I offer it to python packagers? Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751252: caff: doesn't send email found no signed uids
Hi! Putting min-cert-level 1 in .caff/gnupghome/gpg.conf solved, thanks :) The outputs from the two lines you indicated are different: $ gpg --min-cert-level=1 --export-options export-clean --export $keyID | gpg --list-packets | grep 'sigclass 0x11$' |wc -l 11 $ gpg --min-cert-level=2 --export-options export-clean --export $keyID | gpg --list-packets | grep 'sigclass 0x11$' |wc -l 0 I have to retire my statement on Key2: the problem is present also with this key. To verify this I created a new gpg key with an empty pubring and tried to sign with caff that Key2 and it didn't work. With my main key I didn't see the problem because in the past I signed a few userids of that key (with cert-level=3). Thanks, Ilario -- Ilario Gelmetti iocheson...@gmail.com ilario.gelme...@sns.it signature.asc Description: OpenPGP digital signature
Bug#750708: RFS: audiotools/2.21-3 [ITP] -- Collection of audio handling programs for the command line
2014-06-11 12:57 GMT-03:00 Eric Shattow luc...@gmail.com: On Sat, Jun 7, 2014 at 2:23 PM, Eriberto Mota eribe...@eriberto.pro.br wrote: Hi Eric, If it is an ITP, the package no exist in Debian yet. So, you musn't report revisions. Please, remove all entries about the -2 and -3 revisions in d/changelog. I suggest you put the upstream e-mail address in d/copyright. Searching in Google: b...@biosci.umn.edu and tu...@users.sourceforge.net. Yes, added upstream e-mail address, cleaned up (removed) revisions: http://mentors.debian.net/debian/pool/main/a/audiotools/audiotools_2.21-1.dsc Note that I am not able to upload your package. But I want to say that your package appears very good. Regards, Eriberto Thanks! Who can sponsor this package, should I offer it to python packagers? You can try it or try to get someone on Debian IRC. Cheers, Eriberto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751271: usb-modeswitch: doesn't switch Huawei E3131s-2 on boot
Package: usb-modeswitch Version: 2.2.0+repack0-1 After I upgraded usb-modeswitch (2.1.1+repack0-1 = 2.2.0+repack0-1) and usb-modeswitch-data (20140327-1 = 20140529-1), my Huawei E3131s-2 is no longer switched on boot: $ lsusb | grep -w Huawei Bus 001 Device 002: ID 12d1:14fe Huawei Technologies Co., Ltd. I had to physically plug out the device, and then plug it in again to make the switching happen: $ lsusb | grep -w Huawei Bus 001 Device 005: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages usb-modeswitch depends on: ii libc62.19-1 ii libjim0.74 0.74-3 ii libusb-1.0-0 2:1.0.18-2 ii usb-modeswitch-data 20140529-1 Versions of packages usb-modeswitch suggests: pn comgt none ii wvdial 1.61-4.1 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751272: kdeplasma-addons should build depend on libqwt5-qt4-dev to build kdeobservatory
Source: kdeplasma-addons Version: kdeplasma-addons should build dep on libqwt5-qt4-dev Severity: normal Dear Maintainer, Please make kdeplasma-addons build depend on libqwt5-qt4-dev so that the additional package plasma-widget-kdeobservatory can also be built. -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty-proposed'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.0-30-generic (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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750296: autoreconf causes FTBFS in raptor
I just confirmed this issue on arm64 (building raptor for the first time). Removing the autoreconf.mk line from debian/rules lets it build. So the shipped ./configure is OK, but the one generated by the autoreconf isn't. I've not yet investigated further. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750106: bts
Hi, upstream said[0] that this is not a bug in lxc, but in apparmor or the kernel, thus reassigning to apparmor. [0] https://github.com/lxc/lxc/issues/235 There are two problems here: 1. According to John Goerzen's report upstream, lxc-start is confined, but apparently the container is not. That might be a bug in our apparmor package. John, may you please check if processes inside the container are confined (e.g. the shell from which you're writing to /proc/sys/fs/...)? 2. The container profiles (/etc/apparmor.d/lxc/lxc-default) shipped in the lxc package can't possibly work yet, as they all use mount rules, that are only available when using AppArmor 2.8.95 userspace, plus some out-of-tree kernel patches: that's why the Upstart job provided by upstream doesn't load these profiles unless /sys/kernel/security/apparmor/features/mount/mask exists. IMO that's clearly a bug in the lxc package, to ship stuff that depends on a version of another package that's not in Debian yet (in Ubuntu, lxc depends on apparmor (= 2.8.95~2430-0ubuntu4), combined with out-of-tree kernel features that are not in Debian either. *But*, from a let's get better AppArmor support in Debian strategic PoV, I'd rather *not* see the maintainer of lxc in Debian drop the AppArmor support altogether: having it in makes it easier to experiment and improve things, e.g. for anyone who would want to test 2.8.95 + the minimal amount of out-of-tree Linux patches needed for mount mediation, if e.g. they were going to try and get these patches in the kernel we ship in Jessie. So, I'd rather not bother Daniel about this. Still, it would be great if the lxc Debian package did document these limitations. Given that Daniel is not interested in AppArmor, a bug report with a patch attached would seem to be the most sensible approach. Any taker? Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750093: debian-maintainers: Please add Sandro Knauß as a Debian Maintainer
package debian-maintainers 750093 tags - moreinfo stop Uploaded the key with extended expire date ( two years from now on) to pool.sks-keyservers.net. Regards, sandro -- Am Mittwoch, 11. Juni 2014, 19:24:14 schrieb Aníbal Monsalve Salazar: package debian-maintainers 750093 tags + moreinfo stop Hello Sandro, The report of the keycheck.sh script for your key is below. pub 4096R/50605636 2013-08-15 [expires: 2014-08-15] Key fingerprint = 39EC 11A0 2016 B729 2649 1A06 E3AD B008 5060 5636 uid Sandro Knauß b...@sandroknauss.de sig! FDFE09F2 2013-08-30 David Prévot da...@tilapin.org sig! B29B232A 2014-05-05 Maximiliano Curia m...@debian.org sig! 68E7B931 2014-06-04 Hannes von Haugwitz han...@vonhaugwitz.com sig!350605636 2013-08-15 Sandro Knauß b...@sandroknauss.de sub 4096R/F672558F 2013-08-15 [expires: 2014-08-15] sig! 50605636 2013-08-15 Sandro Knauß b...@sandroknauss.de . Key is OpenPGP version 4 or greater. Key has 4096 bits. Valid e flag, but it expires Fri 15 Aug 2014 20:07:47 UTC. This is too soon! Please ask the applicant to extend the lifetime of their OpenPGP key. Valid s flag, but it expires Fri 15 Aug 2014 20:07:47 UTC. This is too soon! Please ask the applicant to extend the lifetime of their OpenPGP key. Please extend the lifetime of your key above. Upload it to a keyserver (I use pgp.net.nz) and delete the moreinfo tag. Cheers, Aníbal signature.asc Description: This is a digitally signed message part.
Bug#751273: ruby-bluecloth: Conflicting declarations of mkd_compile, mkd_string to cause undefined behaviour
Package: ruby-bluecloth Version: 2.2.0-4 Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. Please note that we use our research compiler tool-chain (using tools from the cbmc package), which permits extended reporting on type inconsistencies at link time. [...] gcc -shared -o bluecloth_ext.so bluecloth.o markdown.o html5.o mkdio.o version.o xml.o generate.o css.o setup.o xmlpage.o tags.o emmatch.o docheader.o resource.o Csio.o -L. -L/usr/lib/x86_64-linux-gnu -L. -Wl,-z,relro -L/build/ruby2.1-R1fHdQ/ruby2.1-2.1.2/debian/lib -fstack-protector -rdynamic -Wl,-export-dynamic-lruby-2.1 -lpthread -lgmp -ldl -lcrypt -lm -lc error: conflicting function declarations mkd_compile old definition in module bluecloth file mkdio.h line 23 signed int (void *, unsigned int) new definition in module markdown file markdown.c line 1211 signed int (struct document *doc, unsigned long int flags) error: conflicting function declarations mkd_string old definition in module bluecloth file mkdio.h line 13 void * (const char *, signed int, unsigned int) new definition in module mkdio file mkdio.c line 173 struct document * (const char *buf, signed int len, unsigned long int flags) Makefile:232: recipe for target 'bluecloth_ext.so' failed make[1]: *** [bluecloth_ext.so] Error 64 make[1]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-ruby-bluecloth/ruby-bluecloth-2.2.0/ext' For any platform with sizeof(unsigned int)sizeof(unsigned long int) the behaviour will be undefined in at least one of two ways: several bytes will take an undefined value; for big endian systems, the wrong set of bytes will be extracted. On review of the code, it seems some cleanup of typedefs is required: mkdio.h uses mkd_flag_t while mkdio.c uses DWORD: http://sources.debian.net/src/ruby-bluecloth/2.2.0-4/ext/mkdio.h?hl=13#L13 http://sources.debian.net/src/ruby-bluecloth/2.2.0-4/ext/mkdio.c?hl=173#L173 Best, Michael pgpSUZKOs3VMH.pgp Description: PGP signature
Bug#751274: RM: specimen -- ROM; package is abadoned upstream, alternative exist
Package: ftp.debian.org Severity: normal specimen has been abadoned upstream. regards mira -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678446: Updated util-linux to 2.24.2, ok to upload to experimental?
Hello LaMont Jones, everybody! I've spent a couple of days on updating util-linux to v2.24.2 and preparing the package to in the future be easier to update to new releases. There's still much work to do, but I'm now in a state which feels like a good start to look at ironing out any problems I might have introduced in architecture specific parts of the packaging. I feel that uploading to experimental would be a good start to see which architectures still builds. Do you have anything against me uploading my version to experimental? Regards, Andreas Henriksson PS. I have full git history for my changes based on the patches/v2.20.1 branch in your git repository. If you're interested maybe we could discuss a place to share git branches? collab-maint? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751275: plymouth: Kernel error message regarding DRM shown during boot
Package: src:plymouth
Version: 0.8.5.1-5
Severity: minor
Tags: patch
Hi,
I'm using Debian Wheezy and plymouth 0.8.5.1-5 with Kernel 3.10.40 on
an embedded system equipped with a Radeon E6760. For better graphics
performance I've installed fglrx and use uvesafb to get plymouth working.
Quite early in the boot process a kernel error message appears on the
screen and destroys the otherwise slick boot process:
[1.497550] [drm:drm_pci_agp_init] *ERROR* Cannot initialize
the agpgart module.
[1.497629] DRM: Fill_in_dev failed.
I found out that the drm kernel module is not copied into the
initramfs which apparently causes the error message.
I've attached a patch that addresses that problem and works quite well
for me.
Regards,
Lukas
From a856e7b1e08471d941fe5ca41f6ce67f1f223e03 Mon Sep 17 00:00:00 2001
From: Lukas Anzinger lu...@lukasanzinger.at
Date: Wed, 11 Jun 2014 18:12:24 +0200
Subject: [PATCH] Copy module drm into initramfs to fix annoying drm
initializing error message.
This fixes the following error message:
[1.497550] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart module.
[1.497629] DRM: Fill_in_dev failed.
---
debian/local/plymouth.hook | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/local/plymouth.hook b/debian/local/plymouth.hook
index b499a30..c386704 100644
--- a/debian/local/plymouth.hook
+++ b/debian/local/plymouth.hook
@@ -122,7 +122,7 @@ case ${THEME_NAME} in
copy_exec /usr/lib/@DEB_HOST_MULTIARCH@/plymouth/renderers/drm.so
# add drm modules
- copy_modules_dir kernel/drivers/gpu/drm mga r128 savage sis tdfx via
+ copy_modules_dir kernel/drivers/gpu/drm drm mga r128 savage sis tdfx via
;;
esac
--
2.0.0
Bug#751276: RM: phat -- ROM; package is abadoned upstream
Package: ftp.debian.org Severity: normal phat has been abadoned upstream. Only dependant is specimen package which is also asked for removing. regards mira -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678446: Updated util-linux to 2.24.2, ok to upload to experimental?
On Wed, Jun 11, 2014 at 06:22:56PM +0200, Andreas Henriksson wrote: Do you have anything against me uploading my version to experimental? Yes, because I've been doing the same thing, as well as converting the package to v3 quilt. Did you expect that this work wouldn't clash with anyone else's? ... Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751277: python-biopython: FTBFS on mips* powerpc s390x
Source: python-biopython
Version: 1.64+dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
All four archs fail with a similar error:
E: pybuild pybuild:256: test: plugin custom failed with: exit code=1: mkdir -p
/«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_2.7/build/Doc; \
cp -a Doc/Tutorial.tex
/«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_2.7/build/Doc; \
cp -a Tests
/«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_2.7/build; \
cd
/«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_2.7/build/Tests; \
env DIALIGN2_DIR=/usr/share/dialign
EMBOSS_ROOT=/usr/lib/emboss HOME=/tmp python2.7 run_tests.py --offline
dh_auto_test: pybuild --test -i python{version} -p 2.7 --test --system=custom
--test-args=mkdir -p {build_dir}/Doc; \
cp -a Doc/Tutorial.tex {build_dir}/Doc; \
cp -a Tests {build_dir}; \
cd {build_dir}/Tests; \
env DIALIGN2_DIR=/usr/share/dialign
EMBOSS_ROOT=/usr/lib/emboss HOME=/tmp {interpreter} run_tests.py --offline
--dir . returned exit code 13
make[1]: *** [override_dh_auto_test] Error 13
debian/rules:56: recipe for target 'override_dh_auto_test' failed
make[1]: Leaving directory '/«BUILDDIR»/python-biopython-1.64+dfsg'
make: *** [build-arch] Error 2
debian/rules:48: recipe for target 'build-arch' failed
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750527: mediawiki: Javascript inject by anonymous users on private wikis with $wgRawHtml enabled
Source: mediawiki Source-Version: 1:1.19.16+dfsg-1 On Wed, Jun 04, 2014 at 09:59:39AM +0300, Henri Salo wrote: Package: mediawiki Version: 1:1.19.15+dfsg-2 Severity: normal Tags: security, fixed-upstream Needs wgRawHTML enabled so this may not be easy to exploit and might not be affected by default. Details of the issue: https://bugzilla.wikimedia.org/show_bug.cgi?id=65501 CVE request: http://www.openwall.com/lists/oss-security/2014/06/03/7 This was fixed with the recent mediawiki 1:1.19.16+dfsg-1 upload to unstable. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751093: [Pkg-openssl-devel] Bug#751093: Downgrading to 1.0.1e-2+deb7u9 appears to fix this
On Wed, Jun 11, 2014 at 11:13:03AM +0100, Ian Chard wrote: I downgraded openssl and libssl1.0.0 to 1.0.1e-2+deb7u9 this morning, and my job has been running for two hours without incident. Previously it was failing after 15 minutes or so. I've got someone else reporting the same issue, also with postgres. In that case it was from a box running wheezy (with 1.0.1) connecting to a server running squeeze (with 0.9.8). You also mentioned that it's an upgrade, and maybe postgres is still using libssl0.9.8? Please note that it's not because you have libssl1.0.0 installed that you're also really using it. postgres needs to be linked with that version. I suspect it's still using the 0.9.8 version. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751278: libguestfs: FTBFS on amd64, i386, and mips*
Source: libguestfs Version: 1:1.26.3-1 Severity: serious Justification: fails to build from source (but built successfully in the past) From the build logs, the X86 and mips* issues seem to be different: amd64: make[4]: *** [pkg/linux_amd64/libguestfs.org/guestfs.a] Error 2 Makefile:1821: recipe for target 'pkg/linux_amd64/libguestfs.org/guestfs.a' failed make[4]: Leaving directory '/«PKGBUILDDIR»/debian/build-python3.4/golang' make[3]: *** [all-recursive] Error 1 Makefile:1868: recipe for target 'all-recursive' failed make[3]: Leaving directory '/«PKGBUILDDIR»/debian/build-python3.4' make[2]: *** [all] Error 2 Makefile:1741: recipe for target 'all' failed make[2]: Leaving directory '/«PKGBUILDDIR»/debian/build-python3.4' dh_auto_build: make -j4 INSTALLDIRS=vendor LD_RUN_PATH= EXTRA_JAVAC_FLAGS+=-source 1.6 -target 1.6 returned exit code 2 make[1]: *** [override_dh_auto_build] Error 2 debian/rules:90: recipe for target 'override_dh_auto_build' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-arch] Error 2 debian/rules:153: recipe for target 'build-arch' failed mips: [ 195.276000] hub 1-0:1.0: 2 ports detected [ 242.168000] physmap platform flash device: 0040 at 1e00 [ 331.956000] physmap-flash.0: Found 1 x32 devices at 0x0 in 32-bit bank. Manufacturer ID 0x00 Chip ID 0x00 [ 385.708000] Intel/Sharp Extended Query Table at 0x0031 [ 385.90] Using buffer write method [ 489.968000] Searching for RedBoot partition table in physmap-flash.0 at offset 0x3f [ 490.06] No RedBoot partition table detected in physmap-flash.0 make[2]: *** [quickcheck] Alarm clock Makefile:2375: recipe for target 'quickcheck' failed make[2]: Leaving directory '/«PKGBUILDDIR»/debian/build-default' make[1]: *** [override_dh_auto_test] Error 2 debian/rules:97: recipe for target 'override_dh_auto_test' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-arch] Error 2 debian/rules:153: recipe for target 'build-arch' failed mipsel: make[2]: Leaving directory '/«PKGBUILDDIR»/debian/build-default' make[1]: Leaving directory '/«PKGBUILDDIR»' debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' make -C /«PKGBUILDDIR»/debian/build-default quickcheck make[2]: Entering directory '/«PKGBUILDDIR»/debian/build-default' ../run test-tool/libguestfs-test-tool collect2: error: ld terminated with signal 11 [Segmentation fault]nmake[2]: *** [quickcheck] Error 1 make[1]: *** [override_dh_auto_test] Error 2 Makefile:2375: recipe for target 'quickcheck' failed make[2]: Leaving directory '/«PKGBUILDDIR»/debian/build-default' debian/rules:97: recipe for target 'override_dh_auto_test' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-arch] Error 2 debian/rules:153: recipe for target 'build-arch' failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747341: Info received (Confirmation)
Okay, I ran bash under gdb and got a backtrace which perhaps points to readline. While it's hard to lay blame with a malloc error, this fits with my experience as bash would often crash immediately after exiting a command and returning to the prompt. Josh: Do you have a specialized ~/.inputrc? I do and I wonder if that could be what's triggering the bug for us. A lesser possibility could be a customized prompt. Have you changed your PS1 from Debian's default? My PS1='\h:\W\$ ' My .inputrc follows == # Time-stamp: 2013-09-17 23:27:36 ben -*- conf -*- # This file is read by Bash when the user first logs in # or if the user runs bind -f ~/.inputrc (or hits C-x C-r) # Ben prefers tcsh style history completion for M-p, M-n. \en: history-search-forward \ep: history-search-backward # Keep cursor column when using C-p, C-n # (Ben finds this VERY useful: exploit referential locality) set history-preserve-point on # Don't leave lines in the history edited after hitting return. # (Too many times I've been unable to find commands that I Control-u'd.) set revert-all-at-newline on # Readline should not prevent me from binding ^W. set bind-tty-special-chars off # ^w wipes a region instead of the standard unix word rubout. # Now I can use ^w to cut and ^y to paste, just like in emacs. \C-w: kill-region # M-w copies the region \ew: copy-region-as-kill # ^u should clear everything, not just delete to the left! \C-u: kill-whole-line # I like to see the file types during tab-completion (like ls -F). set visible-stats on # Tab completion should put a slash at the end of a symlink to a directory set mark-symlinked-directories on # Tab completion should not show dot files unless I type a dot first. set match-hidden-files off Experiment: September 17, 2013 # Should normal C-p (or up arrow) also do history-search-backwards? # Let's see if I like it. \C-n: history-search-forward \C-p: history-search-backward \e[B: history-search-forward \e[A: history-search-backward \eOB: history-search-forward \eOA: history-search-backward Experiment: September 17, 2013 # I'm not sure that this is useful, but it certainly doesn't seem harmful. # I'll try it out and see if it bugs me. # # When performing completion in the middle of a word, do not insert # characters from the completion that match characters after point in # the word being completed, so portions of the word following the # cursor are not duplicated. set skip-completed-text on # Experiment: November 10, 2009 # # Disabled on Ursula because Bash 3.2 doesn't have shell-*-word. 4/2010 # # M-f, M-b, M-d, M-DEL refer to *shell* words rather than English words. # # For example, in: mv a\ b\ c\ d z\ y\ x\ w # # a b c d would be one word and z y x w would be another word. # \ef: shell-forward-word # \eb: shell-backward-word # \ed: shell-kill-word # \e\C-?: shell-backward-kill-word # \e\C-h: shell-backward-kill-word # # Also, bind the original English functions to shifted M-F and M-B. # # Note that we can't access the shifted kill-word keys because # # M-D is a VT cursor escape sequence and DEL can't be shifted. # \eF: forward-word # \eB: backward-word ### CRUFT TO REMEMBER # # Instead of ringing the bell, show all completion possibilities? NO! BAD! # Ben was testing. I've left this in here to remind myself that I don't like it. #set show-all-if-ambiguous on # 8-bit keystrokes should be interpreted as meta, not latin1. # (You can to disable this for the next input character with ^V.) # DISABLED APRIL 28th 2006; Ben is moving to UTF-8 now... # INSTEAD USE xterm's metaSendsEscape resource. #set convert-meta on # Mark modified history lines with an asterisk. (UGLY but USEFUL.) # # REASONING: # Sometimes when I'm searching in my history, the command I'm looking # for isn't there anymore. The reason is that I had started editing # the line previously and then used C-n or C-p to go to a different # line. Unlike tcsh, bash does *not* reset the line to be unedited # automatically if you don't execute the edited line. By marking # modified lines, at least I'll know the line was edited and can hit # M-r to reset it manually. # # mark-modified-lines on -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751252: caff: doesn't send email found no signed uids
On Wed, 11 Jun 2014 at 17:56:50 +0200, Ilario Gelmetti wrote: I have to retire my statement on Key2: the problem is present also with this key. To verify this I created a new gpg key with an empty pubring and tried to sign with caff that Key2 and it didn't work. With my main key I didn't see the problem because in the past I signed a few userids of that key (with cert-level=3). I see. In fact gpg's manpage says that “signatures that are not usable” are not exported with option ‘export-clean’, so I manually set (in revision 638) the cutoff level to 1 in such cases. -- Guilhem. signature.asc Description: Digital signature
