Bug#717547: nfs-common: simple remount returns an error

[J. R. Okajima]

Package: nfs-common
Version: 1:1.2.6-4
Severity: normal

Dear Maintainer,

I met a strange behavour of mount.nfs.
When I run "mount -o remount /nfs/mntpnt", it terminated silently but
the exit status was 32. Actually when I add "-v" option, it prints
"mount.nfs: mount(2): Invalid argument".

Here is what I did.

$ mkdir /tmp/4751.exp /tmp/4751.mnt
$ sudo exportfs -i -o rw,async,no_subtree_check,no_root_squash 
localhost:/tmp/4751.exp
$ sudo exportfs -f
$ sudo mount -t nfs -o intr,nfsvers=3 localhost:/tmp/4751.exp /tmp/4751.mnt
$ sudo mount -o remount /tmp/4751.mnt
(silently terminates)

$ sudo mount -v -o remount /tmp/4751.mnt
mount.nfs: mount(2): Invalid argument

I expect such simple remount causes VFS to flush the caches on that
filesystem. Actually older Debian (at least v5 lenny) surely
worked. Upgrading to v7 (wheezy), then mount.nfs retuns an error.


-- Package-specific info:
-- rpcinfo --
   program vers proto   port
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  42522  status
1000241   tcp  34284  status
1000211   udp  39173  nlockmgr
1000213   udp  39173  nlockmgr
1000214   udp  39173  nlockmgr
1000211   tcp  60767  nlockmgr
1000213   tcp  60767  nlockmgr
1000214   tcp  60767  nlockmgr
132   tcp   2049  nfs
133   tcp   2049  nfs
134   tcp   2049  nfs
1002272   tcp   2049
1002273   tcp   2049
132   udp   2049  nfs
133   udp   2049  nfs
134   udp   2049  nfs
1002272   udp   2049
1002273   udp   2049
151   udp  51129  mountd
151   tcp  58113  mountd
152   udp  51458  mountd
152   tcp  34458  mountd
153   udp  47395  mountd
153   tcp  9  mountd
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
jrosysadm:/sysadm /sysadm   nfs ro,soft,intr,bg,proto=udp   0 3
jroproj:/proj   /proj   nfs ro,soft,intr,bg,proto=udp   0 3
jroproj:/proj/aufs /proj/aufs   nfs ro,soft,intr,bg,proto=udp   0 3
jroproj:/proj/open-e /proj/open-e nfs   ro,soft,intr,bg,proto=udp   0 3
jrosrc:/src /srcnfs ro,soft,intr,bg,proto=udp   0 3
jrosrc:/src/linux-2.6 /src/linux-2.6 nfs ro,soft,intr,bg,proto=udp  0 3
-- /proc/mounts --
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
jrosysadm:/sysadm /sysadm nfs 
ro,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,soft,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.1.4,mountvers=3,mountport=46065,mountproto=udp,local_lock=none,addr=192.168.1.4
 0 0
jroproj:/proj /proj nfs 
ro,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,soft,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.1.6,mountvers=3,mountport=46065,mountproto=udp,local_lock=none,addr=192.168.1.6
 0 0
jroproj:/proj/aufs /proj/aufs nfs 
ro,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,soft,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.1.6,mountvers=3,mountport=46065,mountproto=udp,local_lock=none,addr=192.168.1.6
 0 0
jroproj:/proj/open-e /proj/open-e nfs 
ro,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,soft,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.1.6,mountvers=3,mountport=46065,mountproto=udp,local_lock=none,addr=192.168.1.6
 0 0
jrosrc:/src /src nfs 
ro,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,soft,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.1.7,mountvers=3,mountport=46065,mountproto=udp,local_lock=none,addr=192.168.1.7
 0 0
jrosrc:/src/linux-2.6 /src/linux nfs 
ro,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,soft,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.1.7,mountvers=3,mountport=46065,mountproto=udp,local_lock=none,addr=192.168.1.7
 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
localhost:/tmp/4751.exp /tmp/4751.mnt nfs 
rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=127.0.0.1,mountvers=3,mountport=47395,mountproto=udp,local_lock=none,addr=127.0.0.1
 0 0

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

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

Versions of packages nfs-common depends on:
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-41
ii  libc6   2.13-38
ii  libcap2 1:2.22-1.2
ii  libcomerr2  1.42.5-1.1
ii  libdevmapper1

Bug#717546: Wrong VCS fields

[Thomas Goirand]

Package: python-mimeparse
Version: 0.1.3-6
Severity: normal

Hi,

The current VCS fields for python-mimeparse are:

Vcs-Browser: 
http://git.fsinf.at/apt/restauth/trees/master/python-mimeparse-0.1.3
Vcs-Git: http://git.fsinf.at/apt/restauth.git

The first one leads to a 404 page not found. Both are wrong and pointing
to restauth instead of mimeparse anyway. Please fix it.

Cheers,

Thomas Goirand (zigo)


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

Bug#717545: libgmp3c2: Missing in wheezy, which causes some 3rd party programs to fail

[Petr Pudlak]

Package: libgmp3c2
Version: 2:4.3.2+dfsg-1
Severity: normal

After upgrading to wheezy, my installation of Glasgow Haskell Compiler
stopped working. Neither it was possible to reinstall it, the installer
was unable to start. The problem was caused by missing libgmp3c2.

Workaround: Install an old version of the package from squeeze. After
installing it, GHC works again.

I suppose that since the package is included in sid, it's only a bug
that it's missing in wheezy.

Suggested solutions:

- Add libgmp3c2 to wheezy.
- Suggest a how to run programs that were compiled on sqeeze and expect
  the package on wheezy.

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

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

Versions of packages libgmp3c2 depends on:
ii  libc6  2.13-38

libgmp3c2 recommends no packages.

libgmp3c2 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#717544: CVE-2013-2207: pt_chown

[Moritz Muehlenhoff]

Package: libc-bin
Severity: important
Tags: security

Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-2207


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

Bug#717543: mediawiki-extensions-math: Math.php should use full

[Nye Liu]

Package: mediawiki-extensions-math
Version: 2:1.0+git20120528-7
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Latest apache2/php5 requires long 


-- 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#706605: Processed: tagging as pending bugs that are closed by packages in NEW

[Y Giridhar Appaji Nag]

# Bcc: control
tags 706607 - pending
thanks

On 13/07/21 08:09 +, Debian Bug Tracking System said ...
> Processing commands for cont...@bugs.debian.org:
> 
> > # Sunday 21 July  08:04:31 UTC 2013
> > # Tagging as pending bugs that are closed by packages in NEW
> > # http://ftp-master.debian.org/new.html
> > #
> > # Source package in NEW: macfanctld
> > tags 706607 + pending
> Bug #706607 [dput] dput: Invalid warning about orig tarball not being required
> Added tag(s) pending.

The macfanctld package in NEW closes the incorrect bug.  It should be
706605 and not 706607.

Giridhar

-- 
Y Giridhar Appaji Nag | http://people.debian.org/~appaji/


signature.asc
Description: Digital signature

Bug#604560: bts

[Daniel Baumann]

close 604560 3:4.06
thanks

this has been fixed in above version, closing.
-- 

Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


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

Bug#624509: does only send CR LF . instead of CR LF . CR LF on end of smtp transfer

[Erik Thiele]

Hello Carsten,

Am Sun, 21 Jul 2013 10:32:25 +0200
schrieb Carsten Schoenert :

> On Fri, Apr 29, 2011 at 08:55:32AM +0200, Erik Thiele wrote:
> > Package: icedove
> > Version: 3.0.11-1+squeeze1
> > ...
> 
> sounds strange. What about that error with recent versions? Can you
> please recheck that bahaviour?
> What mail server you are working with?
> 
> If you need some help in debugging there hopefully some useful info in
> the wiki [1].
> I think this is no Debian specific problem so maybe there is a already
> open bug in the Mozilla Bugzilla [2]. If you find a opened bug for
> that (or you are willing open up a new bug) please provide the URI to
> it so we can link this together.
> 
> [1] https://wiki.debian.org/Icedove#Debugging
> [2] https://bugzilla.mozilla.org/

I did not have this problem for a long time now. Probably it was
somehow fixed. It's strange that I was the only person to get into this
trouble. Probably you should close this bug then.


Regards
Erik


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

Bug#717542: ITP: python-shortuuid -- generates concise, unambiguous, URL-safe UUIDs

[Kouhei Maeda]

Package: wnpp
Severity: wishlist
Owner: Kouhei Maeda 

* Package name: python-shortuuid
  Version : 0.3
  Upstream Author : Stochastic Technologies
* URL : https://github.com/stochastic-technologies/shortuuid/
* License : BSD
  Programming Lang: Python
  Description : generates concise, unambiguous, URL-safe UUIDs

 Often, one needs to use non-sequential IDs in places where users will see them,
 but the IDs must be as concise and easy to use as possible. shortuuid solves
 this problem by generating uuids using Python's built-in uuid module and then
 translating them to base57 using lowercase and uppercase letters and digits,
 and removing similar-looking characters such as l, 1, I, O and 0.


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

Bug#717150:

[Johnw Qxi]

No one have this problem? only me?
Please help, thanks.

Bug#666076: iozone3: new upstream version avilable

[Steve M. Robbins]

On July 22, 2013 04:43:57 AM Christoph Anton Mitterer wrote:
> Again... much newer upstream version (3.420)... has this package been
> orphaned?

No, it hasn't been orphaned.  But I am guilty of ignoring it for long 
stretches.  So I appreciate this polite reminder.

I would welcome collaborators / co-maintainers!

 
> btw: Is there any reason for not changing to the version numbers used by
> upstream, i.e. package name "iozone" (without 3) and version number,
> e.g. 3.420?

I don't know the history of the name / numbering convention.  I inherited it.  
I can't recall anyone asking about this before but I don't suppose there's 
anything stopping us from changing.

Cheers,
-Steve


signature.asc
Description: This is a digitally signed message part.

Bug#715804: Debian policy for web apps still references /doc as accessible

[Jonathan Nieder]

Charles Plessy wrote:

> On my side, I think that the current practice is not to serve /doc by default,
> and I therefore second the proposition of Thomas to remove point 2 of chapter
> 11.5.
>
> Are there other seconds or objections ?

Seconded.

Thanks,
Jonathan


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

Bug#717332: please create a debian-cross ML

[Siddharth Heroor]

I would subscribe to such a list.

-- 
Sid

Bug#717364: ninja-build: FTBFS on non-Linux: option --platform: invalid choice

[Gary Kramlich]

Upstream accepted a patch for kfreebsd8 before, but wasn't exactly happy,
I'm working on a fix right now.


On Fri, Jul 19, 2013 at 2:14 PM, Aaron M. Ucko  wrote:

> Source: ninja-build
> Version: 1.3.4-1.1
> Severity: serious
> Justification: fails to build from source (but built successfully in the
> past)
>
> Thanks for addressing #716885 promptly.  Alas, ninja-build is still
> running into trouble on kFreeBSD and the Hurd.  Specifically, the Hurd
> build fails with
>
>   configure.py: error: option --platform: invalid choice: 'gnu0' (choose
> from 'linux', 'darwin', 'freebsd', 'openbsd', 'solaris', 'sunos5', 'mingw',
> 'msvc', 'gnukfreebsd8')
>
> and the kFreeBSD builds similarly fail with
>
>   configure.py: error: option --platform: invalid choice: 'gnukfreebsd9'
> (choose from 'linux', 'darwin', 'freebsd', 'openbsd', 'solaris', 'sunos5',
> 'mingw', 'msvc', 'gnukfreebsd8')
>
> Could you please take a look?
>
> Thanks, and sorry for not catching it earlier.
>

Bug#717540: [Pkg-systemd-maintainers] Bug#717540: systemd: Please install zsh completion

[Michael Biebl]

Hi,

Am 22.07.2013 05:16, schrieb Felipe Sateler:
> Systemd ships a zsh completion file, it would be great if systemd
> installed it.
> 
> zsh does have a systemd completion file but it is not really up to par,
> the provided one seems better.

How exactly does zsh completion work? Where would this file have to be
installed? If zsh itself already provides a completion file for sytemd,
would those two conflict? And would that mean, it has to be removed from
zsh first?

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#717541: Please stop shipping udevadm completion file

[Michael Biebl]

Package: bash-completion
Version: 1:2.0-1
Severity: normal

Hi,

udev/systemd upstream ships a completion file for udevadm [1] which is
much more complete then the one provided by bash-completion.

Please consider stopping to install the udevadm completion file in
bash-completion, so we can provide it within the udev package.

Thanks,
Michael

[1] 
http://cgit.freedesktop.org/systemd/systemd/tree/shell-completion/bash/udevadm

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

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

Versions of packages bash-completion depends on:
ii  bash  4.2+dfsg-1
ii  dpkg  1.16.10

bash-completion recommends no packages.

bash-completion 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#717537: youtube-dl: encrypted signature length 85 failure (42.42)

[Rogério Brito]

Hi, Clint.

On Sun, Jul 21, 2013 at 11:39 PM, Clint Adams  wrote:
> Package: youtube-dl
> Version: 2013.07.10-1

Now that the previous version of youtube-dl has migrated to testing, I
will upload a new version to sid (checking first if the new version
fixes this).

