Bug#500375: can you reproduce this?

[Russell Coker]

Please tell me how to reproduce it and I'll fix it.

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


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

Bug#694011: desktop-base: problem after updating from Squeeze to Wheezy

[Boris Pek]

Hi,

>> I faced with problem after updating from Squeeze to Wheezy on my laptop:
>> KDM fails to start because spacefun theme for KDM is absent [1].
> 
> That's not a problem, the Wheezy theme is Joy.

This will be a problem for inexperienced users who will update their systems.

>> I was surprised and checked problem on clean install in VirtualBox.
>> And the bug is reproducible.
> 
> So you installed a clean KDE Squeeze and upgraded to Wheezy?

Yes.

>> Possible fix is pretty simple:
>> 
>> --- desktop-base.links  (revision 0)
>> +++ desktop-base.links  (working copy)
>> @@ -0,0 +1 @@
>> +usr/share/kde4/apps/kdm/themes/joy usr/share/kde4/apps/kdm/themes/spacefun
> 
> That looks like a wrong way to do it. In any case, kdm shouldn't
> directly use spacefun or joy but use a generic name so it's correctly
> handled on upgrades. What puzzles me is that Joy is available since
> months and you're the first one to report an issue with upgrades.

KDE System Settings allow to choose any KDM theme manually. In this case after
updating package desktop-base KDM will fails to start. Maybe the problem is
in KDM: it should use default theme if current theme is not found.
 
> I have no knowledge of KDE so I'll let involved people reply, but
> there's something very fishy here.

Nothing fishy. Everyone could check it using VirtualBox, Qemu and etc.

For a note: I didn't use a CD with KDE, but netinstall + kde metapackage.

Best regards,
Boris

Bug#693655: ugene: Please update ugene to the latest version 1.11.3

[Ivan Efremov]

Hi Andreas,

Thanks for catching this issue.
I agree that (2b) works perfectly for us. Technically, it looks trivial to
split the packages.

We are going to fix our Ubuntu packages. Once this is done it will be easy
to repackage Debian ones. Basically, this would require moving couple of
dynamic libraries (phylip and psipred) to a separate .deb.

I'll post a notification once we are done with Ubuntu packages.
You can track our progress at
https://ugene.unipro.ru/tracker/browse/UGENE-1310 


Regards,
Ivan




> -Original Message-
> From: Andreas Tille [mailto:andr...@an3as.eu]
> Sent: Thursday, November 22, 2012 4:57 PM
> To: Ivan Efremov
> Cc: 693...@bugs.debian.org; 'Logan Rosen'
> Subject: Re: Bug#693655: ugene: Please update ugene to the latest version
> 1.11.3
> 
> Hi,
> 
> On Wed, Nov 21, 2012 at 09:35:10AM +0100, Andreas Tille wrote:
> > Hi Ivan,
> >
> > thanks for the help - I hope to get the Debian packaging soonish.
> 
> hmmm, I guess that there is some showstopper in getting out the latest
> version soon.  I was updating the debian/copyright file and noticed that
> the tarball does contain two non-free components:
> 
> Files: src/plugins_3rdparty/psipred/src/seq2mtx.cpp
>src/plugins_3rdparty/psipred/src/sspred_avpred.cpp
>src/plugins_3rdparty/psipred/src/sspred_hmulti.cpp
> Copyright: C 2000 D.T. Jones 
> License:
> ...
>  1. The User will receive the Software and any related documentation in
> confidence and will not use the same except for the purpose of their
> own
> research. The Software will be used only by such of the User's
> officers or
> employees to whom it must reasonably be communicated to enable them to
> undertake their research and who agree to be bound by the same
> confidence.
> The User shall procure and enforce such agreement from his or her
> staff for
> the benefit of the Copyright holder.
> ...
>  3. All forms of the Software will be kept in a reasonably secure place to
> prevent unauthorised access.
> ...
>  6. The Software may not be sold as a standalone package, or incorporated
> into
> a commercial software package without the written permission of the
> Copyright
> holder. The Software may be used freely for individual academic or
> commercial
> research. The Software may also be made freely available for training
> or
> teaching purposes.
>  .
>  7. The results produced by the Software may not be incorporated into any
> data banks or databases which are subject to the payment of access or
> license fees without the written permission of the Copyright holder.
>  .
>  8. The Software may be made available to users over a local network or
> wide area network (including the Internet), but only if access is
> granted
> free of charge to all authorised users. Incorporation of the Software
> into
> a commercial Web site or other fee paying service is not allowed
> without
> the written permission of the Copyright holder. If PSIPRED results are
> returned to the user via such a network service, then a suitable
> acknowledgement of the PSIPRED method must be returned somewhere in
> the
> output text.
> ...
> 
> 
> That's all pretty non-free.
> 
> Moreover the source does contain a copy of phylip which we all know is
> non-free (and you might even like to try signing a petition to convince
> the
> authors freeing their code[1].)
> 
> 
> So what can we do?
> 
>1. Move whole Ugene package to non-free (simple but gutless)
>2. Splitting those non-free parts from tarball and use Debian packaged
>   code (from non-free - we do have at least phylip there and could try
>   to package psipred as well if urgently needed).
>   Then it depends from the fact whether
>a) component is urgently needed by ugene and we need to add a
>   Depends/Recommends -> ugene needs to go to contrib
>b) ugene runs fine without thes components and these are just an
>   enhancement -> ugene remains in main and just Suggests those
>   non-free components
> 
> I'd consider 2b) the ideal situation but I can neither decide about the
> relation between ugene and those modules nor do I know whether the split
> is technically easily feasible.
> 
> Regarding third party components:  We just replaced zlib but there are a
> real lot of plugins readily packaged for Debian.  I'd really love if we
> could modularise ugene a bit more and use the Debian packaged components
> if this is somehow possible.  I'd volunteer to create a list based on our
> pool of biological applications[2] and libraries[3].
> 
> Kind regards
> 
>   Andreas.
> 
> [1]
> https://wiki.debian.org/DebianMed/Meeting/Southport2012/ePetition_Phylip
> [2] http://debian-med.alioth.debian.org/tasks/bio
> [3] http://debian-med.alioth.debian.org/tasks/bio-dev
> 
> --
> http://fam-tille.de


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

Bug#694028: [wheezy] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)

[Jonathan Nieder]

Hi Daniel,

Daniel Kahn Gillmor wrote:

> As you can see from the dmesg output, i had a kernel oops related
> somehow to a failed paging request.
>
> This happened just about the time that i plugged this laptop (an Asus
> EeePC 900) into wall power, after a brief period of time running from
> the battery.  The machine was using the wireless NIC the entire time.
[...]
> I don't know if this is enough info to debug, or if this is something
> that maybe should be chalked up to hardware failures; but i'd be happy
> to provide more information if it would be useful to anyone.

Thanks for reporting it.  I haven't looked at your log yet, but my
generic advice is: please attach full "dmesg" output from an affected
boot, which will show what happened at initialization time, and full
"acpidump" output, which will show if some of the ACPI tables for
power-related events do strange things.

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#694041: xul-ext-adblock-plus: filters reset after restarting iceweasel

[Sven Joachim]

Package: xul-ext-adblock-plus
Version: 2.2-1
Severity: grave

After upgrading xul-ext-adblock-plus to 2.2-1 and restarting iceweasel,
the browser displayed the Adblockplus start page, and all subscriptions
and personal filters were lost.  Restoring patterns.ini from a backup
via the menus did not help.

Googling for the problem, I found that I'm not alone[1].  The
changelog[2] of the latest development snapshot suggests the bug might
be fixed there:

#3588: 2012-11-22 15:48 +0100 Wladimir Palant
Fixed: Filter reading broken in Firefox 10


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

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

Versions of packages xul-ext-adblock-plus depends on:
ii  iceape 2.7.10-1
ii  icedove10.0.10-1
ii  iceweasel  10.0.11esr-1

xul-ext-adblock-plus recommends no packages.

xul-ext-adblock-plus suggests no packages.

-- no debconf information


1. 
https://adblockplus.org/forum/viewtopic.php?f=1&t=11662&sid=490c273d51be06dcb0a9fee9f3dee33a
2. 
https://adblockplus.org/devbuilds/adblockplus/adblockplus-2.2.1a.3588.changelog.xhtml


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

Bug#694042: 404 Not Found errors using mirror ftp.tw.debian.org

[James Lick]

Package: mirrors
Severity: normal

Receiving the following errors using 'apt-get update' with mirror
ftp.tw.debian.org:

Ign http://ftp.tw.debian.org stable Release.gpg
Ign http://ftp.tw.debian.org/debian/ stable/main Translation-en
Ign http://ftp.tw.debian.org/debian/ stable/main Translation-en_US
Ign http://ftp.tw.debian.org stable Release
Ign http://ftp.tw.debian.org stable/main Sources/DiffIndex
Ign http://ftp.tw.debian.org stable/main i386 Packages/DiffIndex
Ign http://ftp.tw.debian.org stable/main Sources
Ign http://ftp.tw.debian.org stable/main i386 Packages
Ign http://ftp.tw.debian.org stable/main Sources
Ign http://ftp.tw.debian.org stable/main i386 Packages
Err http://ftp.tw.debian.org stable/main Sources
  404  Not Found
Err http://ftp.tw.debian.org stable/main i386 Packages
  404  Not Found
Get:1 http://security.debian.org stable/updates Release.gpg [836 B]
Ign http://security.debian.org/ stable/updates/main Translation-en
Ign http://security.debian.org/ stable/updates/main Translation-en_US
Get:2 http://security.debian.org stable/updates Release [86.9 kB]
Get:3 http://security.debian.org stable/updates/main Sources [90.6 kB]
Get:4 http://security.debian.org stable/updates/main i386 Packages [272 kB]
Fetched 450 kB in 3s (119 kB/s)
W: Failed to fetch
http://ftp.tw.debian.org/debian/dists/stable/main/source/Sources.gz  404
 Not Found

W: Failed to fetch
http://ftp.tw.debian.org/debian/dists/stable/main/binary-i386/Packages.gz
404  Not Found

E: Some index files failed to download, they have been ignored, or old ones
used instead.
Reading package lists... Done

-- 
James Lick -- 黎建溥 -- james.l...@jameslick.com -- http://jameslick.com/

Bug#694011: desktop-base: problem after updating from Squeeze to Wheezy

[Boris Pek]

I have just found bug #570478 and it looks very similar.
But I disagree with "Severity: normal".

Bug#693896: [siege] siege crashes on FQDN in URL

[Török Edwin]

On 11/23/2012 04:55 AM, Josue Abarca wrote:
> On Wed, Nov 21, 2012 at 04:56:55PM +0200, Török Edwin wrote:
>> Package: siege
>> Version: 2.70-4
>> Severity: normal
> ...
>> Architecture: amd64
>> Kernel:   Linux 3.6.6
>>
>> Debian Release: wheezy/sid
>>   500 unstableftp.ro.debian.org
>> 1 experimentalftp.ro.debian.org
>>
>> --- Package information. ---
>> Depends  (Version) | Installed
>> ==-+-===
>> libc6 (>= 2.7) |
>> libssl1.0.0 (>= 1.0.0) |
> 
> Which versions of libc6 and libssl1.0.0 are you using?
> 
> I am trying to reproduce with the latest versions in sid:
> $ dpkg -l libc6
> ii  libc6:amd642.13-37  amd64
> 
> $ dpkg -l libssl1.0.0
> ii  libssl1.0.0:am 1.0.1c-4 amd64

I've got the same.

> 
> I have been trying, but I have not been able to reproduce the bug.
> 
> Maybe you could try to reproduce it with upstream "2.70" version
> http://www.joedog.org/pub/siege/siege-2.70.tar.gz

It doesn't crash, and valgrind doesn't say anything either.

I've done an 'apt-get source siege', and that doesn't crash either if I 
manually build it
(using a simple ./configure && make).
Maybe it has something to do with the way the Debian package is built (I see 
its using hardening-wrapper).

I've rebuilt the Debian package using pbuilder in a wheezy chroot and a squeeze 
chroot.
None of them crash.

I've just checked again and /usr/bin/siege from the Debian repository still 
crashes.

> 
> In the mean time I'll prepare a debug symbols package for you.

Do you remember what environment/compiler versions where used to build it?
Because apparently simply rebuilding the package makes the crash go away, which 
makes me
believe that it might be due to a compiler bug?

> 
> Here is my output, using your ".siegerc" file:
> 
> $ siege -R .siegerc http://www.jmaslibre.org/index.html
> ** SIEGE 2.70
> ** Preparing 15 concurrent users for battle.
> The server is now under siege...
> Lifting the server siege...  done.
> Transactions:   11 hits
> Availability:   100.00 %
> Elapsed time: 9.32 secs
> Data transferred: 0.00 MB
> Response time:2.21 secs
> Transaction rate: 1.18 trans/sec
> Throughput:   0.00 MB/sec
> Concurrency:  2.61
> Successful transactions:  11
> Failed transactions: 0
> Longest transaction:  5.37
> Shortest transaction: 5.33
>  
> FILE: /var/tmp/siege.log
> You can disable this annoying message by editing
> the .siegerc file in your home directory; change
> the directive 'show-logfile' to false.
> 
> $ siege -R .siegerc http://debian.home.lan/index.html
> ** SIEGE 2.70
> ** Preparing 15 concurrent users for battle.
> The server is now under siege...
> Lifting the server siege...  done.
> Transactions:269 hits
> Availability:100.00 %
> Elapsed time:9.95 secs
> Data transferred:0.04 MB
> Response time:   0.00 secs
> Transaction rate:27.04 trans/sec
> Throughput:  0.00 MB/sec
> Concurrency: 0.11
> Successful transactions: 269
> Failed transactions: 0
> Longest transaction: 0.02
> Shortest transaction:0.00
> 
> FILE: /var/tmp/siege.log
> You can disable this annoying message by editing
> the .siegerc file in your home directory; change
> the directive 'show-logfile' to false.
> 
> 
> Cheers,
> 


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

Bug#694011: desktop-base: problem after updating from Squeeze to Wheezy

[Yves-Alexis Perez]

On ven., 2012-11-23 at 12:11 +0400, Boris Pek wrote:
> Hi,
> 
> >> I faced with problem after updating from Squeeze to Wheezy on my laptop:
> >> KDM fails to start because spacefun theme for KDM is absent [1].
> > 
> > That's not a problem, the Wheezy theme is Joy.
> 
> This will be a problem for inexperienced users who will update their systems.

I didn't mean that KDM not starting was not a problem. I meant that
changing theme from Spacefun to Joy was not one.
> 
> >> I was surprised and checked problem on clean install in VirtualBox.
> >> And the bug is reproducible.
> > 
> > So you installed a clean KDE Squeeze and upgraded to Wheezy?
> 
> Yes.
> 
> >> Possible fix is pretty simple:
> >> 
> >> --- desktop-base.links  (revision 0)
> >> +++ desktop-base.links  (working copy)
> >> @@ -0,0 +1 @@
> >> +usr/share/kde4/apps/kdm/themes/joy usr/share/kde4/apps/kdm/themes/spacefun
> > 
> > That looks like a wrong way to do it. In any case, kdm shouldn't
> > directly use spacefun or joy but use a generic name so it's correctly
> > handled on upgrades. What puzzles me is that Joy is available since
> > months and you're the first one to report an issue with upgrades.
> 
> KDE System Settings allow to choose any KDM theme manually. In this case after
> updating package desktop-base KDM will fails to start.

So you didn't just install a clean KDE Squeeze, you also changed the
theme manually?

>  Maybe the problem is
> in KDM: it should use default theme if current theme is not found.

Indeed. Or only present the virtual, Debian theme which points to the
current theme.

Regards,
-- 
Yves-Alexis


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

Bug#694011: desktop-base: problem after updating from Squeeze to Wheezy

[Yves-Alexis Perez]

On ven., 2012-11-23 at 12:26 +0400, Boris Pek wrote:
> I have just found bug #570478 and it looks very similar.
> But I disagree with "Severity: normal".

Yup, looks related.

To me there's two issues/fixes:

1) make KDM correctly handle the case where the selected theme is gone
2) make desktop-base KDE config points to the virtual theme and not the
named theme so it's always available

Both are even better, because I guess that, if one installs a default
KDE Debian and then remove desktop-base the same problem will happen.

Regards,
-- 
Yves-Alexis


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

Bug#693937: [Pkg-xfce-devel] Bug#693937: Bug#693937: Bug#693937: Bug#693937: Acknowledgement (thunar: Thunar crashes when mounting USB stick)

[Yves-Alexis Perez]

On ven., 2012-11-23 at 07:14 +0100, Yves-Alexis Perez wrote:
> On jeu., 2012-11-22 at 23:20 +0100, Frane Šalković wrote:
> > On 11/22/2012 11:10 PM, Yves-Alexis Perez wrote:
> > > Can you provide a backtrace? Do you have any other gvfs packages? And
> > > you you have any gvfs-mounted stuff?
> > >
> > > Regards,
> > I've removed gvfs-fuse now and all the gvfs-* packages. Now Thunar
> > doesn't crash, but now I can access USB only by clicking on /media/usb0.
> > It's not shown on the left side as it was before.
> > 
> Can you provide a backtrace then? There's no reason that gvfs-fuse
> should be required, so I'm unsure what happens there.

I just tested on a sid/amd64 box and it works fine here.

Currently installed gvfs packages are:

gvfs
gvfs-backends
gvfs-bin
gvfs-common
gvfs-daemons
gvfs-libs

Regards,
-- 
Yves-Alexis


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

Bug#694043: /usr/bin/usb-devices: basename: extra operand `driver'

[Vincent Smeets]

Package: usbutils
Version: 0.87-5squeeze1
Severity: normal
File: /usr/bin/usb-devices
Tags: patch


The command usb-devices gives an error for one of my devices.

T:  Bus=01 Lev=03 Prnt=05 Port=00 Cnt=01 Dev#= 11 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=00 Prot=ff MxPS=64 #Cfgs=  1
P:  Vendor=9710 ProdID=7830 Rev=01.00
S:  Manufacturer=Moschip Semiconductor
S:  Product=UA0025C  
S:  SerialNumber=6e01
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
basename: extra operand `driver'
Try `basename --help' for more information.
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=

It gives an error on the command basename for displaying the interfaces.
I have also executed the command using:
bash -x /usr/bin/usb-devices
The relevant part of the error stream is:

+ '[' -L /sys/bus/usb/devices/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.0/driver
']'
++ readlink /sys/bus/usb/devices/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.0/driver
+ driver='../../../../../../../../bus/usb/drivers/MOSCHIP usb-ethernet driver'
++ basename ../../../../../../../../bus/usb/drivers/MOSCHIP usb-ethernet driver
basename: extra operand `driver'
Try `basename --help' for more information.
+ driver=

The problem is that the filename contains spaces and they are passed as
multiple arguments to the basename command. Change the relevant parts of
the bash script from:
driver=`basename $driver`
to
driver=`basename "$driver"`
You should always use quotes "" around variables that can contain spaces
or other special characters. Please check all the occurences in the
file.

Regards,
Vincent Smeets

-- System Information:
Debian Release: 6.0.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.iso88591, LC_CTYPE=de_DE.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages usbutils depends on:
ii  libc6   2.11.3-4 Embedded GNU C Library: Shared lib
ii  libusb-0.1-42:0.1.12-16  userspace USB programming library
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

usbutils recommends no packages.

Versions of packages usbutils suggests:
ii  wget  1.12-2.1   retrieves files from the web

