gmane.linux.debian.devel.bugs.general

Bug#709222: apt-listchanges: Poor grammar in Italian translation of a configuration question

Riccardo Boninsegna — 2013-05-21T17:41:25

Package: apt-listchanges
Version: 2.85.11
Severity: minor
Tags: l10n

As I was reconfiguring apt-listchanges to set my actual user to receive a copy
of changelogs, this dialog popped up:

"È possibile tener traccia dei cambiamenti già mostrate per evitare di
mostrarle nuovamente in seguito. [...]
apt-listchanges deve ignorare i cambiamenti già mostrate?"

This translation of the "Should already seen changelogs be ignored?" question
has gender concordance issues, assuming "changelogs" are female. A correct
phrase would be as follows:
"È possibile tener traccia dei cambiamenti già mostrati per evitare di
mostrarle nuovamente in seguito. [...]
apt-listchanges deve ignorare i cambiamenti già mostrati?"

Bug#367030: Valgrind internal error: Valgrind recieved SIGSEGV -- when valgrinding one app that normally causes glibc free() error

Andreas Metzler — 2013-05-21T17:47:43

reopen 367030
found 367030 1:3.8.1-3
thanks

On 2013-05-10 Alessandro Ghedini <ghedo< at >debian.org> wrote:
[...]


Hello,

I just got exactly the same mesage when trying get valgrind info for a
failing test of gnutls28 on mips[1]:
----------------
(experimental_mips-dchroot)ametzler< at >gabrielli:~/GNUTLS$ valgrind ./gnutls28-3.1.11/tests/mini-xssl
==4877== Memcheck, a memory error detector
==4877== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==4877== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==4877== Command: ./gnutls28-3.1.11/tests/mini-xssl
==4877==
==4877== Source and destination overlap in VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
--4877-- si_code=1;  Faulting address: 0xBB4C;  sp: 0x426bdbd8

valgrind: the 'impossible' happened:
   Killed by fatal signal
==4877==    at 0x380E6AB0: ??? (in /usr/lib/valgrind/memcheck-mips32-linux)
==4877==    by 0x380E7584: ??? (in /usr/lib/valgrind/memcheck-mips32-linux)

sched status:
  running_tid=1

Bug#709216: qemu-system-x86 wants libvirt0 >= 1.0 only available in experimental

Michael Tokarev — 2013-05-21T17:44:21

Oh. I haven't noticed that not all necessary bits are available in unstable.

So, what do you think we should do?  Remove qemu from unstable?

Thanks,

/mjt

Bug#709221: RM: qcad -- ROM; transitional package for Wheezy

Scott Howard — 2013-05-21T17:41:41

Package: ftp.debian.org
Severity: normal

qcad has now transitioned to librecad. We can remove qcad from unstable now.

Bug#709168: src:fftw3: FTBFS on ia64: r2cf_8.c:83:1: internal compiler error

Sébastien Villemot — 2013-05-21T17:35:56

Le mardi 21 mai 2013 à 19:28 +0200, Julien Cristau a écrit :

Thanks for clarifying. Anyways, removing from unstable is not an option
either, given the high number of reverse dependencies.

Bug#709220: gcc-4.6: building fomus crashes gcc

Neuwirth Erich — 2013-05-21T17:28:44

Package: gcc-4.6
Version: 4.6.3-14+rpi1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***

Bug#709219: /etc/pf.conf refers to non-existing /usr/share/examples/pf (should be /usr/share/doc/pf/examples/)

Yaroslav Halchenko — 2013-05-21T17:16:58

Package: pf
Version: 9.0+ds1-10
Severity: minor
File: /etc/pf.conf

cheers

Bug#709218: developers-reference: adjust versioning convention note for security updates

Salvatore Bonaccorso — 2013-05-21T17:31:39

Package: developers-reference
Version: 3.4.10
Severity: normal
Tags: patch

Hi

In #685646 the advise for versioning for {stable,testing}{,-security}
uploads was adjusted. In [1] there is a missing bit for it refering to
the older convention +codename1. I tried to address this change in
attached patch.

 [1] http://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security

Regards,
Salvatore

Bug#709168: src:fftw3: FTBFS on ia64: r2cf_8.c:83:1: internal compiler error

Julien Cristau — 2013-05-21T17:28:59

No, that's not how it works.  In order to be a candidate for testing
migration, it needs to not have out of date binaries *in unstable*.

Cheers,
Julien

Bug#708960: fprintd: Lost enrolled fingerprint after upgrade

Didier 'OdyX' Raboud — 2013-05-21T17:28:22

Hi Michele, and thanks for your bugreport,

Le dimanche, 19 mai 2013 21.03:58, Michele Cane a écrit :

That's puzzling indeed. Did you update both libfprint and fprintd at the same 
time? Would it be possible for you to test whether this also happens if you 1) 
upgrade; 2) reboot; 3) test ?

Meilleures salutations,

OdyX

Bug#707386: grig: diff for NMU version 0.8.0-1.1

Kamal Mostafa — 2013-05-21T17:27:45


Thanks, Sebastian!  Your help is very much appreciated!

 -Kamal

