Bug#1051206: auto-apt-proxy: Optional support for mDNS

[James Tocknell]

I've created a merge request for this at
https://salsa.debian.org/debian/auto-apt-proxy/-/merge_requests/7.

On Tue, 5 Sept 2023 at 02:42, Antonio Terceiro  wrote:
>
> On Mon, Sep 04, 2023 at 11:42:35PM +1000, James Tocknell wrote:
> > Package: auto-apt-proxy
> > Severity: wishlist
> >
> > Dear Maintainer,
> >
> > Would you be open to adding optional support (i.e. at the suggests level) 
> > for
> > mDNS via avahi-browse (or similar mDNS scanning command)? I'd be happy to
> > produce a patch if interested.
>
> Sure.

Bug#1051206: auto-apt-proxy: Optional support for mDNS

[James Tocknell]

Package: auto-apt-proxy
Severity: wishlist

Dear Maintainer,

Would you be open to adding optional support (i.e. at the suggests level) for
mDNS via avahi-browse (or similar mDNS scanning command)? I'd be happy to
produce a patch if interested.

Regards,
James

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

Kernel: Linux 6.4.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages auto-apt-proxy depends on:
ii  apt  2.7.3

Versions of packages auto-apt-proxy recommends:
ii  busybox   1:1.36.1-3.1
ii  iproute2  6.4.0-1

auto-apt-proxy suggests no packages.

Bug#1031425: git-annex-remote-rclone: Update to latest 0.7 release

[James Tocknell]

Package: git-annex-remote-rclone
Version: 0.6-1
Severity: wishlist

Hi, it appears there's a new 0.7 release with a bunch of bug fixes, could it be
included before the freeze?

Thanks!

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

Kernel: Linux 6.1.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git-annex-remote-rclone depends on:
ii  git-annex  10.20230126-1
ii  rclone 1.60.1+dfsg-2+b1

git-annex-remote-rclone recommends no packages.

git-annex-remote-rclone suggests no packages.

-- no debconf information

Bug#1009067: Appears to be fixed upstream

[James Tocknell]

https://github.com/mvo5/squid-deb-proxy/blob/main/apt-avahi-discover
has been converted to use asyncio.

Bug#1000681: linux-image-5.15.0-1-amd64: 5.15 upgrade causes all apps to flicker

[James Tocknell]

Package: src:linux
Version: 5.15.3-1
Severity: important

Dear Maintainer,

Upgrading from 5.14 to 5.15 causes all apps to flicker/have rendering artefacts.
Examples include:
 * black squares appearing and disappearing within firefox
 * menus flickering in and out of existence in 0ad

These effects disappear when downgrading back to 5.14. The 5.16 rc also has
flickering.

I've checked that the recent mesa changes (21.2.5-1 -> 21.2.6-1) do not have any
effect on whether the flickering occurs or not, it does seem localised to the
5.14 -> 5.15 changes.

-- Package-specific info:
** Version:
Linux version 5.15.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.2.0-12) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 
5.15.3-1 (2021-11-18)

** Command line:
BOOT_IMAGE=/vmlinuz-5.15.0-1-amd64 root=/dev/mapper/callisto--vg-root ro quiet

** Not tainted

** Kernel log:
[   14.285552] ACPI: button: Sleep Button [SLPB]
[   14.285582] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
[   14.285597] ACPI: button: Power Button [PWRB]
[   14.285624] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[   14.288082] resource sanity check: requesting [mem 0xfdffe800-0xfe0007ff], 
which spans more than pnp 00:06 [mem 0xfdb0-0xfdff]
[   14.288086] caller pmc_core_probe+0xaa/0x670 [intel_pmc_core] mapping 
multiple BARs
[   14.288099] intel_pmc_core INT33A1:00:  initialized
[   14.302348] ACPI: button: Power Button [PWRF]
[   14.350801] input: PC Speaker as /devices/platform/pcspkr/input/input5
[   14.350802] EDAC ie31200: No ECC support
[   14.351041] EDAC ie31200: No ECC support
[   14.371146] pstore: Using crash dump compression: deflate
[   14.371152] pstore: Registered efi as persistent store backend
[   14.376560] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   14.376614] sd 2:0:0:0: Attached scsi generic sg1 type 0
[   14.377001] sd 5:0:0:0: Attached scsi generic sg2 type 0
[   14.378864] mei_me :00:16.0: enabling device ( -> 0002)
[   14.379845] alx :06:00.0 enp6s0: NIC Up: 1 Gbps Full
[   14.380049] ee1004 0-0051: 512 byte EE1004-compliant SPD EEPROM, read-only
[   14.380077] ee1004 0-0053: 512 byte EE1004-compliant SPD EEPROM, read-only
[   14.380199] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
[   14.380526] iTCO_vendor_support: vendor-support=0
[   14.384590] iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device (Version=4, 
TCOBASE=0x0400)
[   14.384705] iTCO_wdt iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   14.510080] RAPL PMU: API unit is 2^-32 Joules, 2 fixed counters, 655360 ms 
ovfl timer
[   14.510086] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[   14.510089] RAPL PMU: hw unit of domain package 2^-14 Joules
[   14.518766] cryptd: max_cpu_qlen set to 1000
[   14.528637] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
[   14.529337] snd_hda_intel :01:00.1: Disabling MSI
[   14.529347] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[   14.69] AVX2 version of gcm_enc/dec engaged.
[   14.633548] AES CTR mode by8 optimization enabled
[   14.644850] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input6
[   14.644996] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input7
[   14.645160] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input8
[   14.645264] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input9
[   14.645393] input: HDA NVidia HDMI/DP,pcm=10 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10
[   14.672634] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC1220: 
line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
[   14.672646] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   14.672652] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x1b/0x0/0x0/0x0/0x0)
[   14.672656] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   14.672659] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[   14.672662] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   14.672665] snd_hda_codec_realtek hdaudioC0D0:  Front Mic=0x19
[   14.672668] snd_hda_codec_realtek hdaudioC0D0:  Rear Mic=0x18
[   14.672671] snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a
[   14.688580] input: HDA Intel PCH Front Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input11
[   14.688716] input: HDA Intel PCH Rear Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input12
[   14.688823] input: HDA Intel PCH Line as 
/devices/pci:00/:00:1f.3/sound/card0/input13
[   14.688932] input: HDA Intel PCH Line Out Front as 
/devices/pci:00/:00:1f.3/sound/card0/input14
[   14.689028] input: HDA Intel PCH Line Out Surround as 
/devices/pci:00/:00:1f.3/sound/card0/input15
[   14.689122] input: HDA Intel PCH Line Out CLFE 

Bug#953974: ITP: mkcert -- A simple zero-config tool to make locally trusted development certificates with any names you'd like.

[James Tocknell]

Hi Aloïs

Sorry, I haven't looked at this in ages, my need for this disappeared
soon after I started looking at packaging (this should probably be
moved to RFP).
>From what I recall, there was only one dependency that needed to be
packaged, but there was some odd name-mangling going on, and not being
that familiar with packaging go libs, I stopped at that point. If you
want to package it, go ahead.

Regards
James

On Sun, 7 Nov 2021 at 21:25, Aloïs Micard  wrote:
>
> Hello there!
>
> I'm greatly interested about mkcert packaging, have you done any progress?
> Do you need sponsoring?
>
> Cheers,
>
> On Sun, 15 Mar 2020 19:29:57 +1100 James Tocknell  wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: James Tocknell 
> >
> > * Package name: mkcert
> >   Version : 1.4.1-1
> >   Upstream Author : Filippo Valsorda
> > * URL : https://github.com/FiloSottile/mkcert
> > * License : BSD-3-clause
> >   Programming Lang: Go
> >   Description : A simple zero-config tool to make locally trusted
> > development certificates with any names you'd like.
> >
> >  mkcert mkcert is a simple tool for making locally-trusted development
> >  certificates. It requires no configuration.
> >  .
> >  ``` $ mkcert -install Created a new local CA at
> >  "/Users/filippo/Library/Application Support/mkcert"  The local CA
> >  is now installed in the system trust store! ⚡️ The local CA is now
> >  installed in the Firefox trust store (requires browser restart)! 力
> >  .
> >  $ mkcert example.com "*.example.com" example.test localhost 127.0.0.1 ::1
> >  Using the local CA at "/Users/filippo/Library/Application Support/mkcert"
> >  ✨
> >  .
> >  Created a new certificate valid for the following names 
> >   - "example.com" - "*.example.com" - "example.test" - "localhost" -
> >   "127.0.0.1" - "::1"
> >  .
> >  The certificate is at "./example.com+5.pem"
> >  and the key at "./example.com+5-key.pem" ✅ ```  >  align="center"> >  src="
> > https://user-images.githubusercontent.com/1225294/51066373-96d4aa80-15be-11e9-91e2-f4e44a3a4458.png
> > ">
> >  Using certificates from real certificate authorities (CAs) for development
> >  can be dangerous or impossible (for hosts like example.test, localhost
> >  or 127.0.0.1), but self-signed certificates cause trust errors. Managing
> >  your own CA is the best solution, but usually involves arcane commands,
> >  specialized knowledge and manual steps.
> >  .
> >  mkcert automatically creates and installs a local CA in the system
> >  root store, and generates locally-trusted certificates. mkcert does
> >  not automatically configure servers to use the certificates, though,
> >  that's up to you.  Installation Warning: the rootCA-key.pem file that
> >  mkcert automatically generates gives complete power to intercept secure
> >  requests from your machine. Do not share it.  macOS On macOS, use Homebrew
> >  (https://brew.sh/)
> >  .
> >  .
> >  brew install mkcert brew install nss # if you use Firefox
> >  .
> >  .
> >  or MacPorts (https://www.macports.org/).
> >  .
> >  .
> >  sudo port selfupdate sudo port install mkcert sudo port install nss #
> >  if you use Firefox
> >  .
> >  Linux On Linux, first install certutil.
>
> --
> Aloïs Micard 
>
> GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2
>


-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.).
It isn't good enough for Tim Berners-Lee, and it isn't good enough for
me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In
practice, there is.

Bug#892275: Working redshift setup

[James Tocknell]

I have redshift working on both my desktop and laptop, here's how I
have things set up:
* If you don't have "normal" desktop environment like GNOME, then you
need to start the geoclue agent manually (note that the path to it
recently changed, which may be way people have having problems again
recently). Make sure you're running the latest geoclue, as there was
an issue for systems without wifi.
* Ensure redshift and the agent are allowed to access geoclue in
/etc/geoclue/geoclue.conf (again, this is for people who aren't
running GNOME, which includes me).
* I have disabled the user service, mostly because I start things
manually. That may help if people find that redshift keeps restarting
(check your user journal also).
* I don't have a xdg-autostart service running, so I'm not affected by
redshift adding itself there automatically. Not sure if others are
being affected by this though.

I don't think this is grave, important at best, for redshift (I'd say
this is due to geoclue changes, so the bug should be assigned there).
It might be worth seeing though if some kind of autopackagetest could
be added so regressions due to geoclue changes get flagged though.

James

-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.).
It isn't good enough for Tim Berners-Lee, and it isn't good enough for
me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In
practice, there is.

Bug#960342: Bug#975282: RFP: obs-v4l2sink -- OBS Studio plugin providing output capabilities to a Video4Linux2 device

[James Tocknell]

It looks like the latest release
(https://github.com/obsproject/obs-studio/releases/tag/26.1.0) has
this included.

Bug#970419: lilyterm: No longer starts (likely related to VTE changes)

[James Tocknell]

Package: lilyterm
Version: 0.9.9.4+git20150208.f600c0-5
Severity: grave
Justification: renders package unusable

It appears that lilyterm is unable to start, running lilyterm gives the
following errors:

** Message: 11:20:26.198: Can NOT connect to a existing lilyterm socket!

(lilyterm:4801): Gtk-WARNING **: 11:20:26.267: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.267: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.267: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.267: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): VTE-CRITICAL **: 11:20:26.268: gboolean 
vte_terminal_spawn_sync(VteTerminal*, VtePtyFlags, const char*, char**, char**, 
GSpawnFlags, GSpawnChildSetupFunc, gpointer, GPid*, GCancellable*, GError**): 
assertion 'envv == nullptr ||_vte_pty_check_envv(envv)' failed

(lilyterm:4801): Gtk-WARNING **: 11:20:26.268: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.268: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.268: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.268: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): VTE-CRITICAL **: 11:20:26.268: void 
vte_terminal_match_set_cursor_type(VteTerminal*, int, GdkCursorType): assertion 
'tag >= 0' failed

(lilyterm:4801): VTE-CRITICAL **: 11:20:26.268: void 
vte_terminal_match_set_cursor_type(VteTerminal*, int, GdkCursorType): assertion 
'tag >= 0' failed