-- 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#694011: desktop-base: problem after updating from Squeeze to Wheezy

[Boris Pek]

control: reassign 694011 kdm 4:4.8.4-4
control: retitle  694011 kdm: KDM fails to start when current theme is absent

>> I have just found bug #570478 and it looks very similar.
>> But I disagree with "Severity: normal".
> 
> Yup, looks related.
> 
> To me there's two issues/fixes:
> 
> 1) make KDM correctly handle the case where the selected theme is gone
> 2) make desktop-base KDE config points to the virtual theme and not the
> named theme so it's always available
> 
> Both are even better, because I guess that, if one installs a default
> KDE Debian and then remove desktop-base the same problem will happen.

Ok, bug is reassigned.

Regards,
Boris

Bug#690453: android-tools-adb should install udev rules for easy device access

[Vincent Bernat]

Package: android-tools-adb
Version: 4.1.1+git20120801-1
Followup-For: Bug #690453

Hi!

Here is a generic udev rule for this purpose :

✂-
# Set ACLs for console users on ADB compatible devices
# ADB_CLASS== 0xff
# ADB_SUBCLASS == 0x42
# ADB_PROTOCOL == 0x1

ENV{ACL_MANAGE}=="0", GOTO="adb_android_end"
ACTION!="add|change", GOTO="adb_android_end"
SUBSYSTEM=="usb", ENV{ID_USB_INTERFACES}=="*:ff4201:*", TAG+="udev-acl"
LABEL="adb_android_end"
✂-

Otherwise, we could also use ATTRS{bInterfaceClass}==255,
ATTRS{bInterfaceSubClass}==66, ATTRS{bInterfaceProtocol}==1 instead of
ENV{ID_USB_INTERFACES}.

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

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

Versions of packages android-tools-adb depends on:
ii  libc6   2.13-37
ii  zlib1g  1:1.2.7.dfsg-13

android-tools-adb recommends no packages.

android-tools-adb 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#694018: (no subject)

[Nikita V. Youshchenko]

Nor it needs bluetooth


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

Bug#693937: [Pkg-xfce-devel] Bug#693937: Bug#693937: Bug#693937: Bug#693937: Acknowledgement (thunar: Thunar crashes when mounting USB stick)

[Frane Šalković]

On 11/23/2012 10:14 AM, Yves-Alexis Perez wrote:
> I just tested on a sid/amd64 box and it works fine here.
>
> Currently installed gvfs packages are:
>
> gvfs
> gvfs-backends
> gvfs-bin
> gvfs-common
> gvfs-daemons
> gvfs-libs
>
> Regards,
Thank you very much! It's solved now! I've installed those packages you
mentioned, logout and it works fine ;)


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

Bug#693655: ugene: Please update ugene to the latest version 1.11.3

[Andreas Tille]

Hi Ivan,

On Fri, Nov 23, 2012 at 03:19:39PM +0700, Ivan Efremov wrote:
> Thanks for catching this issue.

You are welcome - it is one of the goals of Debian Med project to work
together with upstream as close as possible for a common goal to spread
free software.

> I agree that (2b) works perfectly for us. Technically, it looks trivial to
> split the packages.

That's great.

> We are going to fix our Ubuntu packages. Once this is done it will be easy
> to repackage Debian ones. Basically, this would require moving couple of
> dynamic libraries (phylip and psipred) to a separate .deb.

Phylip is packaged for Debian (and thus also available in Ubuntu).  We do also
have some preparation for psipred in our packaging SVN[1] - so throwing out
packages to non-free should be no real problem (hopefully).

Since you confirmed that it might be technically trivial to split
plugins from Ugene I wonder whether you might support the idea I
expressed in my last mail (see below for the relevant part) to use
Debian packaged versions of those plugins you are providing.  For
instance we do have packaged ball, hmmer2+3, kalign, primer3 and from a
distribution maintenance of view it is a good idea to prevent code
duplication and rather define dependencies to the according packages
(same applies for sure for Ubuntu).  What do you think about this idea.

> I'll post a notification once we are done with Ubuntu packages.
> You can track our progress at
> https://ugene.unipro.ru/tracker/browse/UGENE-1310 

Thanks for the link.  I'll create an according bug report inside Debian
to keep a proper record.

Kind regards

   Andreas.

[1] http://debian-med.debian.net/tasks/bio#psipred 


> -Original Message-
> From: Andreas Tille [mailto:andr...@an3as.eu]
> Sent: Thursday, November 22, 2012 4:57 PM
> To: Ivan Efremov
> Cc: 693...@bugs.debian.org; 'Logan Rosen'
> Subject: Re: Bug#693655: ugene: Please update ugene to the latest version
> 1.11.3
> 
> ...
> Regarding third party components:  We just replaced zlib but there are a
> real lot of plugins readily packaged for Debian.  I'd really love if we
> could modularise ugene a bit more and use the Debian packaged components
> if this is somehow possible.  I'd volunteer to create a list based on our
> pool of biological applications[2] and libraries[3].

> [2] http://debian-med.alioth.debian.org/tasks/bio
> [3] http://debian-med.alioth.debian.org/tasks/bio-dev


-- 
http://fam-tille.de


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

Bug#693960: [Pkg-sysvinit-devel] Bug#693960: sysvinit: Undocumented, obscure limit for "process" field in inittab entries

[Johannes Truschnigg]

On Thu, Nov 22, 2012 at 05:30:31PM -0200, Henrique de Moraes Holschuh wrote:
> Eh, should we also increase that limit to something larger [if it is
> feasible to do so] ?

Whilst I do not like that kind of arbitrary limit, I don't think it's
critically important (let alone good) to have absurdly long lines in inittab.
If you need to do something that doesn't fit in 127 bytes on its command line,
you might just as well write a wrapper, and call that fron inittab. Helps
keeping things tidy - but that's personal preference of course.

-- 
with best regards:
- Johannes Truschnigg ( johan...@truschnigg.info )

www:   http://johannes.truschnigg.info/
phone: +43 650 2 17
xmpp:  johan...@truschnigg.info

Please do not bother me with HTML-email or attachments. Thank you.


signature.asc
Description: Digital signature

Bug#694044: ugene: Source contains non-free components

[Andreas Tille]

Package: ugene
Severity: serious
Tags: experimental upstream
Justification: need to remove non-free components

Hi,

the ugene source code contains two non-free plugins namely phylip
(packaged in non-free) and psipred (prepared by Debian Med team in
SVN[1]).  The issue was reported upstream and is tracked there at

   https://ugene.unipro.ru/tracker/browse/UGENE-1310

The discussion about a solution is done in bug #693655 starting
here[2].

Kind regards

Andreas.

[1] svn://svn.debian.org/debian-med/trunk/packages/psipred/trunk/
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693655#25

-- System Information:
Debian Release: 6.0.6
Architecture: i386 (i686)

Kernel: Linux 2.6.36-xenU-4814-i386 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


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

Bug#690793: Re: Bug#690793: Build for multiarch

[Philipp A. Hartmann]

Hi all,

are there any news on MultiArch support for libelf?

On 17/10/12 23:03, Alex Pennace wrote:
> On Wed, Oct 17, 2012 at 05:49:15PM +0100, Iain Lane wrote:
[snip]
>> I created a patch to enable this. I'd be very grateful if you would
>> review it for inclusion.
[snip]
> Just to confirm, this isn't needed in wheezy, correct?
> 

I don't know the details about the procedures wrt. the MultiArch release
goal in Wheezy, but I'd really like to see a multiarch enabled libelf1
in Wheezy.

We need to run proprietary third-party software, only available as
32-bit binaries on 64-bit Wheezy machines, and it seems that in our case
libelf1 is one of the showstoppers here.

Any chance to still get this into Wheezy?

Thanks,
  Philipp

-- 
Philipp A. Hartmann
Hardware/Software Design Methodology Group

OFFIS Institute for Information Technology
R&D Division Transportation · FuE-Bereich Verkehr
Escherweg 2 · 26121 Oldenburg · Germany · http://offis.de/en/
Phone/Fax: +49-441-9722-420/282 · PGP: 0x9161A5C0 · Skype: phi.har


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

Bug#694039: qa.debian.org: Use a different color for outdated backports

[Bart Martens]

On Fri, Nov 23, 2012 at 08:54:16AM +0100, Mike Hommey wrote:
> When the backports version is outdated compared to the version in
> testing, it would be useful that ddpo displays it in a different color.

Sounds reasonable to want this.  Any suggestions on the colors to use for
up-to-date and outdated backports ?

Regards,

Bart Martens


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

Bug#693595: lintex: Wrong keys in manpage

[Ryan Kavanagh]

tags 693595 + confirmed upstream
thanks

Dear Andreas,
Thanks for the bug report, and good catch!

Best wishes,
Ryan


signature.asc
Description: Digital signature

Bug#694012: [Pkg-xen-devel] Bug#694012: xen-hypervisor-4.1-amd64: powernow-k8: transition frequency failed [filling the syslog]

[Bastian Blank]

Control: reassign -1 src:linux 3.2.32-1
Control: severity -1 important

On Fri, Nov 23, 2012 at 12:28:08AM +0100, Axel Beckert wrote:
> after an upgrade from Squeeze to Wheezy I see about ten of these per
> second filling my system log (about 8 MB/h):
> Nov 23 00:15:37 acromantula kernel: [  462.544193] powernow-k8: fid trans 
> failed, fid 0x2, curr 0x0
> Nov 23 00:15:37 acromantula kernel: [  462.546919] powernow-k8: transition 
> frequency failed
> This seems to be a known upstream issue, see
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1789

This is a bug in the kernel. The hypervisor correctly denies access to
the hardware.

Bastian

-- 
Oblivion together does not frighten me, beloved.
-- Thalassa (in Anne Mulhall's body), "Return to Tomorrow",
   stardate 4770.3.


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

Bug#693485: keyboard-configuration: XKBLAYOUT, XKBOPTIONS values manually set in /etc/default/keyboard lost on upgrade

[Anton Zinoviev]

On Thu, Nov 22, 2012 at 05:19:51AM +0400, Bob Bib wrote:
> Anton Zinoviev:
> > >
> > > 1) Machine #1:
> > 
> > I have no explanation of this change and I am unable to reproduce it. 
> > Is there something particular about this machine and its configuration?
> > 
> Please tell more specifically what config files etc. should I look at.

This was just a random shot.  Unfortunately I have no idea what might 
have caused the value XKBLAYOUT="" regardless of the configuration.

Anton Zinoviev


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

Bug#694039: qa.debian.org: Use a different color for outdated backports

[Mike Hommey]

On Fri, Nov 23, 2012 at 09:50:30AM +, Bart Martens wrote:
> On Fri, Nov 23, 2012 at 08:54:16AM +0100, Mike Hommey wrote:
> > When the backports version is outdated compared to the version in
> > testing, it would be useful that ddpo displays it in a different color.
> 
> Sounds reasonable to want this.  Any suggestions on the colors to use for
> up-to-date and outdated backports ?

Why not the same colors as those for newer ubuntu packages, and newer
upstreams? (which both look the same color)

Mike


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

Bug#605449: Set up for bacula-director-pgsql runs before that of postgresql-8.4.

[Teodor MICU]

Package: bacula-director-common
Version: 5.2.6+dfsg-6

Hi,

Indeed, any SQL backend (postgresql, mysql ..) does not have to be
local. But in case it is local (as I and many probably have) this
needs to be declared correctly in the init script:

#! /bin/sh
### BEGIN INIT INFO
# Provides:  bacula-director
# Required-Start:$remote_fs $syslog
# Should-Start:  bacula-fd postgresql
# Required-Stop: $remote_fs $syslog
# Should-Stop:   bacula-fd postgresql
# Default-Start: 2 3 4 5
# Default-Stop:  0 1 6
### END INIT INFO

Because the declaration is on "Should-*" it doesn't affect those who
don't have the SQL service on the local system. Its the same mechanism
used for 'bacula-fd' (which I don't have it installed on the Bacula
server).

I'm currently settings this in /etc/insserv/overrides/bacula-director.
You might want to add what others provide in their init script too
(i.e. mysql).

Cheers


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

Bug#694046: bacula-common: missing 'create' directive in logrotate.d/bacula-common

[Teodor]

Package: bacula-common
Version: 5.2.6+dfsg-6
Severity: normal

Hi,

Please improve /etc/logrotate.d/bacula-common file with:

/var/log/bacula/log {
  create 0644 bacula bacula
  compress
  delaycompress
  missingok
  notifempty
  rotate 12
  monthly
}

The most important is "create" directive since on the first rotation the
new permissions will be root:root and Bacula service will not be able to
write there anymore.

This applies to older versions too (i.e. from squeeze).

Cheers


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

Kernel: Linux 3.2.0-4-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 bacula-common depends on:
ii  adduser   3.113+nmu3
ii  initscripts   2.88dsf-34
ii  libc6 2.13-37
ii  libcap2   1:2.22-1.2
ii  libgcc1   1:4.7.2-4
ii  libpython2.7  2.7.3-5
ii  libssl1.0.0   1.0.1c-4
ii  libstdc++64.7.2-4
ii  libwrap0  7.6.q-24
ii  zlib1g1:1.2.7.dfsg-13

bacula-common recommends no packages.

Versions of packages bacula-common suggests:
pn  bacula-doc  

-- 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#694047: util-linux: addpart fails with larger partition lengths or start positions

[Adrian Lang]

Package: util-linux
Version: 2.20.1-5.2
Severity: normal

addpart seems to have serious issues above 2147483648 I think. This results in
partitions starting at 0 or having length 0.

As a workaround I copied partx_add_partition from the current linux-utils repo
and called it, basically like that:


static inline int partx_add_partition(int fd, int partno,
  uint64_t start, uint64_t size)
{
  struct blkpg_ioctl_arg a;
  struct blkpg_partition p;

  p.pno = partno;
  p.start = start << 9;
  p.length = size << 9;
  p.devname[0] = 0;
  p.volname[0] = 0;
  a.op = BLKPG_ADD_PARTITION;
  a.flags = 0;
  a.datalen = sizeof(p);
  a.data = &p;

  return ioctl(fd, BLKPG, &a);
}

partx_add_partition(fd, 3, 8392704ULL, 2930259968ULL);


Worked fine.

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

Kernel: Linux 3.6-trunk-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 util-linux depends on:
ii  debconf [debconf-2.0]  1.5.46
ii  dpkg   1.16.9
ii  initscripts2.88dsf-34
ii  install-info   4.13a.dfsg.1-10
ii  libblkid1  2.20.1-5.2
ii  libc6  2.13-37
ii  libncurses55.9-10
ii  libselinux12.1.9-5
ii  libslang2  2.2.4-15
ii  libtinfo5  5.9-10
ii  libuuid1   2.20.1-5.2
ii  lsb-base   4.1+Debian9
ii  tzdata 2012i-1
ii  zlib1g 1:1.2.7.dfsg-13

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  dosfstools  3.0.13-1
ii  kbd 1.15.3-9
pn  util-linux-locales  

-- debconf information excluded


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

Bug#589821: should we close this bug?

[Thomas Lange]

IMO this bug can be closed. Goswin cannot reproduce it.
Since the nis version even in oldstable is 3.17-17 you may want to
remove the code which calls killall, which is only executed if a
version less than 3.9-1 is found, which should not be the case in
these days.
-- 
regards Thomas


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

Bug#694048: systemd: Fetchmail restart failed

[Salvo Tomaselli]

Package: systemd
Version: 44-5
Severity: normal

Dear Maintainer,
Running service fetchmail restart i obtained this in my syslog.

> Nov 23 10:52:37 localhost fetchmail[12963]: Stopping mail retriever agent: 
> fetchmail.
> Nov 23 10:52:37 localhost fetchmail[875]: terminato con segnale 15
> Nov 23 10:52:37 localhost fetchmail[12971]: fetchmail already started; not 
> starting. ... failed!
> Nov 23 10:53:23 localhost fetchmail[13055]: Pidfile not found! Is fetchmail 
> running? ... failed!

This seems to be an heisenbug, and doesn't occur at every restart.

Regards

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

Kernel: Linux 3.6.6a (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  dpkg 1.16.9
ii  initscripts  2.88dsf-34
ii  libacl1  2.2.51-8
ii  libaudit01:1.7.18-1.1
ii  libc62.13-37
ii  libcap2  1:2.22-1.2
ii  libcryptsetup4   2:1.4.3-4
ii  libdbus-1-3  1.6.8-1
ii  libkmod2 9-2
ii  liblzma5 5.1.1alpha+20120614-2
ii  libpam0g 1.1.3-7.1
ii  libselinux1  2.1.9-5
ii  libsystemd-daemon0   44-5
ii  libsystemd-id128-0   44-5
ii  libsystemd-journal0  44-5
ii  libsystemd-login044-5
ii  libudev0 175-7.1
ii  libwrap0 7.6.q-24
ii  udev 175-7.1
ii  util-linux   2.20.1-5.2

Versions of packages systemd recommends:
pn  libpam-systemd  

Versions of packages systemd suggests:
ii  python2.7.3-3
ii  python-cairo  1.8.8-1+b2
ii  python-dbus   1.1.1-1
pn  systemd-gui   

-- 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#693429: Problem solved

[mmc...@tiscali.it]

The problem was in libkmod2 (see http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=689872), but the effect was strange.

There are 
three solution:
1) patch the libkmod2
2) wait for the integration of 
the patch
2) pass the parameter to the command line of grub in the 
debian installer before to start the installation (the libkmod2 in the 
debian installer is not affected)

Please close this bug report.
 

thanks


Invita i tuoi amici e Tiscali ti premia! Il consiglio di un amico vale più di 
uno spot in TV. Per ogni nuovo abbonato 30 € di premio per te e per lui! Un 
amico al mese e parli e navighi sempre gratis: http://freelosophy.tiscali.it/


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

Bug#694049: maxima-share: Do not depend on tex-common

[Elrond]

Package: maxima-share
Version: 5.27.0-3

Hi,

maxima-share currently depends on tex-common.
Basicly, there are no .sty files or alike in it.

There are a few .tex files in it. But they're in maxima's
directories, where the usuel tex-infrastructure wont find
them. So no need to run mktexlsr or whatever.


Cheers

Elrond


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

Bug#639503: gpsprune: please add "nautical mile (nm)" to unit selector

[debian]

tags fixed-upstream
thanks

This has been added in version 14 of GpsPrune, and has been submitted 
for packaging (1 October).  However, the freeze for wheezy is now on so 
the package hasn't been uploaded yet.

If you want to try it out, you can download the jar from the home page.


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

Bug#694050: sbuild: Please add support to sbuild-createchroot to easily create LVM based chroot

[Laurent Bigonville]

Package: sbuild
Version: 0.63.2-1
Severity: wishlist

Hi,

It would be nice if sbuild-createchroot was able to easily create LVM
based chroot.

Create the LV install everything on it and also set the proper options
in the config file.

Cheers

Laurent Bigonville

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

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

Versions of packages sbuild depends on:
ii  adduser 3.113+nmu3
ii  apt-utils   0.9.7.6
ii  libsbuild-perl  0.63.2-1
ii  perl5.14.2-15
ii  perl-modules5.14.2-15

Versions of packages sbuild recommends:
ii  debootstrap  1.0.44
ii  fakeroot 1.18.4-2

Versions of packages sbuild suggests:
pn  deborphan  
ii  wget   1.14-1

-- no debconf information


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

Bug#647433: [l2h] New release of latex2html?