I see that there's been a lot of work upstream with signatures (the
signatures are really trivial, but way too numerous, unfortunately).


Thanks,

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br


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

Bug#715730: [Mayhem] Bug report on nagios-plugins-basic: check_by_ssh crashes with exit status 139

[Jim Barber]

I believe the problem is caused by the 'fix' to bug 709297.
The package maintainer has tried to introduce the ability to pass parameters
to Nagios checks by changing them from:

command_line/usr/lib/nagios/plugins/check_ssh '$HOSTADDRESS$'

to:

command_line/usr/lib/nagios/plugins/check_ssh '$HOSTADDRESS$' '$ARG1$'

If no extra arguments are passed, it forces an empty parameter to be passed
to the command which causes a problem.

I suspect the fix it not to wrap the $ARG1$ within quotes like so:

command_line/usr/lib/nagios/plugins/check_ssh '$HOSTADDRESS$' $ARG1$

This means the parameters passed by the user can still be done, but if nothing 
was
passed, does not result in an empty positional parameter being passed to the 
command.

Regards,

Jim Barber


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

Bug#717540: systemd: Please install zsh completion

[Felipe Sateler]

Package: systemd
Version: 204-1
Severity: wishlist

Systemd ships a zsh completion file, it would be great if systemd
installed it.

zsh does have a systemd completion file but it is not really up to par,
the provided one seems better.

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

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

Versions of packages systemd depends on:
ii  initscripts  2.88dsf-43
ii  libacl1  2.2.52-1
ii  libaudit01:1.7.18-1.1
ii  libc62.17-7
ii  libcap2  1:2.22-1.2
ii  libcryptsetup4   2:1.6.1-1
ii  libdbus-1-3  1.6.12-1
ii  libgcrypt11  1.5.2-3
ii  libkmod2 9-3
ii  liblzma5 5.1.1alpha+20120614-2
ii  libpam0g 1.1.3-9
ii  libselinux1  2.1.13-2
ii  libsystemd-daemon0   204-1
ii  libsystemd-journal0  204-1
ii  libudev1 204-1
ii  libwrap0 7.6.q-24
ii  udev 204-1
ii  util-linux   2.20.1-5.5

Versions of packages systemd recommends:
ii  libpam-systemd  204-1

Versions of packages systemd suggests:
pn  systemd-ui  

-- 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#717539: empathy: Don't build-depend on gnome-doc-utils

[Jeremy Bicha]

Source: empathy
Version: 3.8.3-1
Severity: minor
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy

Please drop gnome-doc-utils from Build-Depends since it has been
replaced by yelp-tools.

Thanks,
Jeremy

- -- System Information:
Debian Release: wheezy/sid
  APT prefers saucy-updates
  APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500,
'raring'), (100, 'saucy-backports')


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

Bug#717533: ratpoints: FTBFS: error: You need the GMP headers to compile ratpoints

[Steve M. Robbins]

On July 21, 2013 09:55:43 PM Aaron M. Ucko wrote:
> Source: ratpoints
> Version: 2.1.3+dfsg-1
> Severity: serious
> Justification: fails to build from source
> 
> Builds of ratpoints in minimal environments (as on the autobuilders)
> have been failing:
> 
>   checking for GMP includes in /usr/include/... not found
>   configure: error: You need the GMP headers to compile ratpoints

In addition to Aaron's suggestions, note also that Debian recently moved the 
headers into the multi-arch friendly location /usr/include/${arch}.  You may 
need to adjust the configure script to locate it.

-Steve



signature.asc
Description: This is a digitally signed message part.

Bug#717538: ITP: python-django-oauth-plus -- Support of OAuth 1.0a in Django using python-oauth2

[Kouhei Maeda]

Package: wnpp
Severity: wishlist
Owner: Kouhei Maeda 

* Package name: python-django-oauth-plus
  Version : 2.1.2
  Upstream Author : David Larlet 
* URL : http://code.larlet.fr/django-oauth-plus/
* License : BSD
  Programming Lang: Python
  Description : Support of OAuth 1.0a in Django using python-oauth2

 The OAuth protocol enables websites or applications (Consumers) to access
 Protected Resources from a web service (Service Provider) via an API, without
 requiring Users to disclose their Service Provider credentials to the
 Consumers. More generally, OAuth creates a freely-implementable and generic
 methodology for API authentication.


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

Bug#666076: iozone3: new upstream version avilable

[Christoph Anton Mitterer]

Again... much newer upstream version (3.420)... has this package been
orphaned?

btw: Is there any reason for not changing to the version numbers used by
upstream, i.e. package name "iozone" (without 3) and version number,
e.g. 3.420?


Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Bug#717537: youtube-dl: encrypted signature length 85 failure (42.42)

[Clint Adams]

Package: youtube-dl
Version: 2013.07.10-1

[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-v', '-t', 
'http://www.youtube.com/watch?v=k7AoPQUBees']
[debug] youtube-dl version 2013.07.10
[debug] Python version 2.7.5+ - Linux-3.9-1-amd64-x86_64-with-debian-jessie-sid
[debug] Proxy map: {}
[youtube] Setting language
[youtube] k7AoPQUBees: Downloading video webpage
[youtube] k7AoPQUBees: Downloading video info webpage
[youtube] k7AoPQUBees: Extracting video information
[youtube] k7AoPQUBees: Encrypted signatures detected.
[youtube] encrypted signature length 85 (42.42), itag 37, html5 player vflSAFCP9
[youtube] encrypted signature length 85 (42.42), itag 22, html5 player vflSAFCP9
[youtube] encrypted signature length 85 (42.42), itag 35, html5 player vflSAFCP9
[youtube] encrypted signature length 85 (42.42), itag 43, html5 player vflSAFCP9
[youtube] encrypted signature length 85 (42.42), itag 34, html5 player vflSAFCP9
[youtube] encrypted signature length 85 (42.42), itag 18, html5 player vflSAFCP9
[youtube] encrypted signature length 85 (42.42), itag 5, html5 player vflSAFCP9
[youtube] encrypted signature length 85 (42.42), itag 36, html5 player vflSAFCP9
[youtube] encrypted signature length 85 (42.42), itag 17, html5 player vflSAFCP9
ERROR: unable to download video


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

Bug#717536: phoronix-test-suite: installs software from outside debian

[Christoph Anton Mitterer]

Package: phoronix-test-suite
Version: 4.6.0-1
Severity: critical
Tags: security
Justification: root security hole


Hi.

The only way to operate PTS seems to be by installing the respective tests
from OpenBenchmarking.org, right?

Given that this introduces completely unchecked and untrusted software, for
which moreover no security support is covered by Debian,... this package
should IMHO give big warnings about that fact, at least:
- in the package description
and-
- in a debconf dialogue.


Marking as root security hole, even though the software runs probably as
normal user, but such remote software could expoloit any further local security
hole.


Cheers,
Chris.


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

Bug#717535: phoronix-test-suite: new upstream version

[Christoph Anton Mitterer]

Package: phoronix-test-suite
Version: 4.6.0-1
Severity: wishlist


Hi.

A new upstream version (4.6.1) is available.

Cheers,
Chris.


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

Bug#713783: Bug #713783 ns3: FTBFS: build hangs

[Aron Xu]

Control: severity -1 normal

Hi,

I cannot reproduce this problem on the server we used to build the
package, it has 12 cpu cores and x2 by multithreading. The test build
is paralleled and suceeded. It is know that building ns3 eats up lots
of memory and needs quite some time, this could be the problem of
failing the build.

-- 
Regards,
Aron Xu


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

Bug#717476: phpmyadmin: breaks apache starting with invalid config file

[Norbert Preining]

reassign 717476 apache2
retitle 717476 updates lost Alias modules
severity 717476 important
thanks

On So, 21 Jul 2013, Thijs Kinkhorst wrote:
> > recently I realized that apache does not start anymore, doing the
> > suggested configtest I get:
> >
> > $ env -i LANG=C PATH=/usr/local/bin:/usr/bin:/bin /usr/sbin/apache2ctl
> > configtest
> > AH00526: Syntax error on line 3 of
> > /etc/apache2/conf-enabled/phpmyadmin.conf:
> > Invalid command 'Alias', perhaps misspelled or defined by a module not
> > included in the server configuration
> > Action 'configtest' failed.
> > The Apache error log may have more information.
> 
> Apparently your installation does not have mod_alias enabled. Using
> mod_alias to configure web applications is the Debian webapps policy
> compliant way to do it.

Thanks, I reassign the bug.

I did not do any configuration of apache, and I guess this happened
during the upgrade 2.2 -> 2.4.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094



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

Bug#717534: partconf: Drop reiserfs support

[Cyril Brulebois]

Source: partconf
Version: 1.42
Severity: important

Hi,

since reiserfs got dropped, various d-i components need to drop support
for it. Most of the changes[1] should already be in the relevant git
repositories, but partconf still needs updating.

 1. Hopefully the documentation under doc/devel/internals in
src:debian-installer should cover most of them.

Mraw,
KiBi.


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

Bug#717533: ratpoints: FTBFS: error: You need the GMP headers to compile ratpoints

[Aaron M. Ucko]

Source: ratpoints
Version: 2.1.3+dfsg-1
Severity: serious
Justification: fails to build from source

Builds of ratpoints in minimal environments (as on the autobuilders)
have been failing:

  checking for GMP includes in /usr/include/... not found
  configure: error: You need the GMP headers to compile ratpoints

Please declare a build dependency on libgmp3-dev and confirm with
pbuilder or the like that you haven't missed any others.

Thanks!


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

Bug#717401: sosreport: fails to install: SyntaxError: invalid syntax

[Adam Stokes]

On Sat, Jul 20, 2013 at 01:54:41PM +0200, Axel Beckert wrote:
> Package: sosreport
> Version: 2.3~git20130509-1
> Severity: grave
> 
> Dear Maintainer,
> 
> sosreport fails to install on both machines where I tried to install it,
> 1x i386 and 1x amd64:
> 
> Setting up sosreport (2.3~git20130509-1) ...
>   File "/usr/lib/python2.7/dist-packages/sos/plugins/logs.py", line 35
> )]
> ^

This was fixed in commit 3abe8e91. I am pushing out an update this week that
will include that commit.

Thanks!

-- 
 _   _   
 ___| |_ ___| |_ ___ ___ 
|_ -|  _| . | '_| -_|_ -|
|___|_| |___|_,_|___|___|
adam.sto...@ubuntu.com
"Don't salt your green beans before you try them, 
 some may think you make rash decisions."


signature.asc
Description: Digital signature

Bug#717511: Kernel does not start up on Pegasos-2

[Milan Kupcevic]

Control: notfound 717511 yaboot-installer/1.1.26

On 07/21/2013 08:49 PM, Ben Hutchings wrote:

On Sun, 2013-07-21 at 20:36 -0400, Milan Kupcevic wrote:

Control: notfound -1 yaboot-installer/1.1.26

On 07/21/2013 04:55 PM, Ben Hutchings wrote:

Control: reassign -1 yaboot-installer 1.1.26

On Mon, 2013-07-22 at 00:38 +0400, Pavel Fedin wrote:
[...]

   So,  it's  not  kernel's  fault. It seems to be installer fault which
does  not generate correct vmlinuz image when not using separate /boot
partition.  vmlinux,  i  know,  is another thing. It's a "plain" image
meant to be ran from GRUB or yaboot. It cannot be run from OFW.
   So,  we  can  close  this,  probably with a notification to Installer
guys.


There is no need to close it.  I'm reassigning to the relevant part of
the installer.




The particular partition/file-system layout reported in this bug report
cannot work.

This platform does not have a boot loader at all.


Sorry, I misunderstood.

[...]

Installer correctly creates ext2 boot partition and ext4 root partition.

[...]

Then how did this go wrong?



User did not let installer to create default partition layout but 
manually created incorrect one, or installed on a previously created 
partitions and used ext4 and ext3 file-systems.


Milan


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

Bug#700064: systemd: Don't run 97-bluetooth.rules under systemd

[Michael Biebl]

The test for a running systemd has changed a little. The recommended one is
test -d /run/systemd/system.

I've updated the patch accordingly.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Description: Don't start bluetoothd directly from the udev rule under systemd
 systemd has better mechanisms to start services when hardware is
 hotplugged so we simply skip this rule when running under systemd.
 The bluetooth.service will be activated via bluetooth.target instead.
Author: Michael Biebl 
Index: bluez-4.99/scripts/bluetooth.rules.in
===
--- bluez-4.99.orig/scripts/bluetooth.rules.in	2013-02-08 01:30:34.469946744 +0100
+++ bluez-4.99/scripts/bluetooth.rules.in	2013-02-08 01:34:31.192666562 +0100
@@ -1,4 +1,6 @@
 # Run helper every time a Bluetooth device appears
 # On remove actions, bluetoothd should go away by itself
+TEST=="/run/systemd/system", GOTO="bluetooth_end"
 ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/lib/udev/bluez-udev --udev"
 ACTION=="change", SUBSYSTEM=="bluetooth", RUN+="/lib/udev/bluez-udev --udev"
+LABEL="bluetooth_end"


signature.asc
Description: OpenPGP digital signature

Bug#717511: Kernel does not start up on Pegasos-2

[Ben Hutchings]