(lilyterm:4801): VTE-CRITICAL **: 11:20:26.269: void 
vte_terminal_match_set_cursor_type(VteTerminal*, int, GdkCursorType): assertion 
'tag >= 0' failed

(lilyterm:4801): VTE-CRITICAL **: 11:20:26.269: void 
vte_terminal_match_set_cursor_type(VteTerminal*, int, GdkCursorType): assertion 
'tag >= 0' failed

and running lilyterm with -s gives:

(lilyterm:4807): Gtk-WARNING **: 11:20:57.451: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.451: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.452: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.452: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): VTE-CRITICAL **: 11:20:57.453: gboolean 
vte_terminal_spawn_sync(VteTerminal*, VtePtyFlags, const char*, char**, char**, 
GSpawnFlags, GSpawnChildSetupFunc, gpointer, GPid*, GCancellable*, GError**): 
assertion 'envv == nullptr ||_vte_pty_check_envv(envv)' failed

(lilyterm:4807): Gtk-WARNING **: 11:20:57.453: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.453: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.454: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.454: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): VTE-CRITICAL **: 11:20:57.454: void 
vte_terminal_match_set_cursor_type(VteTerminal*, int, GdkCursorType): assertion 
'tag >= 0' failed

(lilyterm:4807): VTE-CRITICAL **: 

Bug#953974: ITP: mkcert -- A simple zero-config tool to make locally trusted development certificates with any names you'd like.

[James Tocknell]

Package: wnpp
Severity: wishlist
Owner: James Tocknell 

* Package name: mkcert
  Version : 1.4.1-1
  Upstream Author : Filippo Valsorda
* URL : https://github.com/FiloSottile/mkcert
* License : BSD-3-clause
  Programming Lang: Go
  Description : A simple zero-config tool to make locally trusted
development certificates with any names you'd like.

 mkcert mkcert is a simple tool for making locally-trusted development
 certificates. It requires no configuration.
 .
 ``` $ mkcert -install Created a new local CA at
 "/Users/filippo/Library/Application Support/mkcert"  The local CA
 is now installed in the system trust store! ⚡️ The local CA is now
 installed in the Firefox trust store (requires browser restart)! 力
 .
 $ mkcert example.com "*.example.com" example.test localhost 127.0.0.1 ::1
 Using the local CA at "/Users/filippo/Library/Application Support/mkcert"
 ✨
 .
 Created a new certificate valid for the following names 
  - "example.com" - "*.example.com" - "example.test" - "localhost" -
  "127.0.0.1" - "::1"
 .
 The certificate is at "./example.com+5.pem"
 and the key at "./example.com+5-key.pem" ✅ ``` https://user-images.githubusercontent.com/1225294/51066373-96d4aa80-15be-11e9-91e2-f4e44a3a4458.png