[Robin Fairbairns]

Roland Stigge  wrote:

> > roughly speaking, with abandonware like l2h, we merely go by the
> > licence.  gpl implies (to us) that anyone can hack out a bug and
> > re-release.
> 
> Yes, of course!
> 
> It would be fine if someone steps up and helps Ross (who is still
> responsive and is considering including the "2012" changes into "his"
> lastex2html) to work on this.

yes.  true of an awful lot of abandoned packages, unfortunately.

someone needs a ring to rule them all, to bind them, and to find them
when the lights go out.

> Unfortunately, there was no notice by anyone when and why a release was
> done. Just need to maintain what we accept into Debian for the next few
> years, and trying to prevent a mess caused by random diverging releases
> by different people.

quite.  i used to mirror some web site for l2h, and it was just the same
then, except one assumed that "access to the site" \equiv "has some clue
about what they're doing with l2h".  the announcement situation was
otherwise the same.

maintaining an archive is a case of damned if you do, damned if you
don't.  in that situation, i generally tend not to (after agonising
about it for a while) on the grounds that i don't want to waste any
_more_ time.

sorry you've been inconvenienced.

i hope you understand our situation.

Robin Fairbairns

For the CTAN team


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

Bug#694051: less: leaves alternatives after purge: pager /usr/bin/less

[Andreas Beckmann]

Package: less
Version: 444-4
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 436-1

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8:

http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

The leftover files are actually alternatives that were installed by the
package but have not been properly removed.

While there is ongoing discussion how to remove alternatives correctly
(see http://bugs.debian.org/71621 for details) the following strategy
should work for regular cases:
* 'postinst configure' always installs the alternative
* 'prerm remove' removes the alternative
* 'postrm remove' and 'postrm disappear' remove the alternative
In all other cases a maintainer script is invoked (e.g. upgrade,
deconfigure) the alternatives are not modified to preserve user
configuration.
Removing the alternative in 'prerm remove' avoids having a dangling link
once the actual file gets removed, but 'prerm remove' is not called in
all cases (e.g. unpacked but not configured packages or disappearing
packages) so the postrm must remove the alternative again
(update-alternatives gracefully handles removal of non-existing
alternatives).

Note that the arguments for adding and removing alternatives differ, for
removal it's 'update-alternatives --remove  '.

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

>From the attached log (scroll to the bottom...):

2m12.2s DEBUG: Modified(uid, gid, mode, size, target): 
/etc/alternatives/pager.1.gz (0, 0, l 120777, 29, 
/usr/share/man/man1/more.1.gz) != (0, 0, l 120777, 29, 
/usr/share/man/man1/less.1.gz)
2m12.2s DEBUG: Modified(uid, gid, mode, size, target): /etc/alternatives/pager 
(0, 0, l 120777, 9, /bin/more) != (0, 0, l 120777, 13, /usr/bin/less)
2m12.2s ERROR: FAIL: After purging files have been modified:
  /etc/alternatives/pager -> /bin/more   not owned
  /etc/alternatives/pager.1.gz -> /usr/share/man/man1/more.1.gz  not owned


This problem originates from the package in lenny which used
/usr/bin/less as the pager alternative. In squeeze his was switched to
/bin/less, but no migration path has been added to remove the obsolete
alternative on upgrades.

I would suggest to add 
  update-alternatives --quiet --remove pager /usr/bin/less
to the postinst (after adding the /bin/less alternative). This can be
done unconditionally.
This change needs to get into one stable release.


cheers,

Andreas


less_444-4.log.gz
Description: GNU Zip compressed data

Bug#694052: libphp-magpierss, magpierss: fails to upgrade from 'lenny' - trying to overwrite /usr/share/php/magpierss/scripts/simple_smarty.php

[Andreas Beckmann]

Package: libphp-magpierss,magpierss
Version: 0.72-8+squeeze1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'lenny'.
It installed fine in 'lenny', then the upgrade to 'squeeze' fails
because it tries to overwrite files that are owned by other packages
without declaring a Breaks+Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously deselected package libphp-magpierss.
  Unpacking libphp-magpierss (from 
.../libphp-magpierss_0.72-8+squeeze1_all.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/libphp-magpierss_0.72-8+squeeze1_all.deb (--unpack):
   trying to overwrite '/usr/share/php/magpierss/scripts/simple_smarty.php', 
which is also in package magpierss 0.72-5+lenny1
[...]
  Preparing to replace magpierss 0.72-5+lenny1 (using 
.../magpierss_0.72-8+squeeze1_all.deb) ...
  Unpacking replacement magpierss ...


cheers,

Andreas


magpierss_0.72-8+squeeze1.log.gz
Description: GNU Zip compressed data

Bug#694053: Net-install problem : mirror doesn't support release

[Stéphane Chambrin]

Package: installation-reports

Boot method: ISO mounted on VirtualBox VM
Image version: 
http://napoleon.acc.umu.se/cdimage/wheezy_di_beta4/i386/iso-cd/debian-wheezy-DI-b4-i386-netinst.iso
Date: 2012-11-23 09:00 UTC

Machine: Virtual Box v4.2.4 (host: Asus Laptop N76V)
Processor: 1 CPU PAE/NX (host: i7-3610QM, 2.3GHz)
Memory: 512MiB (host: 8GiB)
Partitions: default installer partition on 10 GB (1 ext4 + 1 swap)Sys.
fich. Type 1K-blocks
Util. Disponible Uti% Monté sur
rootfs rootfs
9848352 42410245107056  46% /
udev   devtmpfs
10240   0  10240   0% /dev
tmpfs  tmpfs
51444 576  50868   2% /run
/dev/disk/by-uuid/51304f99-dd2b-4a4a-a005-8708f519c0c9 ext4
9848352 42410245107056  46% /
tmpfs  tmpfs
5120   0   5120   0% /run/lock
tmpfs  tmpfs
198300 220 198080   1% /run/shm
Résultat de lspci -knn (ou lspci -nn) :00:00.0 Host bridge [0600]:
Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02)
00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA
[Natoma/Triton II] [8086:7000]
00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4
IDE [8086:7111] (rev 01)
Kernel driver in use: ata_piix
00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH
VirtualBox Graphics Adapter [80ee:beef]
00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit
Ethernet Controller [8086:100e] (rev 02)
Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter [8086:001e]
Kernel driver in use: e1000
00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH
VirtualBox Guest Service [80ee:cafe]
00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA
AC'97 Audio Controller [8086:2415] (rev 01)
Subsystem: Intel Corporation Device [8086:]
Kernel driver in use: snd_intel8x0
00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f]
Kernel driver in use: ohci_hcd
00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI
[8086:7113] (rev 08)
00:0b.0 USB controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB2 EHCI Controller [8086:265c]
Kernel driver in use: ehci_hcd
00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM
(ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02)
Kernel driver in use: ahci
Installation du système de base :
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [E]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:
Couldn't find a mirror to install from:

Nov 23 10:09:46 choose-mirror[28544]: DEBUG: command: wget -q
http://ftp.fr.debian.org/debian/dists/wheezy/Release -O - | grep -E
'^(Suite|Codename):'
Nov 23 10:10:04 choose-mirror[28544]: WARNING **: mirror does not
support the specified release (wheezy)
Nov 23 10:10:48 choose-mirror[28548]: DEBUG: command: wget -q
http://debian.proxad.net/debian/dists/wheezy/Release -O - | grep -E
'^(Suite|Codename):'
Nov 23 10:10:51 choose-mirror[28548]: WARNING **: mirror does not
support the specified release (wheezy)

(same with the US debian mirror, I've tried from a first attempt).

Then I continued with minimal install from the cd (without mirror).
After the intial installation, I've been able to setup my sources.list
with the french mirror (ftp.fr.debian.org) and install desktop and ssh
server using tasksel.

I'm using Bridged Networking with a static IP address given by my router's DHCP.

Bug#693937: [Pkg-xfce-devel] Bug#693937: Bug#693937: Bug#693937: Bug#693937: Acknowledgement (thunar: Thunar crashes when mounting USB stick)

[Yves-Alexis Perez]

On ven., 2012-11-23 at 10:35 +0100, Frane Šalković wrote:
> On 11/23/2012 10:14 AM, Yves-Alexis Perez wrote:
> > I just tested on a sid/amd64 box and it works fine here.
> >
> > Currently installed gvfs packages are:
> >
> > gvfs
> > gvfs-backends
> > gvfs-bin
> > gvfs-common
> > gvfs-daemons
> > gvfs-libs
> >
> > Regards,
> Thank you very much! It's solved now! I've installed those packages you
> mentioned, logout and it works fine ;)

Hem, it's not really solved, we still don't know why it segfaults with a
particular set of packages.

-- 
Yves-Alexis


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

Bug#694054: ITP: drumkv1 -- old-school drum-kit sampler

[Alessio Treglia]

Package: wnpp
Severity: wishlist
Owner: Alessio Treglia 

* Package name: drumkv1
  Version : 0.2.0
  Upstream Author : Rui Nuno Capela 
* URL : http://drumkv1.sf.net/
* License : GPL
  Programming Lang: C++
  Description : old-school drum-kit sampler

drumkv1 is an old-school all-digital drum-kit sampler
synthesizer with stereo effects. It is provided in both
forms of a LV2 plugin and a a pure stand-alone JACK
client with JACK-session and both JACK MIDI and ALSA
MIDI input support.


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

Bug#694055: gnome-themes-standard: fails to upgrade from 'sid' - trying to overwrite /usr/share/gnome-background-properties/adwaita.xml

[Andreas Beckmann]

Package: gnome-themes-standard
Version: 3.6.0.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + mutter

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Preparing to replace gnome-themes-standard 3.4.2-2.1 (using 
.../gnome-themes-standard_3.6.0.2-2_amd64.deb) ...
  Unpacking replacement gnome-themes-standard ...
  dpkg: error processing 
/var/cache/apt/archives/gnome-themes-standard_3.6.0.2-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/gnome-background-properties/adwaita.xml', 
which is also in package gnome-themes-standard-data 3.4.2-2.1

cheers,

Andreas


mutter_3.6.1-1.log.gz
Description: GNU Zip compressed data

Bug#694056: Pressing the numlock key makes HDD LED blink shortly

[jaakov jaakov]

Package: gnome
Version: 1:3.4+6
Severity: normal

How to reproduce:

If your Numlock led is lighted:
1. Press the Numlock key.
2. Release the Numlock key, observing that the HDD LED flashes (on and off) 
shortly, for less than 1/3 s.

If your Numlock key is not lighted:
1. Press the Numlock key, observing that the HDD LED flashes (on and off) 
shortly, for less than 1/3 s.
2. Release the Numlock key.

The used computer is Dell Precision M 6700.

I expect that such an innocent action as switching the Numlock state should not 
incur unnecessary disk activity or, even worse, HDD LED blinking without such 
an activity.

Jaakov.

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

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

Versions of packages gnome depends on:
ii  abiword  2.9.2+svn20120603-8
ii  aisleriot1:3.4.1-1
ii  alacarte 3.5.3-1
ii  avahi-daemon 0.6.31-1
ii  cheese   3.4.2-2
ii  cups-pk-helper   0.2.3-2
ii  desktop-base 7.0.3
ii  evolution3.4.4-1
ii  evolution-plugins3.4.4-1
ii  file-roller  3.4.2-1
ii  gedit3.4.2-1
ii  gedit-plugins3.4.0-1
ii  gimp 2.8.2-1
ii  gnome-applets3.4.1-3
ii  gnome-color-manager  3.4.2-1
ii  gnome-core   1:3.4+6
ii  gnome-documents  0.4.2-1
ii  gnome-games  1:3.4.2-3
ii  gnome-media  3.4.0-1
ii  gnome-nettool3.2.0-1
ii  gnome-orca   3.4.2-2
ii  gnome-shell-extensions   3.4.0-2
ii  gnome-tweak-tool 3.4.0.1-2
ii  gnumeric 1.10.17-1.1
ii  gstreamer0.10-ffmpeg 0.10.13-5
ii  gstreamer0.10-plugins-ugly   0.10.19-2+b2
ii  hamster-applet   2.91.3+git20120514.b9fec3e1-1
ii  inkscape 0.48.3.1-1.1
ii  libgtk2-perl 2:1.244-1
ii  libreoffice-calc 1:3.5.4+dfsg-3
ii  libreoffice-gnome1:3.5.4+dfsg-3
ii  libreoffice-impress  1:3.5.4+dfsg-3
ii  libreoffice-writer   1:3.5.4+dfsg-3
ii  nautilus-sendto  3.0.3-2+b1
ii  network-manager-gnome0.9.4.1-2
ii  rhythmbox2.97-2.1
ii  rhythmbox-plugin-cdrecorder  2.97-2.1
ii  rhythmbox-plugins2.97-2.1
ii  rygel-playbin0.14.3-2
ii  rygel-preferences0.14.3-2
ii  rygel-tracker0.14.3-2
ii  seahorse 3.4.1-2
ii  shotwell 0.12.3-2
ii  simple-scan  3.4.2-1
ii  sound-juicer 3.4.0-3
ii  telepathy-gabble 0.16.1-2
ii  telepathy-rakia  0.7.4-1
ii  telepathy-salut  0.8.0-2
ii  tomboy   1.10.0-2
ii  totem3.0.1-8
ii  totem-plugins3.0.1-8
ii  tracker-gui  0.14.1-3
ii  transmission-gtk 2.52-3
ii  vinagre  3.4.2-1
ii  xdg-user-dirs-gtk0.9-1
ii  xul-ext-adblock-plus 2.1-1

Versions of packages gnome recommends:
ii  browser-plugin-gnash 0.8.11~git20120629-1
ii  gdebi0.8.7
ii  gnome-games-extra-data   3.2.0-4
ii  menu-xdg 0.5
ii  nautilus-sendto-empathy  3.4.2.3-1+build1
ii  telepathy-idle   0.1.11-2

Versions of packages gnome suggests:
pn  dia-gnome  
ii  gnome-boxes3.4.3+dfsg-1
pn  gnucash
pn  iceweasel-l10n-all 
ii  libreoffice-evolution  1:3.5.4+dfsg-3
pn  planner
pn  xul-ext-gnome-keyring  

Versions of packages gnome-core depends on:
ii  at-spi2-core2.5.3-2
ii  baobab  3.4.1-1
ii  brasero 3.4.1-4
ii  caribou 0.4.4-1
ii  caribou-antler  0.4.4-1
ii  dconf-gsettings-backend 0.12.1-2
ii  dconf-tools 0.12.1-2
ii  empathy 3.4.2.3-1+build1
ii  eog 3.4.2-1+build1
ii  evince  3.4.0-3
ii  evolution-data-server   3.4.4-1
ii  fonts-cantarell 0.0.9-1
ii  gcalctool   6.4.2.1-2+b1
ii  gconf2  3.2.5-1+build1
ii  gdm33.4.1-4
ii  glib-networking 2.32.3-1
ii  gnome-backgrounds   3.4.2-1
ii  gnome-bluetooth 3.4.2-1
ii  gnome-contacts  3.4.1-1+b1
ii  gnome-control-center1:3.4.2+git20121016.29d7c0-1
ii  gnome-dictionary3.4.0-2
ii  gnome-disk-utility  3.0.2-3
ii  gnome-font-viewer   3.4.0-2
ii  gnome-icon-theme3.4.0-2
ii  gnome-icon-theme-extras

Bug#694057: ed: add a mode to deal with crlf-terminated lines

[Matthew Vernon]

Package: ed
Version: 1.6-2
Severity: wishlist
Tags: upstream

Hi,

ed doesn't deal very nicely with text files generated on inferior
operating systems, e.g. those that have lines that end crlf. The
failure mode is that queries / replacement regexps involving $ don't
do what you want.

It would be nice if ed could have a -crlf mode or similar (or even
arbitrary line-ending mode). Any chance? :)

Thanks,

Matthew

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

Kernel: Linux 3.2.0-3-amd64 (SMP w/8 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 ed depends on:
ii  dpkg  1.16.9
ii  install-info  4.13a.dfsg.1-10
ii  libc6 2.13-35

ed recommends no packages.

ed 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#606148: st: warning when "control" modifier pressed (errkey: 65508)

[Vasudev Kamath]

reassign 606148 stterm
tags 606148 - pending
tags 606148 + wontfix
notfound 606148 39-1
thanks

Jonathan Nieder wrote:

> I don't see any evidence this bug (messages when  key
> pressed) was ever present in the stterm package, so reassigning >back.

st is no longer part of suckless-tools from 39-1 which is uploaded to
experimental additionally 38-2 which was recently uploaded to unstable
with fix to important bug might still have this bug but I think at
this point we can't actually do much as this is not serious bug.

 Besides once wheezy is released I will backport 39-1 which will not
contain st so I'm re-assigning it to stterm if it is not reproducible
please consider closing the bug.

Regards





--

Vasudev Kamath
http://copyninja.info
copyninja@{frndk.de|vasudev.homelinux.net}


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

Bug#694009: qa.debian.org: Please include suite version information in RDF meta data

[Olivier Berger]

Hi.

Arno Töll  writes:


> The RDF pages for a package in the BTS contains lots of

You mean PTS, right ?

> machine-readable information about the package. However, it misses the
> information from the versions column (i.e. the current version of a
> package told apart per suite). It would be super handy to have that
> information encoded in XML as well.

What kind of use case do you have ? I have thought about adding these
kind of meta-data, but haven't yet tackled the problem.

Do you know an existing ontology that could be used to link this version
information to the existing RDF content ?

I'd suggest a Turtle example (see
http://www-public.telecom-sudparis.eu/~berger_o/weblog/2012/08/29/debian-package-tracking-system-now-produces-rdf-description-of-source-packages/
for details on how to generate one using rapper) for the sake of readability.

>
> This should be a fairly simple patch for those of whom the PTS code is not a
> complete mystery (like it is for me). Essentially this would mean, that we'd 
> have
> a (somewhat) easy readable method to retrieve the most current version of a
> package in our suites.

Depending on the use case, you may be interested in the SOAP interface
of the PTS also : see http://packages.qa.debian.org/common/index.html
for pointers.

Best regards,
-- 
Olivier BERGER 
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)


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

Bug#694009: qa.debian.org: Please include suite version information in RDF meta data

[Arno Töll]

On 11/23/2012 12:53 PM, Olivier Berger wrote:
> You mean PTS, right ?

I do, sorry for the confusion :)

>> machine-readable information about the package. However, it misses the
>> information from the versions column (i.e. the current version of a
>> package told apart per suite). It would be super handy to have that
>> information encoded in XML as well.
> 
> What kind of use case do you have ? I have thought about adding these
> kind of meta-data, but haven't yet tackled the problem.

I am trying to implement a sanity check for my dput rewrite (#691624)
which makes sure Debian revision uploads match the orig.tar.gz checksum
of the previous upload. To achieve this, I need the most current version
of a package in a branch and (a) checksum for the orig.tar.gz associated
with it. The latter is already in the RDF.

> Do you know an existing ontology that could be used to link this version
> information to the existing RDF content ?

I'm not sure what exactly you are asking me, but if you ask how to
provide the data in question: Your example data in [1] contains this
information and that would be good enough (altough the associated suite
name, e.g. "stable" would be helpful to know):

# pointer to the release in the different suites :
doap:release , ,
.


> I'd suggest a Turtle example (see
> http://www-public.telecom-sudparis.eu/~berger_o/weblog/2012/08/29/debian-package-tracking-system-now-produces-rdf-description-of-source-packages/
> for details on how to generate one using rapper) for the sake of readability.