Bug#709207: cups: Duplex printing from ios6 via airprint doesn't work

Didier 'OdyX' Raboud — 2013-05-21T16:41:43

Hi Jonas, and thanks for your bugreport,

.oO(Putting Till in copy)

Le mardi, 21 mai 2013 19.31:20, Jonas Meyer a écrit :

This makes me think either the printer itself or the PPD files are at fault 
here. Does the same happen on other printers that you could eventually test?


What "any other way" are you referring to here? Duplex-printing from non-iOS 
devices?


That's a reasonable expectation indeed.

Cheers,

OdyX

Bug#709168: src:fftw3: FTBFS on ia64: r2cf_8.c:83:1: internal compiler error

Julian Taylor — 2013-05-21T17:25:55

setting CC=gcc-4.8 works for fftw3, add it e.g. to archconfflags in
debian/rules:70

Bug#709168: src:fftw3: FTBFS on ia64: r2cf_8.c:83:1: internal compiler error

Anton Gladky — 2013-05-21T17:25:23

Hi,

the same problem is with lammps. It cannot migrate due to fftw3.
So, the removal could be one possible solution.

Thanks,

Anton

On 05/21/2013 07:17 PM, Sébastien Villemot wrote:

Bug#706888: cups: Could not print to server after upgrade: Failed to add Avahi entry

Didier 'OdyX' Raboud — 2013-05-21T17:06:22

Control: tags -1 +moreinfo

Hi Luc, and thanks for your bugreport,

Le dimanche, 5 mai 2013 21.52:37, Luc Castermans a écrit :

Was avahi-daemon installed (it is "Recommended" by cups) and running?

Avahi is needed in a way or another for automated printers discovery and 
bonjour-based printer queues.

Thanks in advance,

OdyX

Bug#696332: lsb-release: release/codename depend on a successful apt-get

Didier 'OdyX' Raboud — 2013-05-21T17:22:09

Control: tags -1 +moreinfo 

Hi varacanero, and thanks for your bugreport,

Le mercredi, 19 décembre 2012 18.20:27, varacanero a écrit :

Even if your log confirms that, I can't reproduce this behaviour on jessie.


How does your /etc/debian_version look like ? And what is the output of `apt-
cache policy` ?

Thanks in advance, cheers,

OdyX

Bug#709217: initscripts: checkfs.sh abend on BTRFS filesystem

JP Pozzi — 2013-05-21T17:00:57

Package: initscripts
Version: 2.88dsf-41
Severity: normal

Dear Maintainer,

I get a message at system startup as "fsck" is incorrect for btrfs file-systems
:

Log of fsck -C -R -A -a
Tue May 21 18:32:07 2013

fsck from util-linux 2.20.1
Unknown option: -a
usage: btrfs [--help] [--version] <group> [<group>...] <command> [<args>]
BOOTB: clean, 720/65536 files, 168362/262135 blocks (check in 4 mounts)
STOCKAGE: clean, 218/1048576 files, 2179291/4194304 blocks
VARLOG: clean, 6205/65536 files, 35419/262144 blocks
AMANDA_HOLD: clean, 12/1048576 files, 109842/4194304 blocks
Unknown option: -a
usage: btrfs [--help] [--version] <group> [<group>...] <command> [<args>]
fsck died with exit status 129

Tue May 21 18:32:08 2013
----------------


I upgrade to unstable yesterday, no problems before.

Regards

JP Pozzi

PS :
reportbug says that a newer version for "initscripts" is available, but I do
not see it in synaptic.

Bug#709168: src:fftw3: FTBFS on ia64: r2cf_8.c:83:1: internal compiler error

Sébastien Villemot — 2013-05-21T17:20:58

Le mardi 21 mai 2013 à 19:17 +0200, Sébastien Villemot a écrit :


I realize this is not possible without removing dozens of package from
testing in ia64, which I guess the Release Team won’t be willing to do.

Another possible solution to try is to force compilation with GCC 4.7 on
ia64 (since currently GCC 4.6 is the default on that arch). If you have
a patch, I can try it on a ia64 porterbox.

Bug#693930: game-data-packager: Please support lgeneral (PING)

Jonathan Dowland — 2013-05-21T17:25:52

Sorry yes, my memory is not great, and I was tracking a few different gdp
things at once, iirc.

I've put a test package at
<http://homepages.cs.ncl.ac.uk/jon.dowland/game-data-packager_33_all.deb>, if
you're happy with the lgeneral bit of it I'll adjust the changelog and upload.


Thanks

Bug#703902: [Piuparts-devel] Bug#703902: adequate testing

Holger Levsen — 2013-05-21T17:21:57

cool!

:-)

Bug#709216: qemu-system-x86 wants libvirt0 >= 1.0 only available in experimental

Vincent Legout — 2013-05-21T17:15:06

Package: qemu-system-x86
Version: 1.5.0+dfsg-1
Severity: serious

Hello,

apt-get dist-upgrade failed because qemu-system-x86 declares a Breaks on
libvirt0 (<< 1.0) but libvirt 1.0 is only available in experimental.

Thanks,
Vincent