">
 Using certificates from real certificate authorities (CAs) for development
 can be dangerous or impossible (for hosts like example.test, localhost
 or 127.0.0.1), but self-signed certificates cause trust errors. Managing
 your own CA is the best solution, but usually involves arcane commands,
 specialized knowledge and manual steps.
 .
 mkcert automatically creates and installs a local CA in the system
 root store, and generates locally-trusted certificates. mkcert does
 not automatically configure servers to use the certificates, though,
 that's up to you.  Installation Warning: the rootCA-key.pem file that
 mkcert automatically generates gives complete power to intercept secure
 requests from your machine. Do not share it.  macOS On macOS, use Homebrew
 (https://brew.sh/)
 .
 .
 brew install mkcert brew install nss # if you use Firefox
 .
 .
 or MacPorts (https://www.macports.org/).
 .
 .
 sudo port selfupdate sudo port install mkcert sudo port install nss #
 if you use Firefox
 .
 Linux On Linux, first install certutil.
 .
 .
 sudo apt install libnss3-tools
 -or-
 sudo yum install nss-tools
 -or-
 sudo pacman -S nss
 -or-
 sudo zypper install mozilla-nss-tools
 .
 .
 Then you can install using Linuxbrew (http://linuxbrew.sh/)
 .
 .
 brew install mkcert
 .
 .
 or build from source (requires Go 1.13+)
 .
 .
 git clone https://github.com/FiloSottile/mkcert && cd mkcert go build
 -ldflags "-X main.Version=$(git describe --tags)"
 .
 .
 or use the pre-built binaries
 (https://github.com/FiloSottile/mkcert/releases).
 .
 For Arch Linux users, mkcert
 (https://www.archlinux.org/packages/community/x86_64/mkcert/) is available
 on the official Arch Linux repository.
 .
 .
 sudo pacman -Syu mkcert
 .
 Windows On Windows, use Chocolatey (https://chocolatey.org)
 .
 .
 choco install mkcert
 .
 .
 or use Scoop
 .
 .
 scoop bucket add extras scoop install mkcert
 .
 .
 or build from source (requires Go 1.10+), or use the pre-built binaries
 (https://github.com/FiloSottile/mkcert/releases).
 .
 If you're running into permission problems try running mkcert as an
 Administrator.  Supported root stores mkcert supports the following root
 stores: • macOS system store• Windows system store• Linux variants
 that provide either • update-ca-trust (Fedora, RHEL, CentOS) or•
 update-ca-certificates (Ubuntu, Debian, OpenSUSE, SLES) or• trust
 (Arch)• Firefox (macOS and Linux only)• Chrome and Chromium•
 Java (when JAVA_HOME is set) To only install the local root CA into
 a subset of them, you can set the TRUST_STORES environment variable
 to a comma-separated list. Options are: "system", "java" and "nss"
 (includes Firefox).  Advanced topicsAdvanced options ```
 -cert-file FILE, -key-file FILE, -p12-file FILE
 Customize the output paths.
 -client
 Generate a certificate for client authentication.
 .
 -ecdsa
 Generate a certificate with an ECDSA key.
 .
 -pkcs12
 Generate a ".p12" PKCS #12 file, also know as a ".pfx" file,
 containing certificate and key for legacy applications.
 .
 -csr CSR
 Generate a certificate based on the supplied CSR. Conflicts with
 all other flags and arguments except -install and -cert-file.
 .
 ```
 .
 Note: You must place these options before the domain names list.  Example
 .
 mkcert -key-file key.pem -cert-file cert.pem example.com *.example.com
 .
 S/MIME mkcert automatically generates an S/MIME certificate if one of
 the supplied names is an email address.
 .
 .
 mkcert fili...@example.com
 .
 Mobile devices For the cert

Bug#953972: ITP: golang-software.sslmate-src-go-pkcs12 -- Go library for encoding and decoding PKCS#12 files

[James Tocknell]

Package: wnpp
Severity: wishlist
Owner: James Tocknell 

* Package name: golang-software.sslmate-src-go-pkcs12
  Version : 0.0~git20190322.6e380ad-1
  Upstream Author : SSLMate
* URL : https://github.com/SSLMate/go-pkcs12
* License : BSD-3-clause
  Programming Lang: Go
  Description : Go library for encoding and decoding PKCS#12 files

 package pkcs12 GoDoc
 (https://godoc.org/software.sslmate.com/src/go-pkcs12) import
 "software.sslmate.com/src/go-pkcs12"
 .
 Package pkcs12 implements some of PKCS#12 (also known as P12 or PFX).
 It is intended for decoding P12/PFX files for use with the crypto/tls
 package, and for encoding P12/PFX files for use by legacy applications
 which do not support newer formats.  Since PKCS#12 uses weak encryption
 primitives, it SHOULD NOT be used for new applications.
 .
 This package is forked from golang.org/x/crypto/pkcs12, which is frozen.
 The implementation is distilled from https://tools.ietf.org/html/rfc7292
 and referenced documents.
 .
 This repository holds supplementary Go cryptography libraries.
 Import Path Note that although the source code and issue tracker
 for this package are hosted on GitHub, the import path is:
 software.sslmate.com/src/go-pkcs12
 .
 Please be sure to use this path when you go get and import this package.
 Download/Install The easiest way to install is to run go get -u
 software.sslmate.com/src/go-pkcs12. You can also manually git clone
 the repository to $GOPATH/src/software.sslmate.com/src/go-pkcs12.
 Report Issues / Send Patches Open an issue or PR at
 https://github.com/SSLMate/go-pkcs12


This is needed for https://github.com/FiloSottile/mkcert

Bug#953964: ITP: python-strictyaml -- Strict, typed YAML parser for Python

[James Tocknell]

Package: wnpp
Severity: wishlist
Owner: James Tocknell 

* Package name: python-strictyaml
  Version : 1.0.6
  Upstream Author : Colm O'Connor 
* URL : https://hitchdev.com/strictyaml/
* License : MIT
  Programming Lang: Python
  Description : Strict, typed YAML parser for Python

StrictYAML is a type-safe YAML parser that parses and validates a restricted
subset of the YAML specification.

Priorities:
 - Beautiful API
 - Refusing to parse the ugly, hard to read and insecure features of YAML like
   the Norway problem.
 - Strict validation of markup and straightforward type casting.
 - Clear, readable exceptions with code snippets and line numbers.
 - Acting as a near-drop in replacement for pyyaml, ruamel.yaml or poyo.
 - Ability to read in YAML, make changes and write it out again with comments
   preserved.
 - Not speed, currently.

---

This is needed for devpi-server, and I plan on maintaining within DMPT (assuming
they accept me).

Bug#779006: Request to join DPMT and PAPT to package devpi

[James Tocknell]

Hi Python Team

Can I join both the DPMT and PAPT to help maintain devpi (and its
associated subprojects)?
I've read both the DPMT and PAPT policies and accept them.
My salsa login is aragilar-guest.

My plan for devpi is to update devpi-common to the latest release, then
work down the list of devpi projects.
I plan on putting the projects under PAPT (apart from devpi-common), unless
there are other suggestions?

James

P.S. I've CC'd in the current ITP bugs for devpi, there will probably be
more as I package further projects.

Bug#950574: sundials: Should ship pkgconfig files

[James Tocknell]

The pkg-config files were an additional thing added in the debian packaging
to make it easier to use sundials (upstream didn't distribute them as far
as I know). Presumably they were dropped in one of the transitions to a
newer version of sundials. The pkg-config modifications should still be in
the git history somewhere, but will probably take some work to update them.

James


On Tue, 4 Feb 2020 at 05:03, Andreas Kloeckner  wrote:

> Source: sundials
> Version: 4.1.0+dfsg-1+b2
> Severity: wishlist
>
> Dear Maintainer,
>
> From https://github.com/bmcage/odes I gather that sundials installs
> pkgconfig files, however those don't seem to be included in the -dev
> packages, which makes sundials harder than necessary to build.
>
> Thanks,
> Andreas
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
> 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.5.0-rc5 (SMP w/8 CPU cores)
> Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
> LANGUAGE=de_DE:de (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
>

-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It
isn't good enough for Tim Berners-Lee
<http://opendotdotdot.blogspot.com/2010/04/rms-and-tim-berners-lee-separated-at.html>,
and it isn't good enough for me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In practice,
there is.

Bug#950123: virtualenvwrapper: Autocomplete not loaded in default install

[James Tocknell]

Package: virtualenvwrapper
Version: 4.8.4-4
Severity: important

Hi virtualenvwrapper maintainers,

virtualenvwrapper doesn't seem to load from the autocomplete launcher in a clean
chroot (created via debootstrap). I've tried digging to why this is, but I'm not
familiar enough with bash's autocomplete to work out whether this is a
virtualenvwrapper bug or a bash-completion bug. My tests have been to add printf
lines to the autocomplete code, but these never appear to print (whether that's
because I've done something wrong, or something else, I'm not sure). Strangely,
this works fine in on my main system, it's in containers or chroots that seem to
be the problem.

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

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FORCED_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualenvwrapper depends on:
ii  python3-virtualenvwrapper  4.8.4-4
ii  virtualenv 15.1.0+ds-2

Versions of packages virtualenvwrapper recommends:
ii  bash-completion  1:2.10-1

Versions of packages virtualenvwrapper suggests:
pn  virtualenvwrapper-doc  

-- no debconf information

Bug#868293: misguesses veth name in stretch

[James Tocknell]

I'm also seeing the veth0 issue on my system, and as far as I know I'm not
doing anything particularly special. I also tried searching for where the
printf style formatting is supposed to be handled, but I couldn't find
anything.

Bug#896095: Current status

[James Tocknell]

Can I ask what the current status of devpi packaging is, is there something
blocking this, or could I look at updating the repos on salsa to the latest
release and try to get devpi into unstable?

James

Bug#944634: nmu: sundials_4.1.0+dfsg-1

[James Tocknell]

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

nmu sundials_4.1.0+dfsg-1 . ANY . experimental . -m "Rebuild against libhypre 
(=2.18.2) - see libhypre README.Debian for more details about the new ABI plan."

Hi Release Team

libsundials in experimental is currently uninstallable due to the packaging
change that the libhypre maintainers made in reaction to the less-than-ideal ABI
stability of upstream libhypre. Can libsundials be rebuilt against the new
libhypre (I think I did this correctly, but this is my first binNMU, so let me
know if I did anything wrong).

Thanks
James

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

Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FORCED_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#939299: virtualenvwrapper incorrectly dropped virtualenv dependency

[James Tocknell]

Package: virtualenvwrapper
Version: 4.8.4-3
Severity: grave
Justification: renders package unusable

It appears the new virtualenvwrapper update dropped the virtualenv requirement,
but it appears that virtualenv (the script) is still required, and depending on
the python module is insufficient. Could the requirement be added back?

Thanks for maintaining virtualenvwrapper

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualenvwrapper depends on:
ii  python3-virtualenvwrapper  4.8.4-3

Versions of packages virtualenvwrapper recommends:
ii  bash-completion  1:2.9-1

Versions of packages virtualenvwrapper suggests:
pn  virtualenvwrapper-doc  

-- no debconf information

Bug#933698: network-manager-gnome: nm-applet fails to detect NetworkManager, possible race condition?

[James Tocknell]

Package: network-manager-gnome
Version: 1.8.22-2
Severity: important

It appears that sometimes nm-applet doesn't find the NetworkManager daemon (or
dbus interface or something), and states "NetworkManager not running". Given I
can see that NetworkManager is running (via nmcli), and I'm connected to the
network, and that if I kill nm-applet and start it up again and it find
NetworkManager running, I'm guessing there's some sort of race condition between
when nm-applet checks for NetworkManager availability and NetworkManager
actually running (or starting the dbus interface or which ever). This is a new
problem (1.8.20 didn't have this problem or at least I never triggered it), I'm
not confident enough yet to call it a regression. Would it be possible to get
nm-applet to poll for NetworkManager's existence if it appear to be not running?

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages network-manager-gnome depends on:
ii  dbus-x11 [dbus-session-bus]  1.12.16-1
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  libatk1.0-0  2.32.0-2
ii  libayatana-appindicator3-1   0.5.3-4
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.60.6-1
ii  libgtk-3-0   3.24.10-1
ii  libjansson4  2.12-1
ii  libmm-glib0  1.10.0-1
ii  libnm0   1.19.90-2
ii  libnma0  1.8.22-2
ii  libnotify4   0.7.7-4
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libsecret-1-00.18.7-1
ii  libselinux1  2.9-2
ii  network-manager  1.19.90-2
ii  policykit-1-gnome [polkit-1-auth-agent]  0.105-7

Versions of packages network-manager-gnome recommends:
ii  awesome [notification-daemon]   4.3-4
ii  dunst [notification-daemon] 1.4.1-1
ii  gnome-keyring   3.28.2-5
ii  iso-codes   4.3-1
ii  mobile-broadband-provider-info  20170903-1

Versions of packages network-manager-gnome suggests:
pn  network-manager-openconnect-gnome  
pn  network-manager-openvpn-gnome  
pn  network-manager-pptp-gnome 
pn  network-manager-vpnc-gnome 

-- no debconf information

Bug#918857: python3-distutils: Newest version appears to be missing py36 modules

[James Tocknell]

Package: python3-distutils
Version: 3.7.2-2
Severity: important

Dear Maintainer,

It looks like the latest version is missing the python 3.6 version of the
distutils module (as reported by
https://packages.debian.org/sid/all/python3-distutils/filelist, dpkg -L, and
through distutils modules failing to import), can they be included again (I
can't see any obvious changes to the packaging which cause this, so I presume
this is unintentional)?

Thanks
James


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

Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-distutils depends on:
ii  python3  3.7.1-3
ii  python3-lib2to3  3.7.2-2

python3-distutils recommends no packages.

python3-distutils suggests no packages.

-- no debconf information

Bug#900936: geoclue: Update to 2.4.10 breaks redshift

[James Tocknell]

As per Eugene's email, the 2.4.11 release seems to fix this, I've
created a MR on salsa with the updated version, plus some other fixes.
Feel free to modify the commits as needed.

James

On 9 June 2018 at 22:40, Zeeshan Ali  wrote:
> Hi,
>
> Agent is required by default now but at the same time, we have enabled the 
> demo-agent to be installed by default and to
> auto-start on all non-GNOME desktops. It's been 5 years since geoclue2 was 
> created, would be nice if other desktops
> would implement an agent too. In the meantime, they can use the demo agent I 
> wrote.
>



-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.).
It isn't good enough for Tim Berners-Lee, and it isn't good enough for
me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In
practice, there is.

Bug#900936: geoclue: Update to 2.4.10 breaks redshift

[James Tocknell]

On 7 June 2018 at 18:41, Laurent Bigonville  wrote:
> Le 07/06/18 à 02:46, James Tocknell a écrit :
>>
>> Dear Maintainer,
>>
>> The update to 2.4.10-1 causes redshift to immediately crash, with the
>> error:
>>
>> Failed to connect to GeoClue2 service:
>> GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'redshift' disallowed,
>> no agent for UID 1000
>
>
> Which desktop environment are you using? Because it's usually the DE that is
> supposed to implement this.

None, I start up the necessary programs via my WM (awesome). I was planning
on adding the agent to my startup, but it fails to work.

>
>> Starting the agent in the demo package manually appears to make no
>> difference.
>> Additionally, I tried to use the where-am-i demo, which produced the same
>> error
>> (again with the agent started).
>>
>> I think the cause is this change referred to in the upstream changelog:
>> "Refuse location access if no app-auth agent is registered. This fixes a
>> security hole where an app requests location access before the agent gets
>> to
>> register itself and we end up giving out locaiton access even though user
>> has
>> disabled it."
>>
>> Can the change be reverted until the agent works?
>
>
> Well, I don't know to be honest, the demo agent is a demo, that should be
> implemented in the DE itself. Only GNOME (and I think enlightenment) are
> implementing this ATM and it could take a long time to be implemented in the
> others. (Don't know if there are even feature requests open)
>
> Couldn't the geolocation feature be disabled in redshift? Or couldn't the
> geoclue config file be adjusted to allow redshift to work without asking the
> agent?

The geolocation can be disabled, but that loses a far bit of the
functionality of
redshift (and doesn't solve the actual problem of programs being unable to get
the current location due to a non-working agent). I've tried adding
redshift (and
the where-am-i demo) to the config (which would have been a nice workaround,
preferable to just downgrading), but that didn't appear to work either
(both with
and without the agent running). The agent is added to the xdg startup dir, so
presumably it's supposed to function when there's no other agent?

Should I create a bug on the upstream tracker about the agent appearing not
to work, and post the url here?

>
>
>> FYI, I make the report critical so that the change doesn't migrate to
>> testing,
>> feel free to drop the severity if you think that's appropriate.
>
>
>



-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.).
It isn't good enough for Tim Berners-Lee, and it isn't good enough for
me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In
practice, there is.

Bug#900936: geoclue: Update to 2.4.10 breaks redshift

[James Tocknell]

Package: geoclue-2.0
Version: 2.4.10-1
Severity: critical
File: geoclue
Tags: upstream

Dear Maintainer,

The update to 2.4.10-1 causes redshift to immediately crash, with the error:

Failed to connect to GeoClue2 service: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'redshift' disallowed, no 
agent for UID 1000

Starting the agent in the demo package manually appears to make no difference.
Additionally, I tried to use the where-am-i demo, which produced the same error
(again with the agent started).

I think the cause is this change referred to in the upstream changelog:
"Refuse location access if no app-auth agent is registered. This fixes a
security hole where an app requests location access before the agent gets to
register itself and we end up giving out locaiton access even though user has
disabled it."

Can the change be reverted until the agent works?

FYI, I make the report critical so that the change doesn't migrate to testing,
feel free to drop the severity if you think that's appropriate.


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

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

Versions of packages geoclue-2.0 depends on:
ii  adduser 3.117
ii  libavahi-client30.7-4
ii  libavahi-common30.7-4
ii  libavahi-glib1  0.7-4
ii  libc6   2.27-3
ii  libglib2.0-02.56.1-2
ii  libjson-glib-1.0-0  1.4.2-4
ii  libmm-glib0 1.7.990-1
ii  libsoup2.4-12.62.2-1

Versions of packages geoclue-2.0 recommends:
ii  avahi-daemon  0.7-4
ii  iio-sensor-proxy  2.4-2
ii  modemmanager  1.7.990-1
ii  wpasupplicant 2:2.6-16

geoclue-2.0 suggests no packages.

-- no debconf information

Bug#898559: newsboat crashes when opening url

[James Tocknell]

Package: newsboat
Version: 2.11.1-1
Severity: important

Dear Maintainer,

I've noticed apparently random what appear to be segfaults with newsboat (which
I didn't see with newsbeuter, so presumably a recent change). I've finally
managed to get a crash when running gdb, the backtrace is below (I have the core
file that this was generated from if that helps). These segfaults don't seem to
have a pattern (different urls).

The message (which may also help) printed was "corrupted double-linked list".

#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7f77b258c231 in __GI_abort () at abort.c:79
#2  0x7f77b25cd7b7 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x7f77b26d60f3 "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x7f77b25d3d5a in malloc_printerr (str=str@entry=0x7f77b26d4256 
"corrupted double-linked list") at malloc.c:5350
#4  0x7f77b25d72d6 in _int_malloc (av=av@entry=0x7f77b290ac40 , 
bytes=bytes@entry=31) at malloc.c:3926
#5  0x7f77b25d872d in __GI___libc_malloc (bytes=31) at malloc.c:3065
#6  0x7f77b2f4de48 in operator new(unsigned long) () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x7f77b2fd8e6b in std::__cxx11::basic_string::_M_mutate(unsigned long, 
unsigned long, char const*, unsigned long) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x7f77b2fd9bdb in std::__cxx11::basic_string::_M_replace(unsigned long, 
unsigned long, char const*, unsigned long) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x55f2f8561af9 in std::__cxx11::basic_string::assign (__s=0x55f2fa313728 
"'180504125859164'", this=0x7ffd2d32acb0)
at /usr/include/c++/7/bits/basic_string.h:1420
#10 std::__cxx11::basic_string::operator= (__s=0x55f2fa313728 "'180504125859164'", 
this=0x7ffd2d32acb0) at /usr/include/c++/7/bits/basic_string.h:694
#11 newsboat::cache::prepare_query 
(this=this@entry=0x55f2f9c18bf0, format="'%q'", argument=@0x7ffd2d32ad90: 
0x7f7765852e98 "180504125859164") at src/cache.cpp:818
#12 0x55f2f855c293 in 
newsboat::cache::prepare_query<>(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string 
const&) (argument=..., format="'%q'", this=0x55f2f9c18bf0) at src/cache.cpp:805
#13 newsboat::cache::fetch_descriptions (this=0x55f2f9c18bf0, 
feed=feed@entry=0x7f777123bec0) at src/cache.cpp:921
#14 0x55f2f85c7142 in newsboat::rss_feed::load (this=0x7f777123bec0) at 
src/rss.cpp:626
#15 0x55f2f8602cbd in newsboat::itemlist_formaction::set_feed 
(this=this@entry=0x55f2fa833d60, fd=std::shared_ptr (use 
count 4, weak count 1292) = {...})
at src/itemlist_formaction.cpp:1072
#16 0x55f2f858d355 in newsboat::view::get_next_unread (this=0x7ffd2d32c880, 
itemlist=itemlist@entry=0x55f2fa833d60, itemview=itemview@entry=0x0) at 
src/view.cpp:720
#17 0x55f2f85fced9 in newsboat::itemlist_formaction::process_operation 
(this=0x55f2fa833d60, op=, automatic=, args=0x0) 
at src/itemlist_formaction.cpp:284
#18 0x55f2f85e964d in newsboat::formaction::process_op 
(this=0x55f2fa833d60, op=op@entry=newsboat::OP_NEXTUNREAD, 
automatic=automatic@entry=false, args=args@entry=0x0) at src/formaction.cpp:139
#19 0x55f2f85925ff in newsboat::view::run (this=0x7ffd2d32c880) at 
src/view.cpp:253
#20 0x55f2f85b45cb in newsboat::controller::run (this=0x7ffd2d32c9e0, 
argc=, argv=0x7ffd2d32ced8) at src/controller.cpp:806
#21 0x55f2f8555721 in main (argc=1, argv=0x7ffd2d32ced8) at newsboat.cpp:30

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

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

Versions of packages newsboat depends on:
ii  libc62.27-3
ii  libcurl3-gnutls  7.58.0-2
ii  libgcc1  1:8.1.0-2
ii  libjson-c3   0.12.1-1.3
ii  libncursesw5 6.1+20180210-3
ii  libsqlite3-0 3.23.1-1
ii  libstdc++6   8.1.0-2
ii  libstfl0 0.22-1.3+b9
ii  libtinfo56.1+20180210-3
ii  libxml2  2.9.4+dfsg1-6.1+b1

newsboat recommends no packages.

newsboat suggests no packages.

-- no debconf information

Bug#852521: [tex-live] unicode-math now unable to process $\widetilde{\mathbf{a}}$

[James Tocknell]

Sorry for the late reply, I'm trying to work out an actual MWE. I did have
the initial MWE work, but it appears I have changed something else after
filing the initial report. What's weird is the initial MWE does not work,
but the two different documents with different settings which break with
2016.20170123-1 do work.

James

On 26 January 2017 at 16:34, Norbert Preining <prein...@logic.at> wrote:

> Hi James,
>
> > I've attached the tex file and output, including stdout and stderr
>
> Hmm, is that from a working version? It doesn't look like.
>
> Furthermore, it seems that something is going completely different on
> your side, because loads of different files are loaded. One reason
> might be your texmf.cnf file:
> /home/aragilar/.tex/tex-config/web2c/texmf.cnf
> can you please tell me what is in there? Also you TEX* env vars.
>
> And if you can, a *working* run (you said it is working with the
> previous version to which you downgraded)!
>
> Thanks
>
> Norbert
>
> --
> PREINING Norbert   http://www.preining.info
> Accelia Inc. +JAIST +TeX Live +Debian Developer
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
>



-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It
isn't good enough for Tim Berners-Lee
<http://opendotdotdot.blogspot.com/2010/04/rms-and-tim-berners-lee-separated-at.html>,
and it isn't good enough for me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In practice,
there is.

Bug#852521: [tex-live] unicode-math now unable to process $\widetilde{\mathbf{a}}$

[James Tocknell]

Hi Norbert

I've attached the tex file and output, including stdout and stderr

James

On 26 January 2017 at 14:28, Norbert Preining <prein...@logic.at> wrote:

> On Thu, 26 Jan 2017, James Tocknell wrote:
> > $\widetilde{\mathbf{a}}$). I've temporary reverted back to
> 2016.20161130-1,
> > as that version works. So this is a regression. Is there an easy way of
>
> Can you please:
> * add
> \listfiles
>   as first line (before \documentclass...)
> * run
> xelatex -recorder ...
> * send me the
> .log
> .fls
>   of the working versions.
>
> Thanks a lot
>
> Norbert
>
> --
> PREINING Norbert   http://www.preining.info
> Accelia Inc. +JAIST +TeX Live +Debian Developer
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
>