Glad you picked my package by the way :>

> Depending on the use case, you may be interested in the SOAP interface
> of the PTS also : see http://packages.qa.debian.org/common/index.html
> for pointers.

Indeed, I didn't know about the SOAP interface. That one seems to
provide the information I need while it does not provide the other
information about file checksums it seems by reading [2].


Moreover, a SOAP interface would be much easier to implement than
parsing XML.


[1] >
http://www-public.telecom-sudparis.eu/~berger_o/weblog/2012/08/29/debian-package-tracking-system-now-produces-rdf-description-of-source-packages/
[2] http://people.debian.org/~zack/pts/soap/

-- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D



signature.asc
Description: OpenPGP digital signature

Bug#694058: TAG:upgrade-intervention -- alarm sound during long upgrade processes

[Peter Davis]

Package: wnpp
Severity: RFP

Sorry if this is the wrong forum or format;  I'm an Ubuntu newbie.  Upgrading 
Ubuntu from one release to the next can take hours, most of which time the 
system just gets on with its work.  Time for a cup of tea, or to get on with a 
bit of Latin translation in another room.  But every now and then, some package 
demands user intervention, sends a request, and just hangs, waiting.  Could you 
ring a bell, or something, to attract user attention, when this happens?  
Otherwise nothing gets done, and the upgrade can take hours longer than it 
need, depending on how often progress is monitored.

Bug#683751: gettext: Please mark gettext M-A: allowed

[Santiago Vila]

On Fri, 23 Nov 2012, Colin Watson wrote:


It also occurred to me that gettext should depend on libasprintf-dev and
libgettextpo-dev, otherwise anything that Build-Depends on gettext
expecting to be able to use one of those libraries will immediately
FTBFS.  Perhaps it will be possible to get rid of this dependency later
after a migration period, as in some ways it's a bit odd for gettext to
suck in development libraries.


I also thought about that, but the names of the new packages have been in
gettext Provides for a long time, which means any package which fails to build
properly because of this split was already buggy in the first place.

Moreover, somebody in this same thread, if I remember will, did a check
and found that there were no packages affected, so my preference would be
to not add those Depends if they are not necessary for our own packages.


I've confirmed that these -dev packages are multiarch-coinstallable,
which is good.  There is one remaining niggle here: while
/usr/share/info/autosprintf.info.gz is currently identical across
architectures, it starts with a line containing "produced by makeinfo
version 4.13".  That means that if gettext ever happens to be built when
texinfo is at different upstream versions on different architectures,
the results will not be multiarch-coinstallable.  I think this is a bit
of a timebomb and we should avoid it.  Perhaps it would make sense to
leave that info documentation in the gettext package, and add a
"Suggests: gettext" in libasprintf-dev?  (We could move it to
gettext-doc instead, but that seems like fairly pointless
deckchair-rearrangement to me.)

I'd like to get this into Ubuntu as soon as possible to replace our
current "Multi-Arch: allowed" hack in sufficient time to undo all the
build-dependencies we've accumulated on "gettext:any".  Do you think it
might be possible to have this patch applied in experimental, or should
we apply it ourselves once we've agreed on package names and contents?


Perhaps we should probably do the split in Debian unstable, as
multiarch is a release goal for wheezy. Are splits already forbidden
in unstable?


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

Bug#694059: libestools2.1-dev: please add Breaks: libestools2.0-dev, libestools1.2-dev

[Andreas Beckmann]

Package: libestools2.1-dev
Version: 1:2.1~release-4
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Control: affects -1 festival-dev

Hi,

during a test with piuparts I noticed your package causes spurious
debsums errors after an upgrade from lenny to squeeze to wheezy.

The libestoolsX.Y-dev packages are not co-installable because they ship
the same files, and therefore utilize a Replaces relation. But without a
corresponding Breaks the replaced package will partially remain
installed but won't be useful for anything - and will be seriously
broken after libestools2.1-dev is removed.
Since libestools2.0-dev and libestools1.2-dev no longer exist in wheezy
the Breaks can be unversioned. Breaking libestools1.2-dev which existed
in lenny is still neccessary since this package may still be installed
on a system that migrated from lenny to squeeze to wheezy.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

debsums reports errors because there are several different md5sums
recorded for the same file in /var/lib/dpkg/info (but the files got
moved around from 1.2 to 2.0 to 2.1 and were changed at the same time).


Andreas


festival-dev_1:2.1~release-5+b1.log.gz
Description: GNU Zip compressed data

Bug#694060: Pressing the numlock key makes HDD LED blink shortly

[jaakov jaakov]

Package: gnome
Version: 1:3.4+6
Severity: normal

How to reproduce:

If your Numlock LED is lighted:
1. Press the Numlock key.
2. Release the Numlock key, observing that the HDD LED flashes. The flash time 
does not exceed 1/3 s.

If your Numlock LED is not lighted:
1. Press the Numlock key, observing that the HDD LED flashes. The flash time 
does not exceed 1/3 s.
2. Release the Numlock key.

The used computer is Dell Precision M 6700.

I expect that such an innocent action as switching the Numlock state should not 
incur unnecessary disk activity or, even worse, HDD LED blinking without such 
an activity.

Jaakov.

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

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

Versions of packages gnome depends on:
ii   abiword 2.9.2+svn20120603-8
ii   aisleriot   1:3.4.1-1
ii   alacarte3.5.3-1
ii   avahi-daemon   0.6.31-1
ii   cheese  3.4.2-2
ii   cups-pk-helper 0.2.3-2
ii   desktop-base   7.0.3
ii   evolution   3.4.4-1
ii   evolution-plugins  3.4.4-1
ii   file-roller3.4.2-1
ii   gedit   3.4.2-1
ii   gedit-plugins  3.4.0-1
ii   gimp2.8.2-1
ii   gnome-applets  3.4.1-3
ii   gnome-color-manager3.4.2-1
ii   gnome-core 1:3.4+6
ii   gnome-documents0.4.2-1
ii   gnome-games1:3.4.2-3
ii   gnome-media3.4.0-1
ii   gnome-nettool  3.2.0-1
ii   gnome-orca 3.4.2-2
ii   gnome-shell-extensions3.4.0-2
ii   gnome-tweak-tool   3.4.0.1-2
ii   gnumeric1.10.17-1.1
ii   gstreamer0.10-ffmpeg  0.10.13-5
ii   gstreamer0.10-plugins-ugly0.10.19-2+b2
ii   hamster-applet 2.91.3+git20120514.b9fec3e1-1
ii   inkscape0.48.3.1-1.1
ii   libgtk2-perl   2:1.244-1
ii   libreoffice-calc   1:3.5.4+dfsg-3
ii   libreoffice-gnome  1:3.5.4+dfsg-3
ii   libreoffice-impress1:3.5.4+dfsg-3
ii   libreoffice-writer 1:3.5.4+dfsg-3
ii   nautilus-sendto3.0.3-2+b1
ii   network-manager-gnome 0.9.4.1-2
ii   rhythmbox   2.97-2.1
ii   rhythmbox-plugin-cdrecorder   2.97-2.1
ii   rhythmbox-plugins  2.97-2.1
ii   rygel-playbin  0.14.3-2
ii   rygel-preferences  0.14.3-2
ii   rygel-tracker  0.14.3-2
ii   seahorse3.4.1-2
ii   shotwell0.12.3-2
ii   simple-scan3.4.2-1
ii   sound-juicer   3.4.0-3
ii   telepathy-gabble   0.16.1-2
ii   telepathy-rakia0.7.4-1
ii   telepathy-salut0.8.0-2
ii   tomboy  1.10.0-2
ii   totem   3.0.1-8
ii   totem-plugins  3.0.1-8
ii   tracker-gui0.14.1-3
ii   transmission-gtk   2.52-3
ii   vinagre 3.4.2-1
ii   xdg-user-dirs-gtk  0.9-1
ii   xul-ext-adblock-plus  2.1-1

Versions of packages gnome recommends:
ii   browser-plugin-gnash  0.8.11~git20120629-1
ii   gdebi   0.8.7
ii   gnome-games-extra-data3.2.0-4
ii   menu-xdg   0.5
ii   nautilus-sendto-empathy   3.4.2.3-1+build1
ii   telepathy-idle 0.1.11-2

Versions of packages gnome suggests:
pn   dia-gnome
ii   gnome-boxes  3.4.3+dfsg-1
pn   gnucash  
pn   iceweasel-l10n-all  
ii   libreoffice-evolution   1:3.5.4+dfsg-3
pn   planner  
pn   xul-ext-gnome-keyring   

Versions of packages gnome-core depends on:
ii   at-spi2-core  2.5.3-2
ii   baobab 3.4.1-1
ii   brasero3.4.1-4
ii   caribou0.4.4-1
ii   caribou-antler0.4.4-1
ii   dconf-gsettings-backend  0.12.1-2
ii   dconf-tools   0.12.1-2
ii   empathy3.4.2.3-1+build1
ii   eog3.4.2-1+build1
ii   evince 3.4.0-3
ii   evolution-data-server3.4.4-1
ii   fonts-cantarell   0.0.9-1
ii   gcalctool 6.4.2.1-2+b1
ii   gconf2 3.2.5-1+build1
ii   gdm3   3.4.1-4
ii   glib-networking   2.32.3-1
ii   gnome-backgrounds 3.4.2-1
ii   gnome-bluetooth   3.4.2-1
ii   gnome-contacts 

Bug#693937: [Pkg-xfce-devel] Bug#693937: Bug#693937: Bug#693937: Bug#693937: Acknowledgement (thunar: Thunar crashes when mounting USB stick)

[Frane Šalković]

On 11/23/2012 12:29 PM, Yves-Alexis Perez wrote:
> On ven., 2012-11-23 at 10:35 +0100, Frane Šalković wrote:
>> On 11/23/2012 10:14 AM, Yves-Alexis Perez wrote:
>>> I just tested on a sid/amd64 box and it works fine here.
>>>
>>> Currently installed gvfs packages are:
>>>
>>> gvfs
>>> gvfs-backends
>>> gvfs-bin
>>> gvfs-common
>>> gvfs-daemons
>>> gvfs-libs
>>>
>>> Regards,
>> Thank you very much! It's solved now! I've installed those packages you
>> mentioned, logout and it works fine ;)
> Hem, it's not really solved, we still don't know why it segfaults with a
> particular set of packages.
>
How we could determine that?


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

Bug#694062: debian Wheezy installer

[Adriano Trentini]

Package: installation-reports

Boot method: netinstall
package: debian-testing-amd64-netinst.iso (
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/)
Date: today failled
Machine: ICP desktop
Processor: intell atom 2
Memory: 2 GB RAM, 500gb rom
Partitions:

Output of lspci -knn (or lspci -nn):

Base System Installation Checklist:
[O] = OK, [E] = Error (it loads the first screen, then type point when I
enyer install), [ ] = didn't try it

Initial boot:   [yes]
Detect network card:[no]
Configure network:  [ no]
Detect CD:  [ yes]
Load installer modules: [no]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:
I have purchased a new computer, with Atom 2, 2Gb RAM,500 GB ROM, an ICP
desktop.
I was unabel to run the Wheezy installer, even as the Ubuntu and the
mini.iso of Ubuntu, yet the Debian 6.0 installer (my old disk) works fine,
even as an old Windows XP installer.
I would like to try the former version of the wheezy installer,if it would
perhaps be more stable then the later.
It goes until the first screen and writtes many points when I type enter to
install.
Em 23/11/2012 11:03, "Adriano Trentini" 
escreveu:

Bug#693998: ITP: linux-minidisc -- Free software for accessing NetMD and HiMD MiniDisc devices

[John Paul Adrian Glaubitz]

On Fri, Nov 23, 2012 at 09:02:18AM +0800, Paul Wise wrote:
> On Fri, Nov 23, 2012 at 3:16 AM, John Paul Adrian Glaubitz wrote:
> 
> > * Package name: linux-minidisc
> 
> Thats a strange name considering it builds and runs on MacOS, Windows,
> Linux, FreeBSD and Haiku.

Yes, the name is indeed somewhat confusing in that regard. But when we
first came up with the project, we were initially only concerned about
Linux, so the name was obvious. Finding a good name for such a project
is complicated because of possible trademark violations.

If you have a better idea, I'd be happy to hear it ;).

Cheers,

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


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

Bug#694063: openafs-fileserver: directory vs. symlink messup after lenny -> squeeze -> wheezy upgrade

[Andreas Beckmann]

Package: openafs-fileserver
Version: 1.6.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + openafs-dbg

Hi,

during a test with piuparts I noticed your package produces some
debsums errors after a lenny->squeeze->wheezy upgrade:

1m14.8s INFO: dirname part contains a symlink:
  /usr/share/doc/openafs-fileserver/NEWS.Debian.gz != 
/usr/share/doc/openafs-client/NEWS.Debian.gz (openafs-fileserver)
  /usr/share/doc/openafs-fileserver/changelog.Debian.gz != 
/usr/share/doc/openafs-client/changelog.Debian.gz (openafs-fileserver)
  /usr/share/doc/openafs-fileserver/changelog.gz != 
/usr/share/doc/openafs-client/changelog.gz (openafs-fileserver)
  /usr/share/doc/openafs-fileserver/copyright != 
/usr/share/doc/openafs-client/copyright (openafs-fileserver)

1m16.3s ERROR: FAIL: debsums reports modifications inside the chroot:
  /usr/share/doc/openafs-client/NEWS.Debian.gz

This looks like in lenny, there was a symlink
  /usr/share/doc/openafs-fileserver -> openafs-client
but in squeeze /usr/share/doc/openafs-fileserver was changed to be a
directory, but without doing a proper migration (dpkg intentionally does
not replace directories with symlinks and vice versa). So the ancient
link is still there and now different packages are overwriting each other
without dpkg having a chance to notice this.

There may be more binary packages built from src:openafs affected by
similar problems (but not tested by piuparts due to failing
dependencies).

Usually a preinst check like

   test ! -L /usr/share/doc/openafs-fileserver || rm 
/usr/share/doc/openafs-fileserver

should solve this.


cheers,

Andreas


openafs-fileserver_1.6.1-2.log.gz
Description: GNU Zip compressed data

Bug#683751: gettext: Please mark gettext M-A: allowed

[Colin Watson]

On Fri, Nov 23, 2012 at 01:31:45PM +0100, Santiago Vila wrote:
> On Fri, 23 Nov 2012, Colin Watson wrote:
> >It also occurred to me that gettext should depend on libasprintf-dev and
> >libgettextpo-dev, otherwise anything that Build-Depends on gettext
> >expecting to be able to use one of those libraries will immediately
> >FTBFS.  Perhaps it will be possible to get rid of this dependency later
> >after a migration period, as in some ways it's a bit odd for gettext to
> >suck in development libraries.
> 
> I also thought about that, but the names of the new packages have been in
> gettext Provides for a long time, which means any package which fails to build
> properly because of this split was already buggy in the first place.
> 
> Moreover, somebody in this same thread, if I remember will, did a check
> and found that there were no packages affected, so my preference would be
> to not add those Depends if they are not necessary for our own packages.

OK, makes sense.

Looking back through the thread: do you still want to remove
libgettextlib.so and libgettextsrc.so?  The most recent version of
Wookey's patch removed those; I restored them in my revision, thinking
that a mistake, but I just noticed discussion earlier in this bug to the
effect that those symlinks should be removed since the libraries are
only for internal use by gettext, so I may have been wrong to restore
these symlinks.

> >I've confirmed that these -dev packages are multiarch-coinstallable,
> >which is good.  There is one remaining niggle here: while
> >/usr/share/info/autosprintf.info.gz is currently identical across
> >architectures, it starts with a line containing "produced by makeinfo
> >version 4.13".  That means that if gettext ever happens to be built when
> >texinfo is at different upstream versions on different architectures,
> >the results will not be multiarch-coinstallable.  I think this is a bit
> >of a timebomb and we should avoid it.  Perhaps it would make sense to
> >leave that info documentation in the gettext package, and add a
> >"Suggests: gettext" in libasprintf-dev?  (We could move it to
> >gettext-doc instead, but that seems like fairly pointless
> >deckchair-rearrangement to me.)

Do you have an opinion on this part?  If not, I think my default would
be for the next version of this patch to move autosprintf.info.gz back
to gettext, for safety.

> >I'd like to get this into Ubuntu as soon as possible to replace our
> >current "Multi-Arch: allowed" hack in sufficient time to undo all the
> >build-dependencies we've accumulated on "gettext:any".  Do you think it
> >might be possible to have this patch applied in experimental, or should
> >we apply it ourselves once we've agreed on package names and contents?
> 
> Perhaps we should probably do the split in Debian unstable, as
> multiarch is a release goal for wheezy. Are splits already forbidden
> in unstable?

Well, on the one hand, multiarch is a release goal, but it can't
realistically be an open-ended one - we have to stop somewhere.  It's
not as if there aren't plenty of other cross-building issues.  On the
other hand, it's true that this particular piece of it is more important
than your average multiarch fix since it blocks cross-building of many
other packages, and I don't actually think it's all that invasive.

http://release.debian.org/wheezy/freeze_policy.html allows "changes for
release goals, if they are not invasive".  I think we would need to ask
the release team for their opinion here; CCing debian-release.

(Background for those not following this long bug: we would like to
split libasprintf-dev and libgettextpo-dev out of gettext, in order to
permit marking gettext as Multi-Arch: foreign, the lack of which blocks
500-odd potentially cross-buildable packages and considerably obscures
our view of how much of even the core of Debian is cross-buildable.  The
earlier proposal reflected in the bug title was to leave these in the
one package and use "Multi-Arch: allowed", but that involves changing
lots of build-dependencies to "gettext:any" and I think everyone
involved is now agreed that this is a less desirable option.)

Thanks,

-- 
Colin Watson   [cjwat...@ubuntu.com]


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

Bug#693937: [Pkg-xfce-devel] Bug#693937: Bug#693937: Bug#693937: Bug#693937: Acknowledgement (thunar: Thunar crashes when mounting USB stick)

[Yves-Alexis Perez]

On ven., 2012-11-23 at 14:01 +0100, Frane Šalković wrote:
> On 11/23/2012 12:29 PM, Yves-Alexis Perez wrote:
> > On ven., 2012-11-23 at 10:35 +0100, Frane Šalković wrote:
> >> On 11/23/2012 10:14 AM, Yves-Alexis Perez wrote:
> >>> I just tested on a sid/amd64 box and it works fine here.
> >>>
> >>> Currently installed gvfs packages are:
> >>>
> >>> gvfs
> >>> gvfs-backends
> >>> gvfs-bin
> >>> gvfs-common
> >>> gvfs-daemons
> >>> gvfs-libs
> >>>
> >>> Regards,
> >> Thank you very much! It's solved now! I've installed those packages you
> >> mentioned, logout and it works fine ;)
> > Hem, it's not really solved, we still don't know why it segfaults with a
> > particular set of packages.
> >
> How we could determine that?

As I already asked, please get a backtrace.
-- 
Yves-Alexis


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

Bug#694064: ITP: openlase -- Laser show software for soundcard operation. Can open, manipulate and save DXF, ILDA and WAVE.

[Richard Ulrich]

Package: wnpp
Owner: Richard Ulrich 
Severity: wishlist

* Package name: openlase
  Version : 2012.06.08
  Upstream Author : Héctor Martín Cantero 