On Sun, 2013-07-21 at 20:36 -0400, Milan Kupcevic wrote:
> Control: notfound -1 yaboot-installer/1.1.26
> 
> On 07/21/2013 04:55 PM, Ben Hutchings wrote:
> > Control: reassign -1 yaboot-installer 1.1.26
> >
> > On Mon, 2013-07-22 at 00:38 +0400, Pavel Fedin wrote:
> > [...]
> >>   So,  it's  not  kernel's  fault. It seems to be installer fault which
> >> does  not generate correct vmlinuz image when not using separate /boot
> >> partition.  vmlinux,  i  know,  is another thing. It's a "plain" image
> >> meant to be ran from GRUB or yaboot. It cannot be run from OFW.
> >>   So,  we  can  close  this,  probably with a notification to Installer
> >> guys.
> >
> > There is no need to close it.  I'm reassigning to the relevant part of
> > the installer.
> >
> 
> 
> The particular partition/file-system layout reported in this bug report 
> cannot work.
> 
> This platform does not have a boot loader at all.

Sorry, I misunderstood.

[...]
> Installer correctly creates ext2 boot partition and ext4 root partition. 
[...]

Then how did this go wrong?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Bug#714710: dpkg: when installed from live usb/cd /sbin/start-stop-daemon is empty shell script

[Edwin Fukunaga]

It looks like the usb-hdd images also have this issue.  If I boot with
the image from

 
http://live.debian.net/cdimage/release/6.0.7/amd64/usb-hdd/debian-live-6.0.7-amd64-gnome-desktop.img

then /sbin/start-stop-daemon is again empty:

 $ cat /sbin/start-stop-daemon
 #!/bin/sh

 exit 0
 $

@Emanoil: It looks like there is no .deb file for dpkg included in the
netboot or usb-hdd images.  I get no output from  find | grep dpkg ,
and the pool/main/d directory doesn't have a dpkg subdirectory.
Actually, maybe the /sbin/start-stop-daemon is being changed by
live-build, because it is the same in the image as it is after booting
(using  unsquashfs -lls filesystem.squashfs /sbin/start-stop-daemon ).

By the way, the iso-hybrid image does not seem to have this issue, at
least the gnome-desktop one from


http://live.debian.net/cdimage/release/6.0.7/amd64/iso-hybrid/debian-live-6.0.7-amd64-gnome-desktop.iso


Thanks,
Edwin