-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It
isn't good enough for Tim Berners-Lee
<http://opendotdotdot.blogspot.com/2010/04/rms-and-tim-berners-lee-separated-at.html>,
and it isn't good enough for me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In practice,
there is.


tex_test.tar.gz
Description: GNU Zip compressed data

Bug#852521: [tex-live] unicode-math now unable to process $\widetilde{\mathbf{a}}$

[James Tocknell]

Hi Norbert

Yes, I can confirm this has worked before, on the 10th on January this year
(that's the latest version of a document which has
$\widetilde{\mathbf{a}}$). I've temporary reverted back to 2016.20161130-1,
as that version works. So this is a regression. Is there an easy way of
bisecting over texlive to find the breaking change?

James

On 26 January 2017 at 02:06, Norbert Preining <prein...@logic.at> wrote:

> Dear James,
>
> I guess you haven't seen the answer on the TeX Live mailing list,
> so I add it here.
>
> It seems that this has been the case before, too, and is well known:
>
>
> *** answer from Ulrike Fischer *
>
> The problem is that \mathbf doesn't use a font with math table and
> accent commands don't like this. You can find quite a number of
> questions about this on tex.sx. E.g.
> http://tex.stackexchange.com/questions/214570/try-to-use-
> ams-blackboard-bold-font-together-with-texgyrepagella
>
> The correct input would be \symbf. Or you must hide the \mathbf in a
> box:
>
> \documentclass{article}
> \usepackage{unicode-math}
>
> \begin{document}
>   $\widetilde{\symbf{a}} \widetilde{\mbox{$\mathbf{a}$}}$
> \end{document}
>
> (\widetilde{\text{$\mathbf{a}$}} with amsmath work too)
>
> 
>
> Can you confirm that this *has* worked before, say in the last
> half year or so?
>
> If not, I will probably close this bug report as usage error
> or upupstream problem.
>
> All the best and hope that helps
>
> Norbert
>
> --
> PREINING Norbert   http://www.preining.info
> Accelia Inc. +JAIST +TeX Live +Debian Developer
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
>



-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It
isn't good enough for Tim Berners-Lee
<http://opendotdotdot.blogspot.com/2010/04/rms-and-tim-berners-lee-separated-at.html>,
and it isn't good enough for me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In practice,
there is.

Bug#852521: texlive-latex-recommended: unicode-math now unable to process $\widetilde{\mathbf{a}}$

[James Tocknell]

Package: texlive-latex-recommended
Version: 2016.20170123-1
Severity: important

Something has changed in the latest version, such that the following MWE fails
to build:

\documentclass{article}
\usepackage{unicode-math}

\begin{document}
  $\widetilde{\mathbf{a}}$
\end{document}

Note that switching the order of the expression ($\mathbf{\widetilde{a}}$),
builds, but is missing the tilde.