* URL : http://marcansoft.com/
* License : GPL-3+
  Programming Lang: C++
  Description : Open realtime laser show graphics toolkit.

OpenLase is an open realtime laser show graphics toolkit.
It pipes realtime laser show data through jack to the soundcard.



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

Bug#694065: installation-reports

[Dr. Johannes-Heinrich Vogeler]

Package: installation-reports

Boot method: CD
Image version: Debian Wheezy Beta3 Installer
Date: 2012-11-04

Machine: ASUS M5A88-V EVO
Processor: AMD Athlon IIx4 (640)
Memory: 16 GB
 

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems: While Squeeze was booting only after some failed tries 
Wheezy (testing) boots regular (up to now 2 freezes from grub "Loading, please 
wait". Wheezy runs without serious problems. The only problem is that HDD are 
running as IDE drives inspite of configuring AHCI in the BIOS main menu. This 
ist due to an issue of the M5A88-V EVO Bios (in the main menu AHCI is 
configured while the boot menu displays IDE hardisks); the ASUS support 
Germany is unwilling to fix this. I shall try to circumvent this problem by 
creating an apprpriate initrd. 

 
 

Bug#694066: gnome-contacts needs a rebuild to update its libcheese-gtk dependency

[Alessio Gaeta]

Package: gnome-contacts
Version: 3.6.1-1
Severity: important

Dear Maintainer,
I'm currently unable to upgrade cheese to 3.6.1 from experimental without
breaking gnome-contacts, which depends from libcheese-gtk21 while cheese 3.6.1
ships libcheese-gtk23.
This in turn renders impossible to upgrade empathy to 3.6.2 because of its
dependency  from libcheese-gtk23.

I guess a rebuild against new libcheese-dev is needed.

Thanks for your work. Best regards
--
Alessio Gaeta



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

Kernel: Linux 3.6.0-7.dmz.1-liquorix-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-contacts depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-2
ii  libc62.13-37
ii  libcairo21.12.2-2
ii  libcheese-gtk21  3.4.2-2
ii  libcheese3   3.4.2-2
ii  libedataserver-1.2-173.6.1-1
ii  libfolks-eds25   0.8.0-2
ii  libfolks-telepathy25 0.8.0-2
ii  libfolks25   0.8.0-2
ii  libgdk-pixbuf2.0-0   2.26.4-2
ii  libgee2  0.6.4-2
ii  libglib2.0-0 2.34.2-1
ii  libgnome-desktop-3-4 3.6.1-1
ii  libgtk-3-0   3.6.1-1
ii  libnotify4   0.7.5-1
ii  libpango1.0-01.30.0-1
ii  libtelepathy-glib0   0.20.1-1

gnome-contacts recommends no packages.

gnome-contacts 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#694012: [Pkg-xen-devel] Bug#694012: xen-hypervisor-4.1-amd64: powernow-k8: transition frequency failed [filling the syslog]

[Axel Beckert]

Hi Waldi,

Bastian Blank wrote:
> Control: reassign -1 src:linux 3.2.32-1
> Control: severity -1 important
> 
> On Fri, Nov 23, 2012 at 12:28:08AM +0100, Axel Beckert wrote:
> > after an upgrade from Squeeze to Wheezy I see about ten of these per
> > second filling my system log (about 8 MB/h):
> > Nov 23 00:15:37 acromantula kernel: [  462.544193] powernow-k8: fid trans 
> > failed, fid 0x2, curr 0x0
> > Nov 23 00:15:37 acromantula kernel: [  462.546919] powernow-k8: transition 
> > frequency failed
> > This seems to be a known upstream issue, see
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1789
> 
> This is a bug in the kernel. The hypervisor correctly denies access to
> the hardware.

Ah, thanks for the summary.

Workaround for me to stop log file filling: "rmmod powernow_k8"

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


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

Bug#683744: Acknowledgement (gnome-terminal: startup broken - the terminal is not usable afterwards (in awesome))

[Toni Mueller]

Hi,

just to add another data point: Konsole works just fine.


Kind regards,
--Toni++


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

Bug#694067: lilypond: Umlauts incorrectly exported to PDF meta data

[Paul Menzel]

Package: lilypond
Version: 2.14.2-3
Severity: normal
Tags: upstream

Dear Debian folks,


with the following minimal example

$ more umlaut.ly
\version "2.14.2"
\header {
  title = "ß"
  composer = "ä ö"
}

{ a4 }

produces a PDF file causing Evince (based on Poppler) to print the
following warnings.

$ lilypond umlaut.ly
$ evince umlaut.pdf
Entity: line 10: parser error : Input is not proper UTF-8, indicate 
encoding !
Bytes: 0xDF 0x3C 0x2F 0x72
1/' dc:format='application/pdf'>

As the warning notes the encoding has to be specified. Or please use
UTF-8 by default. (Evince seems to deal fine with the file though and
the characters are correctly displayed.)

Unfortunately I am not able to test if this is fixed in newer versions,
as LilyPond version 2.16.x in experimental is only available for amd64.


Thanks,

Paul

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

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

Versions of packages lilypond depends on:
ii  ghostscript 9.05~dfsg-6.2
ii  guile-1.8   1.8.8+1-8
ii  guile-1.8-libs  1.8.8+1-8
ii  libc6   2.13-37
ii  libfontconfig1  2.9.0-7
ii  libfreetype62.4.9-1
ii  libgcc1 1:4.7.2-4
ii  libglib2.0-02.33.12+really2.32.4-3
ii  libgmp102:5.0.5+dfsg-2
ii  libltdl72.4.2-1.1
ii  libpango1.0-0   1.30.0-1
ii  libstdc++6  4.7.2-4
ii  lilypond-data   2.14.2-3
ii  python  2.7.3-3

Versions of packages lilypond recommends:
ii  lilypond-doc2.14.2-3
ii  texlive-latex-base  2012.20120611-5

lilypond suggests no packages.

-- no debconf information


umlaut.pdf
Description: Adobe PDF document
\version "2.14.2"
\header {
  title = "ß"
  composer = "ä ö"
}

{ a4 }


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

Bug#683751: gettext: Please mark gettext M-A: allowed

[Wookey]

+++ Colin Watson [2012-11-23 13:31 +]:
> On Fri, Nov 23, 2012 at 01:31:45PM +0100, Santiago Vila wrote:
> > On Fri, 23 Nov 2012, Colin Watson wrote:

> > >I've confirmed that these -dev packages are multiarch-coinstallable,
> > >which is good.  There is one remaining niggle here: while
> > >/usr/share/info/autosprintf.info.gz is currently identical across
> > >architectures, it starts with a line containing "produced by makeinfo
> > >version 4.13".  That means that if gettext ever happens to be built when
> > >texinfo is at different upstream versions on different architectures,
> > >the results will not be multiarch-coinstallable.  I think this is a bit
> > >of a timebomb and we should avoid it.  Perhaps it would make sense to
> > >leave that info documentation in the gettext package, and add a
> > >"Suggests: gettext" in libasprintf-dev?  (We could move it to
> > >gettext-doc instead, but that seems like fairly pointless
> > >deckchair-rearrangement to me.)
> 
> Do you have an opinion on this part?  If not, I think my default would
> be for the next version of this patch to move autosprintf.info.gz back
> to gettext, for safety.

Doesn't this problem of potentially-rebuilt text/doc/info files exist
all over the place? I've come across it in perl docs which embed the
build date, not the doc-creation date, for example. Essentially any
doc in an M-A same package has the issue of rebuilds potentially
changing the text.  i.e. there is nothing special about gettext here.
Is texinfo version skew likely enough to break things that we should
worry.

One way of dealing with this is moving all docs out of M-A: same
packages, and docs are arch-independent stuff so it makes some sense.
But it's also good to keep docs in their most relevant place. I don't
know which package is really 'most relevant' here.

What we really want is QA checks on MA co-installability and
corresponding rebuilds/fixes where it's gone wrong. I'm happy to rely
on that happening in due course, if it would be better the leave the
docs in the -dev package. 

Wookey
-- 
Principal hats:  Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/


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

Bug#694068: netcfg: Wireless connectivity present during an install but absent afterwards

[Brian Potkin]

Package: netcfg
Version: 1.102
Severity: important
Tags: d-i



I installed in expert mode over a wireless link from

Debian GNU/Linux testing "Wheezy" - Official Snapshot i386 NETINST Binary-1 
20121122-21:21

This ISO has netcfg_1.102. Only "Standard system utilities" was selected
as a task. Re-booted as instructed. No network! Checked the contents of
/etc/network/interfaces. The only interface available is lo. I'm still
in a state of shock. :)

>From the netcfg changelog:

* On Linux: Write a network-manager configuration file in perference
  to ifupdown if network-manager is found in the installed system.
  Configure wired networking with ifupdown if not. Do not configure
  wireless networking through ifupdown.

and

 * Reword target_network_config template; do not ask the question.

Not only am I deprived of network connectivity because I did not install
network-manager or use a network cable, but this is done silently.

The machine that Debian was put on is a desktop model and isn't going
anywhere. Now I have try to recollect what to put in /e/n/i to restore
the network connection. Also, the WPA passphrase is a machine generated
63 random characters. With gpm it's a snap to copy and paste. Except

If I'd installed to a laptop I might have wanted wpagui to deal with any
roaming. Or network-manager for that matter. Having to start from
scratch is tiresome.

Anyone who used a network during an install would, in my opinion, most
likely want it available afterwards. Please consider leaving it set up
as configured by ifupdown when the install takes place as described
above.

Some discussion of the issue is in the thread starting at

   http://lists.debian.org/debian-boot/2012/09/msg00252.html


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

Bug#691719: sphinx: Please cherry-pick changeset b7b808e46851 that fixes issues with localized projects

[Dmitry Shachnev]

Control: retitle -1 Cannot build text with footnotes when using l10

Attached updated patch that is based on first one and
http://dev.sphinx-doc.org/sphinx/pull-request/86/fixed-955-footnote-i18n-translation-cause/commits
 .

Does it look better?

--
Dmitry Shachnev
=== modified file 'sphinx/environment.py'
--- sphinx/environment.py	2012-03-12 12:18:37 +
+++ sphinx/environment.py	2012-11-23 14:18:39 +
@@ -213,16 +213,30 @@
 parser = RSTParser()
 
 for node, msg in extract_messages(self.document):
-patch = new_document(source, settings)
 msgstr = catalog.gettext(msg)
 # XXX add marker to untranslated parts
 if not msgstr or msgstr == msg: # as-of-yet untranslated
 continue
+
+patch = new_document(source, settings)
 parser.parse(msgstr, patch)
 patch = patch[0]
 # XXX doctest and other block markup
 if not isinstance(patch, nodes.paragraph):
 continue # skip for now
+
+footnote_refs = [r for r in node.children
+ if isinstance(r, nodes.footnote_reference)
+ and r.get('auto') == 1]
+for i, child in enumerate(patch.children): # update leaves
+if isinstance(child, nodes.footnote_reference) \
+   and child.get('auto') == 1:
+# use original 'footnote_reference' object.
+# this object already registered in self.document.autofootnote_refs
+patch.children[i] = footnote_refs.pop(0)
+# Some duplicated footnote_reference in msgstr causes
+# IndexError by .pop(0). That is invalid msgstr.
+
 for child in patch.children: # update leaves
 child.parent = node
 node.children = patch.children

Bug#682846: gtg: Subtasks are regularly lost and becoming simple tasks

[Sébastien Kalt]

Hi,

2012/11/11 Luca Falavigna 

> I uploaded a new upstream release (0.3-1) to experimental, would you mind
> testing it to see whether this problem has been solved?
>
After one week using this new version, I don't have this problem anymore.

As far as I can tell, this bug is solved, thank you.

Regards,

Sebastien KALT

Bug#694069: gcj-4.7: FTBFS on powerpcspe (powerpc specific asm)

[Roland Stigge]

Package: gcj-4.7
Version: 4.7.2-2
Severity: wishlist
Tags: patch sid
User: debian-powerpc...@breakpoint.cc
Usertags: powerpcspe

Hi,

gcj-4.7 currently FTBFS on powerpcspe[1] like this:

/PKGBUILDDIR/build/./gcc/xgcc -B/PKGBUILDDIR/build/./gcc/ 
-B/usr/powerpc-linux-gnuspe/bin/ -B/usr/powerpc-linux-gnuspe/lib/ -isystem 
/usr/powerpc-linux-gnuspe/include -isystem 
/usr/powerpc-linux-gnuspe/sys-include-g -O2 -O2  -g -O2 -DIN_GCC   -W -Wall 
-Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes 
-Wold-style-definition  -isystem ./include   -fPIC -mlong-double-128 
-mno-minimal-toc -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector   -fPIC 
-mlong-double-128 -mno-minimal-toc -I. -I. -I../.././gcc -I../../../src/libgcc 
-I../../../src/libgcc/. -I../../../src/libgcc/../gcc 
-I../../../src/libgcc/../include -I../../../src/libgcc/../libdecnumber/dpd 
-I../../../src/libgcc/../libdecnumber -DHAVE_CC_TLS  -o crtresfpr_s.o -MT 
crtresfpr_s.o -MD -MP -MF crtresfpr_s.dep -DSHARED -c -xassembler-with-cpp 
../../../src/libgcc/config/rs6000/crtresfpr.S
../../../src/libgcc/config/rs6000/crtresfpr.S: Assembler messages:
../../../src/libgcc/config/rs6000/crtresfpr.S:42: Error: Unrecognized opcode: 
`lfd'
[...]

Seems that some asm instructions for powerpc don't apply to powerpcspe.

Turns out that the same patch that fixed a similar issue for gcc-4.7 also
applies here. Re-attaching.

Thanks,

Roland


[1] http://wiki.debian.org/PowerPCSPEPort


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

Kernel: Linux 3.2.0-4-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/bash
diff -ruN gcc-4.7-4.7.2.backup/debian/patches/powerpc_nofprs.diff gcc-4.7-4.7.2/debian/patches/powerpc_nofprs.diff
--- gcc-4.7-4.7.2.backup/debian/patches/powerpc_nofprs.diff	1970-01-01 01:00:00.0 +0100
+++ gcc-4.7-4.7.2/debian/patches/powerpc_nofprs.diff	2012-11-10 07:53:10.724792401 +0100
@@ -0,0 +1,45 @@
+--- gcc-4.7-4.7.2/src/libgcc/config/rs6000/crtsavfpr.S.orig	2012-11-09 21:11:13.923320372 +0100
 gcc-4.7-4.7.2/src/libgcc/config/rs6000/crtsavfpr.S	2012-11-09 21:12:06.08334 +0100
+@@ -33,6 +33,7 @@
+ 
+ /* On PowerPC64 Linux, these functions are provided by the linker.  */
+ #ifndef __powerpc64__
++#ifndef __NO_FPRS__
+ 
+ /* Routines for saving floating point registers, called by the compiler.  */
+ /* Called with r11 pointing to the stack header word of the caller of the */
+@@ -79,3 +80,4 @@
+ CFI_ENDPROC
+ 
+ #endif
++#endif
+--- gcc-4.7-4.7.2/src/libgcc/config/rs6000/crtresfpr.S.orig	2012-11-10 00:18:44.590113135 +0100
 gcc-4.7-4.7.2/src/libgcc/config/rs6000/crtresfpr.S	2012-11-10 00:19:15.414120795 +0100
+@@ -33,6 +33,7 @@
+ 
+ /* On PowerPC64 Linux, these functions are provided by the linker.  */
+ #ifndef __powerpc64__
++#ifndef __NO_FPRS__
+ 
+ /* Routines for restoring floating point registers, called by the compiler.  */
+ /* Called with r11 pointing to the stack header word of the caller of the */
+@@ -79,3 +80,4 @@
+ CFI_ENDPROC
+ 
+ #endif
++#endif
+--- gcc-4.7-4.7.2/src/libgcc/config/rs6000/crtresxfpr.S.orig	2012-11-10 07:48:47.768732506 +0100
 gcc-4.7-4.7.2/src/libgcc/config/rs6000/crtresxfpr.S	2012-11-10 07:51:31.584768060 +0100
+@@ -33,6 +33,7 @@
+ 
+ /* On PowerPC64 Linux, these functions are provided by the linker.  */
+ #ifndef __powerpc64__
++#ifndef __NO_FPRS__
+ 
+ /* Routines for restoring floating point registers, called by the compiler.  */
+ /* Called with r11 pointing to the stack header word of the caller of the */
+@@ -124,3 +125,4 @@
+ CFI_ENDPROC
+ 
+ #endif
++#endif
diff -ruN gcc-4.7-4.7.2.backup/debian/rules.patch gcc-4.7-4.7.2/debian/rules.patch
--- gcc-4.7-4.7.2.backup/debian/rules.patch	2012-11-11 12:13:52.0 +0100
+++ gcc-4.7-4.7.2/debian/rules.patch	2012-11-09 21:15:28.415383574 +0100
@@ -200,6 +200,7 @@
 
 ifeq ($(DEB_TARGET_ARCH),powerpcspe)
   debian_patches += powerpc_remove_many
+  debian_patches += powerpc_nofprs
 endif
 
 ifeq ($(DEB_TARGET_ARCH),ppc64)

Bug#660862: initscripts: symlink /etc/nologin points to non existent file:

[Carlos Alberto Lopez Perez]

reassign 660862 initscripts
retitle 660862 initscripts: symlink /etc/nologin points to non existent file:
thanks


Same here. 

Such symlink was created by an upgrade of the package initscripts on a system 
running Debian/Squeeze.


Here is the relevant part:


$ grep -C3 /etc/nologin sysvinit-2.88dsf/debian/initscripts.postinst
# Set up nologin symlink so that dynamic-login-disabling will work
# (when DELAYLOGIN is set to "yes")
#
if [ ! -L /etc/nologin ] && [ ! -e /etc/nologin ]
then
rm -f /var/lib/initscripts/nologin
ln -s /var/lib/initscripts/nologin /etc/nologin
fi




I don't know why the postinst script does that.  Can somebody explain?


Thanks!



signature.asc
Description: OpenPGP digital signature

Bug#691148: [Pkg-virtualbox-devel] Bug#691148: Bug#691148: Bug#691148: Please package virtualbox 4.2.2

[Felix Geyer]

On 18.11.2012 18:55, Michael Meskes wrote:
> On Fri, Nov 16, 2012 at 04:28:01PM +0100, Felix Geyer wrote:
>> Removing the Open Watcom source files would be a GPL violation unless 
>> upstream
>> explicitly adds a license to the generated assembler files.
>
> IANAL but wouldn't the general license from the package kick in if there is no
> license mentioned in a source file?

The assembler file explicitly says that it's build from GPL code so the GPL 
rules
for distributing object code applies here. That means you need keep the source
code in the tarball.

>> It's pretty hard to believe that someone could write and maintain 15,000 
>> lines
>> of assembler code without a single comment.
>
> But that's not the point. It's not about whether or not you believe them, it's
> about what the license dictates.

It's not really about licenses. I don't doubt that the VirtualBox BIOS is 
perfectly
fine GPLv2 code.
However the Debian Policy enforces additional restrictions such as everything
in main needs to be buildable from source with software from main.
I think it's a reason to not include software in Debian if we have strong 
doubts whether
upstream ships the real source code and that restricts how we can make 
modifications
to the software.

>> Sure, you can modify those assembler files but they are just a post-processed
>> compiler output. That means in practice you can't modify it in a meaningful
>> way.
>> In fact the files say "Auto Generated source file. Do not edit." ;-)
>
> Ok, for the sake of my argument let's assumed that line was removed. :)
>
>> For example we would be unable to cherry-pick a BIOS fix from trunk.
>
> Good point.
>
>> With the same argument you could declare every disassembled binary that is 
>> built
>> from high level language code as source code.
>
> True. I'm not saying it is, I just wonder whether our restriction makes sense.

The restriction makes sense because it ensures that you have the freedom to 
modify the
code and actually run the modified software.

Felix


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

Bug#694071: FTBFS on powerpc: Minor webrtc issues

[Michel Dänzer]

Source: iceweasel
Version: 17.0-1
Severity: serious
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


The attached patch allows iceweasel 17.0-1 to build and run on powerpc.


- -- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (102, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 3.6.2+
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xulrunner-17.0 depends on:
pn  libasound2
ii  libatk1.0-0   2.6.0-1
ii  libbz2-1.01.0.6-4
ii  libc6 2.13-37
ii  libcairo2 1.12.6-1
ii  libdbus-1-3   1.6.8-1
ii  libdbus-glib-1-2  0.100-1
ii  libevent-2.0-52.0.19-stable-3
ii  libfontconfig12.9.0-7
ii  libfreetype6  2.4.9-1
ii  libgcc1   1:4.7.2-4
ii  libgdk-pixbuf2.0-02.26.4-2
ii  libglib2.0-0  2.34.2-1
ii  libgtk2.0-0   2.24.13-1
ii  libhunspell-1.3-0 1.3.2-4
ii  libjpeg8  8d-1
ii  libmozjs17d   17.0-1
ii  libnspr4  2:4.9.3-1
ii  libnspr4-0d   2:4.9.3-1
ii  libnss3   2:3.14-1
ii  libnss3-1d2:3.14-1
ii  libpango1.0-0 1.30.0-1
ii  libpixman-1-0 0.26.0-3
ii  libsqlite3-0  3.7.14.1-1
ii  libstartup-notification0  0.12-1
ii  libstdc++64.7.2-4
ii  libvpx1   1.1.0-1
ii  libx11-6  2:1.5.0-1
ii  libxext6  2:1.3.1-2
ii  libxrender1   1:0.9.7-1
ii  libxt61:1.1.3-1
ii  zlib1g1:1.2.7.dfsg-13

Versions of packages xulrunner-17.0 suggests:
ii  libcanberra0  0.28-5
ii  libgnomeui-0  2.24.5-2

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iD8DBQFQr5HUWoGvjmrbsgARApTYAKC3SgMYRBgHToTgiWZ8mOU24jd4oACfa81W
ytBQElysrCXrOm/J5wv/TJA=
=rbs0
-END PGP SIGNATURE-
diff -up -ru iceweasel-17.0.orig/media/webrtc/shared_libs.mk iceweasel-17.0/media/webrtc/shared_libs.mk
--- iceweasel-17.0.orig/media/webrtc/shared_libs.mk	2012-11-20 03:46:12.0 +0100
+++ iceweasel-17.0/media/webrtc/shared_libs.mk	2012-11-22 17:39:54.0 +0100
@@ -29,13 +29,11 @@ SHARED_LIBRARY_LIBS += \
   $(call EXPAND_LIBNAME_PATH,rtp_rtcp,$(DEPTH)/media/webrtc/trunk/src/modules/modules_rtp_rtcp) \
   $(call EXPAND_LIBNAME_PATH,udp_transport,$(DEPTH)/media/webrtc/trunk/src/modules/modules_udp_transport) \
   $(call EXPAND_LIBNAME_PATH,video_processing,$(DEPTH)/media/webrtc/trunk/src/modules/modules_video_processing) \
-  $(call EXPAND_LIBNAME_PATH,video_processing_sse2,$(DEPTH)/media/webrtc/trunk/src/modules/modules_video_processing_sse2) \
   $(call EXPAND_LIBNAME_PATH,voice_engine_core,$(DEPTH)/media/webrtc/trunk/src/voice_engine/voice_engine_voice_engine_core) \
   $(call EXPAND_LIBNAME_PATH,audio_conference_mixer,$(DEPTH)/media/webrtc/trunk/src/modules/modules_audio_conference_mixer) \
   $(call EXPAND_LIBNAME_PATH,audio_device,$(DEPTH)/media/webrtc/trunk/src/modules/modules_audio_device) \
   $(call EXPAND_LIBNAME_PATH,audio_processing,$(DEPTH)/media/webrtc/trunk/src/modules/modules_audio_processing) \
   $(call EXPAND_LIBNAME_PATH,aec,$(DEPTH)/media/webrtc/trunk/src/modules/modules_aec) \
-  $(call EXPAND_LIBNAME_PATH,aec_sse2,$(DEPTH)/media/webrtc/trunk/src/modules/modules_aec_sse2) \
   $(call EXPAND_LIBNAME_PATH,apm_util,$(DEPTH)/media/webrtc/trunk/src/modules/modules_apm_util) \
   $(call EXPAND_LIBNAME_PATH,aecm,$(DEPTH)/media/webrtc/trunk/src/modules/modules_aecm) \
   $(call EXPAND_LIBNAME_PATH,agc,$(DEPTH)/media/webrtc/trunk/src/modules/modules_agc) \
@@ -43,3 +41,10 @@ SHARED_LIBRARY_LIBS += \
   $(call EXPAND_LIBNAME_PATH,yuv,$(DEPTH)/media/webrtc/trunk/third_party/libyuv/libyuv_libyuv) \
   $(call EXPAND_LIBNAME_PATH,webrtc_jpeg,$(DEPTH)/media/webrtc/trunk/src/common_video/common_video_webrtc_jpeg) \
   $(NULL)
+
+ifneq (,$(findstring 86,$(CPU_ARCH)))
+	SHARED_LIBRARY_LIBS += \
+	  $(call EXPAND_LIBNAME_PATH,video_processing_sse2,$(DEPTH)/media/webrtc/trunk/src/modules/modules_video_processing_sse2) \
+	  $(call EXPAND_LIBNAME_PATH,aec_sse2,$(DEPTH)/media/webrtc/trunk/src/modules/modules_aec_sse2) \
+	  $(NULL)
+endif
diff -up -ru iceweasel-17.0.orig/media/webrtc/trunk/src/modules/audio_coding/codecs/pcm16b/pcm16b.gypi iceweasel-17.0/media/webrtc/trunk/src/modules/audio_coding/codecs/pcm16b/pcm16b.gypi
--- iceweasel-17.0.orig/media/webrtc/trunk/src/modules/audio_coding/codecs/pcm16b/pcm16b.gypi	2012-11-20 03:46:12.0 +0100
+++ iceweasel-17.0/media/webrtc/trunk/src/modules/audio_coding/codecs/pcm16b/pcm16b.gypi	2012-11-22 16:09:01.0 +0100
@@ -11,6 +11,9 @@
 {
   'target_name': 'PCM16B',
   'type': '<(library)',
+  'dependencies': [
+'<(webrtc_root)/common_audio/common_audio.gyp:si

Bug#693937: [Pkg-xfce-devel] Bug#693937: Bug#693937: Bug#693937: Bug#693937: Acknowledgement (thunar: Thunar crashes when mounting USB stick)

[Yves-Alexis Perez]

On ven., 2012-11-23 at 14:49 +0100, Frane Šalković wrote:
> This is bt now, when everything works...

Quit thunar daemon first, or you won't be able to get a backtrace
anyway. So run:

thunar -q
gdb thunar

> Which packages should I remove and send you backtrace?

Just set you in the previous situation?

Regards,
-- 
Yves-Alexis


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

Bug#694072: RFS: filebot/3.1

[Reinhard Pointner]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my application "filebot"

  Package name: filebot
  Version : 3.1
  Upstream Author : Reinhard Pointner 
  URL :  
http://filebot.sourceforge.net
  License : GPLv2
  Section : misc

To access further information about this application, please visit the 
following URL:
http://filebot.sourceforge.net/

I've got pre-built debs here and all the source is on sourceforge as well:

https://sourceforge.net/projects/filebot/files/filebot/FileBot_3.1/filebot_3.1_i386.deb

https://sourceforge.net/projects/filebot/files/filebot/FileBot_3.1/filebot_3.1_amd64.deb


Regards,
Reinhard Pointner

Bug#683751: gettext: Please mark gettext M-A: allowed

[Colin Watson]

On Fri, Nov 23, 2012 at 02:22:25PM +, Wookey wrote:
> +++ Colin Watson [2012-11-23 13:31 +]:
> > Do you have an opinion on this part?  If not, I think my default would
> > be for the next version of this patch to move autosprintf.info.gz back
> > to gettext, for safety.
> 
> Doesn't this problem of potentially-rebuilt text/doc/info files exist
> all over the place?

Not that widely.  The bulk of documentation in M-A: same packages, as
far as I've seen so far, is just static files, which are just fine.

> I've come across it in perl docs which embed the build date, not the
> doc-creation date, for example.

Those clearly must not be in M-A: same packages because they will rarely
if ever manage to be identical.  That's a different issue from cases
like this, which will generally be identical across architectures but
where we might occasionally be unlucky.

> Essentially any doc in an M-A same package has the issue of rebuilds
> potentially changing the text.  i.e. there is nothing special about
> gettext here.  Is texinfo version skew likely enough to break things
> that we should worry.

I don't like leaving timebombs around behind me.  It seems like the kind
of thing that my future self would be likely to curse me for doing.

> One way of dealing with this is moving all docs out of M-A: same
> packages, and docs are arch-independent stuff so it makes some sense.

That would be drastic overkill, since many documentation files are
obviously invariant across architectures.

We already have a clear rule that says that things that vary across
architectures must not be in M-A: same packages.  This is only a
difficult situation because it will only vary if we get unlucky
(although it's a predictable kind of bad luck, rather than cosmic rays);
but we don't need to generalise the problem further than necessary.

> What we really want is QA checks on MA co-installability and
> corresponding rebuilds/fixes where it's gone wrong.

We should certainly have this, but I don't think it absolves us from
trying to insure against predictable problems up-front.

-- 
Colin Watson   [cjwat...@ubuntu.com]


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

Bug#694020: [Pkg-libvirt-maintainers] Bug#694020: Incorrect LSB header, Should-Start contains obsolete hal

[Michael Biebl]

Hi Guido,

On 23.11.2012 08:00, Guido Günther wrote:
> On Fri, Nov 23, 2012 at 04:20:58AM +0100, Michael Biebl wrote:
>> Package: libvirt-bin
>>
>> HAL has been deprecated and declared dead upstream so we want to
>> get rid of it in Debian [1].
>>
>> The libvirt-bin sysv init script contains in its LSB header
>>
>> # Should-Start:  hal avahi cgconfig
>> # Should-Stop:   hal avahi cgconfig
>>
>> Afaics libvirt-bin does not actually need or use hal so this dependency 
>> should
>> be dropped.
> 
> It's used on non-linux architecture for device enumeration, we'd lose a
> bit of networking support by that on kFreeBSD. Do you know of any
> discussion with the freebsd porters about that? I assume libvirt isn't
> the only package affected?

I forgot to add: since hal_0.5.14-4 [1], the hal sysv init script is gone!
Hal has been changed to use D-Bus activation, so it is started
on-demand. Some HAL clients do not quite cope with that, so you'd have
to test if device enumeration on kbsd is actually still working when
using hal.
That said, it's almost two years, since that change. So either there is
no problem in libvirt or no-one is using libvirt on kbsd.

Aside from that, hal is going away in jessie. The code has been dead
upstream for almost three years now and I don't want to drag it along
for another release (my plan was actually, to already drop it for wheezy).

As for device enumeration on kbsd: I don't use kbsd, so I can't really
help you here. I think there is devd which provides an equivalent to
udev. I hope the Debian kbsd porters can chime in here.

Michael


[1] http://packages.qa.debian.org/h/hal/news/20101117T211711Z.html
-- 
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#693937: [Pkg-xfce-devel] Bug#693937: Bug#693937: Bug#693937: Bug#693937: Acknowledgement (thunar: Thunar crashes when mounting USB stick)

[Frane Šalković]

On 11/23/2012 04:17 PM, Yves-Alexis Perez wrote:
> On ven., 2012-11-23 at 14:49 +0100, Frane Šalković wrote:
>> This is bt now, when everything works...
> Quit thunar daemon first, or you won't be able to get a backtrace
> anyway. So run:
>
> thunar -q
> gdb thunar
>
>> Which packages should I remove and send you backtrace?
> Just set you in the previous situation?
>
> Regards,
Ok, I've removed libfm1, libfm-gtk1, libfm-gtk-bin, libfm-data to set me
in previous situation.

This is bt:
shicy@debian:/$ thunar -q
shicy@debian:/$ gdb thunar
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/bin/thunar...Reading symbols from
/usr/lib/debug/.build-id/a3/5e4675f86e1fcc687b43ebfcab753b346a.debug...done.
done.
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/thunar
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
[New Thread 0xb1c3bb70 (LWP 31298)]

(thunar:31295): GLib-GIO-CRITICAL **: g_mount_get_root: assertion
`G_IS_MOUNT (mount)' failed

(thunar:31295): GLib-GIO-CRITICAL **: g_file_hash: assertion `G_IS_FILE
(file)' failed

(thunar:31295): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed

(thunar:31295): GLib-GIO-CRITICAL **: g_file_query_info: assertion
`G_IS_FILE (file)' failed

(thunar:31295): GLib-GIO-CRITICAL **: g_file_info_get_file_type:
assertion `G_IS_FILE_INFO (info)' failed

(thunar:31295): GLib-GIO-CRITICAL **: g_file_get_basename: assertion
`G_IS_FILE (file)' failed

(thunar:31295): GLib-GIO-CRITICAL **: g_file_has_prefix: assertion
`G_IS_FILE (file)' failed

(thunar:31295): GLib-GIO-CRITICAL **: g_file_is_native: assertion
`G_IS_FILE (file)' failed

(thunar:31295): GLib-GIO-CRITICAL **: g_file_get_uri: assertion
`G_IS_FILE (file)' failed

Program received signal SIGSEGV, Segmentation fault.
0xb75ac020 in g_utf8_validate () from /lib/i386-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0  0xb75ac020 in g_utf8_validate () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb75627f8 in g_filename_display_name () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#2  0x80034b38 in thunar_file_load (file=file@entry=0x80201490,
cancellable=cancellable@entry=0x0, error=error@entry=0xb2ec) at
thunar-file.c:887
#3  0x80036776 in thunar_file_get (gfile=0x0,
error=error@entry=0xb2ec) at thunar-file.c:631
#4  0x80023815 in thunar_browser_poke_volume_finish (object=0x800e4110,
result=0x80240f60, user_data=0x80252060) at thunar-browser.c:443
#5  0xb76f08b5 in g_simple_async_result_complete () from
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0xb76f09db in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#7  0xb757d190 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb757f6d3 in g_main_context_dispatch () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb757fa70 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb757fecb in g_main_loop_run () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#11 0xb7bf8ad0 in gtk_main () from
/usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
#12 0x800194e0 in main (argc=1, argv=0xb5e4) at main.c:294


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

Bug#692222: libtool upload for x32

[Daniel Schepler]

Hi,
Would it be OK for me to upload to experimental a version of libtool with the 
patch I submitted for this bug?  I'd like to have a package version I can tell 
maintainers to install, when I start filing bug reports like "foobar: FTBFS on 
x32: needs libtool update".
-- 
Daniel Schepler


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

Bug#693937: [Pkg-xfce-devel] Bug#693937: Bug#693937: Bug#693937: Bug#693937: Bug#693937: Acknowledgement (thunar: Thunar crashes when mounting USB stick)

[Yves-Alexis Perez]

On ven., 2012-11-23 at 16:48 +0100, Frane Šalković wrote:
> On 11/23/2012 04:17 PM, Yves-Alexis Perez wrote:
> > On ven., 2012-11-23 at 14:49 +0100, Frane Šalković wrote:
> >> This is bt now, when everything works...
> > Quit thunar daemon first, or you won't be able to get a backtrace
> > anyway. So run:
> >
> > thunar -q
> > gdb thunar
> >
> >> Which packages should I remove and send you backtrace?
> > Just set you in the previous situation?
> >
> > Regards,
> Ok, I've removed libfm1, libfm-gtk1, libfm-gtk-bin, libfm-data to set me
> in previous situation.

Those looked to me like completely unrelated. Afaict it was related to
gvfs. I'm sorry but you really need to pinpoint what *specific* package
leads to the crash.
> 
> This is bt:
> shicy@debian:/$ thunar -q
> shicy@debian:/$ gdb thunar
> GNU gdb (GDB) 7.4.1-debian
> Copyright (C) 2012 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i486-linux-gnu".
> For bug reporting instructions, please see:
> ...
> Reading symbols from /usr/bin/thunar...Reading symbols from
> /usr/lib/debug/.build-id/a3/5e4675f86e1fcc687b43ebfcab753b346a.debug...done.
> done.
> (gdb) set pagination 0
> (gdb) run
> Starting program: /usr/bin/thunar
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library
> "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
> [New Thread 0xb1c3bb70 (LWP 31298)]
> 
> (thunar:31295): GLib-GIO-CRITICAL **: g_mount_get_root: assertion
> `G_IS_MOUNT (mount)' failed
> 
> (thunar:31295): GLib-GIO-CRITICAL **: g_file_hash: assertion `G_IS_FILE
> (file)' failed
> 
> (thunar:31295): GLib-GObject-CRITICAL **: g_object_ref: assertion
> `G_IS_OBJECT (object)' failed
> 
> (thunar:31295): GLib-GIO-CRITICAL **: g_file_query_info: assertion
> `G_IS_FILE (file)' failed
> 
> (thunar:31295): GLib-GIO-CRITICAL **: g_file_info_get_file_type:
> assertion `G_IS_FILE_INFO (info)' failed
> 
> (thunar:31295): GLib-GIO-CRITICAL **: g_file_get_basename: assertion
> `G_IS_FILE (file)' failed
> 
> (thunar:31295): GLib-GIO-CRITICAL **: g_file_has_prefix: assertion
> `G_IS_FILE (file)' failed
> 
> (thunar:31295): GLib-GIO-CRITICAL **: g_file_is_native: assertion
> `G_IS_FILE (file)' failed
> 
> (thunar:31295): GLib-GIO-CRITICAL **: g_file_get_uri: assertion
> `G_IS_FILE (file)' failed
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0xb75ac020 in g_utf8_validate () from /lib/i386-linux-gnu/libglib-2.0.so.0

Mhmh, that's really weird.
> (gdb) bt
> #0  0xb75ac020 in g_utf8_validate () from
> /lib/i386-linux-gnu/libglib-2.0.so.0
> #1  0xb75627f8 in g_filename_display_name () from
> /lib/i386-linux-gnu/libglib-2.0.so.0
> #2  0x80034b38 in thunar_file_load (file=file@entry=0x80201490,
> cancellable=cancellable@entry=0x0, error=error@entry=0xb2ec) at
> thunar-file.c:887

If you manually mount the usb key and navigate to the mount point with
Thunar, does it crash?

Can you paste the output of mount when mounted manually and when mounted
through Thunar?

It looks to me like there's an issue with a filename encoding which
makes glib crash.

Regards,
-- 
Yves-Alexis


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

Bug#686637: mutt: Wrong parsing of localized S/MIME Content-Description header

[Christoph Berg]

Control: tag -1 confirmed