On Sun, Jul 7, 2013 at 11:44 PM, Emanoil Kotsev  wrote:
> Hi
> thanks Edwin for reporting the details on your side.
> This is exactly what I have experienced in my case and spent about 4-5h
> looking for an issue with nfs and why it is not mounting remote dir, why
> portmap was not running etc.
> I did check the current 7.x installer debian-7.1.0-amd64-netinst.iso but it
> looks ok there in the dpkg package.
> In debian-testing-amd64-businesscard.iso there is no dpkg package.
> I need to check the backup disks and usb of installation and the notes to
> find out what I have used for setting up the machine but no time left
> unfortunately. I think the machine was installed in Feb or Jan this year.
>
> @Edwin: Can you check if the included dpkg package has this inside
> /sbin/start-stop-daemon in binary, basically I'm wondering if there is a
> script somewhere which overwrites something in /sbin, which would be
> dangerous
> I mount -o loop debianiso and then  find | grep dpkg followed by mkdir
> tmp && dpkg -x dpkg...deb tmp
>
> regards
> 
> From: Guillem Jover 
> To: deloptes ; 714...@bugs.debian.org
> Cc: live-ima...@packages.debian.org
> Sent: Tuesday, July 2, 2013 11:42 AM
> Subject: Re: Bug#714710: dpkg: when installed from live usb/cd
> /sbin/start-stop-daemon is empty shell script
>
> Control: reassign -1 live-images
>
> Hi!
>
> [ I got confirmation off-list this is with official Live images, but
>   feel free to re-reassign as I don't really know what the culprit is. ]
>
> On Tue, 2013-07-02 at 08:29:19 +0200, Guillem Jover wrote:
>> On Tue, 2013-07-02 at 02:33:36 +0200, deloptes wrote:
>> > Package: dpkg
>> > Version: 1.15.8.13
>> > Severity: important
>> >
>> > When installed from live usb/cd /sbin/start-stop-daemon is empty shell
>> > script
>> > This results in strange behaviour of start/stop services like nfs
>> >
>> > I read a whole bunch of issues related to nfs (rpc.statd not running)
>> > While having another machine with same setup and nfs working I excluded
>> > the possibility of being related to some mostly discussed bugs
>> > I noticed that portmap and rpc.statd are simply not starting, because
>> > the start-stop-daemon program was an empty shells script
>> > unfortunately the version reported here was overwritten by dpkg
>> > --reinstall install dpkg, but I hope in this way that other people having
>> > similar issues with daemons not starting properly will solve it easily.
>>
>> This would be an issue with whatever Live USB/CD software you are using.
>> If that's one of the packaged solutions in Debian, then we can reassign
>> the bug report there, otherwise there's not much that can be done, except
>> that you'd need to file such bug report on the project producing those
>> Live images.
>
> Thanks,
> Guillem
>
>


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

Bug#717532: RFP: odb - object-relational mapping (ORM) system for the C++ language

[Onur Aslan]

Package: wnpp
Severity: wishlist

* Package name: odb
  Version : 2.2.2
  Upstream Author : Code Synthesis
* URL : http://www.codesynthesis.com/products/odb/
* License : GPL-2
  Programming Lang: C++
  Description : object-relational mapping (ORM) system for the C++ language

ODB is an open-source, cross-platform, and cross-database object-relational
mapping (ORM) system for C++. It allows you to persist C++ objects to a
relational database without having to deal with tables, columns, or SQL and
without manually writing any mapping code. ODB supports MySQL, SQLite,
PostgreSQL, Oracle, and Microsoft SQL Server relational databases as well
as C++98/03 and C++11 language standards. It also comes with optional
profiles for Boost and Qt which allow you to seamlessly use value types,
containers, and smart pointers from these libraries in your persistent C++
classes.


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

Bug#717531: /sbin/shutdown: shutdown -P sets INIT_HALT to POWERDOWN instead of POWEROFF

[Laurent Bigonville]

Package: sysvinit
Version: 2.88dsf-43
Severity: normal
File: /sbin/shutdown

Hi,

According to the shutdown(8), calling shutdown with the -P argument
should set the INIT_HALT variable to POWEROFF.

For some reasons, this is not the case and INIT_HALT is set to POWEROFF.


HALT OR POWEROFF
   The  -H option just sets the init environment variable INIT_HALT to 
HALT, and the -P option just sets that variable to POWEROFF. The shutdown 
script that calls halt(8) as the last thing in the shut‐
   down sequence should check these environment variables and call halt(8) 
with the right options for these options to actually have any effect.  Debian 
3.1 (sarge) supports this.

Cheers

Laurent Bigonville

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

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

Versions of packages sysvinit depends on:
ii  debianutils 4.3.4
ii  initscripts 2.88dsf-43
ii  libc6   2.17-7
ii  libselinux1 2.1.13-2
ii  libsepol1   2.1.9-2
ii  sysv-rc 2.88dsf-43
ii  sysvinit-utils  2.88dsf-43

sysvinit recommends no packages.

sysvinit 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#717530: js2-mode: emacs21 byte compile fail

[Kevin Ryde]

Package: js2-mode
Version: 0~20120726-1
Severity: wishlist
File: /usr/share/emacs/site-lisp/js2-mode/js2-mode.el

I still have emacs21 installed and js2-mode fails to byte compile with

While compiling toplevel forms in file 
/usr/share/emacs21/site-lisp/js2-mode/js2-mode.el:
  !! Wrong type argument ((listp #[(key &rest strings) ...

I couldn't tell if emacs21 is supposed to work.  I thought it byte
compiled at least until the last release.  If it's no longer meant to
work then /usr/lib/emacsen-common/packages/install/js2-mode could
helpfully exclude it the same as done there for emacs20 etc.


The actual problem seems to be in js2-display-error-list where the
combination of `labels' and `destructuring-bind' does too much
macroexpanding, or something, apparently leading to 'js2-msg evaluating
the js2-msg macro rather than being a symbol.  Dunno if some simplifying
could help.



-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-486
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages js2-mode depends on:
ii  emacs21 [emacsen]21.4a+1-5.7
ii  emacs22-gtk [emacsen]22.3+1-1.2
ii  emacs23-lucid [emacsen]  23.4+1-4
ic  emacs24 [emacsen]24.3+1-1
ii  emacs24-lucid [emacsen]  24.3+1-1
ii  emacsen-common   2.0.5
ii  xemacs21-mule [emacsen]  21.4.22-4

js2-mode recommends no packages.

js2-mode 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#613925: linux-image-3.2.0-4-amd64: reiserfs: deadlock affecting writes, getdents

[Steven Chamberlain]

On 17/07/13 14:02, Steven Chamberlain wrote:
> On 16/07/13 23:02, Moritz Muehlenhoff wrote:
>> Jeff Mahoney has posted patches in the upstream bug in May:
>> https://bugzilla.kernel.org/show_bug.cgi?id=29162
>>
>> Are you in a position to test them and provide him with feedback?
> 
> Yes, I will try those patches over the weekend;

Actually it does not seem so simple now.  The patchset is large and I've
realised it does not all apply against 3.2.x.  That complicates my
testing, and perhaps the ability to backport it to stable kernels.

I think the specific location of this deadlock needs to be identified or
at least narrowed down a bit first.  (Assuming it is in only one place,
which it maybe isn't).

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


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

Bug#717529: vim: FTBFS with perl 5.18

[brian m. carlson]

Source: vim
Version: 7.4a.012-1
Severity: important

I just attempted to build the vim in experimental against perl 5.18, but
it failed due to a test failure:

  cp test95.ok test.ok
  # Sleep a moment to avoid that the xterm title is messed up.
  # 200 msec is sufficient, but only modern sleep supports a fraction of
  # a second, fall back to a second if it fails.
  ../vim -u unix.vim -U NONE --noplugin -s dotest.in test95.in
  # For flaky tests retry one time.
  # Check if the test.out file matches test.ok.
  rm -rf X* test.ok viminfo
  rm -rf test96.failed test.ok test.out X* viminfo
  cp test96.ok test.ok
  # Sleep a moment to avoid that the xterm title is messed up.
  # 200 msec is sufficient, but only modern sleep supports a fraction of
  # a second, fall back to a second if it fails.
  ../vim -u unix.vim -U NONE --noplugin -s dotest.in test96.in
  # For flaky tests retry one time.
  # Check if the test.out file matches test.ok.
  10,12d9
  < Test C:
  <   - 'buftype' of the location list window: quickfix
  <   - buffer displayed in the 2nd window: test://quux.txt
  rm -rf X* test.ok viminfo
  rm -rf test97.failed test.ok test.out X* viminfo
  cp test97.ok test.ok
  # Sleep a moment to avoid that the xterm title is messed up.
  # 200 msec is sufficient, but only modern sleep supports a fraction of
  # a second, fall back to a second if it fails.
  ../vim -u unix.vim -U NONE --noplugin -s dotest.in test97.in
  # For flaky tests retry one time.
  # Check if the test.out file matches test.ok.
  rm -rf X* test.ok viminfo
  rm -rf test98.failed test.ok test.out X* viminfo
  cp test98.ok test.ok
  # Sleep a moment to avoid that the xterm title is messed up.
  # 200 msec is sufficient, but only modern sleep supports a fraction of
  # a second, fall back to a second if it fails.
  ../vim -u unix.vim -U NONE --noplugin -s dotest.in test98.in
  # For flaky tests retry one time.
  # Check if the test.out file matches test.ok.
  rm -rf X* test.ok viminfo
  
  Test results:
  test96 FAILED
  TEST FAILURE
  make[2]: *** [report] Error 1
  make[2]: Leaving directory `/tmp/vim-7.4a.012/src/vim-nox/testdir'
  make[1]: *** [test] Error 2
  make[1]: Leaving directory `/tmp/vim-7.4a.012/src/vim-nox'
  make: *** [install-stamp-vim-basic] Error 2
  dpkg-buildpackage: error: debian/rules binary gave error exit status 2

I recommend using a chroot for building because otherwise installing
perl 5.18 from experimental will remove the Debian kernel packages,
which may be undesirable.  This is severity important because perl 5.18
will be coming to unstable at some point and then the FTBFS will be
serious.

-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.gtk
/usr/bin/vim is /usr/bin/vim.gtk
/usr/bin/gvim is /usr/bin/vim.gtk

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

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

-- no debconf information

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#717526: need to change kdm background artwork

[Holger Levsen]

package: debian-edu-artwork
version: 0.42-1
severity: important

Hi,

kdm cannot deal with the svg file used for the background, see screenshot at 
http://wiki.debian.org/DebianEdu/Documentation/Wheezy/Installation?action=AttachFile&do=get&target=23-Tjener-KDM_Login.png
 


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#717527: no grub artwork

[Holger Levsen]

package: debian-edu-artwork
version: 0.42-1
severity: important

Hi,

the grub artwork is gone, mostly because I used a wrong resolution.
I have a fix locally, and wil commit it as soon as I have network again.


cheers,
Holger



signature.asc
Description: This is a digitally signed message part.

Bug#715804: Debian policy for web apps still references /doc as accessible

[Charles Plessy]

tag 715804 patch
thanks

Le Thu, Jul 11, 2013 at 08:06:33AM +0900, Charles Plessy a écrit :
> Le Thu, Jul 11, 2013 at 01:24:45AM +0800, Thomas Goirand a écrit :
> > 
> > The Debian policy for web apps still references /doc as accessible
> > through the web (see point 3 of chapter 11.5), though it has been removed
> > for security reasons. The policy should be updated.
 
> if the webservers that we distribute have dropped that functionality
> (can you confirm that it is not just apache2 ?), then I also support adjusting
> the Policy accordingly.

I contacted the maintainers of packages which provide 'httpd' and got two
answers, that this feature is not enabled in the uwsgi package and that it is
being removed from the nginx package.  I then realised that I dropped by
mistake the maintainers of the lighttpd package, in which I see that it
contains a snippet that implements the feature, but apparently not by default.

On my side, I think that the current practice is not to serve /doc by default,
and I therefore second the proposition of Thomas to remove point 2 of chapter
11.5.

Are there other seconds or objections ?

Cheers,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


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

Bug#717525: adb starts daemon and then claims daemon is not running

[Joey Hess]

Package: android-tools-adb
Version: 4.2.2+git20130529-2.1
Severity: important

I think that adb was broken by the NMU which makes it use a local
socket.

joey@gnu:~>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon

Each time I run adb shell, it starts another daemon, and then
fails to connect to any of them.

(In the end, I worked around this by starting the adb daemon using the
adb binary distributed with adt-bundle-linux-x86. Once that daemon was
running, the adb from this package was able to connect to it without
difficulty, and adb shell, adb push etc worked.)

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.9-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages android-tools-adb depends on:
ii  libc62.17-7
ii  libssl1.0.0  1.0.1e-3
ii  zlib1g   1:1.2.8.dfsg-1

android-tools-adb recommends no packages.

android-tools-adb suggests no packages.

-- no debconf information

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#717480: Does not even boot for me

[Michael Biebl]

Am 22.07.2013 00:12, schrieb Eric Valette:
> On 21/07/2013 23:12, Eric Valette wrote:
> 
>> Will look at it once I can find a way restart my system. Currently
>> downloading a recent install cd... will do a chroot and tell you. BTW
>> last testing iso image is broken as it does not find kernel modules...
> 
> OK. Back on Linux. Downgrading udev and libudev *only* fixes the boot
> problem. I had to force a conflict with consolekit but will salvage that
> later on.
> 
> indeed I had:
> 
> # CONFIG_DEVTMPFS is not set
> 
> Will set it and try again. I now have :
> 
> CONFIG_DEVTMPFS=y
> CONFIG_DEVTMPFS_MOUNT=y

Ok, since your issue is not related with the original bug reporters
issue, it was probably not a good idea to hijack this bug report in the
first place.

Your problem is, that DEVTMPFS is no longer really optional, and your
kernel misses that.
We could possibly add a preinst check to udev which bails out or shows a
warning if DEVTMPFS is not enabled for self-compiled kernels. Usually,
users with self-compiled kernels should keep an eye on such requirements
[1], but we can try to be extra-nice.

Feel free to file a separate bug report for that.

Michael

[1] http://cgit.freedesktop.org/systemd/systemd/tree/README#n36
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#582109: debian-policy: document triggers where appropriate

[Charles Plessy]

Le Sun, Jul 21, 2013 at 09:36:52PM +0200, Raphael Hertzog a écrit :
> 
> There are no "restrictions" for "postinst configure" (you can rely on
> dependencies — except if you have a dependency cycle) and there should be
> no restrictions for "postinst triggered". But right now, dpkg doesn't
> ensure anything. And instead of nothing checked by dpkg, I suggested to
> ensure some requirements nevertheless but which are less demanding than
> those used by "postinst configure".

Sorry for the poorly chosen use of the word "restrictions" here...

Nevertheless, please let me try to refocus on the question of whether
the Policy can be updated or not.

Here is what is written in the Policy about "postinst configure":

The files contained in the package will be unpacked. All package
dependencies will at least be unpacked.

The corollary is that there is no guarantee that the dependencies will be
configured, and my understanding of #671711 is that it currently applies to
"postinst triggered" as well.

I propose to go ahead with the following:

postinst triggered
  "trigger-name trigger-name ..."

  The files contained in the package will be unpacked.  All
  package dependencies will at least be "Unpacked"
  There is work under way on dpkg to ensure that
  the requirement on postinst triggered is less demanding
  than for postinst configure, see the bug number
  http://bugs.debian.org/671711"; name="671711"> for
  details..


I attached a full version of the latest patch.

I would like to go ahead and close this bug.  If Raphaël confirms that he still
seconds the patch,  I would much appreciate if I could either have support or
actionable objection from others (preferably in the form of "unless X is done,
the patch should not be applied", rather than "it would be good to do Y").

Have a nice day,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan
diff --git a/policy.sgml b/policy.sgml
index 1508231..5308a84 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -900,9 +900,11 @@ zope.
 	the package.  Other control information files include
 	the symbols file
 	or shlibs file
-	used to store shared library dependency information and
+	used to store shared library dependency information,
 	the conffiles file that lists the package's
-	configuration files (described in ).
+	configuration files (described in ), and the
+	triggers file, which defines the package's interaction with
+	dpkg's trigger system.
   
 
   
@@ -3959,6 +3961,51 @@ Checksums-Sha256:
 	
 
 	
+	  Dpkg defines the following states for the packages.
+	  
+	Not-Installed
+	
+	  The package is not installed on the system.
+	
+
+	Config-Files
+	
+	  Only the configuration files of the package exist on the system.
+	
+
+	Half-Installed
+	
+	  The installation of the package has been started, but not
+	  completed for some reason.
+	
+
+	Unpacked
+	
+	  The package is unpacked, but not configured.
+	
+
+	Half-Configured
+	
+	  The package is unpacked and its configuration or the processing
+	  of one of its triggers has not yet completed for some reason.
+	
+
+	Triggers-Awaited
+	
+	  The package awaits trigger processing by another package.
+	
+
+	Triggers-Pending
+	
+	  The package has been triggered.
+	
+
+	Installed
+	
+	  The package is unpacked and configured.
+	
+	  
+	
 	  Broadly speaking the preinst is called before
 	  (a particular version of) a package is unpacked, and the
 	  postinst afterwards; the prerm
@@ -4106,7 +4153,11 @@ Checksums-Sha256:
 	  are no circular dependencies involved, all package
 	  dependencies will be configured.  For behavior in the case
 	  of circular dependencies, see the discussion
-	  in .
+	  in .  Even when called with
+	  configure, this script must do whatever actions are
+	  necessary to deal with any
+	  triggers
+	  activation.
 	
 
 	old-postinst abort-upgrade
@@ -4141,6 +4192,34 @@ Checksums-Sha256:
 	  from the package dependencies are not available is often the
 	  best approach.
 	
+
+	postinst triggered
+	  "trigger-name trigger-name ..."
+	
+	  The files contained in the package will be unpacked.  All
+	  package dependencies will at least be "Unpacked"
+	  There is work under way on dpkg to ensure that
+	  the requirement on postinst triggered is less demanding
+	  than for postinst configure, see the bug number
+	  http://bugs.debian.org/671711"; name="671711"> for
+	  details..
+	  Process one or more triggers that
+	  this package is interested in.  In case of failure the
+	  package's state becomes "Half-Configured" and the task associated
+	  to the trigger processing will be completed by the
+	  postinst configure during the next 

Bug#717523: sbuild: sbuild-shell fails with E: Failed to create build directory /build

[brian m. carlson]

Package: sbuild
Version: 0.64.0-1
Severity: normal

I have followed the directions listed at http://wiki.debian.org/sbuild
to create a chroot, and now trying to run sbuild-shell to install some
packages:

  vauxhall ok % sudo sbuild-shell source:sid-amd64-sbuild
  E: Failed to create build directory /build
  Failed to set up chroot
  Error setting up source:sid-amd64-sbuild chroot
  Chroot setup failed at /usr/bin/sbuild-shell line 42.

Trying sbuild-update fails in a similar way:

  vauxhall no % sudo sbuild-update -ud sid
  E: Failed to create build directory /build
  Failed to set up chroot
  Error setting up sid chroot
  Chroot setup failed at /usr/bin/sbuild-update line 168.

I expect any command that I run will be equally functional.

I have not found any documentation dealing with this issue, so if this
is something trivial to fix, please consider this a request for adding
documentation that will help users solve the problem for themselves.

The chroot information is below:

  [sid-amd64-sbuild]
  type=file
  description=Debian sid/amd64 autobuilder
  file=/var/lib/sbuild/sid-amd64.tar.gz
  groups=root,sbuild
  root-groups=root,sbuild

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

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

Versions of packages sbuild depends on:
ii  adduser 3.113+nmu3
ii  apt-utils   0.9.9.2
ii  libsbuild-perl  0.64.0-1
ii  perl5.14.2-21
ii  perl-modules5.14.2-21

Versions of packages sbuild recommends:
ii  debootstrap  1.0.53
ii  fakeroot 1.19-2

Versions of packages sbuild suggests:
ii  deborphan  1.7.28.8
ii  wget   1.14-2

-- no debconf information

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#717438: pdnsd RUINED

[jidanni]

Yes please work with Thomas about debugging this as he is much better
than me. And thanks Thomas for the dnsmasq tip.


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

Bug#717480: Does not even boot for me

[Eric Valette]

On 21/07/2013 23:12, Eric Valette wrote:


Will look at it once I can find a way restart my system. Currently
downloading a recent install cd... will do a chroot and tell you. BTW
last testing iso image is broken as it does not find kernel modules...


OK. Back on Linux. Downgrading udev and libudev *only* fixes the boot 
problem. I had to force a conflict with consolekit but will salvage that 
later on.


indeed I had:

# CONFIG_DEVTMPFS is not set

Will set it and try again. I now have :

CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y


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

Bug#717488: Please always launch /etc/init.d/ups-monitor when halting the system

[Fabien C.]

Well, I don't know. I guess it just wasn't logic enough to call ups-monitor 
with the "poweroff" argument when the system INIT_HALT is not set to poweroff 
itself...

Let's ask Arnaud and Laurent (nut maintainers) if they have more information on 
the matter (cc).

Regards, 
Fabien C. 

On 21/07/2013 23:26, Roger Leigh wrote:
> On Sun, Jul 21, 2013 at 01:23:28PM +0200, Fabien C. wrote:
>> please launch "/etc/init.d/ups-monitor poweroff" everytime /etc/init.d/halt 
>> is 
>> called, not only when INIT_HALT=POWEROFF. 
>>
>> The current script forbids that behavior because if INIT_HALT is not equal 
>> to 
>> POWEROFF, which is "unfortunately" the case with "shutdown -Hh", then 
>> /etc/init.d/ups-monitor is *never* called. 
> 
> While this change sounds reasonable, I'm not personally aware of the
> reason for the current logic.  Is changing this going to break
> anything?  Why is it currently the way it is?
> 
> 
> Regards,
> Roger
> 


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

Bug#716801: udev: 70-persistent-net.rules isn't generated

[Marco d'Itri]

On Jul 21, Simon Lodal  wrote:

> The functionality was there in squeeze. Could you point me to a changelog 
> entry that describes when it was removed, and why?
If it worked in squeeze for some hypervisor then it was an error which 
has been corrected.

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Bug#716801: udev: 70-persistent-net.rules isn't generated

[Simon Lodal]

> > I WANT to rename the interfaces.
> > 
> > I can create 70-persistent-net.rules manually, then it works perfectly.
> > But
> 
> And it is how it is supposed to work

Says who?

Not the man page for sure.

The functionality was there in squeeze. Could you point me to a changelog 
entry that describes when it was removed, and why?

Or better: Explain how did it work? And why does it not work now? Maybe we can 
even fix it then.


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

Bug#717519: [debian-installer] daily-build cd image won't boot since 20130715

[Eugene Paskevich]

Please also find attached the diff -ruN output between the 20130714 and  
20130716 initrd trees.


--
Eugene Paskevich |   *==)---   | Plug me into
eug...@raptor.kiev.ua|   ---(==*   |  The Matrix

initrd.diff.gz
Description: GNU Zip compressed data

Bug#712855: News about the bug.

[Yohann Ferreira]

Hi,

Tried the kernel version 3.10-1 (amd64) since it got out, and the problem 
remains in this kernel.

I don't know whether this help. I can give system details if requested.

Best regards,

Yohann Ferreira


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

Bug#717522: drupal7: errors when executing the shell cron job

[Fernando Lucas Rodriguez]

Package: drupal7
Version: 7.22-2
Severity: normal
Tags: patch

Dear Maintainer,

I am running into troubles with the current cron shell script. There are
basically two issues:

1) I redirect all my traffic from http to https using a self-signed
certificate. Curl complains about this and does not execute the http request.
2) I use a multisite installation without any "default" site. The cron script
insist in calling the default configuration generating also errors.

I propose the following script solving the issues.




#!/bin/sh

for site in /etc/drupal/7/sites/* ; do
BASE_URL=""
CRON_KEY=""
FULL_URL=""

if [ ! "`basename $site`" = "all" ]; then
for file in $site/baseurl.php $site/settings.php; do
[ -f "$file" ] && BASE_URL=`grep '^$base_url' $file |
cut -d"'" -f2`
[ "X$BASE_URL" != "X" ] && break
done

for file in $site/cronkey.php $site/settings.php; do
[ -f "$file" ] && CRON_KEY=`grep '^$cron_key' $file |
cut -d"'" -f2`
[ "X$CRON_KEY" != "X" ] && break
done

if [ "X$BASE_URL" = "X" ] ; then
if [ -f "$site/settings.php" ]; then
BASE_URL='http://localhost/drupal7'
else
break
fi
fi

if [ "X$CRON_KEY" = "X" ] ; then
FULL_URL="$BASE_URL/cron.php"
else
FULL_URL="$BASE_URL/cron.php?cron_key=$CRON_KEY"
fi

if curl -S --fail --silent --compressed --insecure --location
$FULL_URL ; then
# Success!
true
else
echo "Error running the periodic maintenance for $site:
CURL exit code $?"
echo "Requested URL: $FULL_URL"
fi
fi
done





-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (800, 'testing'), (40, 'unstable'), (30, 'stable'), (20, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages drupal7 depends on:
ii  apache22.2.22-13
ii  apache2-mpm-prefork [httpd]2.2.22-13
ii  curl   7.31.0-2
ii  dbconfig-common1.8.47+nmu1
ii  debconf [debconf-2.0]  1.5.50
ii  exim4-daemon-heavy [mail-transport-agent]  4.80-7
ii  php5   5.4.4-15.1
ii  php5-gd5.4.4-15.1
ii  php5-pgsql 5.4.4-15.1
ii  postgresql-client  9.3+142really9.1+145
ii  postgresql-client-9.1 [postgresql-client]  9.1.9-2+b1
ii  wwwconfig-common   0.2.2

Versions of packages drupal7 recommends:
ii  postgresql  9.3+142really9.1+145

drupal7 suggests no packages.

-- Configuration Files:
/etc/drupal/7/sites/default/settings.php [Errno 2] No such file or directory: 
u'/etc/drupal/7/sites/default/settings.php'

-- debconf information:
  drupal7/pgsql/changeconf: false
  drupal7/dbconfig-remove:
  drupal7/pgsql/authmethod-user:
  drupal7/db/basepath:
  drupal7/upgrade-error: abort
* drupal7/dbconfig-install: true
  drupal7/purge: false
  drupal7/upgrade-backup: true
  drupal7/pgsql/manualconf:
* drupal7/database-type: mysql
  drupal7/internal/reconfiguring: false
  drupal7/install-error: abort
  drupal7/remote/port:
  drupal7/remove-error: abort
  drupal7/mysql/admin-user: root
  drupal7/pgsql/admin-user: postgres
  drupal7/missing-db-package-error: abort
  drupal7/dbconfig-upgrade: true
  drupal7/remote/host:
  drupal7/db/app-user: drupal7
  drupal7/pgsql/authmethod-admin: ident
  drupal7/db/dbname: drupal7
  drupal7/pgsql/no-empty-passwords:
  drupal7/internal/skip-preseed: false
  drupal7/passwords-do-not-match:
  drupal7/dbconfig-reinstall: false
  drupal7/mysql/method: unix socket
  drupal7/pgsql/method: unix socket
  drupal7/remote/newhost:


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

Bug#717488: Please always launch /etc/init.d/ups-monitor when halting the system

[Petter Reinholdtsen]

[Roger Leigh]
> While this change sounds reasonable, I'm not personally aware of the
> reason for the current logic.  Is changing this going to break
> anything?  Why is it currently the way it is?

I have no idea either.  Before my time. :)

-- 
Happy hacking
Petter Reinholdtsen


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

Bug#717521: golang-mode: \s not in emacs21

[Kevin Ryde]

Package: golang-mode
Version: 2:1.1.1-4
Severity: wishlist
File: /usr/share/emacs/site-lisp/golang-mode/go-mode.el

I still have emacs21 installed and golang-mode fails to install with

   While compiling toplevel forms in file 
/usr/share/emacs21/site-lisp/golang-mode/go-mode.el:
 !! error (("Invalid escape character syntax"))

I believe in go--backward-irrelevant the string

   "\n\s\t"

is no good for emacs21 as there's no \s for space there.
It would be helpful if this was a plain space

   "\n \t"


-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-486
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages golang-mode depends on:
ii  emacs21 [emacsen]21.4a+1-5.7
ii  emacs22-gtk [emacsen]22.3+1-1.2
ii  emacs23-lucid [emacsen]  23.4+1-4
ic  emacs24 [emacsen]24.3+1-1
ii  emacs24-lucid [emacsen]  24.3+1-1
ii  emacsen-common   2.0.5
ii  xemacs21-mule [emacsen]  21.4.22-4

golang-mode recommends no packages.

Versions of packages golang-mode suggests:
pn  golang-go  

-- 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#717520: ifupdown: privext option in interfaces(5) should reference RFC 4941 instead of RFC 3041

[Daniel Kahn Gillmor]

Package: ifupdown
Version: 0.7.43
Severity: minor

in interfaces(5), it says (twice):

 privext int
 Privacy extensions (RFC3041) (0=off, 1=assign, 2=prefer)

But RFC 3041 is considered obsolete by the IETF, with RFC 4941
superceding it.

The significant changes between RFC 3041 and 4941 are enumerated in
RFC 4941 itself:

  https://tools.ietf.org/html/rfc4941#section-8

Unless there is reason to believe that the ifupdown configuration (or
the kernel) doesn't support RFC 4941, please update the reference in
the man page to use the non-obsolete RFC.

Thanks for maintaining ifupdown in debian!

Regards,

--dkg

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

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

Versions of packages ifupdown depends on:
ii  dpkg 1.16.10
ii  initscripts  2.88dsf-41
ii  iproute  1:3.9.0-5
ii  libc62.17-7
ii  lsb-base 4.1+Debian12

ifupdown recommends no packages.

Versions of packages ifupdown suggests:
ii  isc-dhcp-client [dhcp-client]  4.2.4-7
ii  net-tools  1.60-25
ii  ppp2.4.5-5.2
pn  rdnssd 

-- debconf-show failed


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

Bug#717488: Please always launch /etc/init.d/ups-monitor when halting the system

[Roger Leigh]

On Sun, Jul 21, 2013 at 01:23:28PM +0200, Fabien C. wrote:
> please launch "/etc/init.d/ups-monitor poweroff" everytime /etc/init.d/halt 
> is 
> called, not only when INIT_HALT=POWEROFF. 
> 
> The current script forbids that behavior because if INIT_HALT is not equal to 
> POWEROFF, which is "unfortunately" the case with "shutdown -Hh", then 
> /etc/init.d/ups-monitor is *never* called. 

While this change sounds reasonable, I'm not personally aware of the
reason for the current logic.  Is changing this going to break
anything?  Why is it currently the way it is?


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.


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

Bug#687227: No relay possible

[Michael Sendrowski]

After a few day of testing the crtmpserver logs

TryLinkToFileStream:No file streams found: foo

I tried many flv player and mplayer should work also with:

mplayer rtmp://10.0.0.213/flvplayback/flv:peterpan.flv


30
false
peterpan

false
/var/lib/crtmpserver/mediaFolder/
false
flv:peterpan

C++ RTMP Server (http://www.rtmpd.com)

0
flv

Bug#702511: golang-mode: does not compile with xemacs21

[Kevin Ryde]

This seems to be better in the current code, addressed by

https://code.google.com/p/go/source/detail?r=ef6c59f8f54f2d2e9d599d1ec86f8c1de6a2ed1a&path=/misc/emacs/go-mode.el


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

Bug#717480: Does not even boot for me

[Eric Valette]

On 21/07/2013 10:49, Michael Biebl wrote:

>> As It does not find the disk except the root partition, when
>> mouting disk for fstab it fails. I have  a strange message saying
>> tmpfs is not started when it is as several tmpfs  FS are already
>> mounted. BTW as my system is quite old I have USR and / on a
>> different partition.
> 
> Can you attached your kernel config, please. Maybe it's related to
> DEVTMPFS

Will look at it once I can find a way restart my system. Currently
downloading a recent install cd... will do a chroot and tell you. BTW
last testing iso image is broken as it does not find kernel modules...

--eric


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

Bug#717511: Kernel does not start up on Pegasos-2

[Ben Hutchings]

Control: reassign -1 yaboot-installer 1.1.26

On Mon, 2013-07-22 at 00:38 +0400, Pavel Fedin wrote:
[...]
>  So,  it's  not  kernel's  fault. It seems to be installer fault which
> does  not generate correct vmlinuz image when not using separate /boot
> partition.  vmlinux,  i  know,  is another thing. It's a "plain" image
> meant to be ran from GRUB or yaboot. It cannot be run from OFW.
>  So,  we  can  close  this,  probably with a notification to Installer
> guys.

There is no need to close it.  I'm reassigning to the relevant part of
the installer.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg


signature.asc
Description: This is a digitally signed message part

Bug#717480: Does not even boot for me

[Michael Biebl]

Am 21.07.2013 22:47, schrieb Eric Valette:
> On 21/07/2013 10:28, Michael Biebl wrote:
>> Am 21.07.2013 22:25, schrieb Michael Biebl:
>>> Am 21.07.2013 22:19, schrieb Eric Valette:
 I suspect the status is worse for me : the kernel detects the
 disks but do not populate udev nor even mount it. I use my own
 kernel tailored for my machine, not initrd. udev 204 breaks the
 boot by not adding sdb* diks entries.
>>>
>>> Can you test with a stock Debian kernel?
> 
> It's complicated has it will reinstall a lot of things I usually
> remove (initramfstools, and various things I will have to remove). And
> as my system is currently broken, it would mean booting in rescue mode
> and using my normal root)
> 
>>
>> It would also be good to know, at which point the boot process
>> get's stuck.
> 
> As It does not find the disk except the root partition, when mouting
> disk for fstab it fails. I have  a strange message saying tmpfs is not
> started when it is as several tmpfs  FS are already mounted. BTW as my
> system is quite old I have USR and / on a different partition.

Can you attached your kernel config, please. Maybe it's related to DEVTMPFS



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#717480: Does not even boot for me

[Eric Valette]

On 21/07/2013 10:28, Michael Biebl wrote:
> Am 21.07.2013 22:25, schrieb Michael Biebl:
>> Am 21.07.2013 22:19, schrieb Eric Valette:
>>> I suspect the status is worse for me : the kernel detects the
>>> disks but do not populate udev nor even mount it. I use my own
>>> kernel tailored for my machine, not initrd. udev 204 breaks the
>>> boot by not adding sdb* diks entries.
>> 
>> Can you test with a stock Debian kernel?

It's complicated has it will reinstall a lot of things I usually
remove (initramfstools, and various things I will have to remove). And
as my system is currently broken, it would mean booting in rescue mode
and using my normal root)

> 
> It would also be good to know, at which point the boot process
> get's stuck.

As It does not find the disk except the root partition, when mouting
disk for fstab it fails. I have  a strange message saying tmpfs is not
started when it is as several tmpfs  FS are already mounted. BTW as my
system is quite old I have USR and / on a different partition.

I will first find a way to restore my system and will continue
debugging later.

--eric


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

Bug#717511: Kernel does not start up on Pegasos-2

[Pavel Fedin]

Hello, Karoly.

21 июля 2013 г., 22:34:12, you wrote:


> Just for the record, I've installed Wheezy successfully on two Pegasos
> IIs, one is a rev 2B1 board, which was installed from scratch, and worked
> without major glitches, apart from the fact that the installer required an
> installation to MBR partitioned disks, because with RDB disks it said
> "Fatal error: Out of memory", when it tried to create the main partition
> on an 80GB ATA disk. :)

 I am sorry for the false alarm...
 After  posting  this message i decided to reinstall the system...
 The  story  begins  with  the  fact  that until now i used single EXT
partition  for  Linux. In the far past it used to be EXT2, then when i
upgraded to Etch it became EXT3. There was no separate /boot partition
because Pegasos firmware was perfectly able to read that partition.
 But  now,  first  i  decided  to  use  EXT4  (yes,  i performed clean
reinstall).  Firmware  did  not  know  what is EXT4 and could not read
/boot directory. Fault.
 I  reinstalled  again,  this  time i used EXT3. But... Hah! This EXT3
appears  to  be  somehow incompatible with my older EXT3. The firmware
was not able to read it.
 But,  fortunately,  MorphOS  was able to. I quickly extracted vmlinux
file  from  /boot directory, copied it to SFS partition (where MorphOS
lives), and booted it from there.
 But this time i decided to do everything in a good way. I cut a small
120MB  piece from my old Linux partition and decided to use it as EXT2
/boot.   The   rest   became   EXT4   again.  I  reinstalled  in  this
configuration,  and...  In  /boot  i saw two images. One had "vmlinux"
name  and  another  had  "vmlinuz"  name. I ran vmlinuz and everything
worked fine! :)
 So,  it's  not  kernel's  fault. It seems to be installer fault which
does  not generate correct vmlinuz image when not using separate /boot
partition.  vmlinux,  i  know,  is another thing. It's a "plain" image
meant to be ran from GRUB or yaboot. It cannot be run from OFW.
 So,  we  can  close  this,  probably with a notification to Installer
guys.

-- 
Kind regards,
 Pavel  mailto:pavel_fe...@mail.ru


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

Bug#717516: linux-image-3.2.0-4-amd64: Segmentation fault in ksoftirqd

[Oliver Lorenz]

On Jul 21, 21:05, Ben Hutchings wrote:
> Control: retitle -1 WARNING from rcu_preempt_check_blocked_tasks() in Xen VM
> Control: tag -1 moreinfo
> 
> Please don't assume that a call trace indicates a segmentation fault.
> You have to look at the message before it.  In this case it is a WARNING
> which indicates a error detected in software and is usually non-fatal.
> 

Then sorry for the noise. Better safe than sorry ;)


signature.asc
Description: Digital signature

Bug#717480: Does not even boot for me

[Michael Biebl]

Am 21.07.2013 22:19, schrieb Eric Valette:
> I suspect the status is worse for me : the kernel detects the disks
> but do not populate udev nor even mount it. I use my own kernel
> tailored for my machine, not initrd. udev 204 breaks the boot by not
> adding sdb* diks entries.

Can you test with a stock Debian kernel?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#717480: Does not even boot for me

[Michael Biebl]

Am 21.07.2013 22:25, schrieb Michael Biebl:
> Am 21.07.2013 22:19, schrieb Eric Valette:
>> I suspect the status is worse for me : the kernel detects the disks
>> but do not populate udev nor even mount it. I use my own kernel
>> tailored for my machine, not initrd. udev 204 breaks the boot by not
>> adding sdb* diks entries.
> 
> Can you test with a stock Debian kernel?

It would also be good to know, at which point the boot process get's stuck.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#716801: udev: 70-persistent-net.rules isn't generated

[Marco d'Itri]

On Jul 21, Simon Lodal  wrote:

> I WANT to rename the interfaces.
> 
> I can create 70-persistent-net.rules manually, then it works perfectly. But 
And it is how it is supposed to work, because your case is highly 
uncommon.

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Bug#717480: Does not even boot for me

[Eric Valette]

I suspect the status is worse for me : the kernel detects the disks
but do not populate udev nor even mount it. I use my own kernel
tailored for my machine, not initrd. udev 204 breaks the boot by not
adding sdb* diks entries.

--eric


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

Bug#717342: Nocheck when cross build

[Thorsten Glaser]

Jonathan Nieder dixit:

>that should be run when cross-building?  Why doesn't the cross-build
>procedure enable nocheck automatically?  I don't like the idea of changing

AFAIR from when I’ve been dealing with cross-deb-builds,
they do, or, at least, adding nocheck to DEB_BUILD_OPTIONS
was in the instructions of what to do for cross-building
properly.

bye,
//mirabilos
-- 
18:47⎜ well channels… you see, I see everything in the
same window anyway  18:48⎜ i know, you have some kind of
telnet with automatic pong 18:48⎜ haha, yes :D
18:49⎜ though that's more tinyirc – sirc is more comfy


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

Bug#717516: linux-image-3.2.0-4-amd64: Segmentation fault in ksoftirqd

[Ben Hutchings]

Control: retitle -1 WARNING from rcu_preempt_check_blocked_tasks() in Xen VM
Control: tag -1 moreinfo

On Sun, 2013-07-21 at 21:26 +0200, Oliver Lorenz wrote:
> Package: src:linux
> Version: 3.2.46-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I saw the segmentation fault in my logs today. Don't know what caused it or 
> how
> to reproduce it.

Please don't assume that a call trace indicates a segmentation fault.
You have to look at the message before it.  In this case it is a WARNING
which indicates a error detected in software and is usually non-fatal.

[...]
> [66283.532082] [ cut here ]
> [66283.532092] WARNING: at 
> /build/linux-s5x2oE/linux-3.2.46/kernel/rcutree_plugin.h:1011 
> rcu_start_gp+0x12f/0x20f()
> [66283.532096] Modules linked in: xt_connlimit xt_tcpudp xt_state ipt_REJECT 
> nf_nat_irc nf_nat_ftp iptable_nat nf_nat nf_conntrack_irc nf_conntrack_ftp 
> nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ip6table_filter ip6_tables tun 
> xt_multiport iptable_filter ip_tables x_tables evdev snd_pcm snd_page_alloc 
> coretemp crc32c_intel snd_timer snd ghash_clmulni_intel soundcore aesni_intel 
> pcspkr aes_x86_64 aes_generic cryptd ext4 crc16 jbd2 mbcache xen_blkfront 
> xen_netfront
> [66283.532131] Pid: 14, comm: ksoftirqd/2 Not tainted 3.2.0-4-amd64 #1 Debian 
> 3.2.46-1
> [66283.532134] Call Trace:
> [66283.532140]  [] ? warn_slowpath_common+0x78/0x8c
> [66283.532145]  [] ? rcu_start_gp+0x12f/0x20f
> [66283.532150]  [] ? __rcu_process_callbacks+0x11d/0x2ce
> [66283.532153]  [] ? rcu_process_callbacks+0x2a/0x54
> [66283.532158]  [] ? __do_softirq+0xb9/0x177
> [66283.532161]  [] ? run_ksoftirqd+0x7a/0x118
> [66283.532165]  [] ? __do_softirq+0x177/0x177
> [66283.532170]  [] ? kthread+0x76/0x7e
> [66283.532176]  [] ? kernel_thread_helper+0x4/0x10
> [66283.532180]  [] ? int_ret_from_sys_call+0x7/0x1b
> [66283.532184]  [] ? retint_restore_args+0x5/0x6
> [66283.532189]  [] ? gs_change+0x13/0x13
> [66283.532191] ---[ end trace 325beebbbd3ea67c ]---
[...]

According to
, this
WARNING could sometimes appear 'legitimately' i.e. it wouldn't indicate
a real error.  (Which would mean the WARNING is itself buggy!)

Unfortunately, there is nothing here that could tell us where the bug
is.  If this error reoccurs then perhaps you can identify some
triggering behaviour.  And if it recocurs frequently, I can provide a
patch based on the thread linked above which you can then use to gather
information for debugging.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg


signature.asc
Description: This is a digitally signed message part

Bug#706973: transition: audit

[Laurent Bigonville]

Hi,

Is anything blocking this transition?

The tracker shows no conflict. libvirt is currently FTBFS but the
version in testing has no dependency against libaudit.

Tell me if I could help with something.

Cheers

Laurent Bigonville


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

Bug#666730: ia32 compat mode, ktimer_create etc return ENOSYS

[Petr Salinger]

Should be fixed in HEAD post r253531.
Please package and upload new snapshot.

Petr


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

Bug#717518: RM: partman-ufs -- ROM; Now obsolete

[Christian Perrier]

Package: ftp.debian.org
Severity: normal


Same rationale than partman-reiserfs : the kernel no longer provides
UFS modules and there is no point in having a D-I udeb for this
filesystem. See #717239.


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

Bug#717517: RM: partman-reiserfs -- ROM; now useless

[Christian Perrier]

Package: ftp.debian.org
Severity: normal

Please remove partman-reiserfs. The kernel package now no longer
provides Reiserfs modules so there is no point in having a D-I udeb
for this filesystem. See #717236...


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

Bug#715327: virtualbox: CVE-2013-3792

[Felix Geyer]

The bug affects version 4.0 and 4.2.0 - 4.2.12 but not 4.1 or 3.x.
This means that the versions in squeeze-backports, wheezy-backports,
testing and unstable are vulnerable.


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

Bug#702580: libxine2: Looks for channels.conf in unexpected location & hangs

[Dmitry Katsubo]

Thanks,

I really meant "non-responsive" as no UI buttons work. The only way to
continue is to kill the app. What if user wants to continue, open some
video file from hard drive? Have you succeeded with that?

On 29/05/2013 14:43, Darren Salt wrote:
> thanks
> 
> linuxtv.org is not xine-project.org ☺
> 
> The page in question does mention the correct location for channels.conf for
> xine-lib 1.2 (though it could probably do so more clearly since 1.1 has been
> deprecated for a while and I now regard it as obsolete).
> 
> It definitely doesn't hang (or I don't see it hanging – you clearly mean
> non-responsive), and it does tell you which file was not found; any problems
> with display of this information is down to the front end (but both xine and
> gxine are fine here).
> 
> ~/.config/xine-lib is correct for xine-lib 1.2.


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

Bug#717342: Nocheck when cross build

[Jonathan Nieder]

Hi Eleanor,

Eleanor Chen wrote:

> When cross build xz-utils, nocheck should be enabled, or it will fail
> when running tests.

I fear I'm missing some context.  Is there any package with a testsuite
that should be run when cross-building?  Why doesn't the cross-build
procedure enable nocheck automatically?  I don't like the idea of changing
all cross-buildable packages to special-case crossbuilding by overriding
the nocheck flag in debian/rules.  Besides, that would remove the benefit
of tests when cross-building to another native arch (e.g., amd64->i386).

I can imagine some setup for cross-testing being invented in the
future (e.g., involving sending native binaries and their dependencies
to another machine and testing them there), but I suspect this would
be something different than the normal build-time tests that are
disabled by the nocheck setting.  For example, autopkgtest might be
the way to go for that.

Hope that helps,
Jonathan


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

Bug#717473: BUG: Null pointer deref in amd64_edac_mod/amd64_probe_one_instance during boot

[Borislav Petkov]

On Sun, Jul 21, 2013 at 06:41:52PM +0100, Ben Hutchings wrote:
> On Sun, 2013-07-21 at 09:54 +0100, Roger Leigh wrote:
> > If the bug is in amd64_edac_mod, there are only two possible commits
> > which could cause the problem:
> > 
> > 1eef12825 amd64_edac: Correct DIMM sizes
> > 94c1acf2c amd64_edac: Add Family 16h support
> > 
> > Which are the only commits between 3.8 and 3.9 (and none made since)
> 
> The crash is at this line:
> 
>   csrow->channels[1]->dimm->nr_pages = row_dct1_pages;

Hmm.

If I can read it correctly above, 3.8 works for you Roger, correct?

If so, can you please enable CONFIG_EDAC_DEBUG, rebuild 3.8 and boot
your machine with it and send me the full dmesg of the boot?

> with csrow->channels[1]->dimm == NULL.
> 
> This code was introduced by the first commit above.  Does the patch
> below fix this?
> 
> Ben.
> 
> ---
> [PATCH] amd64_edac: Fix crash in init_csrows() for memory controller in 
> 64-bit mode
> 
> init_csrows() assumes all processesors after K8 have 2 memory channels.
> But these processors support a mode where only one channel is used.
> It seems that csrow_enabled() may still return true for the second
> channel (BIOS bug?).

Ok, I think I know what the problem is:

[5.815246] EDAC amd64: DRAM ECC enabled.
[5.816328] EDAC amd64: F15h detected (node 0).
[5.817397] EDAC amd64: MC: 0: 0MB 1: 0MB
[5.818379] EDAC amd64: MC: 2: 0MB 3: 0MB
[5.819332] EDAC amd64: MC: 4: 0MB 5: 0MB
[5.820250] EDAC amd64: MC: 6: 0MB 7: 0MB
[5.821176] EDAC amd64: MC: 0:  4096MB 1:  4096MB
[5.822131] EDAC amd64: MC: 2:  4096MB 3:  4096MB
[5.823048] EDAC amd64: MC: 4: 0MB 5: 0MB
[5.823927] EDAC amd64: MC: 6: 0MB 7: 0MB
[5.824818] EDAC amd64: using x4 syndromes.
[5.825680] EDAC amd64: MCT channel count: 1

Roger's DIMMs are only on the one channel and the second one is empty.
Btw, Roger, you might want to move one of the DIMMs to a another DIMM
socket on the board so that you can use both channels for performance
reasons.

I'm saying "one of the DIMMs" because I'm assuming those 4G above are
dual-ranked DIMMs and you have two 8G DIMMs on the board.

If they're single-ranked i.e. 4G each, then you shouldn't have any
choice because your board has only 4 DIMM slots anyway, AFAICT from the
manual:

http://www.asus.com/Motherboards/SABERTOOTH_990FX_R20/#support_Download_10

Which would be buggy because you're still using only one DCT.

Btw if you have two DIMMs on there, please put them according to the
recommended memory configurations, i.e. one in A2 and the other in B2.

Here's my layout, for example:

[5.890887] EDAC MC: DCT0 chip selects:
[5.890888] EDAC amd64: MC: 0:  2048MB 1:  2048MB
[5.890889] EDAC amd64: MC: 2:  2048MB 3:  2048MB
[5.890890] EDAC amd64: MC: 4: 0MB 5: 0MB
[5.890891] EDAC amd64: MC: 6: 0MB 7: 0MB
[5.890893] EDAC MC: DCT1 chip selects:
[5.890894] EDAC amd64: MC: 0:  2048MB 1:  2048MB
[5.890894] EDAC amd64: MC: 2:  2048MB 3:  2048MB
[5.890895] EDAC amd64: MC: 4: 0MB 5: 0MB
[5.890896] EDAC amd64: MC: 6: 0MB 7: 0MB
[5.890897] EDAC amd64: using x4 syndromes.
[5.890901] EDAC amd64: MCT channel count: 2

And I have 4 DIMM slots occupied.

> Check pvt->channel_count before csrow_enabled(), and remove the family
> number conditions.
> 
> Reported-by: Roger Leigh 
> Signed-off-by: Ben Hutchings 
> Cc: 717...@bugs.debian.org
> ---
>  drivers/edac/amd64_edac.c | 9 +++--
>  1 file changed, 3 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c
> index 8b6a034..be9c2fe 100644
> --- a/drivers/edac/amd64_edac.c
> +++ b/drivers/edac/amd64_edac.c
> @@ -2084,10 +2084,8 @@ static int init_csrows(struct mem_ctl_info *mci)
>*/
>   for_each_chip_select(i, 0, pvt) {
>   bool row_dct0 = !!csrow_enabled(i, 0, pvt);
> - bool row_dct1 = false;
> -
> - if (boot_cpu_data.x86 != 0xf)
> - row_dct1 = !!csrow_enabled(i, 1, pvt);

Ok, this shouldn't be set if DCT1 doesn't have enabled csrows. So yes,
Roger, that debugging output would be of great help.

Thanks.

-- 
Regards/Gruss,
Boris.

Sent from a fat crate under my desk. Formatting is fine.
--


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

Bug#582109: debian-policy: document triggers where appropriate

[Raphael Hertzog]

On Sat, 20 Jul 2013, Charles Plessy wrote:
> Can you explain what the bug is and what the correction will be ?  Because I

The bug is that triggers are run while the dependencies of the triggered
package are not satisfied. The fix is not to do that and wait until those
dependencies are satisfied (but guillem mentionned that it also needs some
cycle breaking code).

> The misleading point is "just like packages in installed".  In my
> understanding, when a package is upgraded, the packages that depend on it stay
> in the "Installed" state while the new version of the upgraded package is
> unpacked and configured.  Not just the triggers, but also any other command 
> not
> related to the dpkg or apt session that would happen to run at that time can
> fail if they strictly require a function that is not available between unpack
> and configure.

That's true but it's not really comparable. "postinst triggered" ought to
work like "postinst configure" and there you have the guaranty that the
dependencies are configured.

> I do not see any other solution than applying the same restrictions on
> "postinst triggered" as for "postinst configure".  (PS: after reading the
> thread again, I just noticed that this also what you wrote in #671711#68).

I did not write that. On the contrary, re-read:

“The problematic fix is to ensure the same requirements for "postinst
triggered" as for "postinst configure". But we could enforce some
requirements that would probably solve the issues we saw without
introducing cycles.”

There are no "restrictions" for "postinst configure" (you can rely on
dependencies — except if you have a dependency cycle) and there should be
no restrictions for "postinst triggered". But right now, dpkg doesn't
ensure anything. And instead of nothing checked by dpkg, I suggested to
ensure some requirements nevertheless but which are less demanding than
those used by "postinst configure".

> (PPS: By the way, apart from Manoj's excellent diagrams at
> , is 
> there
> an extensive documentation on how package upgrades are handled by APT and 
> Dpkg ?)

I know https://wiki.debian.org/MaintainerScripts too but that's all.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/


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

Bug#717516: linux-image-3.2.0-4-amd64: Segmentation fault in ksoftirqd

[Oliver Lorenz]

Package: src:linux
Version: 3.2.46-1
Severity: normal

Dear Maintainer,

I saw the segmentation fault in my logs today. Don't know what caused it or how
to reproduce it.

-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1

** Command line:
root=/dev/xvda2 ro root=/dev/xvda2 ro 

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

** Kernel log:
[0.029976] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[0.030068] NET: Registered protocol family 1
[0.030076] PCI: CLS 0 bytes, default 64
[0.030104] Unpacking initramfs...
[0.051542] Freeing initrd memory: 29644k freed
[0.054922] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[0.054928] Placing 64MB software IO TLB between 8800f740 - 
8800fb40
[0.054931] software IO TLB at phys 0xf740 - 0xfb40
[0.054996] platform rtc_cmos: registered platform RTC device (no PNP device 
found)
[0.055233] audit: initializing netlink socket (disabled)
[0.055242] type=2000 audit(1374363613.038:1): initialized
[0.064686] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[0.064873] VFS: Disk quotas dquot_6.5.2
[0.064892] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[0.064933] msgmni has been set to 7896
[0.065040] alg: No test for stdrng (krng)
[0.065062] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 
253)
[0.197138] io scheduler noop registered
[0.197144] io scheduler deadline registered
[0.197185] io scheduler cfq registered (default)
[0.197240] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[0.197254] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[0.197257] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[0.197549] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[0.380183] Linux agpgart interface v0.103
[0.380235] i8042: PNP: No PS/2 controller found. Probing ports directly.
[1.381493] i8042: No controller found
[1.381609] mousedev: PS/2 mouse device common for all mice
[1.421427] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[1.421475] rtc_cmos: probe of rtc_cmos failed with error -38
[1.421607] TCP cubic registered
[1.421672] NET: Registered protocol family 10
[1.421925] Mobile IPv6
[1.421930] NET: Registered protocol family 17
[1.421935] Registering the dns_resolver key type
[1.422060] PM: Hibernation image not present or could not be loaded.
[1.422069] registered taskstats version 1
[1.422089] XENBUS: Device with no driver: device/console/0
[1.422094] XENBUS: Device with no driver: device/vbd/51714
[1.422097] XENBUS: Device with no driver: device/vbd/51713
[1.422101] XENBUS: Device with no driver: device/vif/0
[1.422113] /build/linux-s5x2oE/linux-3.2.46/drivers/rtc/hctosys.c: unable 
to open rtc device (rtc0)
[1.422137] Initializing network drop monitor service
[1.422428] Freeing unused kernel memory: 576k freed
[1.422515] Write protecting the kernel read-only data: 6144k
[1.424677] Freeing unused kernel memory: 652k freed
[1.424979] Freeing unused kernel memory: 692k freed
[1.441065] udevd[60]: starting version 175
[1.452731] Initialising Xen virtual ethernet driver.
[1.464123] blkfront: xvda2: flush diskcache: enabled
[1.465944] blkfront: xvda1: flush diskcache: enabled
[1.466389] Setting capacity to 2097152
[1.466396] xvda1: detected capacity change from 0 to 1073741824
[1.967339] EXT4-fs (xvda2): INFO: recovery required on readonly filesystem
[1.967349] EXT4-fs (xvda2): write access will be enabled during recovery
[2.264914] EXT4-fs (xvda2): orphan cleanup on readonly fs
[2.264925] EXT4-fs (xvda2): ext4_orphan_cleanup: deleting unreferenced 
inode 4849673
[2.264943] EXT4-fs (xvda2): ext4_orphan_cleanup: deleting unreferenced 
inode 4849671
[2.264946] EXT4-fs (xvda2): ext4_orphan_cleanup: deleting unreferenced 
inode 4849670
[2.264950] EXT4-fs (xvda2): ext4_orphan_cleanup: deleting unreferenced 
inode 4849669
[2.264957] EXT4-fs (xvda2): ext4_orphan_cleanup: deleting unreferenced 
inode 4849668
[2.264961] EXT4-fs (xvda2): ext4_orphan_cleanup: deleting unreferenced 
inode 4849667
[2.264980] EXT4-fs (xvda2): 6 orphan inodes deleted
[2.264983] EXT4-fs (xvda2): recovery complete
[2.505149] EXT4-fs (xvda2): mounted filesystem with ordered data mode. 
Opts: (null)
[3.813915] udevd[254]: starting version 175
[3.955272] input: PC Speaker as /devices/platform/pcspkr/input/input0
[3.970151] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
[4.019515] Error: Driver 'pcspkr' is already registered, aborting...
[4.356384] Adding 1048572k swap on /dev/xvda1.  Priority:-1 extents:1 
across:1048572k SS
[4.376210] EXT4-fs (xvda2): re-mounted. Opts: (null)
[4.497794] EXT4-fs (xv

Bug#681088: watchquagga is a beast...

[Harald Kapper]

Hi,
I second that bug and problem.

Trying virtually anything I found out that strings like these: -s 
'/usr/sbin/service_quagga_start_%s' -k '/usr/sbin/service_quagga_stop_%s' do 
work flawless for watchquagga_options.

Also this line gets fully handed over to the watchquagga script:

watchquagga_options=" -dz -R '/usr/sbin/service quagga restart' "

and results in a good looking processlist:
ps xa | grep -i quagga
   6983 ?Ss 0:00 /usr/lib/quagga/zebra --daemon -A 127.0.0.1
   6987 ?Ss 0:00 /usr/lib/quagga/ospfd --daemon -A 127.0.0.1
   6991 ?Ss 0:00 /usr/lib/quagga/ospf6d --daemon -A ::1
   6995 ?Ss 0:00 /usr/lib/quagga/watchquagga -dz -R 
'/usr/sbin/service quagga restart' zebra ospfd ospf6d


But this doesn't work anyway (tested by kililng ospf6d, the down-state gets 
noted, but the restart fails).
Then killed watchquagga and started is as root from a shell:
/usr/lib/quagga/watchquagga -dz -R '/usr/sbin/service quagga restart' zebra 
ospfd ospf6d

It promptly detects the not-running ospf6d and does a clean restart.
After everything is back to normal (watchquagga has been started by the full 
restart by the init-script) I kill ospf6d again and this is it. State down gets 
detected, but the background restart command fails with error-code 2.

I'd appreciate any hints from here on, we're now at the following solution:

/etc/quagga/debian.conf -> watchquagga_enable=no

And we start it separately in a script that does call itself if there is action 
to be done:
/usr/lib/quagga/watchquagga -dz -R '/etc/init.d/quagga restart && 
/etc/rc.watchquagga' ospf6d ospfd zebra

I'm feeling dumb, but that seems to be the only way to get in running on debian 
using the package quagga 0.99.21-4+wheezy1

best regards,
Harald Kapper / kapper.net


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

Bug#522741: ieee-data: not actually including oui.txt

[Octavio Alvarez]

Hi.

I'd like to ask if there was any progress on this. I'd like to package  
ipv6-toolkit but the licensing of oui.txt is "unclear" (to say the best).


there's "progress" in the sense that licensing terms for ieee data are  
not still clear


Some say that it is not copyrightable for being a list of facts [1],  
others say that databases are copyrightable in some places [2], and some  
claim to have written to the IEEE and received a negative permission on  
redistribution of the file [3].


[1] http://lists.debian.org/debian-legal/2006/02/msg00175.html
[2] http://lists.debian.org/debian-legal/2006/02/msg00208.html
[3]  
https://blog.flameeyes.eu/2012/04/who-said-that-ids-wouldn-t-have-license-issues


What if this package downloaded the data live from the Internet like the  
flashplugin-nonfree does?


--
Octavio.


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

Bug#697627: RFS: gogglesmm/0.12.7-1

[Hendrik Rittich]

Hi Sebastian,

thank you for your review.

> Those libraries are linked due to the pkg-config file generated during
> the build of gogglesmm. libfox-1.6-dev's fox.pc only says to link
> against liblFOX-1.6. So using the pkg-config file provided by
> libfox-1.6-dev gets rid of all the unnecessary dependencies.
> 
> Removing the unecessary dependencies means that gogglesmm doesn't need
> to be taken care of if those libraries should ever be transitioned. At
> least for one of the libraries a transition is planned (libpng12 ->
> libpng15).

So that was my mistake. I assumed that fox-config and pkg-config do the
same. Some time ago the package libfox-1.6 did not contain a pkg-config
script. Hence it was necessary to generate one. But fortunately things
have changed so I removed the generation of the pkg-config file.

The corrected version can be obtained via

  dget -x
http://mentors.debian.net/debian/pool/main/g/gogglesmm/gogglesmm_0.12.7-1.dsc

Regards

Hendrik


signature.asc
Description: This is a digitally signed message part

Bug#717515: webalizer: man page states STDIN is default logfile, in reality it is /var/log/apache/access.log.1

[Kenneth Dombrowski]

Package: webalizer
Version: 2.01.10-32.7
Severity: minor


Contrary to the man page statement "If no log file was given, STDIN is used 
for input. If the log filename '-' is specified, STDIN will be forced",
webalizer defaults to /var/log/apache/access.log.1 (probably derived from
debconf setting below) 

This is confusing for users who run webalizer on their logs specifying their
own config with no mention of /var/log/apache/access.log.1 (ex:
mergelog ~/var/log/apache2/*.log.1 | webalizer -c ~/etc/webalizer.conf),
when they receive errors about /var/log/apache not existing.

Forcing STDIN via "-" allows the above command to work as expected.


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

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages webalizer depends on:
ii  debconf [debconf-2.0] 1.5.36.1   Debian configuration management sy
ii  libc6 2.11.3-4   Embedded GNU C Library: Shared lib
ii  libdb4.8  4.8.30-2   Berkeley v4.8 Database Libraries [
ii  libgd2-xpm2.0.36~rc1~dfsg-5  GD Graphics Library version 2
ii  libgeoip1 1.4.7~beta6+dfsg-1 A non-DNS IP-to-country resolver l
ii  libpng12-01.2.44-1+squeeze4  PNG library - runtime
ii  zlib1g1:1.2.3.4.dfsg-3   compression library - runtime

webalizer recommends no packages.

Versions of packages webalizer suggests:
ii  apache2-mpm-prefork [ 2.2.16-6+squeeze11 Apache HTTP Server - traditional n
ii  nginx [httpd] 0.7.67-3+squeeze3  small, but very powerful and effic

-- debconf information:
  webalizer/logfile: /var/log/apache/access.log.1
  webalizer/doc_title: Usage statistics for
  webalizer/upgrading:
  webalizer/dnscache: false
  webalizer/directory: /var/www/webalizer
  webalizer/upgrade2011030:


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

Bug#717511: Kernel does not start up on Pegasos-2

[Karoly Balogh (Charlie/SGR)]

Hi,

Just for the record, I've installed Wheezy successfully on two Pegasos
IIs, one is a rev 2B1 board, which was installed from scratch, and worked
without major glitches, apart from the fact that the installer required an
installation to MBR partitioned disks, because with RDB disks it said
"Fatal error: Out of memory", when it tried to create the main partition
on an 80GB ATA disk. :)

The other one is a rev 2B3 board, it was upgraded from Squeeze, required
some manual fiddling, but worked in the end. Stock 3.2 kernel and
initramfs in both cases, binary from the ISO (or from the net or what
it builds by default anyway).

Both Pegs have 1GB RAM and Radeon 9200. Everything worked, except the
GBit eth controller.

On Sun, 21 Jul 2013, Ben Hutchings wrote:

> >  Unlikely.
> >  Looks  like  the  kernel  simply  does  not  boot up. It does not say
> > anything.  Nor  it  switches video mode. I just enter boot command and
> > see random flashing rectangles like on old good ZX Spectrum :)
> >  I have one suggestion about it. Looks like this kernel has rather big
> > initrd  attached.  If  so, technically it might occasionally overwrite
> > firmware's code in RAM and kill itself even before the actual startup.
>
> If you run the installer in expert mode you can choose to create a
> 'targeted' initramfs which should be much smaller.

I've seen this. I can't recall if the problem was I've booted vmlinux
instead of vmlinuz accidentally, or got the video= arguments wrong.

(Ps: sorry I've not replied to the answer to my previous question, I had
no chance to try the suggestion on the actual machine.)

Regards,
--
Karoly Balogh


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

Bug#717435: sympa: fails to install if ca-certificates trigger has never been run

[Emmanuel Bouthenot]

On Sun, Jul 21, 2013 at 04:03:23PM +0200, Andreas Beckmann wrote:
[...]

> While this can be fixed with a Pre-Depends, I'm not sure whether this is
> the correct approach. There might be more packages affected by similar
> bugs in the future.

I'd like to avoid as much as possible the usage of Pre-Depends if it is
possible to do otherwise.

I've already committed a 5 lines patch[1] which fix this issue. I'm not
very proud of this patch but it just works and I prefer to do it this
way than adding a Pre-Depends.

[...]

> PS: there is pu request #717493 for adding the pre-depends to sympa
Backporting my patch for sympa in wheezy should be straight forward.

On side note, I wonder if this bug really needs to be fixed in wheezy by
a pu upload.

[1] 
http://anonscm.debian.org/gitweb/?p=collab-maint/sympa.git;a=commitdiff;h=7ab6b9b7de9ec7cd27ebf2d8046f7ea227b583a6

Regards,

M.

-- 
Emmanuel Bouthenot
  mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
  xmpp: kol...@im.openics.org  irc: kolter@{freenode,oftc}


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

Bug#717514: nemiver: Please don't build-depend on gnome-doc-utils

[Jeremy Bicha]

Source: nemiver
Version: 0.9.4-1
Severity: minor
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy

Please drop gnome-doc-utils from Build-Depends and explicitly
build-depend on libxml2-utils instead.
gnome-doc-utils has been replaced by yelp-tools/itstool.

Thanks,
Jeremy

- -- System Information:
Debian Release: wheezy/sid
  APT prefers saucy-updates
  APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500,
'raring'), (100, 'saucy-backports')


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

Bug#717513: goobox: Please drop gnome-doc-utils from Build-Depends

[Jeremy Bicha]

You'll need to explicitly add libxml2-utils though.

Thanks,
Jeremy


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

Bug#717511: Kernel does not start up on Pegasos-2

[Ben Hutchings]

On Sun, 2013-07-21 at 22:07 +0400, Pavel Fedin wrote:
> Hello, Ben.
> 
> 21 июля 2013 г., 21:56:24, you wrote:
> 
> 
> > This might be relevant:
> > https://lists.debian.org/debian-powerpc/2013/07/msg8.html
> 
>  Unlikely.
>  Looks  like  the  kernel  simply  does  not  boot up. It does not say
> anything.  Nor  it  switches video mode. I just enter boot command and
> see random flashing rectangles like on old good ZX Spectrum :)
>  I have one suggestion about it. Looks like this kernel has rather big
> initrd  attached.  If  so, technically it might occasionally overwrite
> firmware's code in RAM and kill itself even before the actual startup.

If you run the installer in expert mode you can choose to create a
'targeted' initramfs which should be much smaller.

>  I  have another machine with a serial port here, i'll try to redirect
> the output to serial port and see what happens.
>  Also i'm currently downloading i386 version in order to install on my
> AspireOne.  Using  it i will be able to cross-build PPC version of the
> kernel,  and  try to run it. This will also help me to either prove or
> reject my guess about initrd.
>  However actually this guess comes from two facts:
> 1. Installed vmlinuz takes rather long time to load.
> 2.  CD  installer  kernel  takes  much shorter time to load, and works
> fine.

I would expect the installer initramfs to be bigger than a normal
generic initramfs, but maybe I'm wrong.

Ben.

>  I  don't  believe  there  are many differences between CD version and
> working version. At least not in early startup code.
> 

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg


signature.asc
Description: This is a digitally signed message part

Bug#717435: sympa: fails to install if ca-certificates trigger has never been run

[Emmanuel Bouthenot]

forcemerge 706965 717435
thanks

Hi Andreas,

On Sat, Jul 20, 2013 at 11:05:01PM +0200, Andreas Beckmann wrote:
[...]

> during a test with piuparts I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.

This bug is already fixed in git repository[1]. I'm currently working on
packaging Sympa 6.1.17, hence it will be fixed with the next upload.

Some work remains on the apache 2.4 transition (see #669803) before
uploading this new release in unstable.


[1] 
http://anonscm.debian.org/gitweb/?p=collab-maint/sympa.git;a=commitdiff;h=7ab6b9b7de9ec7cd27ebf2d8046f7ea227b583a6

Regards,

M.

-- 
Emmanuel Bouthenot
  mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
  xmpp: kol...@im.openics.org  irc: kolter@{freenode,oftc}


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

Bug#717435: sympa: fails to install if ca-certificates trigger has never been run

[Andreas Beckmann]

Hi Emmanuel,

On 2013-07-21 20:09, Emmanuel Bouthenot wrote:
> This bug is already fixed in git repository[1]. I'm currently working on
> packaging Sympa 6.1.17, hence it will be fixed with the next upload.
> [1] 
> http://anonscm.debian.org/gitweb/?p=collab-maint/sympa.git;a=commitdiff;h=7ab6b9b7de9ec7cd27ebf2d8046f7ea227b583a6

Nice. Much better than my suggestion of using pre-depends.
Do you think you can cherry-pick this patch for wheezy-pu?
Please reuse #717493 for the pu request.
That might require uploading just this fix to sid first ...


Andreas


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

Bug#717513: goobox: Please drop gnome-doc-utils from Build-Depends

[Jeremy Bicha]

Source: goobox
Version: 3.1.1-1
Severity: minor
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy

Please drop gnome-doc-utils from Build-Depends. It's been replaced by
yelp-tools/itstool.

Thanks,
Jeremy

- -- System Information:
Debian Release: wheezy/sid
  APT prefers saucy-updates
  APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500,
'raring'), (100, 'saucy-backports')


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

Bug#717420: update reSIProcate in stable from 1.8.5 -> 1.8.12

[Adam D. Barratt]

On Sat, 2013-07-20 at 20:26 +0200, Daniel Pocock wrote:
> Package: release.debian.org
> Severity: important

Nope. Bugs in packages may have all kinds of severities, requests to
update packages in stable are "normal" at best. (It would also be
helpful if you used reportbug or otherwise normalised the usertags and
titles when making such requests.)

For the record, I had to dig the mail to which I'm replying out of a BTS
mbox; it never reached the debian-release list, presumably due to the
size of the diff.

> We've found that versions of reSIProcate < 1.8.11-4 are not reliable on
> non-Intel platforms.

Does anyone actually use the package on such architectures?

> In particular, essential code such as the MD5 implementation was not
> being compiled the right way for big endian systems.  The code may
> appear to compile and run but as soon as a user tries to engage in a
> DIGEST authentication they will find that it fails to operate correctly.
[...]
> A long list of other bug fixes is also included, several of them
> eliminate bugs that can cause a crash
> 
> The cumulative effect of all bug fixes on the 1.8.x release branch
> brings a significant improvement in quality and convenience for end users.

The _filtered_ diffstat is "189 files changed, 5819 insertions(+), 2235
deletions(-)" and adds two new packages. We'd need a lot of convincing
that the latter is worth doing, rather than just proving updates via
backports (fwiw, I'm only aware of one occasion where a new package was
introduced to a release once it was stable, and that was
openssh-blacklist via security.d.o, which is a somewhat different
situation).

Regards,

Adam


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

Bug#677246: patch for goobox / musicbrainz5

[Jeremy Bicha]

Version: 3.1.1-1


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

Bug#716720: billard-gl: Crashes when quitting the game

[Markus Koschany]

reassign 716720 freeglut3
forwarded 716720 https://sourceforge.net/p/freeglut/bugs/201/
thanks


On 16.07.2013 22:12, Hans Joachim Desserud wrote:
[...]

> I've done some testing since last time, and I think I've tracked down which 
> change
> caused this issue.
> 
> I have Ubuntu Saucy (the current development release) where the crash is 
> occuring, 
> and Ubuntu 13.04 aka Raring (the latest stable release) where it doesn't 
> crash. Assuming
> whatever causing the crash had been introduced since Raring was released, I 
> figured
> I'd try to install the newer packages on the old system and see what happened.
> 
> First I upgraded billard-gl and -data to 1.17-13, but it closed as expected 
> without any 
> error messages. Ok, next stop dependencies.
> 
> I pulled in the latest version of the freeglut3 package, and then I got the 
> error messages
> and crash when attempting to quit billard-gl. I also verified it went away 
> when I uninstalled
> the package and reinstalled the old one.
> In other words:
> with freeglut3 2.6.0-4ubuntu1 : exits cleanly
> with freeglut3 2.8.1-1 : error message and crash
> 
> I don't have any older Debian releases to test with right now, otherwise I'd 
> done so,
> though since I can reproduce crash in Sid I assume it was also introduced 
> there 
> with the new version of the library.

I think this is most likely a bug and a regression in freeglut3, version
2.8.1. I have forwarded this bug report to freeglut's upstream bug
tracker at sourceforge.net.

https://sourceforge.net/p/freeglut/bugs/201/

I think the way how billard-gl calls "exit" is correct and there is not
much what we can do here to improve the situation.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#717488: Please always launch /etc/init.d/ups-monitor when halting the system

[Fabien C.]

tags 717488 patch
thanks

Here is a patch to describe my bug report. 

Thanks. 
diff -urN a/etc/init.d/halt b/etc/init.d/halt
--- a/etc/init.d/halt	2012-10-15 19:30:41.0 +0200
+++ b/etc/init.d/halt	2013-07-21 20:03:17.840931573 +0200
@@ -33,7 +33,7 @@
 	fi
 
 	# See if we need to cut the power.
-	if [ "$INIT_HALT" = "POWEROFF" ] && [ -x /etc/init.d/ups-monitor ]
+	if [ -x /etc/init.d/ups-monitor ]
 	then
 		/etc/init.d/ups-monitor poweroff
 	fi

Bug#717511: Kernel does not start up on Pegasos-2

[Pavel Fedin]

Hello, Ben.

21 июля 2013 г., 21:56:24, you wrote:


> This might be relevant:
> https://lists.debian.org/debian-powerpc/2013/07/msg8.html

 Unlikely.
 Looks  like  the  kernel  simply  does  not  boot up. It does not say
anything.  Nor  it  switches video mode. I just enter boot command and
see random flashing rectangles like on old good ZX Spectrum :)
 I have one suggestion about it. Looks like this kernel has rather big
initrd  attached.  If  so, technically it might occasionally overwrite
firmware's code in RAM and kill itself even before the actual startup.
 I  have another machine with a serial port here, i'll try to redirect
the output to serial port and see what happens.
 Also i'm currently downloading i386 version in order to install on my
AspireOne.  Using  it i will be able to cross-build PPC version of the
kernel,  and  try to run it. This will also help me to either prove or
reject my guess about initrd.
 However actually this guess comes from two facts:
1. Installed vmlinuz takes rather long time to load.
2.  CD  installer  kernel  takes  much shorter time to load, and works
fine.
 I  don't  believe  there  are many differences between CD version and
working version. At least not in early startup code.

-- 
Kind regards,
 Pavel  mailto:pavel_fe...@mail.ru


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