Error message:
! Internal error: bad native font flag in `map_char_to_glyph'

Build log:
This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/Debian) (preloaded 
format=xelatex)
 restricted \write18 enabled.
entering extended mode
(./test.tex
LaTeX2e <2016/03/31> patch level 3
Babel <3.9r> and hyphenation patterns for 5 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/unicode-math/unicode-math.sty
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty)
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3xdvipdfmx.def))
(/usr/share/texlive/texmf-dist/tex/latex/ucharcat/ucharcat.sty)
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty)
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e.sty)
(/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty
(/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
*
* fontspec warning: "tu-clash"
* 
* I have found the tuenc.def encoding definition file but the TU encoding is
* not defined by the LaTeX2e kernel; attempting to correct but you really
* should update to the latest version of LaTeX2e.
*
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/fontspec/tuenc.def)
(/usr/share/texlive/texmf-dist/tex/latex/fontspec/tulmr.fd)

LaTeX Font Warning: Font shape `TU/cmr/m/n' undefined
(Font)  using `TU/lmr/m/n' instead on input line 105.

) (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.cfg)))
(/usr/share/texlive/texmf-dist/tex/latex/base/fix-cm.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def))
(/usr/share/texlive/texmf-dist/tex/latex/filehook/filehook.sty)
(/usr/share/texlive/texmf-dist/tex/latex/unicode-math/unicode-math-xetex.sty
(/usr/share/texlive/texmf-dist/tex/latex/unicode-math/unicode-math-table.tex)))
(./test.aux)

test.fls:
PWD /home/aragilar/Scratch/test_latex
INPUT /home/aragilar/.tex/tex-config/web2c/texmf.cnf
INPUT /etc/texmf/web2c/texmf.cnf
INPUT /usr/share/texmf/web2c/texmf.cnf
INPUT /usr/share/texlive/texmf-dist/web2c/texmf.cnf
INPUT /var/lib/texmf/web2c/xetex/xelatex.fmt
INPUT test.tex
OUTPUT test.log
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/article.cls
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/article.cls
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
INPUT /usr/share/texlive/texmf-dist/tex/latex/unicode-math/unicode-math.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/unicode-math/unicode-math.sty
INPUT /usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty
INPUT /usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty
INPUT /usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty
INPUT /usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex
INPUT /usr/share/texlive/texmf-dist/tex/generic/unicode-data/UnicodeData.txt
INPUT /usr/share/texlive/texmf-dist/tex/generic/unicode-data/CaseFolding.txt
INPUT /usr/share/texlive/texmf-dist/tex/generic/unicode-data/SpecialCasing.txt
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3xdvipdfmx.def
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3xdvipdfmx.def
INPUT /usr/share/texlive/texmf-dist/tex/latex/ucharcat/ucharcat.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/ucharcat/ucharcat.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty
INPUT 

Bug#824441: [Aptitude-devel] Bug#824441: aptitude segfaults when marking texlive-generic-extra as auto-installed

[James Tocknell]

Hi All

I've tried reproducing this in 0.8.2 and can't, so it does appear to have
been fixed. Thanks for fixing this.

Regards
James

On 11 June 2016 at 09:26, Manuel A. Fernandez Montecelo <
manuel.montez...@gmail.com> wrote:

> Control: tags -1 + pending
>
>
> Hi,
>
> 2016-05-20 08:39 David Kalnischkies:
>
>> Hi,
>>
>> (disclaimer: apt, not aptitude, maintainer talking)
>>
>> On Fri, May 20, 2016 at 09:54:23AM +1000, James Tocknell wrote:
>>
>>> 0x77b3feed in debVersioningSystem::CheckDep(char const*, int,
>>> char
>>> const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
>>> #0  0x77b3feed in debVersioningSystem::CheckDep(char const*, int,
>>> char const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
>>> #1  0x557767c1 in infer_reason (pkg=..., reasons=std::set with 1
>>> elements = {...}) at ../../../../src/generic/apt/infer_reason.cc:178
>>>
>>
>> [It is a bit confusing that the code of frame #1 is actually calling
>> IsSatisfied(), but it is just a wrapper around CheckDep() so lets just
>> ignore that for the moment]
>>
>> 10f0cf4a04b2526e9dea65facde865d993396417 adds this code, which passes
>> the candidate version to IsSatisfied – but not all packages have
>> a candidate! So that code should be adapted to test first if the package
>> has a candidate and only if so check if the candidate satisfies the
>> dependency.
>>
>>
>> Now, we could ask why IsSatisfied requires a valid version and the
>> answer is: nobody (aka me) thought anybody would pass it an invalid
>> version as the soul reason for the one-line IsSatisfied is to hide the
>> call to CheckDep behind a slightly nicer interface (1 vs 3 parameters)
>> and all existing calls in apt passed only valid versions in…
>>
>> I am not sure it is a good idea to add checks to that method as its in
>> various hot paths for apt & it has the potential of hiding bugs (at the
>> expense of opening some like here). Either way, that needs more thought
>> than I can shell out at the moment & adapting the call site should be
>> easy.
>>
>
> Thanks for the dignosis.
>
> Since I couldn't find an easy way to reproduce it (the texlive packages
> are huge for my wrongly-called broadband), I am basing this fix on the
> diagnosis above.
>
>
> 2016-05-24 05:03 James Tocknell:
>
>> I've got a more useful backtrace (had to build apt to get its debug
>> symbols). The issue seems to be line 178 in infer_reason.cc, which
>> got introduced in 0.8. Somehow (I'm not sure, everything seems to have
>> been
>> inlined...), it's calling debVersioningSystem::CheckDep with an invalid
>> address.
>>
>
> It probably happens for the reasons that David explained.
>
> I think that it has to do with the reverse dependencies of virtual
> packages.  I tried to reproduce it with csh|tcsh (virtual package
> c-shell) and some -perl reverse dependency, but I tried to remove them
> and mark as auto in different combinations for many minutes, and I
> couldn't trigger it.
>
> If you still experience this problem, it would be very nice if you
> confirm that it's indeed fixed when we release the next version.
>
>
> Cheers.
> --
> Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
>



-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It
isn't good enough for Tim Berners-Lee
<http://opendotdotdot.blogspot.com/2010/04/rms-and-tim-berners-lee-separated-at.html>,
and it isn't good enough for me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In practice,
there is.

Bug#827713: apt 1.2.13 breaks proxy auto-detection

[James Tocknell]

Package: apt
Version: 1.2.12
Severity: important

Under apt 1.2.13, attempting to use Acquire::http::Proxy-Auto-Detect or
Acquire::http::ProxyAutoDetect with squid-deb-proxy-client seems to always
return "Failed to read in AutoDetectProxy" when there is no nearby server,
which makes squid-deb-proxy-client almost useless.


-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.5\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.5\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.5\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.5\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.5\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.5\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.5\.0-2-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.5\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.5\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.5\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.5\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.6\.0-1-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Update "";
APT::Update::Post-Invoke "";
APT::Update::Post-Invoke:: "[ ! -x /usr/bin/debtags ] || debtags update || 
true";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "200";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "300";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-6";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::lzma "";
APT::Compressor::lzma::Name "lzma";
APT::Compressor::lzma::Extension ".lzma";
APT::Compressor::lzma::Binary "xz";
APT::Compressor::lzma::Cost "400";

Bug#824441: [Aptitude-devel] Bug#824441: aptitude segfaults when marking texlive-generic-extra as auto-installed

[James Tocknell]

I've got a more useful backtrace (had to build apt to get its debug
symbols). The issue seems to be line 178 in infer_reason.cc, which
got introduced in 0.8. Somehow (I'm not sure, everything seems to have been
inlined...), it's calling debVersioningSystem::CheckDep with an invalid
address. I've attached it and a core dump, hopefully this helps.​
 core
<https://drive.google.com/file/d/0ByLxRPizW5wCbkllRjZaeEpBcms/view?usp=drive_web>
​

On 20 May 2016 at 09:54, James Tocknell <aragi...@gmail.com> wrote:

> Found a different case where aptitude segfaults, this time I marked a few
> packages as auto-installed, and after holding the up arrow for a few
> seconds, aptitude segfaulted. A backtrace from this is below:
> Program received signal SIGSEGV, Segmentation fault.
> 0x77b3feed in debVersioningSystem::CheckDep(char const*, int, char
> const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
> #0  0x77b3feed in debVersioningSystem::CheckDep(char const*, int,
> char const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
> #1  0x557767c1 in infer_reason (pkg=..., reasons=std::set with 1
> elements = {...}) at ../../../../src/generic/apt/infer_reason.cc:178
> #2  0x55650418 in reason_fragment (pkg=...,
> breakage=@0x7fffcece: false) at ../../src/reason_fragment.cc:447
> #3  0x5564abcc in info_area_multiplex::set_package
> (this=0x56b436e0, pkg=..., ver=...) at ../../src/pkg_view.cc:454
> #4  0x556227e0 in sigc::internal::signal_emit2<void,
> pkgCache::PkgIterator const&, pkgCache::VerIterator const&,
> sigc::nil>::emit (_A_a2=..., _A_a1=..., impl=0x5604f970)
> at /usr/include/sigc++-2.0/sigc++/signal.h:1266
> #5  sigc::signal2<void, pkgCache::PkgIterator const&,
> pkgCache::VerIterator const&, sigc::nil>::emit (this=,
> _A_a2=..., _A_a1=...) at /usr/include/sigc++-2.0/sigc++/signal.h:2989
> #6  sigc::signal2<void, pkgCache::PkgIterator const&,
> pkgCache::VerIterator const&, sigc::nil>::operator() (_A_a2=..., _A_a1=...,
> this=)
> at /usr/include/sigc++-2.0/sigc++/signal.h:2997
> #7  pkg_item::do_highlighted_changed (this=0x592d43a0,
> highlighted=) at ../../src/pkg_item.cc:115
> #8  0x771d5b8d in sigc::internal::signal_emit1<void,
> cwidget::widgets::treeitem*, sigc::nil>::emit(sigc::internal::signal_impl*,
> cwidget::widgets::treeitem* const&) ()
>from /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #9  0x771cee93 in cwidget::widgets::tree::line_up() () from
> /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #10 0x771d3e41 in
> cwidget::widgets::tree::handle_key(cwidget::config::key const&) () from
> /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #11 0x5561641d in menu_tree::handle_key 
> (this=this@entry=0x55c98cf0,
> k=...) at ../../src/menu_tree.cc:430
> #12 0x55633973 in pkg_tree::handle_key (this=0x55c98cf0,
> k=...) at ../../src/pkg_tree.cc:363
> #13 0x771d9ab3 in
> cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
> /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #14 0x771c1da7 in
> cwidget::widgets::table::handle_key(cwidget::config::key const&) () from
> /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #15 0x771d9ab3 in
> cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
> /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #16 0x771ad4bb in
> cwidget::widgets::passthrough::handle_key(cwidget::config::key const&) ()
> from /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #17 0x771d9ab3 in
> cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
> /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #18 0x771c1da7 in
> cwidget::widgets::table::handle_key(cwidget::config::key const&) () from
> /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #19 0x771d9ab3 in
> cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
> /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #20 0x771ad4bb in
> cwidget::widgets::passthrough::handle_key(cwidget::config::key const&) ()
> from /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #21 0x771d9ab3 in
> cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
> /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #22 0x7718e1f1 in
> cwidget::widgets::menubar::handle_key(cwidget::config::key const&) () from
> /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #23 0x771d9ab3 in
> cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
> /usr/lib/x86_64-linux-gnu/libcwidget.so.3
> #24 0x7715bdc9 in
> cwidget::toplevel::input_thread::get_input_event::dispatch() 

Bug#824441: [Aptitude-devel] Bug#824441: aptitude segfaults when marking texlive-generic-extra as auto-installed

[James Tocknell]

Found a different case where aptitude segfaults, this time I marked a few
packages as auto-installed, and after holding the up arrow for a few
seconds, aptitude segfaulted. A backtrace from this is below:
Program received signal SIGSEGV, Segmentation fault.
0x77b3feed in debVersioningSystem::CheckDep(char const*, int, char
const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
#0  0x77b3feed in debVersioningSystem::CheckDep(char const*, int,
char const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
#1  0x557767c1 in infer_reason (pkg=..., reasons=std::set with 1
elements = {...}) at ../../../../src/generic/apt/infer_reason.cc:178
#2  0x55650418 in reason_fragment (pkg=...,
breakage=@0x7fffcece: false) at ../../src/reason_fragment.cc:447
#3  0x5564abcc in info_area_multiplex::set_package
(this=0x56b436e0, pkg=..., ver=...) at ../../src/pkg_view.cc:454
#4  0x556227e0 in sigc::internal::signal_emit2<void,
pkgCache::PkgIterator const&, pkgCache::VerIterator const&,
sigc::nil>::emit (_A_a2=..., _A_a1=..., impl=0x5604f970)
at /usr/include/sigc++-2.0/sigc++/signal.h:1266
#5  sigc::signal2<void, pkgCache::PkgIterator const&, pkgCache::VerIterator
const&, sigc::nil>::emit (this=, _A_a2=..., _A_a1=...) at
/usr/include/sigc++-2.0/sigc++/signal.h:2989
#6  sigc::signal2<void, pkgCache::PkgIterator const&, pkgCache::VerIterator
const&, sigc::nil>::operator() (_A_a2=..., _A_a1=..., this=)
at /usr/include/sigc++-2.0/sigc++/signal.h:2997
#7  pkg_item::do_highlighted_changed (this=0x592d43a0,
highlighted=) at ../../src/pkg_item.cc:115
#8  0x771d5b8d in sigc::internal::signal_emit1<void,
cwidget::widgets::treeitem*, sigc::nil>::emit(sigc::internal::signal_impl*,
cwidget::widgets::treeitem* const&) ()
   from /usr/lib/x86_64-linux-gnu/libcwidget.so.3
#9  0x771cee93 in cwidget::widgets::tree::line_up() () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#10 0x771d3e41 in
cwidget::widgets::tree::handle_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#11 0x5561641d in menu_tree::handle_key
(this=this@entry=0x55c98cf0,
k=...) at ../../src/menu_tree.cc:430
#12 0x55633973 in pkg_tree::handle_key (this=0x55c98cf0, k=...)
at ../../src/pkg_tree.cc:363
#13 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#14 0x771c1da7 in
cwidget::widgets::table::handle_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#15 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#16 0x771ad4bb in
cwidget::widgets::passthrough::handle_key(cwidget::config::key const&) ()
from /usr/lib/x86_64-linux-gnu/libcwidget.so.3
#17 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#18 0x771c1da7 in
cwidget::widgets::table::handle_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#19 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#20 0x771ad4bb in
cwidget::widgets::passthrough::handle_key(cwidget::config::key const&) ()
from /usr/lib/x86_64-linux-gnu/libcwidget.so.3
#21 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#22 0x7718e1f1 in
cwidget::widgets::menubar::handle_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#23 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#24 0x7715bdc9 in
cwidget::toplevel::input_thread::get_input_event::dispatch() () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#25 0x771536b5 in cwidget::toplevel::mainloop(int) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#26 0x5568c64a in ui_main () at ../../src/ui.cc:3075
#27 0x0000555b50e0 in main (argc=, argv=)
at ../../src/main.cc:1398
quit


On 17 May 2016 at 13:16, James Tocknell <aragi...@gmail.com> wrote:

> amd64 is missing aptitude-dbgsym (which is why I asked), but it appears to
> be created by gbp, so I've used that to build a debug package, which gives
> the following backtrace:
> Program received signal SIGSEGV, Segmentation fault.
> 0x77b3feed in debVersioningSystem::CheckDep(char const*, int, char
> const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
> #0  0x77b3feed in debVersioningSystem::CheckDep(char const*, int,
> char const*) () from /usr/lib/x86_64-linux-gnu/l

Bug#824441: [Aptitude-devel] Bug#824441: aptitude segfaults when marking texlive-generic-extra as auto-installed

[James Tocknell]

amd64 is missing aptitude-dbgsym (which is why I asked), but it appears to
be created by gbp, so I've used that to build a debug package, which gives
the following backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x77b3feed in debVersioningSystem::CheckDep(char const*, int, char
const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
#0  0x77b3feed in debVersioningSystem::CheckDep(char const*, int,
char const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
#1  0x557767c1 in infer_reason (pkg=..., reasons=std::set with 0
elements) at ../../../../src/generic/apt/infer_reason.cc:178
#2  0x55650418 in reason_fragment (pkg=...,
breakage=@0x7fffcf0e: false) at ../../src/reason_fragment.cc:447
#3  0x5564abcc in info_area_multiplex::set_package
(this=0x56b45fb0, pkg=..., ver=...) at ../../src/pkg_view.cc:454
#4  0x55630a7a in sigc::internal::signal_emit0<void,
sigc::nil>::emit (impl=0x55b85090) at
/usr/include/sigc++-2.0/sigc++/signal.h:790
#5  sigc::signal0<void, sigc::nil>::emit (this=) at
/usr/include/sigc++-2.0/sigc++/signal.h:2705
#6  sigc::signal0<void, sigc::nil>::operator() (this=) at
/usr/include/sigc++-2.0/sigc++/signal.h:2713
#7  pkg_tree_node::dispatch_key (this=this@entry=0x578f5990, k=...,
owner=owner@entry=0x55c99330) at ../../src/pkg_node.cc:86
#8  0x55622066 in pkg_item::dispatch_key (this=0x578f5990,
k=..., owner=0x55c99330) at ../../src/pkg_item.cc:404
#9  0x771d3fe5 in
cwidget::widgets::tree::handle_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#10 0x5561641d in menu_tree::handle_key
(this=this@entry=0x55c99330,
k=...) at ../../src/menu_tree.cc:430
#11 0x55633973 in pkg_tree::handle_key (this=0x55c99330, k=...)
at ../../src/pkg_tree.cc:363
#12 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#13 0x771c1da7 in
cwidget::widgets::table::handle_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#14 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#15 0x771ad4bb in
cwidget::widgets::passthrough::handle_key(cwidget::config::key const&) ()
from /usr/lib/x86_64-linux-gnu/libcwidget.so.3
#16 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#17 0x771c1da7 in
cwidget::widgets::table::handle_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#18 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#19 0x771ad4bb in
cwidget::widgets::passthrough::handle_key(cwidget::config::key const&) ()
from /usr/lib/x86_64-linux-gnu/libcwidget.so.3
#20 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#21 0x7718e1f1 in
cwidget::widgets::menubar::handle_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#22 0x771d9ab3 in
cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#23 0x7715bdc9 in
cwidget::toplevel::input_thread::get_input_event::dispatch() () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#24 0x771536b5 in cwidget::toplevel::mainloop(int) () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#25 0x5568c64a in ui_main () at ../../src/ui.cc:3075
#26 0x555b50e0 in main (argc=, argv=)
at ../../src/main.cc:1398

James


On 17 May 2016 at 02:58, Axel Beckert <a...@debian.org> wrote:

> Hi,
>
> Christoph Anton Mitterer wrote:
> > On Mon, 2016-05-16 at 12:01 +1000, James Tocknell wrote:
> > > Are there debug symbols for aptitude in unstable so I can provide a
> > > backtrace, they only appear to be in testing?
> >
> > You probably need to use:
> > https://wiki.debian.org/AutomaticDebugPackages
>
> Correct.
>
> Aptitude's debug package is now named aptitude-dbgsym.
>
> And yes, a backtrace would be nice as I can't reproduce the issue on
> Sid amd64.
>
> Regards, Axel
> --
>  ,''`.  |  Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
> : :' :  |  Debian Developer, ftp.ch.debian.org Admin
> `. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>   `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
>



-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It
isn't good enough for Tim Berners-Lee
<http://opendo

Bug#824441: aptitude segfaults when marking texlive-generic-extra as auto-installed

[James Tocknell]

Package: aptitude
Version: 0.8.1-1
Severity: important

As per the title, aptitude segfaults when marking texlive-generic-extra as
auto-installed. I'm marking it as auto-installed via the keyboard shortcut.
The segfault happens when I'm in the default limit as well as the limit "!~M".
This happens every time I do this, whether it's the first thing I do in
aptitude, or after doing something else.

Are there debug symbols for aptitude in unstable so I can provide a backtrace,
they only appear to be in testing?