> This is basically a new derivate of the already fixed non-locale-related bug 
> reported at
> http://debian.2.n7.nabble.com/Bug-328655-mutt-Verification-failure-PKCS7-verify-wrong-content-type-pk7-smime-c-173-td51012.html#a3108819

(That was #328655, for reference.)

> The problem of mutt's failure to detect S/MIME encrypted messages
> persists when receiving mail with localized Content-Description header
> for S/MIME, i.e.
> 
>  Content-Description: S/MIME Encrypted Message
> 
> will work and display the encryption flag "P" correctly in the mail index, 
> while
> the localized german description header
> 
>  Content-Description: S/MIME Verschlüsselte Nachricht
> 
> will NOT work, i.e. neither flag the message as encrypted, not decrypt
> the message using the set smime_decrypt_command. Changing the header to
> english manually is a valid, yet uncomfortable workaround.

I have the same problem, ack.

> It is apparently not a good idea to use the Content-Description alone as
> indicator of S/MIME encryption since this is subject to localization on
> the senders side.

Mutt does try to do something with the mail, so it actually knows it
is s/mime encoded. No idea what extra use looking at
Content-Description serves at all...

> Maybe it would be better to distinguish by presence of the headers
>  Content-Type: application/pkcs7-mime
> vs.
>  Content-Type: multipart/signed;
> protocol="application/pkcs7-signature"
> whether or not we have an encrypted/signed message.

Sounds plausible.

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


signature.asc
Description: Digital signature

Bug#694073: RFP: python-clouddns -- Python interface to Rackspace Cloud DNS

[Alexandre Viau]

package: wnpp

Severity:  wishlist
homepage: https://github.com/rackspace/python-clouddns
license: BSD

Description: python-clouddns proviced a python interface to Rackspace's Cloud 
DNS platform.


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

Bug#694048: systemd: Fetchmail restart failed

[Michael Biebl]

On 23.11.2012 11:39, Salvo Tomaselli wrote:
> Package: systemd
> Version: 44-5
> Severity: normal
> 
> Dear Maintainer,
> Running service fetchmail restart i obtained this in my syslog.
> 
>> Nov 23 10:52:37 localhost fetchmail[12963]: Stopping mail retriever agent: 
>> fetchmail.
>> Nov 23 10:52:37 localhost fetchmail[875]: terminato con segnale 15
>> Nov 23 10:52:37 localhost fetchmail[12971]: fetchmail already started; not 
>> starting. ... failed!
>> Nov 23 10:53:23 localhost fetchmail[13055]: Pidfile not found! Is fetchmail 
>> running? ... failed!
> 
> This seems to be an heisenbug, and doesn't occur at every restart.

Does this only happen under systemd?
when you get those error messages, is fetchmail running afterwards?

Could you post your fetchmail config details

> Versions of packages systemd recommends:
> pn  libpam-systemd  

Please do install libpam-systemd.

-- 
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#667459: Update

[Meike Reichle]

Michel Dänzer @ 09/11/12 15:32:

On Fre, 2012-11-09 at 14:52 +0100, Meike Reichle wrote:

Michel Dänzer @ 09/11/12 10:03:

On Fre, 2012-11-09 at 09:12 +0100, Meike Reichle wrote:


I am using a standard Debian kernel (linux-image-3.2.0-4-686-pae) but
apparently no KMS, I suppose my graphics card (Mobility Radeon HD 3200)
does not support it.


Not sure why it wouldn't, please provide your dmesg output.


I've attached it to this mail.


Hmm, thanks, but it doesn't show why KMS is disabled. Is it disabled
in /etc/modprobe.d/radeon-kms.conf?


It seems to be already enabled there:

mre@jet:~$ cat /etc/modprobe.d/radeon-kms.conf
options radeon modeset=1
mre@jet:~$



If that still doesn't explain it, can you try passing radeon.modeset=1
on the kernel command line and see if that enables it?


That did the trick. With that command line I got KMS. I've attached the 
dmesg from that boot. I guess the question now it why it isn't enabled by 
/etc/modprobe.d/radeon-kms.conf ...


Regards,
Meike
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.2.0-4-686-pae (debian-ker...@lists.debian.org) 
(gcc version 4.6.3 (Debian 4.6.3-12) ) #1 SMP Debian 3.2.32-1
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e820:  - 0009dc00 (usable)
[0.00]  BIOS-e820: 0009dc00 - 000a (reserved)
[0.00]  BIOS-e820: 000d - 0010 (reserved)
[0.00]  BIOS-e820: 0010 - 6fed (usable)
[0.00]  BIOS-e820: 6fed - 6fedc000 (ACPI data)
[0.00]  BIOS-e820: 6fedc000 - 6fede000 (ACPI NVS)
[0.00]  BIOS-e820: 6fede000 - 8000 (reserved)
[0.00]  BIOS-e820: e000 - f000 (reserved)
[0.00]  BIOS-e820: fec0 - fec1 (reserved)
[0.00]  BIOS-e820: fee0 - fee01000 (reserved)
[0.00]  BIOS-e820: fff0 - 0001 (reserved)
[0.00] NX (Execute Disable) protection: active
[0.00] DMI present.
[0.00] DMI: LENOVO 287655G/287655G, BIOS 6XET44WW (1.27 ) 07/21/2010
[0.00] e820 update range:  - 0001 (usable) 
==> (reserved)
[0.00] e820 remove range: 000a - 0010 (usable)
[0.00] last_pfn = 0x6fed0 max_arch_pfn = 0x100
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-C write-protect
[0.00]   D-D uncachable
[0.00]   E-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 00 mask FF8000 write-back
[0.00]   1 disabled
[0.00]   2 disabled
[0.00]   3 disabled
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[0.00] found SMP MP-table at [c00f7df0] f7df0
[0.00] initial memory mapped : 0 - 01a0
[0.00] Base memory trampoline at [c0099000] 99000 size 16384
[0.00] init_memory_mapping: -379fe000
[0.00]  00 - 20 page 4k
[0.00]  20 - 003780 page 2M
[0.00]  003780 - 00379fe000 page 4k
[0.00] kernel direct mapping tables up to 379fe000 @ 19fa000-1a0
[0.00] RAMDISK: 368f2000 - 37471000
[0.00] ACPI: RSDP 000f7ac0 00024 (v02 PTLTD )
[0.00] ACPI: XSDT 6fed1e2b 0005C (v01 LENOVO TP-6X1270  LTP 
)
[0.00] ACPI: FACP 6fedbb59 000F4 (v03 LENOVO TP-6X1270 ATI  
000F4240)
[0.00] ACPI: DSDT 6fed1e87 09CD2 (v01 LENOVO TP-6X1270 MSFT 
0301)
[0.00] ACPI: FACS 6feddfc0 00040
[0.00] ACPI: TCPA 6fedbcc1 00032 (v02 LENOVO TP-6X1270 PTEC 
)
[0.00] ACPI: SSDT 6fedbcf3 000D3 (v01 LENOVO TP-6X1270 AMD  
0001)
[0.00] ACPI: APIC 6fedbdc6 00050 (v01 LENOVO TP-6X1270  LTP 
)
[0.00] ACPI: MCFG 6fedbe16 0003C (v01 LENOVO TP-6X1270  LTP 
)
[0.00] ACPI: HPET 6fedbe52 00038 (v01 LENOVO TP-6X1270  LTP 
0001)
[0.00] ACPI: SLIC 6fedbe8a 00176 (v01 LENOVO TP-6X1270  LTP 
)
[0.00] ACPI: Local APIC address 0xfee0
[0.00] 900MB HIGHMEM available.
[0.00] 889MB LOWMEM available.
[0.00]   mapped low ram: 0 - 379fe000
[0.00]   low ram: 0 - 379fe000
[0.00] Zone PFN ranges:
[0.00]   DMA  0x0010 -> 0x1000
[0.00]   Normal   0x1000 -> 0x000379fe
[0.00]   HighMem  0x000379fe -> 0x0006fed0
[0.00] Movable zone start PFN for eac

Bug#667459: Update

[Michel Dänzer]

On Fre, 2012-11-23 at 17:24 +0100, Meike Reichle wrote: 
> Michel Dänzer @ 09/11/12 15:32:
> >
> > If that still doesn't explain it, can you try passing radeon.modeset=1
> > on the kernel command line and see if that enables it?
> 
> That did the trick. With that command line I got KMS. I've attached the 
> dmesg from that boot. I guess the question now it why it isn't enabled by 
> /etc/modprobe.d/radeon-kms.conf ...

Indeed... The only explanations I can think of:

  * /etc/modprobe.d/radeon-kms.conf says modeset=0 in the initrd.
'sudo update-initramfs -k $(uname -r) -u' should fix it in this
case. 
  * There's another configuration file on your system that says
modeset=0.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast |  Debian, X and DRI developer


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

Bug#694074: conky-all: Incorrect link in man page

[Sharon Kimble]

Package: conky-all
Version: 1.9.0-2
Severity: minor

Dear Maintainer,

At the end of the man page it says 'SEE ALSO' where there is the link to
http://wiki.conky.be which is a 'joke site' and nothing to do with conky the
programme.

I feel that this link should be removed, to improve the quality of the
information in the man page.

Thank you
Sharon Kimble.



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

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
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 conky-all depends on:
ii  libaudclient2 3.2.3-2
ii  libc6 2.13-35
ii  libcairo2 1.12.2-2
ii  libcurl3-gnutls   7.26.0-1
ii  libdbus-glib-1-2  0.100-1
ii  libglib2.0-0  2.33.12+really2.32.4-3
ii  libimlib2 1.4.5-1
ii  libiw30   30~pre9-8
ii  liblua5.1-0   5.1.5-4
ii  libncurses5   5.9-10
ii  libtinfo5 5.9-10
ii  libx11-6  2:1.5.0-1
ii  libxdamage1   1:1.1.3-2
ii  libxext6  2:1.3.1-2
ii  libxfixes31:5.0-4
ii  libxft2   2.3.1-1
ii  libxml2   2.8.0+dfsg1-6
ii  libxmmsclient60.8+dfsg-4
ii  libxnvctrl0   304.48-1

conky-all recommends no packages.

Versions of packages conky-all suggests:
pn  apcupsd
ii  audacious  3.2.3-2
pn  moc
pn  mpd
ii  xmms2  0.8+dfsg-4

-- 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#559927: /usr/lib/avahi/avahi-daemon-check-dns.sh significantly delays the boot sequence

[Lluís Gili]

Package: avahi-daemon
Version: 0.6.31-1
Followup-For: Bug #559927

Dear Maintainer,
this script is linked from /etc/network/if-post-down.d/avahi-daemon too,
it is delaying my shutdown sequence for about 30 seconds (2 network
interfaces, taking about 15 seconds each)
Boot process is delayed too, but not as much as shutdown

kind regards,
Lluís


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

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

Versions of packages avahi-daemon depends on:
ii  adduser3.113+nmu3
ii  bind9-host [host]  1:9.8.1.dfsg.P1-4.4
ii  dbus   1.6.8-1
ii  host   1:9.8.1.dfsg.P1-4.4
ii  libavahi-common3   0.6.31-1
ii  libavahi-core7 0.6.31-1
ii  libc6  2.13-35
ii  libcap21:2.22-1.2
ii  libdaemon0 0.14-2
ii  libdbus-1-31.6.8-1
ii  libexpat1  2.1.0-1
ii  lsb-base   4.1+Debian8

Versions of packages avahi-daemon recommends:
ii  libnss-mdns  0.10-3.2

Versions of packages avahi-daemon suggests:
pn  avahi-autoipd  

-- 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#693937: [Pkg-xfce-devel] Bug#693937: Bug#693937: Bug#693937: Bug#693937: Bug#693937: Acknowledgement (thunar: Thunar crashes when mounting USB stick)

[Frane Šalković]

On 11/23/2012 05:03 PM, Yves-Alexis Perez wrote:
> On ven., 2012-11-23 at 16:48 +0100, Frane Šalković wrote:
>> On 11/23/2012 04:17 PM, Yves-Alexis Perez wrote:
>>> On ven., 2012-11-23 at 14:49 +0100, Frane Šalković wrote:
 This is bt now, when everything works...
>>> Quit thunar daemon first, or you won't be able to get a backtrace
>>> anyway. So run:
>>>
>>> thunar -q
>>> gdb thunar
>>>
 Which packages should I remove and send you backtrace?
>>> Just set you in the previous situation?
>>>
>>> Regards,
>> Ok, I've removed libfm1, libfm-gtk1, libfm-gtk-bin, libfm-data to set me
>> in previous situation.
> Those looked to me like completely unrelated. Afaict it was related to
> gvfs. I'm sorry but you really need to pinpoint what *specific* package
> leads to the crash.
How can I specify which package leads to the crash?
TIA
>> This is bt:
>> shicy@debian:/$ thunar -q
>> shicy@debian:/$ gdb thunar
>> GNU gdb (GDB) 7.4.1-debian
>> Copyright (C) 2012 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later
>> 
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>> and "show warranty" for details.
>> This GDB was configured as "i486-linux-gnu".
>> For bug reporting instructions, please see:
>> ...
>> Reading symbols from /usr/bin/thunar...Reading symbols from
>> /usr/lib/debug/.build-id/a3/5e4675f86e1fcc687b43ebfcab753b346a.debug...done.
>> done.
>> (gdb) set pagination 0
>> (gdb) run
>> Starting program: /usr/bin/thunar
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library
>> "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
>> [New Thread 0xb1c3bb70 (LWP 31298)]
>>
>> (thunar:31295): GLib-GIO-CRITICAL **: g_mount_get_root: assertion
>> `G_IS_MOUNT (mount)' failed
>>
>> (thunar:31295): GLib-GIO-CRITICAL **: g_file_hash: assertion `G_IS_FILE
>> (file)' failed
>>
>> (thunar:31295): GLib-GObject-CRITICAL **: g_object_ref: assertion
>> `G_IS_OBJECT (object)' failed
>>
>> (thunar:31295): GLib-GIO-CRITICAL **: g_file_query_info: assertion
>> `G_IS_FILE (file)' failed
>>
>> (thunar:31295): GLib-GIO-CRITICAL **: g_file_info_get_file_type:
>> assertion `G_IS_FILE_INFO (info)' failed
>>
>> (thunar:31295): GLib-GIO-CRITICAL **: g_file_get_basename: assertion
>> `G_IS_FILE (file)' failed
>>
>> (thunar:31295): GLib-GIO-CRITICAL **: g_file_has_prefix: assertion
>> `G_IS_FILE (file)' failed
>>
>> (thunar:31295): GLib-GIO-CRITICAL **: g_file_is_native: assertion
>> `G_IS_FILE (file)' failed
>>
>> (thunar:31295): GLib-GIO-CRITICAL **: g_file_get_uri: assertion
>> `G_IS_FILE (file)' failed
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0xb75ac020 in g_utf8_validate () from /lib/i386-linux-gnu/libglib-2.0.so.0
> Mhmh, that's really weird.
>> (gdb) bt
>> #0  0xb75ac020 in g_utf8_validate () from
>> /lib/i386-linux-gnu/libglib-2.0.so.0
>> #1  0xb75627f8 in g_filename_display_name () from
>> /lib/i386-linux-gnu/libglib-2.0.so.0
>> #2  0x80034b38 in thunar_file_load (file=file@entry=0x80201490,
>> cancellable=cancellable@entry=0x0, error=error@entry=0xb2ec) at
>> thunar-file.c:887
> If you manually mount the usb key and navigate to the mount point with
> Thunar, does it crash?
Thunar doesn't crash when I manually mount the usb and navigate to the
mount point (through Thunar).

>
> Can you paste the output of mount when mounted manually and when mounted
> through Thunar?
When I manually mount usb:

root@debian:/media# mount /dev/sdb1 /media/usb0/
root@debian:/media# exit
exit
shicy@debian:/media$ thunar
^C
(Thunar didn't crash, so i closed it)


When mounted through Thunar:

root@debian:/media# umount /dev/sdb1
root@debian:/media# exit
exit
shicy@debian:/media$ thunar
thunar-volman: Unsupported USB device type.
thunar-volman: Unsupported USB device type.
thunar-volman: Unknown block device type.
thunar-volman: Unable to locate mount point.

(thunar:2557): GLib-GIO-CRITICAL **: g_mount_get_root: assertion
`G_IS_MOUNT (mount)' failed

(thunar:2557): GLib-GIO-CRITICAL **: g_file_hash: assertion `G_IS_FILE
(file)' failed

(thunar:2557): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed

(thunar:2557): GLib-GIO-CRITICAL **: g_file_query_info: assertion
`G_IS_FILE (file)' failed

(thunar:2557): GLib-GIO-CRITICAL **: g_file_info_get_file_type:
assertion `G_IS_FILE_INFO (info)' failed

(thunar:2557): GLib-GIO-CRITICAL **: g_file_get_basename: assertion
`G_IS_FILE (file)' failed

(thunar:2557): GLib-GIO-CRITICAL **: g_file_has_prefix: assertion
`G_IS_FILE (file)' failed

(thunar:2557): GLib-GIO-CRITICAL **: g_file_is_native: assertion
`G_IS_FILE (file)' failed

(thunar:2557): GLib-GIO-CRITICAL **: g_file_get_uri: assertion
`G_IS_FILE (file)' failed
Segmentation fault
 
> It looks to me like there's an issue with a filename encoding which
> makes glib crash.
>
> Rega

Bug#694075: ITP: gtkparasite -- GTK+ debugging and development tool

[Anthony Wong]

Package: wnpp
Severity: wishlist

Package name: gtkparasite
Homepage: http://chipx86.github.com/gtkparasite/
License: MIT
Description: GTK+ debugging and development tool
 Parasite is a debugging and development tool that runs inside your GTK+
 application's process. It can inspect your application, giving you detailed
 information on your UI, such as the hierarchy, X window IDs, widget
 properties, and more. You can modify properties on the fly in order to
 experiment with the look of your UI.
 .
 But you can go further than that. You can actually modify your application
 logic while the program is running! Parasite includes an embedded Python
 shell that lets you write new code that directly interacts with your
 application's UI, regardless of the language the application is written in.
 Create new dialogs, attach temporary signal handlers to buttons, test out
 new logic, and gather additional debug information.

This package had been packaged by Devid in 2009 [1] but was later removed
on request due to lack of upstream activity [2]. Lately upstream started to
support GTK3 so we should provide this package again.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514033
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638178

Thanks,
Anthony


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

Bug#693937: [Pkg-xfce-devel] Bug#693937: Bug#693937: Bug#693937: Bug#693937: Bug#693937: Acknowledgement (thunar: Thunar crashes when mounting USB stick)

[Yves-Alexis Perez]

On ven., 2012-11-23 at 17:51 +0100, Frane Šalković wrote:

> How can I specify which package leads to the crash?

I don't know. You're the one having issue, try to investigate? See what
packages are involved and try removing them one by one?

> > Can you paste the output of mount when mounted manually and when mounted
> > through Thunar?
> When I manually mount usb:
> 
> root@debian:/media# mount /dev/sdb1 /media/usb0/
> root@debian:/media# exit
> exit
> shicy@debian:/media$ thunar
> ^C
> (Thunar didn't crash, so i closed it)
> 
> 
> When mounted through Thunar:
> 
> root@debian:/media# umount /dev/sdb1
> root@debian:/media# exit
> exit
> shicy@debian:/media$ thunar
> thunar-volman: Unsupported USB device type.
> thunar-volman: Unsupported USB device type.
> thunar-volman: Unknown block device type.
> thunar-volman: Unable to locate mount point.
> 
> (thunar:2557): GLib-GIO-CRITICAL **: g_mount_get_root: assertion
> `G_IS_MOUNT (mount)' failed
> 
> (thunar:2557): GLib-GIO-CRITICAL **: g_file_hash: assertion `G_IS_FILE
> (file)' failed
> 
> (thunar:2557): GLib-GObject-CRITICAL **: g_object_ref: assertion
> `G_IS_OBJECT (object)' failed
> 
> (thunar:2557): GLib-GIO-CRITICAL **: g_file_query_info: assertion
> `G_IS_FILE (file)' failed
> 
> (thunar:2557): GLib-GIO-CRITICAL **: g_file_info_get_file_type:
> assertion `G_IS_FILE_INFO (info)' failed
> 
> (thunar:2557): GLib-GIO-CRITICAL **: g_file_get_basename: assertion
> `G_IS_FILE (file)' failed
> 
> (thunar:2557): GLib-GIO-CRITICAL **: g_file_has_prefix: assertion
> `G_IS_FILE (file)' failed
> 
> (thunar:2557): GLib-GIO-CRITICAL **: g_file_is_native: assertion
> `G_IS_FILE (file)' failed
> 
> (thunar:2557): GLib-GIO-CRITICAL **: g_file_get_uri: assertion
> `G_IS_FILE (file)' failed
> Segmentation fault
>  

And where is the output of mount in both cases?

Regards,
-- 
Yves-Alexis


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

Bug#683010: FTBFS on ia64: one or more PCH files were found, but they were invalid

[Axel Beckert]

Hi Luca,

Luca Falavigna wrote:
> Source: evolvotron
> Version: 0.6.1-2
> Severity: serious
> Justification: fails to build from source
> 
> 
> evolvotron fails to build from source on ia64, but built in the past:

Nevertheless no change in evolvotron seems to be the cause for that but a
change somewhere in the build-dependencies/toolchain as versions which
built before now FTBFS, too, namely the version in Wheezy (0.6.1-1)
FTBFS on Wheezy on ia64, too. Which means this bug is relevant for the
next release, too.

I'm trying to find a fix.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


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

Bug#694076: update eventmachine to latest upstream release

[Praveen A]

package: ruby-eventmachine
version: 0.12.10-3

needs newer eventmachine for em-htt-request. I'm working on an update.
--
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
You have to keep reminding your government that you don't get your
rights from them; you give them permission to rule, only so long as
they follow the rules: laws and constitution.

Bug#667459: Update

[Meike Reichle]

Michel Dänzer @ 23/11/12 17:36:

On Fre, 2012-11-23 at 17:24 +0100, Meike Reichle wrote:

Michel Dänzer @ 09/11/12 15:32:


If that still doesn't explain it, can you try passing radeon.modeset=1
on the kernel command line and see if that enables it?


That did the trick. With that command line I got KMS. I've attached the
dmesg from that boot. I guess the question now it why it isn't enabled by
/etc/modprobe.d/radeon-kms.conf ...


Indeed... The only explanations I can think of:

   * /etc/modprobe.d/radeon-kms.conf says modeset=0 in the initrd.
 'sudo update-initramfs -k $(uname -r) -u' should fix it in this
 case.
   * There's another configuration file on your system that says
 modeset=0.


update-initramfs fixed it. After that I could also re-upgrade the packages 
I had put on hold (see earlier mail for the list and versions).


Thank you very much for helping me out on this!

Kind regards,
Meike


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

Bug#694078: unblock: etw/3.6+svn140-4

[Markus Koschany]

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

Dear release team,

please unblock etw. I have recently adopted the package and discovered
that it is not possible to load the configuration, like video and
audio settings, from the user's home directory thus the game always
uses the same values after a restart.  

The changes are small and they include a fix to load the configuration from
$HOME/.etw/ and an improved README.Debian which explains the
situation.

I'd be glad if you would consider releasing this version with Wheezy. 

Attached is the debdiff.

Regards,

Markus

unblock etw/3.6+svn140-4

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

Kernel: Linux 3.2.0-4-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


etw.debdiff.gz
Description: GNU Zip compressed data

Bug#694077: RFP: qlc -- application for controlling DMX or analog lighting systems

[nodiscc]

Package: wnpp
Severity: wishlist

* Package name: qlc
  Version : 3.2.2
  Upstream Author : Heikki Junnila 
* URL : http://qlc.sourceforge.net/
* License : GPL
  Programming Lang: C, C++
  Description : application for controlling DMX or analog lighting systems

Q Light Controller is a cross-platform application for controlling DMX or
analog lighting systems like moving heads, dimmers, scanners etc. The goal is
to replace hard-to-learn and somewhat limited commercial lighting desks with
FLOSS. 

Lots of additional DMX interfaces are supported thru the Open Lighting
Architecture (OLA) on Linux and Mac OS X.


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

Bug#694076: one test is failing

[Praveen A]

/usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby
/usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
Running tests for ruby1.8 using debian/ruby-tests.rb...
./tests/em_test_helper.rb:54: warning: already initialized constant
TIMEOUT_INTERVAL
Loaded suite debian/ruby-tests
Started
...
...
..E
===
Error: test_set_sock_opt(TestSetSockOpt)
Errno::EACCES: Permission denied - setsockopt
./debian/ruby-eventmachine//usr/lib/ruby/vendor_ruby/em/connection.rb:280:in
`set_sock_opt'
 277: end
 278:
 279: def set_sock_opt level, optname, optval
  => 280:   EventMachine::set_sock_opt @signature, level, optname, optval
 281: end
 282:
 283: # A variant of {#close_connection}.
./debian/ruby-eventmachine//usr/lib/ruby/vendor_ruby/em/connection.rb:280:in
`set_sock_opt'
./tests/test_set_sock_opt.rb:22:in `post_init'
./debian/ruby-eventmachine//usr/lib/ruby/vendor_ruby/em/connection.rb:58:in
`new'
./debian/ruby-eventmachine//usr/lib/ruby/vendor_ruby/em/connection.rb:49:in
`instance_eval'
./debian/ruby-eventmachine//usr/lib/ruby/vendor_ruby/em/connection.rb:49:in
`new'
./debian/ruby-eventmachine//usr/lib/ruby/vendor_ruby/eventmachine.rb:670:in
`bind_connect'
./debian/ruby-eventmachine//usr/lib/ruby/vendor_ruby/eventmachine.rb:640:in
`connect'
./tests/test_set_sock_opt.rb:20:in `test_set_sock_opt'
./debian/ruby-eventmachine//usr/lib/ruby/vendor_ruby/eventmachine.rb:187:in
`call'
./debian/ruby-eventmachine//usr/lib/ruby/vendor_ruby/eventmachine.rb:187:in
`run_machine'
./debian/ruby-eventmachine//usr/lib/ruby/vendor_ruby/eventmachine.rb:187:in
`run'
./tests/test_set_sock_opt.rb:19:in `test_set_sock_opt'
===
..

Finished in 17.601444 seconds.

211 tests, 335 assertions, 0 failures, 1 errors, 0 pendings, 0
omissions, 0 notifications
99.5261% passed

11.99 tests/s, 19.03 assertions/s

Test "ruby1.8" failed. Continue building the package? (Y/N) y
/usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby
/usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
Running tests for ruby1.9.1 using debian/ruby-tests.rb...
Loaded suite debian/ruby-tests
Started
...
...
..E
===
Error: test_set_sock_opt(TestSetSockOpt)
Errno::EACCES: Permission denied - setsockopt
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/debian/ruby-eventmachine/usr/lib/ruby/vendor_ruby/em/connection.rb:280:in
`set_sock_opt'
 277: end
 278:
 279: def set_sock_opt level, optname, optval
  => 280:   EventMachine::set_sock_opt @signature, level, optname, optval
 281: end
 282:
 283: # A variant of {#close_connection}.
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/debian/ruby-eventmachine/usr/lib/ruby/vendor_ruby/em/connection.rb:280:in
`set_sock_opt'
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/tests/test_set_sock_opt.rb:22:in
`block (3 levels) in test_set_sock_opt'
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/debian/ruby-eventmachine/usr/lib/ruby/vendor_ruby/em/connection.rb:58:in
`block in new'
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/debian/ruby-eventmachine/usr/lib/ruby/vendor_ruby/em/connection.rb:49:in
`instance_eval'
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/debian/ruby-eventmachine/usr/lib/ruby/vendor_ruby/em/connection.rb:49:in
`new'
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/debian/ruby-eventmachine/usr/lib/ruby/vendor_ruby/eventmachine.rb:670:in
`bind_connect'
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/debian/ruby-eventmachine/usr/lib/ruby/vendor_ruby/eventmachine.rb:640:in
`connect'
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/tests/test_set_sock_opt.rb:20:in
`block in test_set_sock_opt'
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/debian/ruby-eventmachine/usr/lib/ruby/vendor_ruby/eventmachine.rb:187:in
`call'
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/debian/ruby-eventmachine/usr/lib/ruby/vendor_ruby/eventmachine.rb:187:in
`run_machine'
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/debian/ruby-eventmachine/usr/lib/ruby/vendor_ruby/eventmachine.rb:187:in
`run'
/media/forge/debian/git/pkg-ruby-extras/ruby-eventmachine/tests/test_set_sock_opt.rb:19:in
`test_set_sock_opt'
===
..

Finished in 19.462458462 seconds.

211 tests, 335 assertions, 0 failures

Bug#694079: linux-image-2.6.32-5-amd64: kernel BUG makes server unstable

[Santiago Bosio]

Package: linux-2.6
Version: 2.6.32-46
Severity: important

Kernel oops present make server unstable, even crash. I need to reboot manually.


-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-46) (da...@debian.org) (gcc version 
4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 10:07:46 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 
root=UUID=04e90568-d268-4638-be3b-e177a4c74831 ro quiet

** Tainted: D (128)
 * Kernel has oopsed before.

** Kernel log:
[15195.802306] st 2:0:0:0: Attached scsi tape st0
[15195.802309] st 2:0:0:0: st0: try direct i/o: yes (alignment 512 B)
[15195.843026] osst :I: Tape driver with OnStream support version 0.99.4
[15195.843028] osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $
[107944.206846] [ cut here ]
[107944.206851] kernel BUG at 
/build/buildd-linux-2.6_2.6.32-46-amd64-_ApuPc/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/slub.c:2969!
[107944.206855] invalid opcode:  [#1] SMP 
[107944.206859] last sysfs file: 
/sys/devices/pci:00/:00:1d.2/usb3/3-1/3-1:1.0/host2/target2:0:0/2:0:0:0/scsi_tape/nst0a/uevent
[107944.206862] CPU 1 
[107944.206864] Modules linked in: osst st usb_storage vboxnetadp vboxnetflt 
vboxdrv cpufreq_userspace cpufreq_conservative cpufreq_powersave cpufreq_stats 
parport_pc ppdev lp parport binfmt_misc fuse loop radeon ttm drm_kms_helper drm 
i2c_algo_bit i2c_core hpilo hpwdt shpchp pci_hotplug iTCO_wdt 
iTCO_vendor_support psmouse evdev pcspkr serio_raw processor button power_meter 
container joydev ext4 mbcache jbd2 crc16 sr_mod cdrom ata_generic usbhid hid 
hpsa ata_piix uhci_hcd ehci_hcd usbcore libata nls_base bnx2 cciss thermal 
scsi_mod thermal_sys [last unloaded: scsi_wait_scan]
[107944.206914] Pid: 3644, comm: udisks-daemon Not tainted 2.6.32-5-amd64 #1 
ProLiant DL380 G7
[107944.206917] RIP: 0010:[]  [] 
kfree+0x55/0xcb
[107944.206930] RSP: 0018:88021c7ffa48  EFLAGS: 00010246
[107944.206933] RAX: 0600082c RBX: 88021c705a70 RCX: 
a00104c0
[107944.206936] RDX: 88021c705a40 RSI: 8802274120d0 RDI: 
ea000e00
[107944.206939] RBP: 8804 R08: 8149bd88 R09: 
81479930
[107944.206942] R10: 0001019b8b6c R11: 810b5dcb R12: 
a01386db
[107944.206945] R13: 0001 R14: 8804 R15: 
88041eac8360
[107944.206949] FS:  7fa52774a7a0() GS:88022740() 
knlGS:
[107944.206952] CS:  0010 DS:  ES:  CR0: 8005003b
[107944.206955] CR2: 7f9a6d38c000 CR3: 00021cd1c000 CR4: 
26e0
[107944.206958] DR0:  DR1:  DR2: 

[107944.206961] DR3:  DR6: 0ff0 DR7: 
0400
[107944.206964] Process udisks-daemon (pid: 3644, threadinfo 88021c7fe000, 
task 880213c8f100)
[107944.206967] Stack:
[107944.206968]  88021c705a70 88021c705a40  
a01386db
[107944.206973] <0> 0296 88021c7ffa98 88021c7ffef8 
81067ccf
[107944.206977] <0> 88021c7ffb88 812fc4bf 88041cc0fa99 
8802274101b0
[107944.206982] Call Trace:
[107944.206991]  [] ? sr_media_change+0x253/0x27a [sr_mod]
[107944.206998]  [] ? hrtimer_cancel+0xc/0x16
[107944.207004]  [] ? schedule_hrtimeout_range+0xd5/0x112
[107944.207011]  [] ? media_changed+0x42/0x74 [cdrom]
[107944.207018]  [] ? check_disk_change+0x22/0x53
[107944.207023]  [] ? cdrom_open+0x8d2/0x962 [cdrom]
[107944.207030]  [] ? do_sys_poll+0x316/0x391
[107944.207034]  [] ? __pollwait+0x0/0xd6
[107944.207038]  [] ? pollwake+0x0/0x59
[107944.207042]  [] ? pollwake+0x0/0x59
[107944.207047]  [] ? apic_timer_interrupt+0xe/0x20
[107944.207054]  [] ? cap_inode_permission+0x0/0x3
[107944.207060]  [] ? kobject_get+0x12/0x17
[107944.207065]  [] ? get_disk+0x95/0xb4
[107944.207072]  [] ? kobj_lookup+0x169/0x1a1
[107944.207075]  [] ? kobject_get+0x12/0x17
[107944.207081]  [] ? sr_block_open+0x86/0x9f [sr_mod]
[107944.207084]  [] ? __blkdev_get+0x258/0x342
[107944.207088]  [] ? blkdev_open+0x0/0x96
[107944.207091]  [] ? blkdev_open+0x67/0x96
[107944.207096]  [] ? __dentry_open+0x19d/0x2bf
[107944.207100]  [] ? do_filp_open+0x4e4/0x94b
[107944.207106]  [] ? cdrom_release+0x1ae/0x1fe [cdrom]
[107944.207113]  [] ? rcu_start_gp+0x197/0x1c0
[107944.207119]  [] ? read_tsc+0xa/0x20
[107944.207124]  [] ? timekeeping_get_ns+0xe/0x2e
[107944.207129]  [] ? alloc_fd+0x67/0x10c
[107944.207133]  [] ? do_sys_open+0x55/0xfc
[107944.207137]  [] ? system_call_fastpath+0x16/0x1b
[107944.207139] Code: 83 c3 08 48 83 3b 00 eb ec 48 83 fd 10 0f 86 89 00 00 00 
48 89 ef e8 b9 e8 ff ff 48 89 c7 48 8b 00 84 c0 78 13 66 a9 00 c0 75 04 <0f> 0b 
eb fe 5b 5d 41 5c e9 38 54 fd ff 48 8b 4c 24 18 4c 8b 4f 
[107944.207171] RIP  [] kfree+0x55/0xcb
[107944.207176]  RSP 
[107944.207193] ---[ end trace 6c2b060670efb8dc ]---
[177673.044881] general protection fault:  [#2] SMP 
[177673.04488

Bug#693495: RFS: wmtime/1.0b2-13 2012-11-20 13:32

[Bart Martens]

Hi Doug,

The file wmtime_1.0b2.orig.tar.gz at mentors is not identical to the one in
Debian.  What is debian/0001-Packaging-for-Debian.patch for ? The changelog
entry of 1.0b2-13 "Rebuilding source package correctly" is not useful if you
didn't change the source package.  The homepage in the "Homepage" field is not
useful since it states that http://packages.qa.debian.org/w/wmtime.html is the
(home) website, and the version available for download is older than the newest
already in Debian.  I suggest to not use this website in the "Homepage" field,
and also not in debian/watch.  Using 7 in debian/compat is quite low nowadays.
Some changes are not mentioned in debian/changelog, for example replacing
dh_clean by dh_prep.  Isn't it better to use a higher debian/compat number so
that debian/rules can be simplified instead ? I suggest to add the fixes for
bugs 639626 and 661843 in debian/patches.

Regards,

Bart Martens


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

Bug#694080: ITP: avw.lv2 -- collection of Voltage Controlled LV2 modules

[Alessio Treglia]

Package: wnpp
Severity: wishlist
Owner: Alessio Treglia 

* Package name: avw.lv2
  Version : 0.0.8
  Upstream Author : Aurélien Leblond 
* URL : https://sourceforge.net/projects/avwlv2/
* License : GPL, ISC
  Programming Lang: C++
  Description : collection of Voltage Controlled LV2 modules

avw.lv2 consists in a subset of the AMS internal modules
ported into LV2 plugins. It provides VCOs, LFOs, Filters
and other modules controlled using Voltage Controls.


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

Bug#692222: libtool upload for x32

[Kurt Roeckx]

On Fri, Nov 23, 2012 at 08:02:13AM -0800, Daniel Schepler wrote:
> Hi,
> Would it be OK for me to upload to experimental a version of libtool with the 
> patch I submitted for this bug?  I'd like to have a package version I can 
> tell 
> maintainers to install, when I start filing bug reports like "foobar: FTBFS 
> on 
> x32: needs libtool update".

I don't see a problem with uploading it to unstable.  Feel free to
upload to whereever you want.


Kurt


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

Bug#694081: DDPO: maintainer's name is taken from revoked GPG uid

[duck]

Package: qa.debian.org
Severity: normal


Coin,

Looking at:
  http://qa.debian.org/developer.php?login=d...@debian.org&comaint=yes
or
  
http://qa.debian.org/developer.php?login=d...@duckcorp.org&comaint=yes

I see:
  Packages overview for The Duck
  Maintainer: The Duck 
  Maintainer: The Duck 

The string "The Duck" comes from an *ancient* uid, revoked a long long 
time ago. Please filter revoked keys in order to have a proper realname, 
thanks.


Regards.


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

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

--
Marc Dequènes


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

Bug#694082: mountmedia: Please revert the change made to 0.20

[Brian Potkin]

Package: mountmedia
Version: 0.21
Severity: wishlist
Tags: d-i


This is by way of being a reminder about what was said in

   http://lists.debian.org/debian-boot/2012/08/msg00483.html

#684293 is marked as done by Ben Hutchings and D-I now has kernel version
3.2.0-4. If I delete the workaround lines added in 0,21 of mountmedia
the discovery and installation of firmware proceeds as one would expect.

Regards,

Brian.


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

Bug#694083: Please install socket6 documentation as a manpage

[Ian Jackson]

Package: libsocket6-perl
Version: 0.23-1
Severity: wishlist

chiark:~> man socket6
No manual entry for socket6
chiark:~> perldoc Socket6
Socket6(3)User Contributed Perl Documentation Socket6(3)


Thanks,
Ian.


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