Bug#755423: Any news?

[Paolo Cavallini]

I see that there is work going on:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239578

https://github.com/lwfinger/rtlwifi_new

Any hope to have it included in the package?

Thanks.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
*New course* "QGIS for naturalists":
http://www.faunalia.eu/en/nat_course.html


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777197: glibc: CVE-2015-1472

[Moritz Muehlenhoff]

Package: glibc
Severity: grave
Tags: security
Justification: user security hole

Hi,
please see https://sourceware.org/bugzilla/show_bug.cgi?id=16618
The patch is here: 
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5bd80bfe9ca0d955bfbbc002781bc7b01b6bcb06

This was introduced by 
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=3f8cc204fdd0
(2.15). Since the patch was backported into wheezy, it is also
affected (while squeeze is not).

Cheers,
Moritz


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777138: 777138 vs 776065

[Mathieu Malaterre]

On Thu, Feb 5, 2015 at 9:09 PM, Debian Bug Tracking System
 wrote:
> Processing commands for cont...@bugs.debian.org:
>
>> severity 777138 normal
> Bug #777138 [src:libvirt] 'internal error: Cannot find suitable CPU model for 
> given data'
> Severity set to 'normal' from 'grave'

It breaks my heart :( I fail to see how virt-manager can possibly be
used on jessie. Anyway you may want to clarify commit 4c14b8:

http://anonscm.debian.org/cgit/pkg-libvirt/libvirt.git/commit/?id=4c14b837b35a176fe72fde897197b4e94a92e544

It reads as:

Bug-Debian: https://bugs.debian.org/776065

while it should be (IMHO):

Bug-Debian: https://bugs.debian.org/777138

regards


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#771587: caja: Please provide an option to start caja desktop

[Manuel Gräber]

Package: caja
Version: 1.8.2-1
Followup-For: Bug #771587

Dear Maintainer,

I am using caja desktop as the default desktop background on xfce4 (instead of
xfdesktop). Since the patch I am no longer able to start the desktop background
outside of MATE. Would it be possible to add an option to just start mate
desktop regardless of of the running desktop envoronment?

Manuel



-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (600, 'unstable'), (590, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.18-2.towo-siduction-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages caja depends on:
ii  caja-common   1.8.2-1
ii  desktop-file-utils0.22-1
ii  gvfs  1.22.2-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-14
ii  libcairo2 1.14.0-2.1
ii  libcaja-extension11.8.2-1
ii  libexempi32.2.1-2
ii  libexif12 0.6.21-2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-2
ii  libgail18 2.24.25-1
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libglib2.0-0  2.42.1-1
ii  libglib2.0-data   2.42.1-1
ii  libgtk2.0-0   2.24.25-1
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.8.1+dfsg1-2
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libselinux1   2.3-2
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libunique-1.0-0   1.1.6-5
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.2+dfsg1-3
ii  libxrender1   1:0.9.8-1+b1
ii  mate-desktop  1.8.1+dfsg1-2
ii  shared-mime-info  1.3-1

caja recommends no packages.

Versions of packages caja suggests:
ii  engrampa 1.8.1+dfsg1-1
ii  gstreamer0.10-tools  0.10.36-1.5
ii  meld 3.12.1-2

-- 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#765577: (no subject)

[Christof Böckler]

Being redirected from my bugreport #777126 I can confirm that this 
happens with automatic installations.
Although it does not happen all the time. With a Lenovo Thinkpad X61 for 
example, I got this /etc/udev/rules.d/70-persistent-net.rules:


# PCI device 0x8086:0x1049 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:16:d3:ca:56:05", ATTR{dev_id}=="0x0", 
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"


# PCI device 0x8086:0x4230 (iwl4965)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:13:e8:ab:5d:43", ATTR{dev_id}=="0x0", 
ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"


Maybe it is has to do with the presence of a second networking device?

Greetings
Christof


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777140: Using mdadm to install Debian on Intel RST RAID array stopped working between Wheezy 7.8 and Jessie RC1

[Michael Tokarev]

Control: retitle -1 Using mdadm to install Debian on Intel IMSM RAID array 
stopped working between Wheezy 7.8 and Jessie RC1
Control: reassign -1 mdadm
Control: tag -1 + help

05.02.2015 17:43, Benjamin Black wrote:
> Package: debian-installer
> Version: used in Debian GNU/Linux Jessie-DI-rc1 "Jessie" - Official RC amd64 
> CD Binary-1 20150109-01:06 image
> 
> My UEFI motherboard has an Intel RST chip on it, which I use to set up a pair 
> of SSD drives in a RAID-0 array.  I have successfully installed Debian Wheezy 
> on this array in the past, using an expert set up and some manual 
> configuration during the install.  I tried repeating that process using the 
> Jessie RC1 installer, and it failed.
> 
> For Wheezy, I used the image Debian GNU/Linux 7.8.0 "Wheezy" - Official amd64 
> CD Binary-1 20150110-14:43
> 
> For Jessie, I used the image Debian GNU/Linux Jessie-DI-rc1 "Jessie" - 
> Official RC amd64 CD Binary-1 20150109-01:06
> 
> Both images were written to a USB stick, and both installers were booted in 
> UEFI mode.
> 
> To do the installation, I run through the first few steps of the expert 
> install, up to and including detecting disks.  At that point, I switch to the 
> console (Alt-F2), to assemble and start the software arrays.  First I load 
> the kernel modules for RAID, which also loads the md_mod module, and then I 
> execute mdadm to assemble and start the arrays.
> 
> When I do this in Wheezy, it successfully builds the arrays and starts them:
> 
> ~ # modprobe raid0
> ~ # mdadm --assemble --scan --verbose
> mdadm: looking for devices for further assembly
> mdadm: /dev/sdb is identified as a member of /dev/md/imsm0, slot -1.
> mdadm: /dev/sda is identified as a member of /dev/md/imsm0, slot -1.
> mdadm: added /dev/sda to /dev/md/imsm0 as -1
> mdadm: added /dev/sdb to /dev/md/imsm0 as -1
> mdadm: Container /dev/md/imsm0 has been assembled with 2 drives
> mdadm: looking in container /dev/md127
> mdadm: found match on member /md127/0 in /dev/md127
> mdadm: Started /dev/md/Boot_0 with 2 devices
> 
> However, following the same steps in Jessie, mdadm fails to start the array 
> because of some file permission problem:
> 
> ~ # modprobe raid0
> ~ # mdadm --assemble --scan --verbose
> mdadm: looking for devices for further assembly
> mdadm: /dev/sdb is identified as a member of /dev/md/imsm0, slot -1.
> mdadm: /dev/sda is identified as a member of /dev/md/imsm0, slot -1.
> mdadm: added /dev/sda to /dev/md/imsm0 as -1
> mdadm: added /dev/sdb to /dev/md/imsm0 as -1
> mdadm: Container /dev/md/imsm0 has been assembled with 2 drives
> mdadm: cannot open device /dev/md/imsm0: No such file or directory

I don't see any permission problems in here, but indeed, mdadm is
unable to complete the process.

Since this has nothing to do with the installer really, -- you're
trying to assemble the array manually using mdadm and it fails,
I'm reassigning this bugreport to mdadm package.

However, since I don't have hardware where I can test this, I'm
tagging this as "help", -- because I can't debug it myself.  Maybe
someone with the hardware will be able to understand what's going
on.

BTW, does /dev/md/ directory exists?

Thanks,

/mjt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#388141: Relicensing of debian-www pages

[Riley Baird]

Hi -www!

>From #388141, it seems that Debian is in the process of relicensing the
www pages. So far, after contacting all of the contributors, most of
them have agreed to relicense but there are still some that have not
responded and it is unlikely that they will. Because of this, Stefano
Zacchiroli and Bradley M. Kuhn have devised a relicensing plan.[1]

It seems that the next step in this plan is to make "a list of website
"lines" that are: 1/ still active, and 2/ for which we do *not* have
received permission to relicence."

Does this list already exist? If not, would anyone be interested in
making it?

Yours sincerely,

Riley Baird


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=388141#356


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777196: activemq: CVE-2014-8110 CVE-2014-3612 CVE-2014-3600

[Moritz Muehlenhoff]

Package: activemq
Severity: important
Tags: security

Hi,
please see
http://activemq.apache.org/security-advisories.data/CVE-2014-8110-announcement.txt
(but the admin console isn't enabled, so this should be moot? (702670))

http://activemq.apache.org/security-advisories.data/CVE-2014-3612-announcement.txt
http://activemq.apache.org/security-advisories.data/CVE-2014-3600-announcement.txt

Cheers,
Moritz


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#765479: squid3: Seem to ignore size restriction set by cache_dir (overflow partition)

[Roman Mamedov]

Hello,

I can confirm this behavior. It occurs simply during normal usage.

I am using:

  cache_dir aufs /var/spool/squid3 1 16 32

However the cache dir on one host was way over that, close to 30 GB. Luckily
that partition still had a considerable amount of free space.



-- 
With respect,
Roman


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776719: icu: CVE-2015-1205 regex out of bounds issues

[Moritz Muehlenhoff]

retitle 776719 icu: CVE-2015-1205 / CVE-2014-9654
thanks 

On Sat, Jan 31, 2015 at 11:58:35AM -0500, Michael Gilbert wrote:
> package: src:icu
> severity: serious
> tags: security, patch
> 
> There is another icu issue fixed in chromium:
> https://marc.info/?l=oss-security&m=142244042307425&w=2
> 
> Links to upstream patches in that mail.
> 
> This was rated as high severity by chromium.

And this issue was assigned CVE-2014-9654:
https://ssl.icu-project.org/trac/changeset/36801
https://chromium.googlesource.com/chromium/deps/icu/+/dd727641e190d60e4593bcb3a35c7f51eb4925c5

Cheers,
Moritz


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777195: [squid3] tcp_outgoing_address ignored

[Roman Mamedov]

Package: squid3
Version: 3.4.8-5~bpo70+1
Severity: normal

Hello,

On some occasions I was using the directive "tcp_outgoing_address 0.0.0.0" to
force Squid on a dual-stack host to be IPv4-only.

This works fine on 3.1.20-2.2+deb7u2 currently in Wheezy.

However, this directive is ignored on the 3.4 version from backports.

Even setting "tcp_outgoing_address [actual IPv4 address of the host]" does not
help, Squid still makes outgoing connections from IPv6 as well.

-- 
With respect,
Roman


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777194: makes stable apt annoying without even installing php5-facedetect (versioned provides)

[Helmut Grohne]

Package: php5-facedetect
Version: 1.1.0+git20140717-1
Severity: important

php5-facedetect declares a versioned provides. While this seems covered
by jessie's dpkg and apt. A stable apt chokes:

| W: Ignoring Provides line with DepCompareOp for package php5-php-facedetect
| W: You may want to run apt-get update to correct these problems

Please defer using this feature until after the jessie release, such
that QA tooling has a chance to upgrade.

For further discussion see a similar bug #774815.

Helmut


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#734649: really close it

[Russell Coker]

close 734649
thanks


-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#771484: fixed in 2.20140421-8

[Russell Coker]

close 771484
thanks


Version 2.20140421-8 fixed this.

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777165: linux-image-3.16.0-4-amd64: WARNING and guest crash when using nested virtualisation

[Jérôme Deuchnord]

I have the same problem, and wrote a bug, but nobody answered me: 
https://lists.debian.org/20150131113439.1239.79224.reportbug@JeromeTanghe-Debian
The screen on the photo doesn't say the same thing, but sometimes my PC writes 
these messages too...Le 5 févr. 2015 21:20, Rik Theys  a 
écrit :
>
> Package: src:linux 
> Version: 3.16.7-ckt4-3 
> Severity: normal 
>
> Hi, 
>
> I enabled nested virtualisation on the kvm_intel module and 
> created a virtual machine (using virt-manager). The VM had the host cpu flags 
> copied so it also had the vmx cpu flag. 
>
> Inside this VM I configured another virtual machine (also using 
> virt-manager). 
> As soon as the new VM (inside the first VM) is launched, the following 
> WARNING is 
> reported on the host kernel and the first VM reboots. 
>
> [  187.013217] [ cut here ] 
> [  187.013242] WARNING: CPU: 1 PID: 2394 at 
> /build/linux-y7bjb0/linux-3.16.7-ckt4/arch/x86/kvm/vmx.c:8699 
> nested_vmx_vmexit+0x7f3/0x820 [kvm_intel]() 
> [  187.013245] Modules linked in: vhost_net vhost macvtap macvlan tun 
> xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat 
> ipt_REJECT bridge stp llc bnep bluetooth 6lowpan_iphc binfmt_misc 
> cpufreq_userspace cpufreq_powersave cpufreq_conservative cpufreq_stats 
> nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp 
> nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter 
> ip_tables x_tables snd_hda_codec_hdmi cx88_blackbird cx2341x cx22702 iTCO_wdt 
> iTCO_vendor_support cx88_dvb cx88_vp3054_i2c videobuf_dvb arc4 dvb_core 
> wm8775 tuner_simple tuner_types tda9887 tda8290 coretemp tuner 
> snd_hda_codec_via snd_hda_codec_generic rt61pci rt2x00pci rt2x00mmio 
> rt2x00lib snd_hda_intel joydev evdev cx8802 snd_hda_controller snd_hda_codec 
> eeprom_93cx6 snd_hwdep mac80211 
> [  187.013297]  cx8800 cx88_alsa snd_pcm cfg80211 cx88xx kvm_intel kvm 
> snd_timer psmouse serio_raw nouveau btcx_risc tveeprom mxm_wmi wmi video 
> videobuf_dma_sg videobuf_core rc_core rfkill i7core_edac ttm drm_kms_helper 
> v4l2_common drm videodev snd edac_core i2c_i801 soundcore media i2c_algo_bit 
> i2c_core shpchp lpc_ich mfd_core asus_atk0110 button acpi_cpufreq processor 
> thermal_sys loop firewire_sbp2 fuse parport_pc ppdev lp parport autofs4 ext4 
> crc16 mbcache jbd2 btrfs xor raid6_pq dm_mod raid1 raid0 md_mod sg sd_mod 
> crc_t10dif crct10dif_generic sr_mod cdrom crct10dif_common hid_generic usbhid 
> hid usb_storage crc32c_intel ahci libahci libata firewire_ohci xhci_hcd 
> scsi_mod ehci_pci r8169 ehci_hcd firewire_core crc_itu_t mii usbcore 
> usb_common 
> [  187.013374] CPU: 1 PID: 2394 Comm: qemu-system-x86 Not tainted 
> 3.16.0-4-amd64 #1 Debian 3.16.7-ckt4-3 
> [  187.013376] Hardware name: System manufacturer System Product 
> Name/P7P55D-E, BIOS 1504    12/14/2010 
> [  187.013379]  0009 815096a7  
> 810676f7 
> [  187.013383]  8800a498f000 0014  
>  
> [  187.013387]   a083dec3  
> a0734daf 
> [  187.013391] Call Trace: 
> [  187.013399]  [] ? dump_stack+0x41/0x51 
> [  187.013406]  [] ? warn_slowpath_common+0x77/0x90 
> [  187.013416]  [] ? nested_vmx_vmexit+0x7f3/0x820 
> [kvm_intel] 
> [  187.013435]  [] ? kvm_mmu_load+0x26f/0x400 [kvm] 
> [  187.013452]  [] ? kvm_arch_vcpu_ioctl_run+0xde5/0x1110 
> [kvm] 
> [  187.013458]  [] ? futex_wake+0x6f/0x120 
> [  187.013471]  [] ? kvm_vcpu_ioctl+0x2f1/0x590 [kvm] 
> [  187.013477]  [] ? eventfd_ctx_read+0x58/0x1e0 
> [  187.013482]  [] ? wake_up_state+0x10/0x10 
> [  187.013487]  [] ? do_vfs_ioctl+0x2cf/0x4b0 
> [  187.013491]  [] ? eventfd_read+0x37/0x60 
> [  187.013506]  [] ? kvm_on_user_return+0x4c/0x80 [kvm] 
> [  187.013510]  [] ? SyS_ioctl+0x81/0xa0 
> [  187.013515]  [] ? int_signal+0x12/0x17 
> [  187.013520]  [] ? system_call_fast_compare_end+0x10/0x15 
> [  187.013523] ---[ end trace ae3922755979b8ad ]--- 
>
> When I retry to create the VM inside the first VM, the first VM keeps on 
> crashing but the WARNING is not repeated 
> on the host kernel. But I assume this is by design. 
>
> Regards, 
>
> Rik 
>
> -- Package-specific info: 
> ** Version: 
> Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
> 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) 
>
> ** Command line: 
> BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/vg_saturn-root ro 
> init=/bin/systemd audit=1 quiet systemd.show_status=1 
>
> ** Tainted: W (512) 
> * Taint on warning. 
>
> ** Kernel log: 
> [   12.610352] [TTM] Initializing DMA pool allocator 
> [   12.610362] nouveau  [ DRM] VRAM: 512 MiB 
> [   12.610366] nouveau  [ DRM] GART: 1048576 MiB 
> [   12.610369] nouveau  [ DRM] TMDS table version 2.0 
> [   12.610371] nouveau  [ DRM] DCB version 4.0 
> [   12.610372] nouveau  [ DRM] DCB outp 00: 02000300  
> [   12.6

Bug#777166: Please consider not hard coding the name "Debian" into error messages

[Christian PERRIER]

Quoting Phillip Susi (ps...@ubuntu.com):
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Package: partman-efi
> Version: 59
> 
> Recently a new message was added to d-i:
> 
>  This machine's firmware has started the installer in UEFI mode but
>  it looks like there may be existing operating systems already
>  installed using "BIOS compatibility mode". If you
>  continue to install Debian in UEFI mode, it might be difficult to
>  reboot the machine into any BIOS-mode operating systems later.
> 
> Please consider replacing "Debian" with `lsb_release -si` or similar
> so that people installing other distros based on debian don't get a
> message about a different operating system than the one they are
> installing.

Doh. That one escaped my attention when this message was added.

We usually avoid hardcoding "Debian" and this is probably one of the
very rare cases where we failed. The message was added in a bit of a
hurry recently and that failed to be catched by the review:-(

Sadly, I'd prefer us not to change  this now.as it will require
Yet Another Round of translation updateswhich takes weeks to
achieve.

I'd prefer something like "If you continue to install in UEFI
mode, it might be difficult to reboot the machine into any BIOS-mode
operating systems later" and avoid "the distro" or anything like
that. The output of "lsb_release -si" is likely to not work.

But even just dropping "Debian" does not guarantee we can easily fix
translations as it is likely that, for some languages, dropping the
distro name wouldn't be enough.



signature.asc
Description: Digital signature

Bug#623271: Adoption of Slides (Python-based Slide Maker)

[Riley Baird]

Hi Matthias,

A couple of years ago, you orphaned the "slides" package. I'd like to
adopt it, but since I'm not a DD, I can't upload the package. Would you
be interested in sponsoring my uploads?

You can get the new version of the package with this command:
dget -x
http://mentors.debian.net/debian/pool/main/s/slides/slides_1.0.1-14.dsc

For your reference, the changelog entry is:
  * New maintainer (closes: #623271).
  * Upgraded to Debhelper 9/pybuild
  * Bumped standards version to 3.9.6
  * Added Vcs and Homepage fields to d/control
  * Changed dependencies
  * Added DEP-5 copyright
  * Extended the description of slides-doc
  * Updated source format to "3.0 (quilt)"



signature.asc
Description: OpenPGP digital signature

Bug#777193: unbound: Fails to start daemon when using scriptable interface

[Narumi Hirai]

Package: unbound
Version: 1.4.17-3+deb7u2

Hello,

I am going to use unbound scriptable interface.
I am also using python-unbound-1.4.17-3+deb7u2 for scriptable interface.
But, unbound daemon fails to start.
Here is a transcript:

# service unbound start
Starting recursive DNS server: unbound[1423199360]
unbound-checkconf[9751:0] fatal error: module conf 'validator python
iterator' is not known to work
.
#

I investigated the problem, and was found a problem area in
unbound-checkconf.c:
if(strcmp(cfg->module_conf, "iterator") != 0
&& strcmp(cfg->module_conf, "validator iterator") != 0
#ifdef WITH_PYTHONMODULE
&& strcmp(cfg->module_conf, "python iterator") != 0
&& strcmp(cfg->module_conf, "python validator iterator") !=
0
&& strcmp(cfg->module_conf, "validator python iterator") !=
0
#endif
) {
fatal_exit("module conf '%s' is not known to work",
cfg->module_conf);
}

I think WITH_PYTHONMODULE is not defined.

Kind regards,

-- 
Narumi Hirai
E-mail: n.hira...@gmail.com
GPG key: 0x9F897A53 at pgp.nic.ad.jp

Bug#777192: mirrors: Argonne public software mirror service has removed public access via HTTP, FTP, and rsync

[Donald Norwood]

Package: mirrors
Severity: important

The Argonne Mirror Service has removed public access. This effects users who 
attempt downloads from mirror.anl.gov

Announcement:

To users of the Argonne public software mirror service,

Public access to the Argonne software mirror via HTTP, FTP, and rsync has been 
removed.

The following websites are no longer be accessible from the Internet:
* http://mirror.anl.gov 
* http://mirror.mcs.anl.gov 
* http://mirror.ipv6.anl.gov

This was a difficult decision as the Argonne public software mirror has been 
one of the more popular mirrors in North America for open source software, 
receiving millions of unique visits a year. However, it has expanded beyond the 
core scope and mission of the Laboratory, which is to perform world-class 
scientific research.

If you require access to mirrored software repositories, you will need to 
reconfigure your system to use a different public software mirror. Please go to 
the software's website to find a list of alternative mirrors.

We cannot thank you enough for making the Argonne public software mirror such a 
success.

Argonne National Laboratory




-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776939: mime-support: please make the build reproducible

[Charles Plessy]

Control: tag -1 pending

Le Tue, Feb 03, 2015 at 12:37:21PM +, Chris Lamb a écrit :
> 
> While working on the "reproducible builds" effort [1], we have noticed
> that mime-support could not be built reproducibly.

Hi Chris,

this is actually fixed already in the package's VCS thanks to the new Lintian
warning, but not uploaded yet because of the Freeze.

Thanks anyway for your work on this issue.  It is both important and exciting
development.

Have a nice day,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776676: Acknowledgement (grub-efi-amd64: grub-probe, update-grub cannot detect zfs filesystem running with the latest code)

[Azeem Esmail]

Control: retitle -1 grub-efi-amd64: grub-probe, update-grub on Debian Jessie 
cannot detect zfs filesystem running with the latest code
Control: severity -1 critical


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777156: ksystemlog: "ksystemlog viewer" crashes all the time.

[Ezequiel]

Package: ksystemlog
Version: 4:4.14.0-1
Followup-For: Bug #777156

Update to bug number: 777156

This is the backtrace info, hope it helps squash this bug:

Application: KSystemlog (ksystemlog), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f37810cfe38 in QStandardItem::child(int, int) const () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x7f37810d0042 in QStandardItemModel::data(QModelIndex const&, int)
const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#8  0x7f3780efc421 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9  0x7f3780effebf in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x7f37817d6f4c in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x7f3781823394 in QAbstractItemModel::rowsInserted(QModelIndex const&,
int, int) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x7f37817bb372 in QAbstractItemModel::endInsertRows() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x7f37810d274f in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x7f3780f01499 in QComboBox::insertItem(int, QIcon const&, QString
const&, QVariant const&) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#15 0x0042fcb0 in _start ()



-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ksystemlog depends on:
ii  kde-runtime  4:4.14.2-2
ii  libc62.19-13
ii  libkdecore5  4:4.14.2-5
ii  libkdeui54:4.14.2-5
ii  libkio5  4:4.14.2-5
ii  libqtcore4   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libstdc++6   4.9.1-19

ksystemlog recommends no packages.

ksystemlog 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#777191: grub-efi-amd64 on Debian Jessie cannot boot zfs native root filesystem running the latest git code soon to be 0.6.4 tagged - official release

[Azeem Esmail]

Package: grub-efi-amd64
Version: 2.02~beta2-20
Severity: critical
Tags: patch, upstream, d-i, jessie
Control: control commands

grub-efi-amd64 on Debian Jessie,

Works with 0.6.3 (v0.6.3-766_gfde0d6d)
Does not work with 0.6.3 latest code (dailies version). 

Tested on VitualBox (v4.3.20 r96997) with,

UEFI partition on sda1
ZFS on sd[a-d]2
/boot either on (ext4 RAID 1, sd[a-b]3) OR (ext4 RAID 10, sd[a-d]3) OR (zfs)


Pool was create with,
zpool create spool mirror /dev/disk/by-id /dev/disk/by-id mirror
/dev/disk/by-id /dev/disk/by-id

After system setup, initrd.img-3.16.0-4-amd64 was regenerated:
update-initramfs -c -k all

'update-grub' was run to rebuild grub.cfg and the following line was
added/corrected if missing/incorrect:
root=ZFS=spool/ROOT/debian

Also tired manually entering different combination of the following through
the grub boot menu while trouble shooting:
boot=zfs rpool=spool bootfs=spool/ROOT/debian

For example:
linux /vmlinuz-3.16.0-4-amd64 root=zfs=spool/ROOT/debian ro quiet boot=zfs
rpool=spool bootfs=spool/ROOT/debian



***

At first reboot, the screen freezes with the following message:

mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
/init: line 335: can't open /root/dev/console: no such file
...
[end Kernel panic - not syncing: attempting to kill init!
exitcode=0x0200

After a cold boot the following message appears:

sh: argument expected <- repeated 4 times

Command: mount -o zfsutil -t zfs - /root
Message: filesystem '-' cannot be mounted, unable to open the dataset
mount: mounting - on /root failed: No such file or directory
Error: 1

Manually mount the root filesystem on /root and then exit.

BusyBox v1.22.1 (Debian ...

/bin/sh: can't access tty; job control turned off
/#



***

NOTE: When I don't add "boot=zfs rpool=spool bootfs=spool/ROOT/debian" in
the grub menu boot command line, the boot message is slightly different:

modprobe: module unknow not found in modules.dep
mount: mounting ZFS=spool/ROOT/debian on /root failed: no such file or
directory
mount: mounting /dev on /root/dev failed: No such file or directory
Target filesystem does't have requested /sbin/init.
no init found. Try passing init- bootarg.
modprobe: module ehci-orion not found in modules.dep

BusyBox v1.22.1 (Debian...

/bin/sh: can't access tty; job control tuned off
(initramfs)



***

This may be related to:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776676
https://github.com/zfsonlinux/grub/issues/19
https://github.com/zfsonlinux/grub/issues/18
https://github.com/zfsonlinux/zfs/issues/3047



***

A likely fix is to use patches that work with the MBR patched version of
grub (2.02~beta2-9) tested to works with the latest ZoL code (dailies
version).

https://github.com/zfsonlinux/grub/tree/snapshot/debian/wheezy/2.02_beta2+gi
tbac5d-9.ZOL1


LIST OF PATCHES USED IN THE FIX:

https://github.com/zfsonlinux/grub/tree/snapshot/debian/wheezy/2.02_beta2%2B
gitbac5d-9.ZOL1/debian/patches


10_linux_zfs.patch
blacklist_1440x900x32.patch
core_in_fs.patch
default_grub_d.patch
disable_floppies.patch
dpkg_version_comparison.patch
elf_bi_endian.patch
feature_flags.patch
first_device.patch
fix_variable_redeclarations.patch
gettext_quiet.patch
gfxpayload_dynamic.patch
gfxpayload_keep_default.patch
grub-shell-no-pad.patch
grub-tester-zfs.patch
grub.cfg_400.patch
grub_legacy_0_based_partitions.patch
ignore_grub_func_test_failures.patch
install_efi_fallback.patch
install_locale_langpack.patch
install_powerpc_machtypes.patch
install_stage2_confusion.patch
linuxefi.patch
linuxefi_amd64_only.patch
linuxefi_debug.patch
linuxefi_non_sb_fallback.patch
linuxefi_require_shim.patch
maybe_quiet.patch
mkconfig_loopback.patch
mkconfig_mid_upgrade.patch
mkconfig_nonexistent_loopback.patch
mkconfig_recovery_title.patch
mkconfig_signed_kernel.patch
mkconfig_ubuntu_distributor.patch
mkconfig_ubuntu_recovery.patch
multiple-raidz-device-detection.txt
no_insmod_on_sb.patch
no_redefine_MIN-MAX.patch
probe_fusionio.patch
quick_boot.patch
restore_mkdevicemap.patch
series  * Add support for spacemap_histogram, enabled_txg,
extensible_dataset.
skip_gettext_strings_test.patch
sleep_shift.patch
uefi_firmware_setup.patch
vt_handoff.patch
wubi_no_windows.patch


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777189: link to discussion

[Stephen Crowley]

http://askubuntu.com/questions/42915/how-to-get-rid-of-pidgin-purples-statuses-evil-and-depression


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777190: libmhash2: The mhash_end_m function fails call a custom allocator (upstream bug)

[bri]

Package: libmhash2
Version: 0.9.9.9-7
Severity: normal

Dear Maintainer,

The mhash_end_m API function does not operate as documented/intended.

On line 408 of lib/mhash.c, instead of calling the proferred callback
function, the internal allocator is called.  Compare to line 520-522
of the same file, where the corresponding function mhash_hmac_end_m
uses the proferred callback function.

Expected behavior: mhash_end_m calls back to the program to allocate
memory.
Actual behavior: mhash_end_m allocates memory internally and the
callback is never invoked.

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-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
Init: sysvinit (via /sbin/init)

Versions of packages libmhash2 depends on:
ii  libc6  2.19-14
ii  multiarch-support  2.19-14

libmhash2 recommends no packages.

libmhash2 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#777189: pidgin statuses "evil" and "depression" , wtf?

[Me]

Package: pidgin
Version: 2.10.11-1
Severity: minor

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

It seems it would be in better taste and a bit less moribund, to have
a patch exist to remove these, I read that they are hardcoded in the
upstream source

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


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pidgin depends on:
ii  gconf2  3.2.6-3
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-13
ii  libcairo2   1.14.0-2.1
ii  libdbus-1-3 1.8.12-3
ii  libdbus-glib-1-20.102-1
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.5.2-2
ii  libgadu31:1.12.0-5
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.1-1
ii  libgstreamer0.10-0  0.10.36-1.5
ii  libgtk2.0-0 2.24.25-1
ii  libgtkspell02.0.16-1.1
ii  libice6 2:1.0.9-1+b1
ii  libpango-1.0-0  1.36.8-3
ii  libpangocairo-1.0-0 1.36.8-3
ii  libpangoft2-1.0-0   1.36.8-3
ii  libpurple0  2.10.11-1
ii  libsm6  2:1.2.2-1+b1
ii  libx11-62:1.6.2-3
ii  libxml2 2.9.1+dfsg1-4
ii  libxss1 1:1.2.2-1
ii  perl-base [perlapi-5.20.1]  5.20.1-5
ii  pidgin-data 2.10.11-1

Versions of packages pidgin recommends:
ii  gstreamer0.10-alsa  0.10.36-2
pn  gstreamer0.10-ffmpeg
ii  gstreamer0.10-plugins-base  0.10.36-2
ii  gstreamer0.10-plugins-good  0.10.31-3+nmu4+b1

Versions of packages pidgin suggests:
ii  libsqlite3-0  3.8.7.1-1

-- 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#756627: postfix-pgsql still broken with 9.4

[Antony]

Package: postfix-pgsql 9.4 not playing so well with postfix
Version: 2.11.0
Severity: important

Dear Maintainer,

Same bug...just spent 2 days trying to get Postfix to work on a new 
install where I used pgsql 9.4. I had previously installed three 4 or 5 
successful boxes running postfix/dovecot with pgsql 9.3 so I was 
surprised I had so much trouble.


I even have a bash script that worked fine on the other machines, so I 
was completely baffled.


All the usual suspects of non-working db, wrong password, incorrect 
config files didn't help me.


Stack-exchange and server-fault don't have this particular bug discussed 
and I was at wits end until I read it! Thanks Michael Berg.


I didn't do proxy, but purged 9.4 and put on 9.3 and...works like a 
charm like the others.


Hope this helps someone as much as your thread did me.

Kind regards,
-a


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777157: [gimp] arbitrary rotation grid should should stay fixed

[Ari Pollak]

Wouldn't using the existing grids or guides accomplish the same thing?

Bug#777188: nmh: amd64 unsatisfiable Depends: libdb5.1

[HIGUCHI Daisuke (VDR dai)]

Package: nmh
Version: 1.6-3
Severity: important

Dear Maintainer,

nmh amd64 package depends libdb5.1 does not exist in sid.
please rebuild with proper libdb.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to ja_JP.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nmh depends on:
ii  libc6 2.19-14
ii  libdb5.1  5.1.29-5
ii  liblockfile1  1.09-6
ii  libsasl2-22.1.26.dfsg1-12
ii  libssl1.0.0   1.0.1k-1
ii  libtinfo5 5.9+20140913-1+b1
ii  netbase   5.3

Versions of packages nmh recommends:
ii  postfix [mail-transport-agent]  2.11.3-1

Versions of packages nmh suggests:
pn  exmh
ii  libmailtools-perl   2.13-1
ii  libmime-tools-perl  5.505-1
pn  mh-book 
pn  mh-e
pn  par 

-- no debconf information


signature.asc
Description: Digital signature

Bug#777187: golang-go.tools: godoc fails with golang 1.4

[Hilko Bengen]

Package: golang-go.tools
Version: 0.0~hg20140703-4
Severity: important

After installing golang 2:1.4.1-1~exp1 from experimental, godoc no
longer works. This is because the location where the source files are
kept has been changed from $GOROOT/src/pkg/ to $GOROOT/src/, as
documented in .

Cheers,
-Hilko

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages golang-go.tools depends on:
ii  libc6 2.19-14
ii  libjs-jquery  1.7.2+dfsg-3.2

golang-go.tools recommends no packages.

golang-go.tools 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#777186: libsdl2: please make the build reproducible

[Chris Lamb]

Source: libsdl2
Version: 2.0.2+dfsg1-6
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: username
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that libsdl2 could not be built reproducibly.

The attached patch removes usernames from the build system. Once
applied, libsdl2 can be built reproducibly in our current experimental
framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/rules b/debian/rules
index af65dd2..31472fa 100755
--- a/debian/rules
+++ b/debian/rules
@@ -69,7 +69,7 @@ override_dh_auto_configure:
 
 override_dh_auto_build:
dh_auto_build
-   tar czf debian/examples.tar.gz test
+   tar czf debian/examples.tar.gz test --owner=0 --group=0
 
 override_dh_auto_clean:
dh_auto_clean

Bug#777064: ITA: surf -- Simple web browser by suckless community

[Cameron Norman]

Hello,

On Wed, 4 Feb 2015 21:43:20 +0530 Vasudev Kamath 
 wrote:

> Package: wnpp
> Severity: normal
>
> As I don't have enough time to take care of this package, I request 
an

> adopter for the surf package.
>
> The package description is:
>  surf is a simple web browser based on WebKit/GTK+. It is able to 
display
>  websites and follow links. It supports the XEmbed protocol which 
makes it
>  possible to embed it in another application. Furthermore, one can 
point surf to

>  another URI by setting its XProperties.

I would be happy to adopt the surf package. It seems to be a fairly 
simple little C program.


Best regards,
--
Cameron Norman

Bug#777185: cli-common-dev: please make the debhelper script additions reproducible

[Chris Lamb]

Source: cli-common-dev
Version: 0.9
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain randomness
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that dh_cligacpolicy is populating postinst and postrm scripts with
snippets in a random order.

A patch is attached that fixes this.

 [1]: https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/dh_cligacpolicy b/dh_cligacpolicy
index 47eda19..8932a9a 100755
--- a/dh_cligacpolicy
+++ b/dh_cligacpolicy
@@ -204,7 +204,7 @@ foreach my $package (@{$dh{DOPACKAGES}})
 # Once all the various  tags are consolidated, we
 # then generate the policy files. This will result in one policy file for
 # a given assembly, key file, and A.B version.
-foreach my $pk (keys %policies)
+foreach my $pk (sort keys %policies)
 {
# Get the pkg_dir
my ($snk, $assembly, $version_map, $priority) =

Bug#777183: debirf: please make the build reproducible

[Chris Lamb]

Source: debirf
Version: 0.34
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that debirf could not be built reproducibly.

The attached patch removes timestamps from the build system. Once
applied, debirf can be built reproducibly in our current experimental
framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad debirf.orig/debirf-0.34/Makefile debirf/debirf-0.34/Makefile
--- debirf.orig/debirf-0.34/Makefile2015-02-06 00:21:39.924918777 +
+++ debirf/debirf-0.34/Makefile 2015-02-06 00:37:36.881716535 +
@@ -7,6 +7,7 @@
 # Licensed under GPL v3 or later
 
 VERSION := `head -n1 debian/changelog | sed 's/.*(\([^-]*\).*/\1/'`
+BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date)
 
 PREFIX ?= /usr
 MANPREFIX ?= $(PREFIX)/share/man
@@ -23,6 +24,8 @@
for m in $(shell cat $<); do ln -s /usr/share/debirf/modules/$$m $@/; 
done
 
 doc/example-profiles/%.tgz: doc/example-profiles/% 
doc/example-profiles/%/modules
+   # Ensure deterministic mtimes
+   find $< -print0 | xargs -0r touch --no-dereference 
--date="$(BUILD_DATE)"
(cd doc/example-profiles && tar c --exclude='*~' $(notdir $<)) | gzip 
-9 -n > "$@"
 
 install: installman profiles

Bug#777182: kerberos-configs: please make the build reproducible

[Chris Lamb]

Source: kerberos-configs
Version: 2.3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that kerberos-configs could not be built reproducibly.

The attached patch removes randomness from the build system. Once
applied, kerberos-configs can be built reproducibly in our current
experimental
framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad kerberos-configs.orig/kerberos-configs-2.3/genblob 
kerberos-configs/kerberos-configs-2.3/genblob
--- kerberos-configs.orig/kerberos-configs-2.3/genblob  2015-02-06 
00:13:44.314829566 +
+++ kerberos-configs/kerberos-configs-2.3/genblob   2015-02-06 
00:16:14.332891883 +
@@ -5,6 +5,9 @@
 our (%domain_map, %realm_map);
 use Data::Dumper;
 
+# Ensure deterministic output
+$Data::Dumper::Sortkeys = 1;
+
 do "krb5confparse.pl";
 read_config("krb5.conf.template");
 print "no strict; \n BEGIN {\n";

Bug#773354: please add breaks: live-tools (<< 4.0.1-1)

[Gaudenz Steinlin]

Hi Andreas

Andreas Henriksson  writes:

> Hi!
>
> On Thu, Feb 05, 2015 at 01:46:22PM +0100, Gaudenz Steinlin wrote:
> [...]
>> I'll try to find a list of other packages affected by the live-tools bug
>> and submit bug reports.
>
> Fwiw, I noticed live-tools is targeted for auto-removal soon when
> reading through the recent release team announcement. Maybe fixing
> live-tools itself would be your first stop. I guess otherwise the
> workarounds aren't a good use of your time.

I already fixed this RC bug before doing the util-linux upload. So this
should be taken care of unless the release team does not approve the
unblock request.

And as packages are not automatically removed on upgrade the bug would
even show up when live-tools is removed from testing.

Gaudenz


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777181: nmu: nmh_1.6-3

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu nmh_1.6-3 . amd64 . -m "Rebuild against libdb5.3"

maintainer upload was built against libdb5.1

Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777180: ITP: leveldb-java -- Port of LevelDB to Java

[Emmanuel Bourg]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg 

* Package name: leveldb-java
  Version : 0.7
  Upstream Author : Dain Sundstrom 
* URL : http://github.com/dain/leveldb
* License : Apache-2.0
  Programming Lang: Java
  Description : Port of LevelDB to Java

Port of LevelDB in Java with the goal of having a feature complete
implementation that is within 10% of the performance of the C++ original
and produces byte-for-byte exact copies of the C++ code.

This library is required to package Hadoop.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#738453: Hyvää päivää,

[thomas wysiadly]

Hyvää päivää,
  Tämä viesti on peräisin asiakaspalveluun yritys. Tämä on
ilmoittaa teille, että annamme lainaa korolla 2% tässä kuussa sekä
vanhoja ja uusia asiakkaita ja meidän etumme tässä kuussa lainaa on
erittäin edullinen ja meidän laina prosessi on hyvin nopea. Sillä
kaikki kiinnostuneet yritykset, rahoituslaitokset ja
yksityishenkilöille, ota yhteyttä takaisin tänään alla olevaan
saamiseksi lainaa.

Lainan määrä:
Laina Kesto:
Puhelin:
Maa:

Ystävällisin terveisin
Pääjohtaja / toimitusjohtaja
Asiakaspalvelu


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#767546: pypy: Build cppyy backend

[Stefano Rivera]

Hi Debian (2014.10.31_17:20:52_-0700)
> We should build it. Possibly in a separate binary package.

This currently requires a fork of reflex -
http://cern.ch/wlav/reflex-2014-10-20.tar.bz2

So, I guess this isn't currently worth pursuing. When the cling
implementation is ready, we can look at that.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777169: FTBFS on sparc64: symbol errors

[Matthias Klose]

On 02/05/2015 10:05 PM, Helmut Grohne wrote:
> Source: gcc-4.9
> Version: 4.9.1-17
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> gcc-4.9 currently FTBFS on sparc64 due to symbol errors. While the last
> two builds on sompek failed due to -ENOSPC the build of 4.9.1-17 shows
> proper symbol diffs:
> 
> http://buildd.debian-ports.org/status/fetch.php?pkg=gcc-4.9&arch=sparc64&ver=4.9.1-17&stamp=1413678403
> 
> The very same issue is reproducible with 4.9.2-10 in a cross-build
> setting:
> 
> https://jenkins.debian.net/job/rebootstrap_sparc64_gcc49/105/console
> 
> You can find the relevant excerpt from the native build at the end of
> this mail.
> 
> Reporting during freeze without any expectation of having this fixed
> before the jessie release.

sparc64 is not a release architecture, and with the current level of support I
don't recommend making it a release architecture.  This is probably just the
first issue, so expect that more work is required.  Send a patch if you feel it
is worth it.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776545: game-data-packager: please add support for residualvm

[Alexandre Detiste]

Here is a patch for G-D-P to let it package Grim Fandango's demo.

https://github.com/a-detiste/game-data-packager/commit/0c9b107ba3afb0510b761c3c992fff7fb4166dbe


It also include a plugin that generate this .dekstop file:

cat /usr/share/applications/grimfandango-demo-data.desktop
[Desktop Entry]
Name=Grim Fandango (demo)
GenericName=Adventure Game
TryExec=residualvm
Exec=residualvm -p /usr/share/games/grimfandango grim
Icon=/usr/share/pixmaps/residualvm.xpm
Terminal=false
Type=Application
Categories=Game

from this template:

cat data/residualvm-common.desktop.in 
[Desktop Entry]
Name=LONG
GenericName=Adventure Game
TryExec=residualvm
Exec=residualvm -p /PATH GAME
Icon=/usr/share/pixmaps/residualvm.xpm
Terminal=false
Type=Application
Categories=Game

This will be re-used for the other residualvm games. (and adapted for scummvm 
games)




If the residualvm-data start including nice DFSG icons for each game, this 
would be even better :-)

> This residualvm engine can run these games:
> 
> - Grim Fandango
> - Escape from Monkey Island
> - Myst 3 Exile
> 
> http://www.residualvm.org/compatibility/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#666726: debian-policy: Clarify if empty control fields are ollowed or not

[Bill Allombert]

On Mon, Nov 24, 2014 at 08:58:44AM +0900, Charles Plessy wrote:
> Hi Henrique and Bill,
> 
> first, on the original purpose of this bug, it is to document that empty 
> fields
> in binary package control files are not supported and can crash tools such as
> apt.  There, "empty" meant that the semicolon at the end of a field name is
> followed by a newline character.  A member FTP team answered to the submitter
> by confirming that binary packages with empty fields in their control file are
> rejected from the Debian archive.
> 
> I think that we all agree to document that fields must not be empty in binary
> package control files. 

Agreed.

>  Let's see the other points under discussion. 
> 
>  * The definition of "empty".  Henrique has used the word "empty" to designate
>fields of a source package control file that contain a substitution 
> variable
>that may not contain a value at build time.  I think that this complicates 
> the
>defintion of "empty" too much, since in that case one has to build a 
> package to
>determine if a field is empty or not.

Unfortunately that is an interpretation of "empty" that is natural to people 
used to
variable substitution (one tends to think subconciously of the document as if 
all
substutions has been performed). Thus some readers will interpret it this way 
even 
if we like it to mean something else.

>The answer would even depend on the
>state of the archive !  Regarding the submitter's definition, it is a bit
>stricter than what the syntax of control fields allows, where a field in 
> which
>the colon after the name is followed by spaces is also empty.
> 
>  * Whether to disallow empty fields in other control files.  I have not seen 
> empty
>fields elsewhere, and I am not aware of plan to use some.  Empty fields 
> are not
>used when a field is solely needed as a flag, such as the "Essential" 
> field.
>Altogether, I think that it would be neater to clarify the section about 
> the syntax
>of control files that fields must not be empty, than to make this a special
>restriction of binary package control files.

But at this point, there is no consensus that such empty fields should be
forbidden in source packages and they have been allowed for a long time
(and discarded by dpkg-gencontrol).

Thus I would like to restrict this bug to what is agreed, i.e. binary
package control files. This also side-step nicely the definition of "empty".

Cheers,
-- 
Bill. 

Imagine a large red swirl here.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777179: p0f: please make the build reproducible

[Chris Lamb]

Source: p0f
Version: 2.0.8-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that p0f could not be built reproducibly.

The attached patch removes timestamps from the build system. Once
applied, p0f can be built reproducibly in our current experimental
framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad p0f.orig/p0f-2.0.8/debian/rules p0f/p0f-2.0.8/debian/rules
--- p0f.orig/p0f-2.0.8/debian/rules 2015-02-05 22:38:19.039955070 +
+++ p0f/p0f-2.0.8/debian/rules  2015-02-05 22:38:41.268707603 +
@@ -42,12 +42,12 @@
 
$(install_dir) debian/tmp/usr/share/man/man1/
$(install_file) p0f.1 debian/tmp/usr/share/man/man1/
-   gzip -9v debian/tmp/usr/share/man/man1/*
+   gzip -9vn debian/tmp/usr/share/man/man1/*
 
$(install_dir) debian/tmp/usr/share/doc/p0f/
$(install_file) README doc/CREDITS doc/KNOWN_BUGS doc/TODO 
debian/tmp/usr/share/doc/p0f/
$(install_file) debian/changelog 
debian/tmp/usr/share/doc/p0f/changelog.Debian
-   gzip -9v debian/tmp/usr/share/doc/p0f/*
+   gzip -9vn debian/tmp/usr/share/doc/p0f/*
$(install_file) debian/copyright debian/tmp/usr/share/doc/p0f/
 
$(install_dir) debian/tmp/usr/share/doc/p0f/examples/

Bug#777178: pulseaudio: Pulseaudio often crashes. Makes crackling sound on (re)start

[christoph]

Package: pulseaudio
Version: 5.0-13
Severity: important

Dear Maintainer,

Pulseaudio often crashes when i start applications that use Pulseaudio (like
chrome, vlc, virtualbox, ...). It always crashes when i start pavucontrol.
When it crashes i get this output at the terminal:

(  77.968|   0.000) I: [pulseaudio] source-output.c: Trying to change sample
rate
(  77.968|   0.000) E: [pulseaudio] source.c: Assertion '(default_rate % 4000
== 0) || (default_rate % 11025 == 0)' failed at pulsecore/source.c:1016,
function pa_source_update_rate(). Aborting.
[1]8720 abort  pulseaudio -vvv --log-time


When Pulseaudio restarts it makes a crackling sound for about 5 seconds.
I have this problem since my update from stable to testing



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser   3.113+nmu3
ii  libasound21.0.28-1
ii  libasound2-plugins1.0.28-1+b1
ii  libc6 2.19-13
ii  libcap2   1:2.24-6
ii  libdbus-1-3   1.8.12-3
ii  libfftw3-single3  3.3.4-2
ii  libgcc1   1:4.9.1-19
ii  libice6   2:1.0.9-1+b1
ii  libltdl7  2.4.2-1.11
ii  liborc-0.4-0  1:0.4.22-1
ii  libpulse0 5.0-13
ii  libsamplerate00.1.8-8
ii  libsm62:1.2.2-1+b1
ii  libsndfile1   1.0.25-9.1
ii  libspeexdsp1  1.2~rc1.2-1
ii  libstdc++64.9.1-19
ii  libsystemd0   215-10
ii  libtdb1   1.3.1-1
ii  libudev1  215-10
ii  libwebrtc-audio-processing-0  0.1-3
ii  libx11-6  2:1.6.2-3
ii  libx11-xcb1   2:1.6.2-3
ii  libxcb1   1.10-3+b1
ii  libxtst6  2:1.2.2-1+b1
ii  lsb-base  4.1+Debian13+nmu1
ii  pulseaudio-utils  5.0-13
ii  udev  215-10

Versions of packages pulseaudio recommends:
ii  pulseaudio-module-x11  5.0-13
ii  rtkit  0.11-2

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
pn  pavucontrol  
pn  pavumeter

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
# USA.

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
# USA.

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; syste

Bug#777176: pre-approval: unblock: phpldapadmin/1.2.2-5.2

[Mika Pflüger]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

phpldapadmin has bug #761637, which I think is RC for phpldapadmin. The short 
version is: phpldapadmin is a frontend to manage ldap directories. As a 
regression from stable, the version in testing crashes if an entry in the 
managed ldap directory contains a password field. As it is /very/ common to 
have password fields in ldap entries, this renders the package unusable for a 
large portion of the user base.
Fortunately, the fix for this is small, as the issue is already partly fixed by 
version 1.2.2-5.1 which is already in testing. It was missing:
* A single line change in the code.
* An update of the config file
* A NEWS entry to explain users how to update their config.
I have prepared a package containing the fix, which can provisionally be found 
at https://mentors.debian.net/package/phpldapadmin . The meat of the debdiff is:

diff -Nru phpldapadmin-1.2.2/debian/changelog 
phpldapadmin-1.2.2/debian/changelog
--- phpldapadmin-1.2.2/debian/changelog 2014-05-02 04:30:44.0 +0200
+++ phpldapadmin-1.2.2/debian/changelog 2015-02-05 01:02:16.0 +0100
@@ -1,3 +1,11 @@
+phpldapadmin (1.2.2-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update the php 5.5 compatibility patch for the password_hash_custom
+setting (Closes: #761637).
+
+ -- Mika Pflüger   Thu, 05 Feb 2015 00:41:07 +0100
+
 phpldapadmin (1.2.2-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru phpldapadmin-1.2.2/debian/patches/php-5.5-compat.patch 
phpldapadmin-1.2.2/debian/patches/php-5.5-compat.patch
--- phpldapadmin-1.2.2/debian/patches/php-5.5-compat.patch  2014-05-02 
04:28:13.0 +0200
+++ phpldapadmin-1.2.2/debian/patches/php-5.5-compat.patch  2015-02-05 
01:13:38.0 +0100
+Index: phpldapadmin-1.2.2/config/config.php.example
+===
+--- phpldapadmin-1.2.2.orig/config/config.php.example
 phpldapadmin-1.2.2/config/config.php.example
+@@ -379,7 +379,7 @@ $servers->setValue('server','name','My L
+ 
+ /* Default password hashing algorithm. One of md5, ssha, sha, md5crpyt, smd5,
+blowfish, crypt or leave blank for now default algorithm. */
+-// $servers->setValue('appearance','password_hash','md5');
++// $servers->setValue('appearance','password_hash_custom','md5');
+ 
+ /* If you specified 'cookie' or 'session' as the auth_type above, you can
+optionally specify here an attribute to use when logging in. If you enter
+@@ -546,7 +546,7 @@ $servers->setValue('sasl','authz_id_rege
+ $servers->setValue('sasl','authz_id_replacement','$1');
+ $servers->setValue('sasl','props',null);
+ 
+-$servers->setValue('appearance','password_hash','md5');
++$servers->setValue('appearance','password_hash_custom','md5');
+ $servers->setValue('login','attr','dn');
+ $servers->setValue('login','fallback_dn',false);
+ $servers->setValue('login','class',null);
+Index: phpldapadmin-1.2.2/lib/TemplateRender.php
+===
+--- phpldapadmin-1.2.2.orig/lib/TemplateRender.php
 phpldapadmin-1.2.2/lib/TemplateRender.php
+@@ -2466,7 +2466,7 @@ function deleteAttribute(attrName,friend
+   if ($val = $attribute->getValue($i))
+   $default = get_enc_type($val);
+   else
+-  $default = 
$this->getServer()->getValue('appearance','password_hash');
++  $default = 
$this->getServer()->getValue('appearance','password_hash_custom');
+ 
+   if (! $attribute->getPostValue())
+   printf('',$attribute->getName(),$i);

(the version currently at mentors has a slightly larger debdiff due to quilt 
refresh'ing of the php-5.5-compat.patch, but with no further real changes).

If you pre-approve the unblock request, I will write a NEWS entry, seek a 
sponsor and come back to you. I am using a fixed version at a reasonably busy 
site for two weeks now.

One thing to note is that the version currently in testing deviates from the 
upstream solution, possibly because it predates it. The setting which collides 
with a php-internal function name ('password_hash' in debian stable) was 
[incompletely, hence this bug] changed to 'password_hash_custom' in debian, but 
to 'pla_password_hash' in the 1.2.3 upstream version. That is clearly a 
suboptimal situation, as this will confuse users and will come back to bite us 
later. However, I guess changing 'password_hash_custom' to 'pla_password_hash' 
is a bit intrusive at this stage of the release cycle. If you disagree, I can 
also prepare a patch which aligns with upstream's choice of bike shed colour.

Cheers,

Mika

unblock phpldapadmin/1.2.2-5.2

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (650, 'testing'), (450, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kern

Bug#777177: asciidoc: please make the build reproducible

[Chris Lamb]

Source: asciidoc
Version: 8.6.9-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that asciidoc could not be built reproducibly.

The attached patch removes timestamps from the build system. Once
applied, asciidoc can be built reproducibly in our current experimental
framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad asciidoc.orig/asciidoc-8.6.9/debian/rules 
asciidoc/asciidoc-8.6.9/debian/rules
--- asciidoc.orig/asciidoc-8.6.9/debian/rules   2015-02-05 22:18:14.323446923 
+
+++ asciidoc/asciidoc-8.6.9/debian/rules2015-02-05 22:28:04.691226747 
+
@@ -36,6 +36,7 @@
cp -aL doc/ debian/asciidoc/usr/share/doc/asciidoc/
rm debian/asciidoc/usr/share/doc/asciidoc/doc/*.1
./asciidoc.py  -b xhtml11 -a iconsdir=/usr/share/asciidoc/images/icons \
+   -a footer-style=none \
-o debian/asciidoc/usr/share/doc/asciidoc/userguide.html 
doc/asciidoc.txt
 
 override_dh_link:

Bug#768978: marked as done (apt-show-versions: No longer displays installed packages with "No available version in archive")

[Bob Proulx]

Christoph Martin wrote:
> schrieb Bob Proulx:
> > Christoph Martin wrote:
> >> I don't know if we can get it into testing. You could try to advocate it.
> > 
> > For the purposes of this bug issue this does not need to go into
> > Testing.  This bug was introduced after Testing was frozen.  Testing
> > has version 0.20 and this bug seems to have been introduced in 0.22.6
> > timeframe.  (I didn't search to the exact version but that was the
> 
> Testing has 0.20.4

Oops.  Yes.  I fumbled that version number.  Sorry.  But just the same
Testing's version 0.20.4 works fine and doesn't have this problem
though, right?

  # apt-get install apt-show-versions=0.22.4
  ...

  $ apt-show-versions | grep xlockmore
  xlockmore:amd64 1:5.31-1.1 installed: No available version in archive

I installed 0.22.5 and 0.22.6 and both of those were problem versions
and showed the problem.  So it appears to me that the problem was
introduced in 0.22.5 and therefore misses Jessie Testing.

Looks okay to me.  Am I missing something?

Thanks again for maintaining this very useful package! :-)

Bob

Details of my testing from a moment ago:

  # apt-get install apt-show-versions=0.22.4 # from Testing
  ...
  $ apt-show-versions | grep xlockmore
  xlockmore:amd64 1:5.31-1.1 installed: No available version in archive

  # apt-get install apt-show-versions=0.22.5 # from snapshot.debian.org
  ...
  $ apt-show-versions | grep xlockmore
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.

  # apt-get install apt-show-versions=0.22.6 # from snapshot.debian.org
  ...
  $ apt-show-versions | grep xlockmore
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.
  Use of uninitialized value $archiv in concatenation (.) or string at 
/usr/bin/apt-show-versions line 318.

  # apt-get install apt-show-versions=0.22.7 # from Sid
  ...
  $ apt-show-versions | grep xlockmore
  xlockmore:amd64 1:5.31-1.1 installed: No available version in archive


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#772963: release-notes: cellphone friendly CSS

[Stephan Beck]

Am 31.01.2015 um 17:14 schrieb Stéphane Blondon:
> Thank you Niels for your help! I cloned your git repository and
> patched the debian.css file.
> I attach here the new file and a diff. If it's nicer for you, I could
> create a temporary repository on GitHub. I've got a account on alioth
> (sblondon-guest) too.

Me, too (stebe-guest). It would be nice to exchange ideas there, if desired and
possible.
> 
> The temporary demo:
> http://stephane.yaal.fr/tmp/release-notes.amd64.html/index.en.html

> The home image is below the arrows. In my opinion, it would be better
> to display it at the same height than the arrows. I don't know if it's
> hard to do.

The first quick and dirty solution (only touching the .html file) is to suppress
the second table row in the.html file. (1) I've only applied it to the What's
new in Debian 8.html, just as an example. In this case you do not have to change
anything in the .css. Disadvantage: The footer has lost height.
For now, I cannot provide a demo url and I don't want to attach a file because
it's too large for a mailing list. Below you find a simple diff.

A second solution I'll work on is to replace the table with a
"div id="navfooter" containing a nav element that includes anchors and images.
I think it's better to use "table" only for "real" tables, not as a space
structuring design element. This solution will imply changes to the .css.

(1) diff --suppress-common-lines ch-whats-new.en-old.html ch-whats-new.en.html
215c215
<  Chapter 1. Introduction  Chapter 3. Installation
System
\ no line-break at end of file
---
>Chapter 1.
Introduction Chapter 3. Installation System 
\ no line-break at end of file

> 
> 
> What do you think about these changes?
> 
> For next improvement, we could replace the caution and note images
> with more modern ones (from the publican project or tango desktop
> project for example).

I haven't had time to check but if there's still time I'll check some new 
designs.
> 

Regards

Stephan







signature.asc
Description: OpenPGP digital signature

Bug#765298: Workaround

[Andrew Ayer]

I tracked down the bug in Archive::Zip, which was a doozy, and reported
it upstream:

https://github.com/redhotpenguin/perl-Archive-Zip/issues/11

Meanwhile, I've worked around it in strip-nondeterminism, so this
shouldn't be an issue for us anymore.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777175: unblock: libdate-calc-perl/6.3-2, libdate-calc-xs-perl/6.3-2 and libdate-pcalc-perl/6.1-4

[Damyan Ivanov]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

This is a bit of an unusual unblock request, because it affects three packages. 
The reason to have all three in one request is that the patch that is added is 
almost exactly the same. the first package's patch has an offset of +2 lines 
compared to the patch that is applied to the other two.

Please unblock packages libdate-calc-perl, libdate-calc-xs-perl and 
libdate-pcalc-perl.

The patch that is added to them is for fixing test failures during building 
(#775628, #775617 and #775632 respectively).

The reason the tests fail is because they depend on the current year. The tests 
try to ensure that conversion from a short year without a century to a fully 
written year work correctly in different situations. The year that was used is 
1964, '64' in the short form. That '64' was interpreted as '1964' up until 31 
Dec 2014, but since 1 Jan 2015 '64' is interpreted as '2064', because that year 
is closer to 2015 than is 1964. This behaviour is consistent with the modules' 
documentation.

The patch that is applied replaces the hardcoded years with the year 45 years 
in the past (long and short form). 45 is taken from the distance between 1964 
(which was the hardcoded year) and 2009, when the tests were written upstream.

The patch is lenghty, but is all the same all around. Replace '64' with '$y' 
and '1964' with '$Y', having set $y and $Y in the top. Obviously the three 
packages build fine today.

Attached are:

 * the standalone patch that was included as a quilt patch in the three 
   packages

 * debdiffs of the three packages since the version in jessie

unblock libdate-calc-perl/6.3-2

unblock libdate-calc-xs-perl/6.3-2

unblock libdate-pcalc-perl/6.1-4


Thanks for considering,
dam

-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Description: fix tests that got broken in 2015
 The tests use the 2-digit-year '64' and check that it expands to 1964; which
 worked until 2014-12-31. Since 2015-01-01 it expands to 2064, and this
 behaviour is consistent with the module documentation.
 .
 So the patch changes the hardcoded '1964' and '64' with the year 45 in the
 past from now, full and century-less version.
 .
 45 is how far in the past 1964 was in 2009, when the tests were written.

Bug: https://rt.cpan.org/Public/Bug/Display.html?id=101232
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=101232
Bug-Debian: https://bugs.debian.org/775617
Author: Damyan Ivanov , Gregor Herrmann 

--- a/t/f016.t
+++ b/t/f016.t
@@ -11,55 +11,58 @@ use Date::Calc qw( Decode_Date_EU Decode
 #   ($year,$mm,$dd) = Decode_Date_US($buffer);
 # ==
 
+my $Y = 1900 + (localtime)[5] - 45; # expected year (e.g. 1965 in 2009)
+my $y = sprintf("%02d", $Y % 100);  # short year(e.g. 65)
+
 print "1..25\n";
 
 $n = 1;
-if ((($year,$mm,$dd) = Decode_Date_EU("3.1.64")) &&
-($year==1964)&&($mm==1)&&($dd==3))
+if ((($year,$mm,$dd) = Decode_Date_EU("3.1.$y")) &&
+($year==$Y)&&($mm==1)&&($dd==3))
 {print "ok $n\n";} else {print "not ok $n\n";}
 $n++;
-if ((($year,$mm,$dd) = Decode_Date_EU("3 1 64")) &&
-($year==1964)&&($mm==1)&&($dd==3))
+if ((($year,$mm,$dd) = Decode_Date_EU("3 1 $y")) &&
+($year==$Y)&&($mm==1)&&($dd==3))
 {print "ok $n\n";} else {print "not ok $n\n";}
 $n++;
-if ((($year,$mm,$dd) = Decode_Date_EU("03.01.64")) &&
-($year==1964)&&($mm==1)&&($dd==3))
+if ((($year,$mm,$dd) = Decode_Date_EU("03.01.$y")) &&
+($year==$Y)&&($mm==1)&&($dd==3))
 {print "ok $n\n";} else {print "not ok $n\n";}
 $n++;
-if ((($year,$mm,$dd) = Decode_Date_EU("03/01/64")) &&
-($year==1964)&&($mm==1)&&($dd==3))
+if ((($year,$mm,$dd) = Decode_Date_EU("03/01/$y")) &&
+($year==$Y)&&($mm==1)&&($dd==3))
 {print "ok $n\n";} else {print "not ok $n\n";}
 $n++;
-if ((($year,$mm,$dd) = Decode_Date_EU("3. Ene 1964",4)) &&
-($year==1964)&&($mm==1)&&($dd==3))
+if ((($year,$mm,$dd) = Decode_Date_EU("3. Ene $Y",4)) &&
+($year==$Y)&&($mm==1)&&($dd==3))
 {print "ok $n\n";} else {print "not ok $n\n";}
 $n++;
-if ((($year,$mm,$dd) = Decode_Date_EU("Geburtstag: 3. Januar '64 in Backnang/Württemberg",3)) &&
-($year==1964)&&($mm==1)&&($dd==3))
+if ((($year,$mm,$dd) = Decode_Date_EU("Geburtstag: 3. Januar '$y in Backnang/Württemberg",3)) &&
+($year==$Y)&&($mm==1)&&($dd==3))
 {print "ok $n\n";} else {print "not ok $n\n";}
 $n++;
-if ((($year,$mm,$dd) = Decode_Date_EU("03-Jan-64")) &&
-($year==1964)&&($mm==1)&&($dd==3))
+if ((($year,$mm,$dd) = Decode_Date_EU("03-Jan-$y")) &&
+($year==$Y)&&($mm==1)&&($dd==3))
 {print "ok $n\n";} else {print "not ok $n\n";

Bug#775870: libfile-stripnondeterminism-perl: Does not strip javadoc's header

[Andrew Ayer]

On Tue, 20 Jan 2015 23:30:14 +0100
Peter De Wachter  wrote:

> Javadoc files, at least the ones I've looked at, have, in addition
> to the "Generated by javadoc" comment, a timestamp in a  name="date"> tag.

Excellent catch; thanks!  I've enhanced the javadoc handler to also
normalize this tag.  It's in 0.004, which I'm currently uploading to
the Reproducible APT archive.

-- Andrew


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777174: g15stats: cpu information isnt shown

[treaki]

Package: g15stats
Version: 1.9.2-2
Severity: important

there is an error whith showing cpu information, just guessed 5% of the time a 
value is showen, the rest just -nan is shown. You see a photo in the 
attachmant. plz fix that.

thanks in advance and greetings

treaki


-- System Information:
Debian Release: 7.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages g15stats depends on:
ii  g15daemon 1.9.5.3-8.2
ii  libc6 2.13-38+deb7u6
ii  libg15daemon-client1  1.9.5.3-8.2
ii  libg15render1 1.3.0~svn316-2.2
ii  libglib2.0-0  2.33.12+really2.32.4-5
ii  libgtop2-72.28.4-3

g15stats recommends no packages.

g15stats suggests no packages.

-- no debconf information

Bug#775795: [Pkg-puppet-devel] Bug#775795: Patch to use /usr/sbin/service in Debian service provider

[Stig Sandbeck Mathisen]

Gaudenz Steinlin  writes:

> Attached is an updated patch that uses a propoer Ruby constant for
> /usr/sbin/service. The first patch was botched by my "Pythonistic"
> approach to code this.

Patch committed. I've tested the packages with autopkgtest as well as
manually. I've uploaded the new packages, and sent an unblock request to
the release team.

Thank you. :)

-- 
Stig Sandbeck Mathisen


signature.asc
Description: PGP signature

Bug#768978: marked as done (apt-show-versions: No longer displays installed packages with "No available version in archive")

[Christoph Martin]

Am 05.02.2015 um 19:01 schrieb Bob Proulx:
> Christoph Martin wrote:
>> I don't know if we can get it into testing. You could try to advocate it.
> 
> For the purposes of this bug issue this does not need to go into
> Testing.  This bug was introduced after Testing was frozen.  Testing
> has version 0.20 and this bug seems to have been introduced in 0.22.6
> timeframe.  (I didn't search to the exact version but that was the

Testing has 0.20.4


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#484974: Surely ntpdate is unnecessary (if we have ntpd)

[Pierre Colombier]

This is just my point of view but I still think that the event "network 
going up" should not be linked with "Starting time synchronisation" 
since there there is no logical link between theses two kind of events.


I think that syncing with internet time must be considered as a service, 
not an event-driven task.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777173: unblock: puppet/3.7.2-2

[Stig Sandbeck Mathisen]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package puppet


The puppet provider for handling services (starting, stopping, status
query) executed "/etc/init.d/$service", which has unpredictable
results when using an init other than sysvinit.

A patch has been added to make puppet execute "/usr/sbin/service
$service" instead, ensuring that puppet can handle services no matter
which init system is used.



diff -Nru puppet-3.7.2/debian/changelog puppet-3.7.2/debian/changelog
--- puppet-3.7.2/debian/changelog   2014-10-24 13:47:25.0 +0200
+++ puppet-3.7.2/debian/changelog   2015-02-05 22:50:31.0 +0100
@@ -1,3 +1,11 @@
+puppet (3.7.2-2) unstable; urgency=medium
+
+  [ Gaudenz Steinlin ]
+  * [558cce5] Use /usr/sbin/service in the Debian service provider
+(Closes: #775795)
+
+ -- Stig Sandbeck Mathisen   Thu, 05 Feb 2015 22:44:49 +0100
+
 puppet (3.7.2-1) unstable; urgency=medium
 
   * Imported upstream release 3.7.2
diff -Nru 
puppet-3.7.2/debian/patches/0004-debian-service-provider-use-service.patch 
puppet-3.7.2/debian/patches/0004-debian-service-provider-use-service.patch
--- puppet-3.7.2/debian/patches/0004-debian-service-provider-use-service.patch  
1970-01-01 01:00:00.0 +0100
+++ puppet-3.7.2/debian/patches/0004-debian-service-provider-use-service.patch  
2015-02-05 22:50:31.0 +0100
@@ -0,0 +1,56 @@
+From: Gaudenz Steinlin 
+Subject: Use /usr/sbin/service for service management on Debian
+
+In Debian jessie systemd will be the default init system. But the old system V
+and other alternative init systems are still supported. /usr/sbin/service
+provides an abstraction layer which is able to start, stop and restart
+services independent of the init system used.
+
+Bug: https://tickets.puppetlabs.com/browse/PUP-2023
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775795
+---
+Index: puppet/lib/puppet/provider/service/debian.rb
+===
+--- puppet.orig/lib/puppet/provider/service/debian.rb  2015-02-05 
12:07:37.451292892 +0100
 puppet/lib/puppet/provider/service/debian.rb   2015-02-05 
12:13:06.500095957 +0100
+@@ -16,6 +16,11 @@
+   # is resolved.
+   commands :invoke_rc => "/usr/sbin/invoke-rc.d"
+ 
++  # This isn't being used directly, it's just here to ensure
++  # that the /usr/sbin/service binary is available.
++  SERVICE = "/usr/sbin/service"
++  commands :service_cmd => SERVICE
++
+   defaultfor :operatingsystem => :debian
+ 
+   # Remove the symlinks
+@@ -61,4 +66,28 @@
+ update_rc "-f", @resource[:name], "remove"
+ update_rc @resource[:name], "defaults"
+   end
++
++  # The start, stop, restart and status command use service
++  # this makes sure that these commands work with whatever init
++  # system is installed
++  def startcmd
++[SERVICE, @resource[:name], :start]
++  end
++
++  # The stop command is just the init script with 'stop'.
++  def stopcmd
++[SERVICE, @resource[:name], :stop]
++  end
++
++  def restartcmd
++(@resource[:hasrestart] == :true) && [SERVICE, @resource[:name], :restart]
++  end
++
++  # If it was specified that the init script has a 'status' command, then
++  # we just return that; otherwise, we return false, which causes it to
++  # fallback to other mechanisms.
++  def statuscmd
++(@resource[:hasstatus] == :true) && [SERVICE, @resource[:name], :status]
++  end
++
+ end
diff -Nru puppet-3.7.2/debian/patches/series puppet-3.7.2/debian/patches/series
--- puppet-3.7.2/debian/patches/series  2014-10-24 13:47:25.0 +0200
+++ puppet-3.7.2/debian/patches/series  2015-02-05 22:50:31.0 +0100
@@ -1,3 +1,4 @@
 0001-Do-not-require-rubygems.patch
 0002-Set-passenger-puppet-master-document-root.patch
 0003-fix-puppet-master-logcheck-rule.patch
+0004-debian-service-provider-use-service.patch




unblock puppet/3.7.2-2

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.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
Init: systemd (via /run/systemd/system)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#773557: debian-policy: Avoid unsafe RPATH/RUNPATH

[Bill Allombert]

On Fri, Dec 19, 2014 at 11:49:49PM +0100, Martin Carpenter wrote:
> Package: debian-policy
> Severity: important
> Tags: patch
> 
> Dear Maintainer,
> 
> The existing policy does not specify that the RPATH or RUNPATH (if
> present) should not contain relative paths or paths that traverse
> dangerous (eg world writable) directories. There is some discussion
> of this on the OSS-security list starting at:
> http://seclists.org/oss-sec/2014/q4/761
> 
> Example bugs that could be avoided with such a policy:
> https://bugs.debian.org/754278
> https://bugs.debian.org/759868

Alas policy by itself does not prevent bugs, a lintian test is more efficient,

> (There is an existing check for RPATH in lintian
> (binary-or-shlib-defines-rpath) but it is only "Certainty: possible"
> due to possible caveats. Relative RPATH/RUNPATH on the other hand is
> slam-dunk certain).

Then maybe lintian should have a separate test for relative RPATH/RUNPATH.

> There is some good discussion in these last two reports but they are
> both stale (5 years). I suspect that this is because the scope of these
> proposals is quite broad. Therefore I'd like to propose a (hopefully
> uncontraversial) paragraph that addresses at least the security concern
> and that may provide a base for further refinements in the spirit of
> #458824 and #555982 as well as a raison d'etre for a future lintian
> check to help avoid these security exposures.

It is not necessary to document in policy all the obvious invalid behaviours
of packages prior to have them check by lintian.

> > 8.7 RUNPATH and RPATH
> >
> > Libraries and executables should not define RPATH or RUNPATH unless
> > absolutely necessary.
> >
> > Those that do should ensure that relative paths or paths that traverse
> > insecure directories (eg /tmp or /var/tmp) are not included. This
> > is to prevent an executable from loading a library from an untrusted
> > location. (This should include the corner cases whereby the path list
> > starts or ends with a colon, or includes two consecutive colons).

I would further suggest we forbid /usr/lib  and /usr/lib//,
and only allow RUNPATH to other subdirectories of /usr/lib (to support
what policy call plug-in).

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777146: Fiona does not build

[Johan Van de Wauw]

>> Also fiona requires a recent version of Cython, so building under
>> jessie is not possible without further tweaking.
>
> jessie & sid have the same cython version, so it should work. The wheezy
> version is not sufficient though.


Interesting. In that case it got a freeze exception. When I last
checked it was still at an older version [1].
So I really closed a jessie RC bug there :-).

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754752


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777170: [pkg-wpa-devel] Bug#777170: wpasupplicant: lots of CTRL-EVENT-SIGNAL-CHANGE messages in syslog and couldn't connect to wireless network

[Stefan Lippers-Hollmann]

tags -1 moreinfo

Hi

On 2015-02-05, Julian Gilbey wrote:
> Package: wpasupplicant
> Version: 2.3-1
> Severity: normal
> 
> I was trying to connect to a wireless network from my MacBook Pro
> running testing today, and it connected only intermittently.  I'm
> using network-manager, if that makes any difference.  It may be the
> network involved, as I can connect to my home network with no
> difficulties.

What wireless card are you using in your system/ which kernel driver
is in use? Overcrowded and noisy environments can certainly make the
situation worse, especially when you're almost out of reach of your
AP and may even hop between different, equally bad APs. I guess this
part of the issue is more of kernel issue though.

> The log file was filled with thousands of lines of the form:
> 
> Feb  5 16:54:18 redfield wpa_supplicant[2925]: wlan0: 
> CTRL-EVENT-SIGNAL-CHANGE above=1 signal=0 noise=0 txrate=48000
> 
> which were appearing at the rate of about 10 per second.

CTRL-EVENT-SIGNAL-CHANGE is emitted at the MSG_INFO (default) logging
level - you can tune wpa_supplicant's logging level to reduce (and
subsequently hide) these messages. If you start wpa_supplicant by hand,
the parameters are -d, -dd, ... (to increase the logging level) or -q, 
-qq, ... (to reduce the logging level. ifupdown's wpa_supplicant 
integration allows you to set a debugging level via 
"wpa-debug-level %d" (where %d stands for positive or negative numbers,
e.g. -3, ..., 0, ..., 3). I do not know how (or if) networkmanager 
exposes access to these settings.

As long as your kernel driver/ module is working fine, you're usually
not supposed to get bothered by this event - it may be emitted 
occassionally, but rarely enough not to be noticed.

> I had a similar problem last week, and I wonder whether the same was
> happening then.
> 
> A reboot did not help.

Try to move around, closer to an access point, and check if the 
situation improves. Chances for wireless problems typically increase
in noisy environments.

> It made no difference whether I was plugged in or working on battery
> power, and I have also uninstalled laptop-mode-tools thinking that
> this might have been a contributory factor.

This should not affect your problem (but you never know).

> I can happily do further experiments next week if that would help.
[...]

Unless you're simply having problems with your signal level (too much
noise, APs (almost) out of range), this is most likely a kernel 
problem (and probably needs to get re-assigned there, wpa_supplicant
emitting these event notices is then merely a consequence of your
network going away/ re-appearing. While it's not impossible that this
might also be an interoperability problem between the AP and your 
client (where either kernel or wpa_supplicant might be to blame, but
given that hostapd, the other component of src:wpa, is the effective
reference implementation for APs, this is slightly less likely), I 
don't think this to be the issue here.

Regards
Stefan Lippers-Hollmann


pgpHs1yTg10Rv.pgp
Description: Digitale Signatur von OpenPGP

Bug#765499: Patch to make policy document 32-bit uids

[Bill Allombert]

On Mon, Feb 02, 2015 at 08:51:44PM +0100, Julien Cristau wrote:
> On Sun, Feb  1, 2015 at 23:38:24 +0100, Bill Allombert wrote:
> 
> > On Sat, Jan 31, 2015 at 12:28:22PM -0800, Russ Allbery wrote:
> > > Bill Allombert  writes:
> > > 
> > > > + 4294967294:
> > > > + 
> > > > +   
> > > > + (uid_t)(-2) == (gid_t)(-2) must
> > > > + not be used, because it is mistaken for
> > > > +  65534 nobody by some
> > > > +  programs.
> > > > +   
> > > > + 
> > > 
> > > I would instead say:
> > > 
> > > must not be used, because it is used as the anonymous,
> > > unauthenticated user by some NFS implementations.
> > 
> > OK I offer an updated patch.
> > 
> > Third time's a charm I hope.
> > 
> Seconded.

This makes two seconds.

I have created a branch bug765499-bill with this patch that I will merge
shortly if there is no further comments. 

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777146: Fiona does not build

[Sebastiaan Couwenberg]

On 02/05/2015 10:33 PM, Johan Van de Wauw wrote:
> It works for me in unstable. You will need a recent update of unstable
> as fiona relies on python-cligj which was only added yesterday.

You don't need to have python-cligj installed locally to build the
package with pbuilder, you do need cython and libgdal-dev.

> Also fiona requires a recent version of Cython, so building under
> jessie is not possible without further tweaking.

jessie & sid have the same cython version, so it should work. The wheezy
version is not sufficient though.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/E88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777164: systemd: libvirt cgroups start to disappear from machine.slice after systemctl daemon-reload

[Michael Biebl]

contol: forwarded -1 https://bugzilla.redhat.com/show_bug.cgi?id=1139223

Am 5. Februar 2015 20:06:56 MEZ, schrieb Mateusz Nalewajski 
:
>Package: systemd
>Version: 215-10
>Severity: important
>
>Dear Maintainer,
>
>I use libvirt with KVM on Debian Jessie for virtualizing my lab
>environment. However when I tried once to connect an USB host device to
>the virtual machine, libvirt complained about missing cgroup. When I
>went through the /sys/fs/cgroup I found that cgroups of some running
>virtual machines are not in machine.slice anymore.
>
>Here is a link to a similar bug on Red Hat Bugzilla
>https://bugzilla.redhat.com/show_bug.cgi?id=1139223


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775795: [Pkg-puppet-devel] Bug#775795: Patch to use /usr/sbin/service in Debian service provider

[Stig Sandbeck Mathisen]

Gaudenz Steinlin  writes:

> Attached is an updated patch that uses a propoer Ruby constant for
> /usr/sbin/service. The first patch was botched by my "Pythonistic"
> approach to code this.

That looks much better, thanks.

-- 
Stig Sandbeck Mathisen


signature.asc
Description: PGP signature

Bug#777146: Fiona does not build

[Sebastiaan Couwenberg]

On 02/05/2015 10:22 PM, Andreas Tille wrote:
> I: pybuild base:170: python3.4 setup.py clean 
> WARNING:root:Failed to get options via gdal-config: [Errno 2] No such file or 
> directory: 'gdal-config'
> CRITICAL:root:Cython.Build.cythonize not found. Cython is required to build 
> from a repo.
> E: pybuild pybuild:256: clean: plugin distutils failed with: exit code=1: 
> python3.4 setup.py clean 

Looks like you don't have all build dependencies installed locally
(libgdal-dev includes gdal-config).

My builds on sid succeeded without issues.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/E88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#756499: O: postpone -- schedules commands to be executed later

[Christoph Berg]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: postpone -- RoM; not really useful

Re: To Debian Bug Tracking System 2014-07-30 
<20140730114910.ga3...@msg.df7cb.de>
> Package: wnpp
> Severity: normal
> 
> I've never really used "postpone", and the intended use in package
> maintainer scripts is obsoleted by the advent of dpkg triggers. Hence
> I'm orphaning the package. If no one is picking it up, I'll request
> removal from the archive before the jessie release.

Please remove postpone from unstable and testing.

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


signature.asc
Description: Digital signature

Bug#777146: Fiona does not build

[Johan Van de Wauw]

Strange,

gdal-config (libgdal-dev) and cython are in the control file.
Something strange seems to be happening in that pbuilder.

It works for me in unstable. You will need a recent update of unstable
as fiona relies on python-cligj which was only added yesterday.

Also fiona requires a recent version of Cython, so building under
jessie is not possible without further tweaking.

Johan

On Thu, Feb 5, 2015 at 10:22 PM, Andreas Tille  wrote:
> Hi Johan,
>
> when trying to build fiona I get:
>
> ...
> Cythonizing fiona/ogrext.pyx
> /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution 
> option: 'metadata_version'
>   warnings.warn(msg)
> /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution 
> option: 'requires_python'
>   warnings.warn(msg)
> /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution 
> option: 'requires_external'
>   warnings.warn(msg)
> running clean
> removing 
> '/home/andreas/debian-maintain/alioth/debian-gis/build-area/fiona-1.5.0/.pybuild/pythonX.Y_2.7/build'
>  (and everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-2.7' does not exist -- can't clean it
> I: pybuild base:170: python3.4 setup.py clean
> WARNING:root:Failed to get options via gdal-config: [Errno 2] No such file or 
> directory: 'gdal-config'
> CRITICAL:root:Cython.Build.cythonize not found. Cython is required to build 
> from a repo.
> E: pybuild pybuild:256: clean: plugin distutils failed with: exit code=1: 
> python3.4 setup.py clean
> dh_auto_clean: pybuild --clean -i python{version} -p 3.4 --dir . returned 
> exit code 13
> debian/rules:14: recipe for target 'clean' failed
> make: *** [clean] Error 13
> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
> gbp:error: '~/bin/git-pbuilder' failed: it exited with 2
>
>
> Kind regards
>
>   Andreas.
>
>
> --
> http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777146: Fiona does not build

[Andreas Tille]

Hi Johan,

when trying to build fiona I get:

...
Cythonizing fiona/ogrext.pyx
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution 
option: 'metadata_version'
  warnings.warn(msg)
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution 
option: 'requires_python'
  warnings.warn(msg)
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution 
option: 'requires_external'
  warnings.warn(msg)
running clean
removing 
'/home/andreas/debian-maintain/alioth/debian-gis/build-area/fiona-1.5.0/.pybuild/pythonX.Y_2.7/build'
 (and everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-2.7' does not exist -- can't clean it
I: pybuild base:170: python3.4 setup.py clean 
WARNING:root:Failed to get options via gdal-config: [Errno 2] No such file or 
directory: 'gdal-config'
CRITICAL:root:Cython.Build.cythonize not found. Cython is required to build 
from a repo.
E: pybuild pybuild:256: clean: plugin distutils failed with: exit code=1: 
python3.4 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 3.4 --dir . returned exit 
code 13
debian/rules:14: recipe for target 'clean' failed
make: *** [clean] Error 13
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
gbp:error: '~/bin/git-pbuilder' failed: it exited with 2


Kind regards

  Andreas.


-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777172: python3-numpy: typo in the help(numpy.kron) message

[Alexei Andreanov]

Package: python3-numpy
Version: 1:1.8.2-2
Severity: minor

Dear Maintainer,

If numpy as imported (I assume under the name of "numpy"), then the help 
message for the function
numpy.kron invoked with "help(numpy.kron)" contains a typo in the section 
"Notes":
"dimenensions" should read "dimensions"

Regards,
Alexei

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.5-0 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages python3-numpy depends on:
ii  libatlas3-base [liblapack.so.3]3.10.2-7
ii  libblas3 [libblas.so.3]1.2.20110419-10
ii  libc6  2.19-13
ii  libgcc11:4.9.1-19
ii  libgfortran3   4.9.1-19
ii  liblapack3 [liblapack.so.3]3.5.0-4
ii  libopenblas-base [liblapack.so.3]  0.2.12-1+custom1
ii  libquadmath0   4.9.1-19
ii  python33.4.2-2
ii  python3.4  3.4.2-1

python3-numpy recommends no packages.

Versions of packages python3-numpy suggests:
ii  gcc4:4.9.1-5
ii  gfortran   4:4.9.1-5
pn  python-numpy-doc   
ii  python3-dev3.4.2-2
ii  python3-nose   1.3.4-1
pn  python3-numpy-dbg  

-- 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#777171: grub-pc: no partitions found after loading the ohci module

[Vincent Duvert]

Package: grub-pc
Version: 2.02~beta2-21
Severity: important

Dear Maintainer,

Upon using "insmod ohci" from the grub prompt to load the ohci module, grub
stops recognizing the available disks and partitions.

grub> insmod ohci
error : disk "hd0,msdos3" not found.
grub>
The keyboard stops working afterwards. On another machine, the keyboard
continues to work, but none of the commands work:

grub> ls
(hd0) (hd0,msdos5) (hd0,msdos1) (fd0)
grub> insmod ohci
grub> ls

grub> help
error: disk "hd0,msdos1" not found.

With grub 1.99-27+deb7u2, the module is loaded correctly without side effects.

Thanks.



-- Package-specific info:

*** BEGIN /proc/mounts
/dev/disk/by-uuid/0bca68af-8a13-4010-8b34-c70dcffce40a / ext4 
rw,noatime,errors=remount-ro,data=ordered 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos3'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 
--hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3  
0bca68af-8a13-4010-8b34-c70dcffce40a
else
  search --no-floppy --fs-uuid --set=root 0bca68af-8a13-4010-8b34-c70dcffce40a
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=fr_FR
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=-1
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd0,msdos3'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 
--hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3  
0bca68af-8a13-4010-8b34-c70dcffce40a
else
  search --no-floppy --fs-uuid --set=root 0bca68af-8a13-4010-8b34-c70dcffce40a
fi
insmod png
if background_image /usr/share/images/desktop-base/lines-grub.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-0bca68af-8a13-4010-8b34-c70dcffce40a' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos3'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 
--hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3  
0bca68af-8a13-4010-8b34-c70dcffce40a
else
  search --no-floppy --fs-uuid --set=root 
0bca68af-8a13-4010-8b34-c70dcffce40a
fi
echo'Chargement de Linux 3.16.0-4-amd64…'
linux   /boot/vmlinuz-3.16.0-4-amd64 
root=UUID=0bca68af-8a13-4010-8b34-c70dcffce40a ro  quiet
echo'Chargement du disque mémoire initial…'
initrd  /boot/initrd.img-3.16.0-4-amd64
}
submenu 'Options avancées pour Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-0bca68af-8a13-4010-8b34-c70dcffce40a' {
menuentry 'Debian GNU/Linux, avec Linux 3.16.0-4-amd64' --class debian 
--class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-3.16.0-4-amd64-advanced-0bca68af-8a13-4010-8b34-c70dcffce40a' {
load_video
  

Bug#777010: reportbug crashes when trying to submit bug report

[Oxan van Leeuwen]

Hi,

On 05-02-15 13:15, Sandro Tosi wrote:

You are using paranoid mode, which makes reportbug print the message
right before submitting it, and there is where you are seeing the
traceback.

Yes, that's correct. reportbug crashes immediately after I exit the pager.


Given your particular EDITOR env var, is it possible that
PAGER is also set to something "uncommon"?
No, the PAGER environment variable is unset; and the pager started was 
simply less.



are you able to replicate this bug or was just "one off"?
Yes, I was able to replicate it twice. Some further testing just now 
revealed that I can reproduce it reliably but only when I attach a 
specific file, which I've attached to this message.


Let me know if I can do more to help.

Regards,
Oxan
[0.00] CPU0 microcode updated early to revision 0x1c, date = 2014-07-03
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.18.0-trunk-amd64 
(debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP 
Debian 3.18.5-1~exp1 (2015-01-31)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-3.18.0-trunk-amd64 
root=UUID=452d1dc1-2c61-4bba-b64a-8137c122bf0b ro net.ifnames=1 
netconsole=@130.89.172.53/eth0,@130.89.171.131/60:a4:4c:d6:77:4d
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x00057fff] usable
[0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved
[0.00] BIOS-e820: [mem 0x00059000-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x0010-0xc29e4fff] usable
[0.00] BIOS-e820: [mem 0xc29e5000-0xc29ebfff] ACPI NVS
[0.00] BIOS-e820: [mem 0xc29ec000-0xc2e2efff] usable
[0.00] BIOS-e820: [mem 0xc2e2f000-0xc33b] reserved
[0.00] BIOS-e820: [mem 0xc33c-0xd4dabfff] usable
[0.00] BIOS-e820: [mem 0xd4dac000-0xd4e43fff] reserved
[0.00] BIOS-e820: [mem 0xd4e44000-0xd4e94fff] usable
[0.00] BIOS-e820: [mem 0xd4e95000-0xd4fc7fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xd4fc8000-0xd5f80fff] reserved
[0.00] BIOS-e820: [mem 0xd5f81000-0xd5ffefff] type 20
[0.00] BIOS-e820: [mem 0xd5fff000-0xd5ff] usable
[0.00] BIOS-e820: [mem 0xd700-0xdf1f] reserved
[0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00031fdf] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.31 by American Megatrends
[0.00] efi:  ACPI=0xd4f99000  ACPI 2.0=0xd4f99000  SMBIOS=0xf04d0  
MPS=0xfd500 
[0.00] efi: mem00: [Boot Code  |   |  |  |  |   |WB|WT|WC|UC] 
range=[0x-0x8000) (0MB)
[0.00] efi: mem01: [Conventional Memory|   |  |  |  |   |WB|WT|WC|UC] 
range=[0x8000-0x00058000) (0MB)
[0.00] efi: mem02: [Reserved   |   |  |  |  |   |WB|WT|WC|UC] 
range=[0x00058000-0x00059000) (0MB)
[0.00] efi: mem03: [Conventional Memory|   |  |  |  |   |WB|WT|WC|UC] 
range=[0x00059000-0x0005f000) (0MB)
[0.00] efi: mem04: [Boot Data  |   |  |  |  |   |WB|WT|WC|UC] 
range=[0x0005f000-0x0006) (0MB)
[0.00] efi: mem05: [Boot Code  |   |  |  |  |   |WB|WT|WC|UC] 
range=[0x0006-0x0009f000) (0MB)
[0.00] efi: mem06: [Reserved   |   |  |  |  |   |WB|WT|WC|UC] 
range=[0x0009f000-0x000a) (0MB)
[0.00] efi: mem07: [Loader Data|   |  |  |  |   |WB|WT|WC|UC] 
range=[0x0010-0x00f68000) (14MB)
[0.00] efi: mem08: [Conventional Memory|   |  |  |  |   |WB|WT|WC|UC] 
range=[0x00f68000-0x361bc000) (850MB)
[0.00] efi: mem09: [Loader Data|   |  |  |  |   |WB|WT|WC|UC] 
range=[0x361bc000-0x370d6000) (15MB)
[0.00] efi: mem10: [Conventional Memory|   |  |  |  |   |WB|WT|WC|UC] 
range=[0x370d6000-0x8d955000) (1384MB)
[0.00] efi: mem11: [Loader Data|   |  |  |  |   |WB|WT|WC|UC] 
range=[0x8d955000-0xbf4dd000) (795MB)
[0.0

Bug#776821: icu-devtools is wrongly marked Multi-Arch:foreign

[Helmut Grohne]

Control: tags -1 + patch

On Mon, Feb 02, 2015 at 08:08:31PM +0100, Helmut Grohne wrote:
> Funny, cross building libxml2 only works after dropping M-A:foreign, so
> your claim clearly is wrong. The reverse holds: Dropping M-A:foreign
> makes some reverse depends of libicu-dev cross-buildable!

Given that:
 * icu-devtools currently can cause broken native builds (which is a
   regression from wheezy).
 * icu was not multiarch-aware in wheezy, so making it non-multiarch is
   not a regression.
 * Some packages (e.g. libxml2) become cross-buildable by removing
   M-A:foreign.

I believe that removing M-A:foreign is the right fix with minimal
changes for jessie. To that end I created a patch. Any objections to
NMUing that?

Helmut
diff -Nru icu-52.1/debian/changelog icu-52.1/debian/changelog
--- icu-52.1/debian/changelog   2015-01-22 03:47:39.0 +0100
+++ icu-52.1/debian/changelog   2015-02-05 22:10:26.0 +0100
@@ -1,3 +1,11 @@
+icu (52.1-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove M-A:foreign from icu-devtools as icu-config is
+architecture-specific. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 05 Feb 2015 22:10:05 +0100
+
 icu (52.1-7) unstable; urgency=high
 
   * Patch to CVE-2014-6591, CVE-2014-6585 a font parsing bug.
diff -Nru icu-52.1/debian/control icu-52.1/debian/control
--- icu-52.1/debian/control 2015-01-22 03:47:39.0 +0100
+++ icu-52.1/debian/control 2015-02-05 22:10:34.0 +0100
@@ -44,7 +44,6 @@
 Package: icu-devtools
 Section: libdevel
 Architecture: any
-Multi-Arch: foreign
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Replaces: libicu-dev (<< ${binary:Version}), icu-tools (<< 52.1-3~)

Bug#777170: wpasupplicant: lots of CTRL-EVENT-SIGNAL-CHANGE messages in syslog and couldn't connect to wireless network

[Julian Gilbey]

Package: wpasupplicant
Version: 2.3-1
Severity: normal

I was trying to connect to a wireless network from my MacBook Pro
running testing today, and it connected only intermittently.  I'm
using network-manager, if that makes any difference.  It may be the
network involved, as I can connect to my home network with no
difficulties.

The log file was filled with thousands of lines of the form:

Feb  5 16:54:18 redfield wpa_supplicant[2925]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=0 noise=0 txrate=48000

which were appearing at the rate of about 10 per second.

I had a similar problem last week, and I wonder whether the same was
happening then.

A reboot did not help.

It made no difference whether I was plugged in or working on battery
power, and I have also uninstalled laptop-mode-tools thinking that
this might have been a contributory factor.

I can happily do further experiments next week if that would help.

Thanks!

   Julian

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages wpasupplicant depends on:
ii  adduser   3.113+nmu3
ii  libc6 2.19-13
ii  libdbus-1-3   1.8.12-3
ii  libnl-3-200   3.2.24-2
ii  libnl-genl-3-200  3.2.24-2
ii  libpcsclite1  1.8.13-1
ii  libreadline6  6.3-8+b3
ii  libssl1.0.0   1.0.1k-1
ii  lsb-base  4.1+Debian13+nmu1

wpasupplicant recommends no packages.

Versions of packages wpasupplicant suggests:
pn  libengine-pkcs11-openssl  
pn  wpagui

-- 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#777169: FTBFS on sparc64: symbol errors

[Helmut Grohne]

Source: gcc-4.9
Version: 4.9.1-17
User: helm...@debian.org
Usertags: rebootstrap

gcc-4.9 currently FTBFS on sparc64 due to symbol errors. While the last
two builds on sompek failed due to -ENOSPC the build of 4.9.1-17 shows
proper symbol diffs:

http://buildd.debian-ports.org/status/fetch.php?pkg=gcc-4.9&arch=sparc64&ver=4.9.1-17&stamp=1413678403

The very same issue is reproducible with 4.9.2-10 in a cross-build
setting:

https://jenkins.debian.net/job/rebootstrap_sparc64_gcc49/105/console

You can find the relevant excerpt from the native build at the end of
this mail.

Reporting during freeze without any expectation of having this fixed
before the jessie release.

Helmut

| dh_makeshlibs -plib32stdc++6 
| objdump: 
debian/lib32stdc++6/usr/share/gdb/auto-load/usr/lib32/libstdc++.so.6.0.20-gdb.py:
 File format not recognized
| dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
| dpkg-gensymbols: warning: debian/lib32stdc++6/DEBIAN/symbols doesn't match 
completely debian/lib32stdc++6.symbols.sparc64
| --- debian/lib32stdc++6.symbols.sparc64 (lib32stdc++6_4.9.1-17_sparc64)
| +++ dpkg-gensymbolsEGATZT 2014-10-19 00:24:57.244023375 +
| @@ -452,9 +452,9 @@
|   _ZNKSt14error_category10equivalentERKSt10error_codei@GLIBCXX_3.4.11 4.4.0
|   _ZNKSt14error_category10equivalentEiRKSt15error_condition@GLIBCXX_3.4.11 
4.4.0
|   _ZNKSt14error_category23default_error_conditionEi@GLIBCXX_3.4.11 4.4.0
| - _ZNKSt15__exception_ptr13exception_ptr20__cxa_exception_typeEv@CXXABI_1.3.3 
4.4.0
| - _ZNKSt15__exception_ptr13exception_ptrcvMS0_FvvEEv@CXXABI_1.3.3 4.4.0
| - _ZNKSt15__exception_ptr13exception_ptrntEv@CXXABI_1.3.3 4.4.0
| +#MISSING: 4.9.1-17# 
_ZNKSt15__exception_ptr13exception_ptr20__cxa_exception_typeEv@CXXABI_1.3.3 
4.4.0
| +#MISSING: 4.9.1-17# 
_ZNKSt15__exception_ptr13exception_ptrcvMS0_FvvEEv@CXXABI_1.3.3 4.4.0
| +#MISSING: 4.9.1-17# _ZNKSt15__exception_ptr13exception_ptrntEv@CXXABI_1.3.3 
4.4.0
|   _ZNKSt15basic_streambufIcSt11char_traitsIcEE4gptrEv@GLIBCXX_3.4 4.1.1
|   _ZNKSt15basic_streambufIcSt11char_traitsIcEE4pptrEv@GLIBCXX_3.4 4.1.1
|   _ZNKSt15basic_streambufIcSt11char_traitsIcEE5ebackEv@GLIBCXX_3.4 4.1.1
| @@ -1570,17 +1570,17 @@
|   _ZNSt12system_errorD0Ev@GLIBCXX_3.4.11 4.4.0
|   _ZNSt12system_errorD1Ev@GLIBCXX_3.4.11 4.4.0
|   _ZNSt12system_errorD2Ev@GLIBCXX_3.4.11 4.4.0
| - _ZNSt13__future_base11_State_baseD0Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base11_State_baseD1Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base11_State_baseD2Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base12_Result_baseC1Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base12_Result_baseC2Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base12_Result_baseD0Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base12_Result_baseD1Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base12_Result_baseD2Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base19_Async_state_commonD0Ev@GLIBCXX_3.4.17 4.7.0~rc1
| - _ZNSt13__future_base19_Async_state_commonD1Ev@GLIBCXX_3.4.17 4.7.0~rc1
| - _ZNSt13__future_base19_Async_state_commonD2Ev@GLIBCXX_3.4.17 4.7.0~rc1
| +#MISSING: 4.9.1-17# _ZNSt13__future_base11_State_baseD0Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base11_State_baseD1Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base11_State_baseD2Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base12_Result_baseC1Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base12_Result_baseC2Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base12_Result_baseD0Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base12_Result_baseD1Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base12_Result_baseD2Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# 
_ZNSt13__future_base19_Async_state_commonD0Ev@GLIBCXX_3.4.17 4.7.0~rc1
| +#MISSING: 4.9.1-17# 
_ZNSt13__future_base19_Async_state_commonD1Ev@GLIBCXX_3.4.17 4.7.0~rc1
| +#MISSING: 4.9.1-17# 
_ZNSt13__future_base19_Async_state_commonD2Ev@GLIBCXX_3.4.17 4.7.0~rc1
|   _ZNSt13bad_exceptionD0Ev@GLIBCXX_3.4 4.1.1
|   _ZNSt13bad_exceptionD1Ev@GLIBCXX_3.4 4.1.1
|   _ZNSt13bad_exceptionD2Ev@GLIBCXX_3.4 4.1.1
| @@ -2009,7 +2009,7 @@
|   _ZNSt14numeric_limitsIeE10is_integerE@GLIBCXX_3.4 4.1.1
|   _ZNSt14numeric_limitsIeE11round_styleE@GLIBCXX_3.4 4.1.1
|   _ZNSt14numeric_limitsIeE12has_infinityE@GLIBCXX_3.4 4.1.1
| - (arch=!powerpc !ppc64 
!sparc)_ZNSt14numeric_limitsIeE12max_digits10E@GLIBCXX_3.4.14 4.5.0
| +#MISSING: 4.9.1-17# (arch=!powerpc !ppc64 
!sparc)_ZNSt14numeric_limitsIeE12max_digits10E@GLIBCXX_3.4.14 4.5.0
|   _ZNSt14numeric_limitsIeE12max_exponentE@GLIBCXX_3.4 4.1.1
|   _ZNSt14numeric_limitsIeE12min_exponentE@GLIBCXX_3.4 4.1.1
|   _ZNSt14numeric_limitsIeE13has_quiet_NaNE@GLIBCXX_3.4 4.1.1
| @@ -2317,18 +2317,18 @@
|   _ZNSt15_List_node_base7reverseEv@GLIBCXX_3.4 4.1.1
|   _ZNSt15_List_node_base8transferEPS_S0_@GLIBCXX_3.4 4.1.1
|   _ZNSt15_List_node_base9_M_unhookEv@GLIBCXX_3.4.14 4.5
| - _ZNSt15__exception_

Bug#777047: pu: vpim

[Adam D. Barratt]

Control: tags -1 + pending

On Wed, 2015-02-04 at 21:27 +0100, Daniel Pocock wrote:
> 
> On 04/02/15 20:32, Adam D. Barratt wrote:
> > Please go ahead.
> > 
> 
> dput complained that wheezy-proposed-updates wasn't a valid codename, it
> ran successfully when I changed this to stable-proposed-updates
> 
> Please let me know if this is correct or if there is any other action I
> need to take.

Flagged for acceptance.

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776884: wheezy-pu: clamav/0.98.6+dfsg-0+deb7u1

[Adam D. Barratt]

Control: tags -1 + pending

On Wed, 2015-02-04 at 21:37 +0100, Sebastian Andrzej Siewior wrote:
> On 2015-02-04 19:48:27 [+], Adam D. Barratt wrote:
> > Please go ahead.
> Done, thanks.

Flagged for acceptance, thanks.

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777046: wheezy-pu: package phpbb3/3.0.10-4+deb7u2

[Adam D. Barratt]

Control: tags -1 + pending

On Wed, 2015-02-04 at 17:24 -0400, David Prévot wrote:
> Hi,
> 
> Le 04/02/2015 15:34, Adam D. Barratt a écrit :
> 
> > Please go ahead, thanks.
> 
> Uploaded and accepted, thanks.

Flagged for acceptance.

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777168: sensible-utils: Infinite loop in select-editor when nano is not installed (batch-mode)

[Niels Thykier]

Package: sensible-utils
Version: 0.0.9
Severity: minor
File: /usr/bin/select-editor

Hi,

It is possible to trigger an infinite loop in select-editor by doing
the following steps.

 * Uninstall nano
 * Run select-editor which stdin being /dev/null (or closed)

Fortunately, sensible-editor checks that stdin is a tty before trying
to run select-editor, so I suspect this is mostly a theoratical issue.

The issue in a nutshell:

"""
editors=`update-alternatives --list editor`
for e in $editors; do
i=`expr $i + 1`
desc=
if [ $e = "/bin/nano" ]; then
desc="< ` gettext 'easiest'`"
 ** simple=$i
fi
echo "  $i. $e$desc"
done
[...]
 ** while /bin/true; do
 ** if [ -z "$selected" -a ! -z "$simple" ]; then
 ** selected="$simple"
[...]
else
break
fi
done
"""

With "simple" always being unset/empty *unless* update-alternative
mentions "/bin/nano".

Thanks,
~Niels


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777165: Looks similar to RHEL bug

[Rik Theys]

Hi,

This bug looks like a similar bug in the RHEL bugzilla:

https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1086058

Regards,

Rik

Bug#773952: Fwd: O: e2ps -- Convert plain text into PostScript

[Ana Guerrero Lopez]

On Thu, Feb 05, 2015 at 10:19:34AM +0100, Denis Briand wrote:
> 

> From: Denis Briand 
> To: cont...@bugs.debian.org, submit...@bugs.debian.org,
>  773...@bugs.debian.org
> Date: Thu, 5 Feb 2015 10:13:25 +0100
> Subject: O: e2ps -- Convert plain text into PostScript
> User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; )
> Message-Id: <201502051013.44192.deb...@denis-briand.fr>
> 
> owner 773952 !
> retitle 773952 ITA: e2ps -- Convert plain text into PostScript
> thanks 
> 
> I intend to adopt this little package.
> Is there any upstream web page or repository?
>

It seems to be abandoned by upstream, which means that adopting
this package in Debian, you will have to become upstream too.

Ana


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777167: www.debian.org: Vendor List, adding a new entry

[Alexandre Delanoe]

Package: www.debian.org
Severity: normal

Dear Maintainer,

We received a new entry on Sat, 2 Nov 2013 14:54:21 +0530
Message-ID was 


I have asked V Linux if they still wanted to be in the list. 

They confirmed but changed url (updated in the diff below):

Index: vendors.CD
===
RCS file: /cvs/webwml/webwml/english/CD/vendors/vendors.CD,v
retrieving revision 1.600
diff -u -r1.600 vendors.CD
--- vendors.CD  24 Dec 2014 20:46:41 -  1.600
+++ vendors.CD  5 Feb 2015 20:40:01 -
@@ -690,6 +690,17 @@
 #ship="no"
 #dvd="yes"
 #architectures="amd64, i386"/>
+http://vlinux.asia/";
+   deburl="http://vlinux.asia/os/debian";
+   contacturl="mailto:vli...@gmail.com";
+   country="in"
+   contribution="yes"
+   ship="yes"
+   cd="no"
+   dvd="yes"
+   architectures="amd64 i386"/>
+
 http://www.zyxware.com";
 
deburl="http://www.zyxware.com/requestcd/%252Fresults/field_distribution_name%3A%22Debian%22";
@@ -700,8 +711,10 @@
 cd="yes"
 dvd="yes"
 architectures="i386" />
+
 
 
+
 
 http://linuxshop.ir";


Many thankd for taking into account this new entry.

Kind regards,
Alexandre (anoe)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#738668: RFP: whatsapp-purple -- WhatsApp protocol plugin for libpurple

[Graham Inggs]

retitle 738668 ITP: RFP: whatsapp-purple -- WhatsApp protocol plugin
for libpurple
owner 738668 !
thanks

Hi David

I think it would be good to have this in Debian.
I'll work on packaging this, although you have done most of the work already!

Regards
Graham


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776778: Please play nicely with resolvconf

[Thomas Hood]

On 5 February 2015 at 16:35, Axel Beckert  wrote:
> Ondřej Surý wrote:
>> There's already a unblock bug filled as well.

Great!


>> Then we need to come up with solution that doesn't break resolvconf when
>> installing it after dnssec-trigger is already installed.
>
> Just an idea, but what about resolvconf checking in its postinst if
> dnssec-triggerd is available and if so restarting it first? Then
> dnssec-triggerd would notice that resolvconf is installed (as
> /sbin/resolvconf already exists) and talks to resolvconf instead
> making /etc/resolv.conf immutable again.


Well, first, if resolvconf is installed then dnssec-trigger should
refrain from any further futzing with /etc/resolv.conf. Thus any code
in the dnssec-trigger package that futzes with /etc/resolv.conf should
be bracketed with the equivalent of "if ! [ -x /sbin/resolvconf ] ;
then futz ; fi". It shouldn't be necessary to restart dnssec-trigger
for it to behave according to the newfound presence of resolvconf.

Second, it might be simpler just for resolvconf to detect that
dnssec-triggerd is running and, in that case, to override the
immutability attribute when installing the symlink at
/etc/resolv.conf.

So when dnssec-trigger has been installed and resolvconf is
subsequently installed, (1) /sbin/resolvconf appears on the
filessystem causing dnssec-trigger to refrain from any further futzing
with /etc/resolv.conf; (2) resolvconf's postinst deimmutabilizes
/etc/resolv.conf and installs the symlink.

On installation, before the next reboot, resolvconf includes existing
nameserver information in its database, so the information about the
local "unbound" instance will not be lost. However, this information
may not be prioritized correctly. So (3) resolvconf should then cause
unbound to restart so that unbound notices resolvconf's presence and
registers its address with resolvconf. The way to do this is for the
unbound package to include a script
/usr/lib/resolvconf/dpkg-event.d/unbound which restarts unbound.
Resolvconf runs the script /usr/lib/resolvconf/dpkg-event.d/foo at
postinst time for each package foo (having such a script) that is
already installed at resolvconf preinst time. See dnsmasq for an
example of a package which has such a resolvconf packaging event hook
script.

I don't know dnssec-trigger very well. It it possible that it does
other things that conflict with what resolvconf does.
-- 
Thomas


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777166: Please consider not hard coding the name "Debian" into error messages

[Phillip Susi]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: partman-efi
Version: 59

Recently a new message was added to d-i:

 This machine's firmware has started the installer in UEFI mode but
 it looks like there may be existing operating systems already
 installed using "BIOS compatibility mode". If you
 continue to install Debian in UEFI mode, it might be difficult to
 reboot the machine into any BIOS-mode operating systems later.

Please consider replacing "Debian" with `lsb_release -si` or similar
so that people installing other distros based on debian don't get a
message about a different operating system than the one they are
installing.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBAgAGBQJU09MKAAoJENRVrw2cjl5RvvMH/1WYchn0xt77ZRySIodqz9sx
VgDNmuXNbafhE6NATzOSnQxYwwprMHcS5HD8rfNoF6G9Zg//a6pGQa6BJ73C0Zn/
1oeb5fiOFTlcaJbpelDsx7cxH9aWWrSRN4HEiJIeR9u3FssJcJEU9r5Iuw7Kj+f/
uT8qNdibKnyKZziYeCgw06DGdtA6l64PgH4apjlCUcKr1q9x+zlP0HE1lASJxKas
gSfRjeDLtus4SFsAq3EhEZd/W9QfttFTG7aknsJgqmAoVZn2pq+ceogD9CfTA121
8E3iACB7icTGOE7z+j13VRCkIh3Zmi2Xp+b92pj9BkXGnrXpFEOBfx1RZXr5tXI=
=zk48
-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#777165: linux-image-3.16.0-4-amd64: WARNING and guest crash when using nested virtualisation

[Rik Theys]

Package: src:linux
Version: 3.16.7-ckt4-3
Severity: normal

Hi,

I enabled nested virtualisation on the kvm_intel module and 
created a virtual machine (using virt-manager). The VM had the host cpu flags
copied so it also had the vmx cpu flag.

Inside this VM I configured another virtual machine (also using virt-manager).
As soon as the new VM (inside the first VM) is launched, the following WARNING 
is
reported on the host kernel and the first VM reboots.

[  187.013217] [ cut here ]
[  187.013242] WARNING: CPU: 1 PID: 2394 at 
/build/linux-y7bjb0/linux-3.16.7-ckt4/arch/x86/kvm/vmx.c:8699 
nested_vmx_vmexit+0x7f3/0x820 [kvm_intel]()
[  187.013245] Modules linked in: vhost_net vhost macvtap macvlan tun 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat 
ipt_REJECT bridge stp llc bnep bluetooth 6lowpan_iphc binfmt_misc 
cpufreq_userspace cpufreq_powersave cpufreq_conservative cpufreq_stats 
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter 
ip_tables x_tables snd_hda_codec_hdmi cx88_blackbird cx2341x cx22702 iTCO_wdt 
iTCO_vendor_support cx88_dvb cx88_vp3054_i2c videobuf_dvb arc4 dvb_core wm8775 
tuner_simple tuner_types tda9887 tda8290 coretemp tuner snd_hda_codec_via 
snd_hda_codec_generic rt61pci rt2x00pci rt2x00mmio rt2x00lib snd_hda_intel 
joydev evdev cx8802 snd_hda_controller snd_hda_codec eeprom_93cx6 snd_hwdep 
mac80211
[  187.013297]  cx8800 cx88_alsa snd_pcm cfg80211 cx88xx kvm_intel kvm 
snd_timer psmouse serio_raw nouveau btcx_risc tveeprom mxm_wmi wmi video 
videobuf_dma_sg videobuf_core rc_core rfkill i7core_edac ttm drm_kms_helper 
v4l2_common drm videodev snd edac_core i2c_i801 soundcore media i2c_algo_bit 
i2c_core shpchp lpc_ich mfd_core asus_atk0110 button acpi_cpufreq processor 
thermal_sys loop firewire_sbp2 fuse parport_pc ppdev lp parport autofs4 ext4 
crc16 mbcache jbd2 btrfs xor raid6_pq dm_mod raid1 raid0 md_mod sg sd_mod 
crc_t10dif crct10dif_generic sr_mod cdrom crct10dif_common hid_generic usbhid 
hid usb_storage crc32c_intel ahci libahci libata firewire_ohci xhci_hcd 
scsi_mod ehci_pci r8169 ehci_hcd firewire_core crc_itu_t mii usbcore usb_common
[  187.013374] CPU: 1 PID: 2394 Comm: qemu-system-x86 Not tainted 
3.16.0-4-amd64 #1 Debian 3.16.7-ckt4-3
[  187.013376] Hardware name: System manufacturer System Product Name/P7P55D-E, 
BIOS 150412/14/2010
[  187.013379]  0009 815096a7  
810676f7
[  187.013383]  8800a498f000 0014  

[  187.013387]   a083dec3  
a0734daf
[  187.013391] Call Trace:
[  187.013399]  [] ? dump_stack+0x41/0x51
[  187.013406]  [] ? warn_slowpath_common+0x77/0x90
[  187.013416]  [] ? nested_vmx_vmexit+0x7f3/0x820 [kvm_intel]
[  187.013435]  [] ? kvm_mmu_load+0x26f/0x400 [kvm]
[  187.013452]  [] ? kvm_arch_vcpu_ioctl_run+0xde5/0x1110 
[kvm]
[  187.013458]  [] ? futex_wake+0x6f/0x120
[  187.013471]  [] ? kvm_vcpu_ioctl+0x2f1/0x590 [kvm]
[  187.013477]  [] ? eventfd_ctx_read+0x58/0x1e0
[  187.013482]  [] ? wake_up_state+0x10/0x10
[  187.013487]  [] ? do_vfs_ioctl+0x2cf/0x4b0
[  187.013491]  [] ? eventfd_read+0x37/0x60
[  187.013506]  [] ? kvm_on_user_return+0x4c/0x80 [kvm]
[  187.013510]  [] ? SyS_ioctl+0x81/0xa0
[  187.013515]  [] ? int_signal+0x12/0x17
[  187.013520]  [] ? system_call_fast_compare_end+0x10/0x15
[  187.013523] ---[ end trace ae3922755979b8ad ]---

When I retry to create the VM inside the first VM, the first VM keeps on 
crashing but the WARNING is not repeated 
on the host kernel. But I assume this is by design.

Regards,

Rik

-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/vg_saturn-root ro 
init=/bin/systemd audit=1 quiet systemd.show_status=1

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[   12.610352] [TTM] Initializing DMA pool allocator
[   12.610362] nouveau  [ DRM] VRAM: 512 MiB
[   12.610366] nouveau  [ DRM] GART: 1048576 MiB
[   12.610369] nouveau  [ DRM] TMDS table version 2.0
[   12.610371] nouveau  [ DRM] DCB version 4.0
[   12.610372] nouveau  [ DRM] DCB outp 00: 02000300 
[   12.610374] nouveau  [ DRM] DCB outp 01: 01000302 00020030
[   12.610375] nouveau  [ DRM] DCB outp 02: 01011310 
[   12.610377] nouveau  [ DRM] DCB outp 03: 02032362 00020010
[   12.610378] nouveau  [ DRM] DCB conn 00: 1030
[   12.610379] nouveau  [ DRM] DCB conn 01: 0100
[   12.610381] nouveau  [ DRM] DCB conn 02: 2261
[   12.645691] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   12.645693] [drm] Driver supports precise vblank timestamp query.
[   12.684832] nouveau  [ DRM] M

Bug#733615: wiki.debian.org: DM Graph outdated (https://wiki.debian.org/DebianMaintainer)

[Jonathan Wiltshire]

Control: tag -1 confirmed

Hi,

On Mon, Dec 30, 2013 at 01:25:10PM +0100, Simon Kainz wrote:
> On > > https://wiki.debian.org/DebianMaintainer
> 
> the Debian Maintainers graph (red line on black bg) is supposedly based on the
> data from the link above, but the data is from 2007-10 til 2009-09.  So there
> seems to be no more new data or the tool gathering DM data/generating the 
> graph
> does not work anymore.

The source for that image is https://people.debian.org/~anibal/dm/dm.png

Cc'ing Anibal.


Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#773701: Acknowledgement (libreoffice: will not open files on a gvfs share)

[Bjoern Michaelsen]

On Thu, Feb 05, 2015 at 05:17:24PM +, Andrew Gallagher wrote:
> I found the solution here:
> 
> http://geekphreek.com/fix-libreoffice-4-2-not-opening-files-on-gvfs/
> 
> sed -i 's/X-GIO-NoFuse=true/#X-GIO-NoFuse=true/'
> /usr/share/applications/libreoffice-*

That is not a solution as:

 
http://cgit.freedesktop.org/libreoffice/core/commit/?id=f574e1defdb537bdd741edd2523563aa0b03be5a

was done for a good reason.

> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1253620

makes clear in the imported comments at:

 https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1253620/comments/62
 https://bugs.documentfoundation.org/show_bug.cgi?id=67527#c59 ff.

that to the best of our knowledge, people either:
- dont have libreoffice-gnome and friends installed, which you should if you 
use gvfs
- or they are suffering from a glib bug:
  https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1214352
  which is in a header file, thus would require a full rebuild of all rdepends
  of glib and so would be very hard to fix properly on a stable release.

Best, Bjoern


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777024: gmediarender segfaults on startup on armel, raspbian and possiblly other architectures if gstreamer1.0-plugins-bad is installed.

[peter green]

notfound 777024 1.4.3-2
found 777024 1.4.4-2
thanks

Sorry screwed up the version number


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776982: [Debconf-team] Bug#776982: Bug#776982: Request for summit.debconf.org pseudo-package

[Eric Dantan Rzewnicki]

On Thu, Feb 05, 2015 at 07:49:32PM +0100, Richard Hartmann wrote:
> On Thu, Feb 5, 2015 at 7:04 PM, Eric Dantan Rzewnicki  wrote:
> >> > I suggest debconf-sum...@lists.debian.org.
> >
> > Not a slightly broader debconf-infra@l.d.o ?
> 
> I pondered that as well. But what if bursaries, front desk, etc want
> to talk about summit specifically?

Then that's on -team? or those teams perhaps need a designated
infra-liason? I don't know.

> OTOH, what if we use something else
> in a few years?

You mean if the current re-org structure doesn't pan out? Then what
about debconf-devel@ ? Surely DebConf will never evolve beyond having
development needs.

> > Who should make the request? I'll do it if you want and the listmasters
> > accept new list requests from mere users.
> 
> It probably makes most sense if tumbleweed and/or me make the request.
> Or you do it and point to here once we know what we want/need. Either
> way is fine.

Ok. You seem to have a lot on your plate, and are some kind of manager
or something, so I'll take it on.

-edrz


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#774133: debian-maintainers: Trouble replacing short key for Thomas Friedrichsmeier

[Jonathan Wiltshire (Front Desk)]

I just noticed you asked on a public bug. I suggest following up to front
desk directly instead: n...@debian.org.

Thanks,


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#774133: debian-maintainers: Trouble replacing short key for Thomas Friedrichsmeier

[Jonathan Wiltshire (Front Desk)]

Hi Thomas,

On Mon, Dec 29, 2014 at 10:41:51AM +0100, Thomas Friedrichsmeier wrote:
> Apologies if this is not the right place to bring this request. But my
> current key (as a DM) is about to be removed from the keyring for being
> too short (1024 bits), and I am having trouble meeting the formal
> requirements for my replacement key.

Where exactly are you located? And I presume the answer is no, but are you
expecting to travel anywhere in the coming months?

Thanks,

For front desk:
-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#772691: Disc icon not displayed

[jnqnfe]

Control: retitle -1 autorun.inf improvements
thanks

Updated patch, rebased on latest changes in git
commit 1f1ad6a6aba20a0fc0938198c0a24fb85e7c6cc8
Author: jnqnfe 
Date:   Wed Dec 10 05:24:53 2014 +

Improve autorun.inf

diff --git a/tools/boot/jessie/boot-hurd b/tools/boot/jessie/boot-hurd
index 884b374..bfbff40 100644
--- a/tools/boot/jessie/boot-hurd
+++ b/tools/boot/jessie/boot-hurd
@@ -85,6 +85,7 @@ if [ -f $CDDIR/README.html ]; then
todos > $CDDIR/autorun.inf < $CDDIR/autorun.bat < $CDDIR/autorun.inf < $CDDIR/autorun.bat < $CDDIR/autorun.inf < $CDDIR/autorun.inf < $CDDIR/autorun.bat < $CDDIR/autorun.inf < $CDDIR/autorun.bat < $CDDIR/autorun.inf < $CDDIR/autorun.bat < $CDDIR/autorun.inf < $CDDIR/autorun.inf < $CDDIR/autorun.bat <

Bug#777163: unblock: gnome-control-center/1:3.14.2-3

[Andreas Henriksson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package gnome-control-center

The new package revision reverts the changes in previous package
revision to fix #774257.

Having system-config-printer installed is still needed to be able
to add new printers. For the details please see:
https://git.gnome.org/browse/gnome-control-center/tree/panels/printers/pp-new-printer.c?h=gnome-3-14#n643

unblock gnome-control-center/1:3.14.2-3

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Index: debian/changelog
===
--- debian/changelog	(revision 44087)
+++ debian/changelog	(working copy)
@@ -1,3 +1,10 @@
+gnome-control-center (1:3.14.2-3) unstable; urgency=medium
+
+  * Re-add system-config-printer recommendation. (Closes: #774257)
+- it's still needed to be able to add new printers.
+
+ -- Andreas Henriksson   Thu, 05 Feb 2015 19:44:41 +0100
+
 gnome-control-center (1:3.14.2-2) unstable; urgency=medium
 
   * Remove system-config-printer recommendation.
Index: debian/control
===
--- debian/control	(revision 44087)
+++ debian/control	(working copy)
@@ -90,6 +90,7 @@
 mousetweaks,
 policykit-1-gnome,
 rygel | rygel-tracker,
+system-config-printer (>= 1.4),
 network-manager-gnome (>= 0.9.8),
 libnss-myhostname,
 cracklib-runtime,
Index: debian/control.in
===
--- debian/control.in	(revision 44087)
+++ debian/control.in	(working copy)
@@ -86,6 +86,7 @@
 mousetweaks,
 policykit-1-gnome,
 rygel | rygel-tracker,
+system-config-printer (>= 1.4),
 network-manager-gnome (>= 0.9.8),
 libnss-myhostname,
 cracklib-runtime,

Bug#776982: [Debconf-team] Bug#776982: Bug#776982: Request for summit.debconf.org pseudo-package

[Richard Hartmann]

On Thu, Feb 5, 2015 at 7:04 PM, Eric Dantan Rzewnicki  wrote:
>> > I suggest debconf-sum...@lists.debian.org.
>
> Not a slightly broader debconf-infra@l.d.o ?

I pondered that as well. But what if bursaries, front desk, etc want
to talk about summit specifically? OTOH, what if we use something else
in a few years?


> Who should make the request? I'll do it if you want and the listmasters
> accept new list requests from mere users.

It probably makes most sense if tumbleweed and/or me make the request.
Or you do it and point to here once we know what we want/need. Either
way is fine.


Richard


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#698982: libdumbnet RC bug fix? + Fwd: libnet-{libdnet6,frame-device,libdnet}-perl are marked for autoremoval from testing [origin: nore...@release.debian.org]

[Bernd Zeimetz]

hi,

>> Ah, right, thanks for the eye-opener. Oof, yeah, I should've
>> wondered why the BTS still lists the bug as open :( OK, I'll get
>> right on it.

I have a fix ready to upload, if you want me to.
Patch is attached, in case you want to upload.

cheers,

bernd


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F
diff -u libdumbnet-1.12/debian/changelog libdumbnet-1.12/debian/changelog
--- libdumbnet-1.12/debian/changelog
+++ libdumbnet-1.12/debian/changelog
@@ -1,3 +1,11 @@
+libdumbnet (1.12-6) unstable; urgency=medium
+
+  * QA upload.
+  * Make people who test upgrades from testing to unstable
+happy (Closes: #775896).
+
+ -- Bernd Zeimetz   Thu, 05 Feb 2015 19:06:08 +0100
+
 libdumbnet (1.12-5) unstable; urgency=medium
 
   * QA upload.
diff -u libdumbnet-1.12/debian/control libdumbnet-1.12/debian/control
--- libdumbnet-1.12/debian/control
+++ libdumbnet-1.12/debian/control
@@ -26,6 +26,7 @@
 Package: libdumbnet-dev
 Section: libdevel
 Depends: ${shlibs:Depends}, libdumbnet1 (= ${binary:Version})
+Pre-Depends: dpkg (>= 1.17.14)
 Architecture: any
 Description: A dumb, portable networking library -- development files
  libdumbnet provides a simplified, portable interface to several low-level
reverted:
--- libdumbnet-1.12/debian/preinst
+++ libdumbnet-1.12.orig/debian/preinst
@@ -1,21 +0,0 @@
-#!/bin/sh
-set -e
-
-case "$1" in
-install|upgrade)
-# dpkg does not replace directories by symlinks or vice versa.
-if [ -L /usr/share/doc/libdumbnet-dev ]; then
-rm -f /usr/share/doc/libdumbnet-dev
-fi
-;;
-abort-upgrade)
-;;
-*)
-echo "preinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-#DEBHELPER#
-
-exit 0
only in patch2:
unchanged:
--- libdumbnet-1.12.orig/debian/libdumbnet-dev.postinst
+++ libdumbnet-1.12/debian/libdumbnet-dev.postinst
@@ -0,0 +1,8 @@
+#!/bin/sh
+set -e
+
+dpkg-maintscript-helper symlink_to_dir /usr/share/doc/libdumbnet-dev 
/usr/share/doc/libdumbnet1 '1.12-6~' libdumbnet-dev  -- $@
+
+#DEBHELPER#
+
+exit 0
only in patch2:
unchanged:
--- libdumbnet-1.12.orig/debian/libdumbnet-dev.postrm
+++ libdumbnet-1.12/debian/libdumbnet-dev.postrm
@@ -0,0 +1,8 @@
+#!/bin/sh
+set -e
+
+dpkg-maintscript-helper symlink_to_dir /usr/share/doc/libdumbnet-dev 
/usr/share/doc/libdumbnet1 '1.12-6~' libdumbnet-dev -- $@
+
+#DEBHELPER#
+
+exit 0
only in patch2:
unchanged:
--- libdumbnet-1.12.orig/debian/libdumbnet-dev.preinst
+++ libdumbnet-1.12/debian/libdumbnet-dev.preinst
@@ -0,0 +1,8 @@
+#!/bin/sh
+set -e
+
+dpkg-maintscript-helper symlink_to_dir /usr/share/doc/libdumbnet-dev 
/usr/share/doc/libdumbnet1 '1.12-6~' libdumbnet-dev  -- $@
+
+#DEBHELPER#
+
+exit 0

Bug#777146: RFS: fiona/1.5.0-1 [ITP]

[Sebastiaan Couwenberg]

On 02/05/2015 06:39 PM, Sebastiaan Couwenberg wrote:
> [...] I'll leave it at this.

Famous last words. There is just one more thing.

The doc-base control file has an unusual suffix:
.docbase instead of .doc-base.

It also uses an unusual Document ID: fiona.docbase, using the (source)
package name is more common for Document IDs.

The doc-base control file references the HTML documentation included in
the fiona-doc package, but the control file is used for the fiona package.

For references see:

https://www.debian.org/doc/manuals/maint-guide/dother.en.html#doc-base
http://manpages.debian.org/cgi-bin/man.cgi?query=dh_installdocs

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/E88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#774889: removed packages not even part stable.... who's the maintainer?!

[Andreas Henriksson]

Hello Andreas Beckmann!

Thanks for your bug report(s) and testing.

For the case in #774889 I don't think the changes you suggest
are useful at all. The gdm package has been removed from Debian and is
not part of *stable*. If you intentionally keep it around anyway then in
my point of view you are the maintainer of it and you need to make sure
that it does not conflict with an official debian package. Requiring
that debians official gdm3 package to *for all eternity* carry conflict
avoidance is in my point of view not a realistic and useful requirement.
The upgrade path from oldstable->stable did work. The solution is to
uninstall packages you no longer want to have installed since they are
not supported after removal from the archive.

I'd argue that the severity of this bug report should be adjusted to
wishlist, if not simply closed because no real users where harmed by
this. (Can I reassign bugs to removed packages and then close them
based on the package being removed? ;P)

I'd like to hear your point of view on why this should be considered
a release critical bug.

Regards,
Andreas Henriksson


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776982: [Debconf-team] Bug#776982: Bug#776982: Request for summit.debconf.org pseudo-package

[Eric Dantan Rzewnicki]

On Thu, Feb 05, 2015 at 11:01:09AM +0100, Richard Hartmann wrote:
> On Thu, Feb 5, 2015 at 10:42 AM, Gaudenz Steinlin  wrote:
> > I think the best would be to create a new list for this on
> > lists.debian.org. We want to move all the debconf lists to the Debian
> > list infrastructure anyway.
> Yes.
> 
> > I suggest debconf-sum...@lists.debian.org.

Not a slightly broader debconf-infra@l.d.o ?
 
> Fine by me.
> 
> I would prefer not to need a new ML, but it seems as if we need one, so...

Who should make the request? I'll do it if you want and the listmasters
accept new list requests from mere users.

-edrz


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777158: libimage-magick-perl: QueryFontMetrics segfaults on i386

[Matthias Großmann]

Package: libimage-magick-perl
Version: 8:6.8.9.9-5
Severity: normal

Dear Maintainer,

the attached Perl program segfaults while calling QueryFontMetrics.
I tested this on two different Jessie i386 systems. The progam 
works fine on Jessie armel.


-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libimage-magick-perl depends on:
ii  libimage-magick-q16-perl  8:6.8.9.9-5
ii  perl  5.20.1-5

libimage-magick-perl recommends no packages.

Versions of packages libimage-magick-perl suggests:
pn  imagemagick-doc  

-- no debconf information

*** TestQueryFontMetrics.pl
#!/usr/bin/perl

use Image::Magick;

$image = Image::Magick->new(size=>"720x576", depth=>8);
$image->Read('canvas:blue');
$image->QueryFontMetrics(text=>'Test', font=>'Liberation-Sans', pointsize=>12);

*** TestQueryFontMetrics.backtrace
(gdb) r
Starting program: /usr/bin/perl TestQueryFontMetrics.pl
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
__GI___libc_realloc (oldmem=0x1, bytes=4096) at malloc.c:2977
2977malloc.c: No such file or directory.
(gdb) bt
#0  __GI___libc_realloc (oldmem=0x1, bytes=4096) at malloc.c:2977
#1  0xb7b3c320 in ResizeMagickMemory (memory=0x1, size=4096) at 
../../magick/memory.c:1140
#2  0xb7b3c396 in ResizeQuantumMemory (memory=0x1, count=4096, quantum=1) at 
../../magick/memory.c:1205
#3  0xb7bc6c8e in CloneString (destination=0x823c80c, source=0xb7d4ef1f "") at 
../../magick/string.c:287
#4  0xb7d2b692 in XS_Image__Magick__Q16_QueryFontMetrics (my_perl=0x8214008, 
cv=0xfff9) at Q16.xs:12322
#5  0x080f1554 in Perl_pp_entersub ()
#6  0x080ea237 in Perl_runops_standard ()
#7  0x0807f61a in perl_run ()
#8  0x0805ee4a in main ()
(gdb) q


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#768978: marked as done (apt-show-versions: No longer displays installed packages with "No available version in archive")

[Bob Proulx]

Christoph Martin wrote:
> I don't know if we can get it into testing. You could try to advocate it.

For the purposes of this bug issue this does not need to go into
Testing.  This bug was introduced after Testing was frozen.  Testing
has version 0.20 and this bug seems to have been introduced in 0.22.6
timeframe.  (I didn't search to the exact version but that was the
original report by Carlos.)  The problem was always in Sid as far as I
know.  Just a normal Sid bug and bug fix in Sid as far as I can see.
When I test Testing it appears to work correctly there for me.

So no need to advocate it for Testing.  All is good! :-)

Bob


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org