-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.1
Compiler: g++ 5.3.1 20160429
Compiled against:
  apt version 5.0.0
  NCurses version 6.0
  libsigc++ version: 2.8.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20160319
  cwidget version: 0.5.17
  Apt version: 5.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffec6f6d000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7fe2abcde000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fe2abaae000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7fe2ab883000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fe2ab67c000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7fe2ab37f000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fe2ab084000)
libboost_iostreams.so.1.58.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.58.0 (0x7fe2aae6a000)
libboost_filesystem.so.1.58.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.58.0 (0x7fe2aac51000)
libboost_system.so.1.58.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.58.0 (0x7fe2aaa4c000)
libxapian.so.22 => /usr/lib/x86_64-linux-gnu/libxapian.so.22 
(0x7fe2aa648000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fe2aa42b000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fe2aa0aa000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fe2a9dac000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fe2a9b96000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fe2a97f1000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fe2a95ee000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fe2a93ea000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fe2a91d2000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fe2a8fb7000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fe2a8da7000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fe2a8b83000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7fe2a8971000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fe2a8768000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fe2a8563000)
/lib64/ld-linux-x86-64.so.2 (0x562319c83000)

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

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

Versions of packages aptitude depends on:
ii  aptitude-common0.8.1-1
ii  libapt-pkg5.0  1.2.12
ii  libboost-filesystem1.58.0  1.58.0+dfsg-5+b1
ii  libboost-iostreams1.58.0   1.58.0+dfsg-5+b1
ii  libboost-system1.58.0  1.58.0+dfsg-5+b1
ii  libc6  2.22-9
ii  libcwidget3v5  0.5.17-4+b1
ii  libgcc11:6.1.1-3
ii  libncursesw5   6.0+20160319-1
ii  libsigc++-2.0-0v5  2.8.0-1
ii  libsqlite3-0   3.12.2-1
ii  libstdc++6 6.1.1-3
ii  libtinfo5  6.0+20160319-1
ii  libxapian22v5  1.2.23-1

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-8
ii  sensible-utils 0.0.9

Versions of packages aptitude suggests:
ii  apt-xapian-index0.47+nmu2
pn  aptitude-doc-en | aptitude-doc  
ii  debtags 2.1
pn  tasksel 

-- no debconf information

Bug#800370: python3.4: namedtuple does not have __dict__ attr any more

[James Tocknell]

python3.4 3.4.3-8

On 11 October 2015 at 21:13, Matthias Klose <d...@debian.org> wrote:

> Control: forwarded -1 http://bugs.python.org/issue24931
> Control: tags -1 + upstream
>
>
> On 11.10.2015 12:06, Matthias Klose wrote:
>
>> which was the last version which had this behaviour?
>>
>
>


-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It
isn't good enough for Tim Berners-Lee
<http://opendotdotdot.blogspot.com/2010/04/rms-and-tim-berners-lee-separated-at.html>,
and it isn't good enough for me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In practice,
there is.

Bug#800370: python3.4: namedtuple does not have __dict__ attr any more

[James Tocknell]

Package: python3.4
Version: 3.4.3-9
Severity: normal

collections.namedtuple appears to not to create namedtuples which have the
__dict__ attribute any more. Given that the stdlib docs stated that using
vars() (and hence the existence of __dict__) was preferred, it seems odd that
it has disappeared.


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

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

Versions of packages python3.4 depends on:
ii  libpython3.4-stdlib  3.4.3-9
ii  mime-support 3.59
ii  python3.4-minimal3.4.3-9

python3.4 recommends no packages.

Versions of packages python3.4 suggests:
ii  binutils2.25.1-3
pn  python3.4-doc   
pn  python3.4-venv  

-- no debconf information

Bug#658669: Patch to fix bash-completion

[James Tocknell]

This patch is the same as suggested by #658773, it appears to work for
dlocate also.

James

--
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.).
It isn't good enough for Tim Berners-Lee, and it isn't good enough for
me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In
practice, there is.


dlocate.patch
Description: Binary data

Bug#679409: lightdm: Fails to start on boot, invoke-rc.d lightdm start fails

[James Tocknell]

Roger

I've tested the patch, and it doesn't fix the issue I'm having. I'm
using Upstart
as my init daemon, and lightdm still fails, with no useful output in
/var/log/boot. However, lightdm does start when I use sysvinit as the init
daemon, with the patch. Could this be a Upstart issue? I know lightdm has
some association with Ubuntu, and Upstart is Ubuntu's default init daemon,
could the issue be with the very different versions of Upstart in Ubuntu and
Debian? The problem could lie in the fix for the bug #660824, which was a
change between the version of sysvinit-utils that works for me and don't work
for me, as it's Upstart related.

James

On Sun, Aug 12, 2012 at 7:23 AM, Roger Leigh rle...@codelibre.net wrote:
 On Sat, Aug 11, 2012 at 05:26:29PM +0100, Roger Leigh wrote:
 On Wed, Jul 11, 2012 at 02:06:52PM +1000, James Tocknell wrote:
  On Mon, Jul 2, 2012 at 6:04 PM, Yves-Alexis Perez cor...@debian.org 
  wrote:
   On lun., 2012-07-02 at 10:02 +0200, Petter Reinholdtsen wrote:
   [Yves-Alexis Perez]
James, in any case, I think providing /etc/init.d/.depend.* might
help solving this.
  
   Actually, it is better to provide the output from
   /usr/share/insserv/make-testsuite, which allow the boot sequence to be
   reproduced using dummy init.d scripts.
  
Please keep me on CC: so I'm informed of the development. It might
be interesting to provide /var/log/lightdm.log and
/var/log/lightdm-gtk-greeeter.log, although the fact it works with
startx might means it won't show anything.
  
   To debug this, try to disable concurrent booting (and keep dependency
   based boot sequencing), and see if it work better.  Also, it would be
   useful to get the boot log (/var/log/boot.log) after enabling
   bootlogd.

 I've installed lightdm on my system, and I do see the occasional
 failure to start.  This would indicate some race in parallelisation
 which would be indicative of a missing dependency.

 Please could you try sysvinit with the patch attached here?  This special
 cases lightdm in startpar, since gdm/kdm/xdm are already special cased
 here.

 http://anonscm.debian.org/gitweb/?p=collab-maint/sysvinit;a=commitdiff;h=34ee13ba8d509183b568c70511289f7f7579502b

 If you're unable to build yourself, let me know and I'll prepare some
 packages.


 Thanks,
 Roger

 --
   .''`.  Roger Leigh
  : :' :  Debian GNU/Linuxhttp://people.debian.org/~rleigh/
  `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
`-GPG Public Key  F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800



-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.).
It isn't good enough for Tim Berners-Lee, and it isn't good enough for
me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In
practice, there is.


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

Bug#682371: iceweasel: Change WM_CLASS back to Iceweasel

[James Tocknell]

Package: iceweasel
Version: 14.0.1-2
Severity: normal

In Iceweasel 14, the class of the browser window has changed from Icewasel to
Firefox-bin. It would be logical to change it back, since most people would
expect to look for windows with class Iceweasel than Firefox-bin.


-- Package-specific info:

-- Extensions information
Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled

Name: Add-on Compatibility Reporter
Location: ${PROFILE_EXTENSIONS}/compatibil...@addons.mozilla.org.xpi
Status: enabled

Name: All-in-One Sidebar
Location: ${PROFILE_EXTENSIONS}/{097d3191-e6fa-4728-9826-b533d755359d}.xpi
Status: enabled

Name: British English Dictionary
Location: ${PROFILE_EXTENSIONS}/en...@dictionaries.addons.mozilla.org
Status: enabled

Name: CheckPlaces
Location: ${PROFILE_EXTENSIONS}/checkpla...@andyhalford.com.xpi
Status: user-disabled

Name: Collusion
Location: ${PROFILE_EXTENSIONS}/jid1-f9uj2thwoam...@jetpack.xpi
Status: user-disabled

Name: Cookie Monster
Location: ${PROFILE_EXTENSIONS}/{45d8ff86-d909-11db-9705-005056c8}.xpi
Status: user-disabled

Name: Debian Linux theme
Status: enabled

Name: Default theme
Location: /usr/lib/iceweasel/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: user-disabled

Name: DNSSD for Firefox
Location: ${PROFILE_EXTENSIONS}/bonjourf...@bonjourfoxy.net
Status: user-disabled

Name: DownThemAll!
Location: ${PROFILE_EXTENSIONS}/{DDC359D1-844A-42a7-9AA1-88A850A938A8}.xpi
Status: enabled

Name: English (Australian) Dictionary
Location: ${PROFILE_EXTENSIONS}/en...@dictionaries.addons.mozilla.org
Status: enabled

Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: enabled

Name: Firefox B theme
Status: user-disabled

Name: Flagfox
Location: ${PROFILE_EXTENSIONS}/{1018e4d6-728f-4b20-ad56-37578a4de76b}
Status: enabled

Name: Ghostery
Location: ${PROFILE_EXTENSIONS}/fire...@ghostery.com
Status: enabled

Name: Gmail Unlabelled 2.0 user-script
Status: user-disabled

Name: Greasemonkey
Location: ${PROFILE_EXTENSIONS}/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}
Status: enabled

Name: HTTPS-Everywhere
Location: ${PROFILE_EXTENSIONS}/https-everywh...@eff.org
Status: enabled

Name: IpProtocols
Location: ${PROFILE_EXTENSIONS}/ipprotocols@jcp.convenant
Status: enabled

Name: keyconfig
Location: ${PROFILE_EXTENSIONS}/keycon...@dorando.xpi
Status: enabled

Name: Morning Coffee
Location: ${PROFILE_EXTENSIONS}/morningcof...@shaneliesegang.xpi
Status: user-disabled

Name: Mozilla Labs: Prospector - Tab Focus
Location: ${PROFILE_EXTENSIONS}/tabfo...@prospector.labs.mozilla.xpi
Status: enabled

Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
Status: enabled

Name: OpenAttribute
Location: ${PROFILE_EXTENSIONS}/fire...@openattribute.com.xpi
Status: enabled

Name: Places Maintenance
Location: ${PROFILE_EXTENSIONS}/places-maintena...@bonardo.net.xpi
Status: user-disabled

Name: RSS Icon
Location: ${PROFILE_EXTENSIONS}/kitsune...@gmail.com.xpi
Status: enabled

Name: Showcase
Location: ${PROFILE_EXTENSIONS}/{89506680-e3f4-484c-a2c0-ed711d481eda}.xpi
Status: user-disabled

Name: Status-4-Evar
Location: ${PROFILE_EXTENSIONS}/status4e...@caligonstudios.com.xpi
Status: enabled

Name: StumbleUpon
Location: ${PROFILE_EXTENSIONS}/{AE93811A-5C9A-4d34-8462-F7B864FC4696}.xpi
Status: user-disabled

Name: Tab History Redux
Location: ${PROFILE_EXTENSIONS}/tab-history-re...@efinke.com.xpi
Status: enabled

Name: Tab Mix Plus
Location: ${PROFILE_EXTENSIONS}/{dc572301-7619-498c-a57d-39143191b318}.xpi
Status: enabled

Name: Ubiquity
Location: ${PROFILE_EXTENSIONS}/ubiqu...@labs.mozilla.com
Status: enabled

Name: Zotero
Location: ${PROFILE_EXTENSIONS}/zot...@chnm.gmu.edu
Status: enabled

-- Plugins information
Name: Shockwave Flash
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled


-- Addons package information
ii  iceweasel  14.0.1-2 amd64Web browser based on Firefox

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages iceweasel depends on:
ii  debianutils 4.3.2
ii  fontconfig  2.9.0-6
ii  libc6   2.13-34
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.32.3-1
ii  libgtk2.0-0 2.24.10-1
ii  libnspr42:4.9.2-1
ii  libnspr4-0d 2:4.9.2-1
ii  libsqlite3-03.7.13-1
ii  libstdc++6  4.7.1-5
ii  procps  1:3.3.3-2
ii  xulrunner-14.0  14.0.1-2

iceweasel recommends no packages.

Versions of packages iceweasel suggests:
ii  fonts-stix [otf-stix]  1.1.0-1
ii  libgssapi-krb5-2   1.10.1+dfsg-1
pn  mozplugger none
ii  otf-stix   

Bug#679409: lightdm: Fails to start on boot, invoke-rc.d lightdm start fails

[James Tocknell]

Here's the output from /usr/share/insserv/make-testsuite from two systems,
one (desktop) using sysvinit-utils 2.88dsf-28, which does not work, and the
other (laptop) with 2.88dsf-22.1, which does. Both work with 2.88dsf-22.1,
and don't work woth 2.88dsf-28.

James

On Mon, Jul 2, 2012 at 6:04 PM, Yves-Alexis Perez cor...@debian.org wrote:
 On lun., 2012-07-02 at 10:02 +0200, Petter Reinholdtsen wrote:
 [Yves-Alexis Perez]
  James, in any case, I think providing /etc/init.d/.depend.* might
  help solving this.

 Actually, it is better to provide the output from
 /usr/share/insserv/make-testsuite, which allow the boot sequence to be
 reproduced using dummy init.d scripts.

  Please keep me on CC: so I'm informed of the development. It might
  be interesting to provide /var/log/lightdm.log and
  /var/log/lightdm-gtk-greeeter.log, although the fact it works with
  startx might means it won't show anything.

 To debug this, try to disable concurrent booting (and keep dependency
 based boot sequencing), and see if it work better.  Also, it would be
 useful to get the boot log (/var/log/boot.log) after enabling
 bootlogd.

 What exactly is needed to reproduce the problem?

 It might help to actually put the reporter on CC: :)
 --
 Yves-Alexis



-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.).
It isn't good enough for Tim Berners-Lee, and it isn't good enough for
me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In
practice, there is.


init_test.tar.gz
Description: GNU Zip compressed data

Bug#679409: [Pkg-xfce-devel] Bug#679409: lightdm: Fails to start on boot, invoke-rc.d lightdm start fails

[James Tocknell]

Lightdm works for the earlier versions.

I don't know enough about the init system to know where the problem
would lie, but what I do know is that dependency based booting is now
required for the broken versions. I've also looked though all log
files that I know of, and I can't find anything related with lightdm.

James

On Thu, Jun 28, 2012 at 11:55 PM, Yves-Alexis Perez cor...@debian.org wrote:
 On jeu., 2012-06-28 at 23:27 +1000, James Tocknell wrote:
 Package: lightdm
 Version: 1.2.2-3
 Severity: grave
 Justification: renders package unusable

 With sysvinit  2.88dsf-22.1, lightdm fails to start, and invoke-rd.d lightdm
 start fails with the message start: Job failed to start. Using startx does
 work, so the issue isn't with X.

 What if you downgrade to previous sysvinit? It looks to me like an issue
 there.
 --
 Yves-Alexis



-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.).
It isn't good enough for Tim Berners-Lee, and it isn't good enough for
me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In
practice, there is.



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

Bug#679409: lightdm: Fails to start on boot, invoke-rc.d lightdm start fails

[James Tocknell]

Package: lightdm
Version: 1.2.2-3
Severity: grave
Justification: renders package unusable

With sysvinit  2.88dsf-22.1, lightdm fails to start, and invoke-rd.d lightdm
start fails with the message start: Job failed to start. Using startx does
work, so the issue isn't with X.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages lightdm depends on:
ii  adduser3.113+nmu3
ii  consolekit 0.4.5-3
ii  dbus   1.6.2-1
ii  debconf [debconf-2.0]  1.5.44
ii  libc6  2.13-33
ii  libglib2.0-0   2.32.3-1
ii  libpam0g   1.1.3-7.1
ii  libxcb11.8.1-1
ii  libxdmcp6  1:1.1.1-1
ii  lightdm-gtk-greeter1.1.6-2

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+1

Versions of packages lightdm suggests:
ii  accountsservice  0.6.21-5

-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm



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

Bug#663572: [Pkg-xfce-devel] Bug#663572: lightdm does not allow use of compose key

[James Tocknell]

I've tested lightdm with with a different session which explicitly
called xmodmap,
and the compose key works in that session. I've also looked at why my setup
worked in gdm3, and found that in /etc/gdm3/Xsession xmodmap is called. I
guess the bug report should be changed to wishlist, with the request that
xmodmap be called during startup.

James

On Thu, Mar 15, 2012 at 4:22 AM, Yves-Alexis Perez cor...@debian.org wrote:

 On mer., 2012-03-14 at 20:39 +1100, James Tocknell wrote:
  The output in both sessions is:
 
  Trying to build keymap using the following components:
  keycodes:   evdev+aliases(qwerty)
  types:      complete
  compat:     complete
  symbols:    pc+us+inet(evdev)+terminate(ctrl_alt_bksp)
  geometry:   pc(pc105)
 
  The compose key is enabled using a .Xmodmap file.

 So that means the xmodmap is not really enabled at login time, which
 might be related on what session you start in both cases?
 --
 Yves-Alexis




--
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.).
It isn't good enough for Tim Berners-Lee, and it isn't good enough for
me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In
practice, there is.



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

Bug#663572: [Pkg-xfce-devel] Bug#663572: lightdm does not allow use of compose key

[James Tocknell]

The output in both sessions is:

Trying to build keymap using the following components:
keycodes:   evdev+aliases(qwerty)
types:  complete
compat: complete
symbols:pc+us+inet(evdev)+terminate(ctrl_alt_bksp)
geometry:   pc(pc105)

The compose key is enabled using a .Xmodmap file.

James

On Tue, Mar 13, 2012 at 12:29 AM, Yves-Alexis Perez cor...@debian.org wrote:
 tag 663572 moreinfo unreproducible
 thanks

 On lun., 2012-03-12 at 23:54 +1100, James Tocknell wrote:
 Package: lightdm
 Version: 1.0.9-1
 Severity: important

 The compose key does not work in sessions launched by lightdm. If the
 same
 sessions are launched by gdm3, the compose key works in those
 sessions.

 It works for me… That looks more like a keymap issue or something. Could
 you post the result of setxkbmap -v in both cases?

 Regards,
 --
 Yves-Alexis




-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.).
It isn't good enough for Tim Berners-Lee, and it isn't good enough for
me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In
practice, there is.



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

Bug#663572: lightdm does not allow use of compose key

[James Tocknell]

Package: lightdm
Version: 1.0.9-1
Severity: important

The compose key does not work in sessions launched by lightdm. If the same
sessions are launched by gdm3, the compose key works in those sessions.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.3.0-rc6-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lightdm depends on:
ii  adduser3.113+nmu1
ii  consolekit 0.4.5-3
ii  dbus   1.4.18-1
ii  debconf [debconf-2.0]  1.5.41
ii  libc6  2.13-27
ii  libglib2.0-0   2.30.2-6
ii  libpam0g   1.1.3-7
ii  libxcb11.8.1-1
ii  libxdmcp6  1:1.1.0-4
ii  lightdm-gtk-greeter1.0.9-1

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.6+12

Versions of packages lightdm suggests:
ii  accountsservice  0.6.15-4

-- debconf information excluded



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

Bug#661971: apt-cacher-ng does not work with http://http.debian.net/

[James Tocknell]

Package: apt-cacher-ng
Severity: important
Tags: upstream

When using http://http.debian.net/ as a mirror in my sources.list, if I set the
proxy to be apt-cacher-ng, then apt-cacher-ng fails to download the package due
to the use of 307 http messages.



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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



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

Bug#655944: linux-image-3.1.0-1-amd64: Kernel threads use significant amount of CPU

[James Tocknell]

Package: linux-2.6
Version: 3.1.8-2
Severity: normal

On my laptop, kernel threads use somewhere between 25% - 80% of one of the
CPUs, even on idle.
At the suggestion of a friend, I looked at the contents of
/sys/firmware/acpi/interrupts/, and noticed that gpe18 was rising at about
10 a second.
Searching through the standard logfiles didn't show anything related to gpe18,
however looking through the installation logs, I found this line
  ACPI Error: No handler or method for GPE[18], disabling event
(20090903/evgpe-706)
which suggested that the issue was with ACPI.

Decompiling the dsdt table and then recompiling according to http://en.gentoo-
wiki.com/wiki/ACPI/Fix_common_problems in order to try to guess what hardware
was the issue, gave me the three following errors:

dsdt.dsl  2124: 0x, // Length
Error4122 -  ^ Invalid combination of Length
and Min/Max fixed flags

dsdt.dsl  2131: 0x07E0, // Length
Error4118 -  ^ Length is not equal to fixed
Min/Max window

dsdt.dsl  2138: 0x0F00, // Length
Error4118 -  ^ Length is not equal to fixed
Min/Max window

Is there any other information that would be useful in finding out why the CPU
usage is so high?

-- Package-specific info:
** Version:
Linux version 3.1.0-1-amd64 (Debian 3.1.8-2) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Tue Jan 10 05:01:58 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/pandora-root ro quiet

** Not tainted

** Kernel log:
[5.369898] ATOM BIOS: Lenovo
[5.369958] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[5.369962] radeon :01:00.0: GTT: 512M 0x4000 - 
0x5FFF
[5.377902] iwlagn :03:00.0: device EEPROM VER=0x15d, CALIB=0x6
[5.377906] iwlagn :03:00.0: Device SKU: 0X50
[5.377909] iwlagn :03:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3
[5.381232] iwlagn :03:00.0: Tunable channels: 13 802.11bg, 0 802.11a 
channels
[5.381236] [drm] Detected VRAM RAM=1024M, BAR=256M
[5.381239] [drm] RAM width 128bits DDR
[5.381294] [TTM] Zone  kernel: Available graphics memory: 4089264 kiB.
[5.381296] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB.
[5.381298] [TTM] Initializing pool allocator.
[5.381323] [drm] radeon: 1024M of VRAM memory ready
[5.381325] [drm] radeon: 512M of GTT memory ready.
[5.381342] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[5.381344] [drm] Driver supports precise vblank timestamp query.
[5.381355] iwlagn :03:00.0: RF_KILL bit toggled to disable radio.
[5.381434] radeon :01:00.0: irq 44 for MSI/MSI-X
[5.381442] radeon :01:00.0: radeon: using MSI.
[5.381489] [drm] radeon: irq initialized.
[5.381495] [drm] GART: num cpu pages 131072, num gpu pages 131072
[5.382093] [drm] Loading REDWOOD Microcode
[5.386113] iwlagn :03:00.0: loaded firmware version 39.31.5.1 build 
35138
[5.386225] Registered led device: phy0-led
[5.389763] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[5.393030] radeon :01:00.0: WB enabled
[5.398958] input: Ideapad extra buttons as 
/devices/platform/ideapad/input/input8
[5.409318] [drm] ring test succeeded in 1 usecs
[5.409449] [drm] radeon: ib pool ready.
[5.409515] [drm] ib test succeeded in 0 usecs
[5.409521] failed to evaluate ATIF got AE_BAD_PARAMETER
[5.409913] [drm] Radeon Display Connectors
[5.409916] [drm] Connector 0:
[5.409918] [drm]   LVDS
[5.409921] [drm]   DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 
0x656c
[5.409923] [drm]   Encoders:
[5.409925] [drm] LCD1: INTERNAL_UNIPHY
[5.409927] [drm] Connector 1:
[5.409929] [drm]   HDMI-A
[5.409931] [drm]   HPD1
[5.409934] [drm]   DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 
0x643c
[5.409936] [drm]   Encoders:
[5.409938] [drm] DFP1: INTERNAL_UNIPHY1
[5.409940] [drm] Connector 2:
[5.409942] [drm]   VGA
[5.409945] [drm]   DDC: 0x64d8 0x64d8 0x64dc 0x64dc 0x64e0 0x64e0 0x64e4 
0x64e4
[5.409947] [drm]   Encoders:
[5.409949] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[5.419121] hda_codec: ALC272: BIOS auto-probing.
[5.420993] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input9
[5.423385] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input10
[5.423457] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input11
[5.791097] input: PS/2 Generic Mouse as 
/devices/platform/i8042/serio3/input/input12
[5.890320] [drm] Radeon display connector LVDS-1: No monitor connected or 
invalid EDID
[5.902185] [drm] Radeon display connector HDMI-A-1: No monitor connected or 

Bug#604115: latex-beamer: Beamer version is old

[James Tocknell]

Package: latex-beamer
Version: 3.07-2
Severity: wishlist

The version of beamer in Debian is old, newer versions can be found at
http://bitbucket.org/rivanvx/beamer/downloads.



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 
'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages latex-beamer depends on:
ii  latex-xcolor  2.11-1 Easy driver-independent TeX class 
ii  pgf   2.00-1 TeX Portable Graphic Format
ii  texlive-latex-base2009-11TeX Live: Basic LaTeX packages

latex-beamer recommends no packages.

latex-beamer 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#600547: python-scipy: Scipy Documentation not in Debian

[James Tocknell]

Package: python-scipy
Version: 0.7.2+dfsg1-1
Severity: normal

Debian does not include the html/pdf documentation on the Scipy website
(http://docs.scipy.org/doc/). The docstring of the package also says the module
docs can be found at /usr/share/doc/python2.6/html/library/scipy.html, which
they cannot.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 
'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-scipy depends on:
ii  libamd2.2.0  1:3.4.0-2   approximate minimum degree orderin
ii  libatlas3gf-base [liblapack. 3.8.3-27Automatically Tuned Linear Algebra
ii  libc62.11.2-6Embedded GNU C Library: Shared lib
ii  libgcc1  1:4.4.5-3   GCC support library
ii  libgfortran3 4.4.5-3 Runtime library for GNU Fortran ap
ii  libstdc++6   4.4.5-3 The GNU Standard C++ Library v3
ii  libumfpack5.4.0  1:3.4.0-2   sparse LU factorization library
ii  python   2.6.6-3 interactive high-level object-orie
ii  python-central   0.6.16+nmu1 register and build utility for Pyt
ii  python-numpy 1:1.4.1-5   Numerical Python adds a fast array

Versions of packages python-scipy recommends:
ii  g++ [c++-compiler]4:4.4.5-1  The GNU C++ compiler
ii  g++-4.4 [c++-compiler]4.4.5-3The GNU C++ compiler

Versions of packages python-scipy suggests:
pn  python-profiler   none (no description available)

-- 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#596029: fluxbox: Restart only quits, not restart

[James Tocknell]

Fluxbox appears to work now with the newest update.

James

On Wed, Sep 8, 2010 at 4:03 PM, James Tocknell aragi...@gmail.com wrote:

 I've checked the menu settings, yes it should restart, also I tried
 restarting fluxbox via fluxbox-remote, it also caused fluxbox to quit.

 I attached the log output with verbose on. (fluxbox -verbose -log
 /home/aragilar/.log/fluxbox.log)

 Also, something I noticed when trying to get fluxbox to restart properly is
 that gdm doesn't load again on Ctrl-Alt-7 again, it moves to Ctrl-Alt-8
 (repeated restarts still leave it on Ctrl-Alt-8), and Ctrl-Alt-7 becomes
 blank.

 James


 On Wed, Sep 8, 2010 at 2:07 PM, Paul Tagliamonte paul...@ubuntu.comwrote:

 I can't reproduce this, are you sure your menu is setup right?

 Perhaps you can debug the issue, and get a trace / dump?

 Thanks,
 Paul

 On Tue, Sep 7, 2010 at 10:58 PM, James Tocknell aragi...@gmail.com
 wrote:
  Package: fluxbox
  Version: 1.1.1+dfsg2-1
  Severity: normal
 
  The new version of Fluxbox (1.1.1+git20100807.0cc08f9-1), breaks the
 restart
  functionality. Instead, it quits when restart is selcted in the menu and
 using a
  keyboard shortcut in the keys file.
 
  -- System Information:
  Debian Release: squeeze/sid
   APT prefers testing-proposed-updates
   APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500,
 'testing'), (1, 'experimental')
  Architecture: i386 (i686)
 
  Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
  Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /bin/dash
 
  Versions of packages fluxbox depends on:
  ii  libc6   2.11.2-5 Embedded GNU C Library:
 Shared lib
  ii  libfontconfig1  2.8.0-2.1generic font configuration
 library
  ii  libfreetype62.4.2-2  FreeType 2 font engine,
 shared lib
  ii  libgcc1 1:4.4.4-13   GCC support library
  ii  libice6 2:1.0.6-1X11 Inter-Client Exchange
 library
  ii  libimlib2   1.4.2-8+b2   powerful image loading and
 renderi
  ii  libsm6  2:1.1.1-1X11 Session Management
 library
  ii  libstdc++6  4.4.4-13 The GNU Standard C++
 Library v3
  ii  libx11-62:1.3.3-3X11 client-side library
  ii  libxext62:1.1.2-1X11 miscellaneous extension
 librar
  ii  libxft2 2.1.14-2 FreeType-based font drawing
 librar
  ii  libxinerama12:1.1-3  X11 Xinerama extension
 library
  ii  libxpm4 1:3.5.8-1X11 pixmap library
  ii  libxrandr2  2:1.3.0-3X11 RandR extension library
  ii  libxrender1 1:0.9.6-1X Rendering Extension
 client libra
  ii  menu2.1.44   generates programs menu for
 all me
  ii  zlib1g  1:1.2.3.4.dfsg-3 compression library -
 runtime
 
  Versions of packages fluxbox recommends:
  ii  xfonts-terminus   4.30-2 Fixed-width fonts for fast
 reading
 
  Versions of packages fluxbox suggests:
  pn  fbdesknone (no description available)
  pn  fbpager   none (no description available)
  pn  fluxconf  none (no description available)
 
  -- no debconf information
 
 
 
 



 --
 #define sizeof(x) rand()
 :wq




 --
 Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It
 isn't good enough for Tim 
 Berners-Leehttp://opendotdotdot.blogspot.com/2010/04/rms-and-tim-berners-lee-separated-at.html,
 and it isn't good enough for me either. For more information visit
 http://www.gnu.org/philosophy/no-word-attachments.html.

 Truly great madness cannot be achieved without significant intelligence.
  - Henrik Tikkanen

 If you're not messing with your sanity, you're not having fun.
  - James Tocknell

 In theory, there is no difference between theory and practice; In practice,
 there is.




-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It
isn't good enough for Tim
Berners-Leehttp://opendotdotdot.blogspot.com/2010/04/rms-and-tim-berners-lee-separated-at.html,
and it isn't good enough for me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In practice,
there is.

Bug#596029: fluxbox: Restart only quits, not restart

[James Tocknell]

I've checked the menu settings, yes it should restart, also I tried
restarting fluxbox via fluxbox-remote, it also caused fluxbox to quit.

I attached the log output with verbose on. (fluxbox -verbose -log
/home/aragilar/.log/fluxbox.log)

Also, something I noticed when trying to get fluxbox to restart properly is
that gdm doesn't load again on Ctrl-Alt-7 again, it moves to Ctrl-Alt-8
(repeated restarts still leave it on Ctrl-Alt-8), and Ctrl-Alt-7 becomes
blank.

James

On Wed, Sep 8, 2010 at 2:07 PM, Paul Tagliamonte paul...@ubuntu.com wrote:

 I can't reproduce this, are you sure your menu is setup right?

 Perhaps you can debug the issue, and get a trace / dump?

 Thanks,
 Paul

 On Tue, Sep 7, 2010 at 10:58 PM, James Tocknell aragi...@gmail.com
 wrote:
  Package: fluxbox
  Version: 1.1.1+dfsg2-1
  Severity: normal
 
  The new version of Fluxbox (1.1.1+git20100807.0cc08f9-1), breaks the
 restart
  functionality. Instead, it quits when restart is selcted in the menu and
 using a
  keyboard shortcut in the keys file.
 
  -- System Information:
  Debian Release: squeeze/sid
   APT prefers testing-proposed-updates
   APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500,
 'testing'), (1, 'experimental')
  Architecture: i386 (i686)
 
  Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
  Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /bin/dash
 
  Versions of packages fluxbox depends on:
  ii  libc6   2.11.2-5 Embedded GNU C Library:
 Shared lib
  ii  libfontconfig1  2.8.0-2.1generic font configuration
 library
  ii  libfreetype62.4.2-2  FreeType 2 font engine,
 shared lib
  ii  libgcc1 1:4.4.4-13   GCC support library
  ii  libice6 2:1.0.6-1X11 Inter-Client Exchange
 library
  ii  libimlib2   1.4.2-8+b2   powerful image loading and
 renderi
  ii  libsm6  2:1.1.1-1X11 Session Management
 library
  ii  libstdc++6  4.4.4-13 The GNU Standard C++ Library
 v3
  ii  libx11-62:1.3.3-3X11 client-side library
  ii  libxext62:1.1.2-1X11 miscellaneous extension
 librar
  ii  libxft2 2.1.14-2 FreeType-based font drawing
 librar
  ii  libxinerama12:1.1-3  X11 Xinerama extension
 library
  ii  libxpm4 1:3.5.8-1X11 pixmap library
  ii  libxrandr2  2:1.3.0-3X11 RandR extension library
  ii  libxrender1 1:0.9.6-1X Rendering Extension client
 libra
  ii  menu2.1.44   generates programs menu for
 all me
  ii  zlib1g  1:1.2.3.4.dfsg-3 compression library -
 runtime
 
  Versions of packages fluxbox recommends:
  ii  xfonts-terminus   4.30-2 Fixed-width fonts for fast
 reading
 
  Versions of packages fluxbox suggests:
  pn  fbdesknone (no description available)
  pn  fbpager   none (no description available)
  pn  fluxconf  none (no description available)
 
  -- no debconf information
 
 
 
 



 --
 #define sizeof(x) rand()
 :wq




-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It
isn't good enough for Tim
Berners-Leehttp://opendotdotdot.blogspot.com/2010/04/rms-and-tim-berners-lee-separated-at.html,
and it isn't good enough for me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In practice,
there is.
--
Log File: /home/aragilar/.log/fluxbox.log
Fluxbox version: git
GIT Revision: 0cc08f90d2d46b6467e06e16bb3d4c740b6c2cc5
Compiled: Aug 13 2010 02:55:05
Compiler: GCC
Compiler version: 4.4.4

Defaults:
menu: /etc/X11/fluxbox/fluxbox.menu-user
   style: /usr/share/fluxbox/styles/debian_dark
keys: /etc/X11/fluxbox/keys
init: /etc/X11/fluxbox/init
nls: /usr/share/fluxbox/nls

Compiled options (- = disabled): 
-DEBUG
EWMH
GNOME
IMLIB2
NLS
REMEMBER
RENDER
SHAPE
SLIT
TOOLBAR
XFT
XINERAMA
XMB
XPM

--
Failed to read theme item: window.label.focus
Failed to read theme item: window.title.focus
Failed to read theme item: window.button.focus
Failed to read theme item: window.button.pressed
Failed to read theme item: window.button.focus.picColor
Failed to read theme item: window.roundCorners
Failed to read theme item: window.label.unfocus
Failed to read theme item: window.title.unfocus
Failed to read theme item: window.button.unfocus
Failed to read theme item: window.button.pressed
Failed to read theme item: window.button.unfocus.picColor

Bug#596029: fluxbox: Restart only quits, not restart

[James Tocknell]

Package: fluxbox
Version: 1.1.1+dfsg2-1
Severity: normal

The new version of Fluxbox (1.1.1+git20100807.0cc08f9-1), breaks the restart
functionality. Instead, it quits when restart is selcted in the menu and using a
keyboard shortcut in the keys file.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 
'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages fluxbox depends on:
ii  libc6   2.11.2-5 Embedded GNU C Library: Shared lib
ii  libfontconfig1  2.8.0-2.1generic font configuration library
ii  libfreetype62.4.2-2  FreeType 2 font engine, shared lib
ii  libgcc1 1:4.4.4-13   GCC support library
ii  libice6 2:1.0.6-1X11 Inter-Client Exchange library
ii  libimlib2   1.4.2-8+b2   powerful image loading and renderi
ii  libsm6  2:1.1.1-1X11 Session Management library
ii  libstdc++6  4.4.4-13 The GNU Standard C++ Library v3
ii  libx11-62:1.3.3-3X11 client-side library
ii  libxext62:1.1.2-1X11 miscellaneous extension librar
ii  libxft2 2.1.14-2 FreeType-based font drawing librar
ii  libxinerama12:1.1-3  X11 Xinerama extension library
ii  libxpm4 1:3.5.8-1X11 pixmap library
ii  libxrandr2  2:1.3.0-3X11 RandR extension library
ii  libxrender1 1:0.9.6-1X Rendering Extension client libra
ii  menu2.1.44   generates programs menu for all me
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages fluxbox recommends:
ii  xfonts-terminus   4.30-2 Fixed-width fonts for fast reading

Versions of packages fluxbox suggests:
pn  fbdesknone (no description available)
pn  fbpager   none (no description available)
pn  fluxconf  none (no description available)

-- 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#568972: python-vte: No support for python2.6

[James Tocknell]

Package: python-vte
Version: 1:0.22.5-1+b1
Severity: important

The library does not support python2.6.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 
'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-vte depends on:
ii  libatk1.0-0   1.28.0-1   The ATK accessibility toolkit
ii  libc6 2.10.2-2   GNU C Library: Shared libraries
ii  libcairo2 1.8.8-2The Cairo 2D vector graphics libra
ii  libfontconfig12.8.0-2generic font configuration library
ii  libfreetype6  2.3.11-1   FreeType 2 font engine, shared lib
ii  libglib2.0-0  2.22.4-1   The GLib library of C routines
ii  libgtk2.0-0   2.18.6-1   The GTK+ graphical user interface 
ii  libncurses5   5.7+20090803-2 shared libraries for terminal hand
ii  libpango1.0-0 1.26.2-1   Layout and rendering of internatio
ii  libvte9   1:0.22.5-1+b1  Terminal emulator widget for GTK+ 
ii  python2.5.4-9An interactive high-level object-o
ii  python-gtk2   2.16.0-2   Python bindings for the GTK+ widge
ii  python-support1.0.6  automated rebuilding support for P

python-vte recommends no packages.

python-vte 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#541334: python-doc: In contrib, but no non-free dependencies

[James Tocknell]

Package: python-doc
Severity: important

python-doc, and the packages it points to, are all in contrib, but their 
dependencies are in main, not non-free.

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



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