Bug#657416: xinit: startx does not start window manager

[Adrian Kieß]

Der Julien,

I'm sorry for this false bug report. I have a somewhat complex .xinitrc and
the behaviour of gnome-settings-daemon changed with the release of GNOME
3.0 so i had to background it and that fixed it.

Please excuse the inconvenience.

You can delete this bug report.

Sincerely,

Adrian Kiess

On Thu, Jan 26, 2012 at 9:03 PM, Julien Cristau  wrote:

> On Thu, Jan 26, 2012 at 05:30:28 +0100, root wrote:
>
> > Package: xinit
> > Version: 1.3.1-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > startx does not start the window manager in debian/testing. It boots to
> the default background image and then hangs. Same sign when starting System
> Session through GDM.
> > Selecting GNOME or KDE session through GDM though works fine.
> >
> Please attach:
> - ~/.xinitrc
> - ~/.xsessionrc
> - ~/.xsession
> - ~/.xsession-errors
>
> And the full output from startx.
>
> Cheers,
> Julien
>



-- 
Adrian Immanuel Kieß (adrian at immanuelK.net)

Bug#657076: Updating and maintaining barry in Debian / Ubuntu

[Chris Frey]

On Fri, Jan 27, 2012 at 10:20:10AM +0100, intrigeri wrote:
> I don't understand very well what you are expecting from the
> Debian maintainer. Be them anyone else or (soon?) yoursef, what they
> must put in debian/changelog is:

Oh, I know the changelog must be updated, but some maintainers have
the opinion that upstream should not have a debian/ directory.
So when they do, there's conflicts.

If the Debian maintainer wants to keep it up to date, I'm happy to let
him, since my main changelog is in the git commit fields anyway.  I don't
usually get patches to my repo for the debian/ directory, so I ended up
trying to keep changes to debian/ minimal, so that the diffs for downstream
would be smaller.

Of course, if I'm the maintainer, I'll have to keep it more up to date
than I have been.


>   * use git-dch to get intermediary snapshots versions (this will give
> you something like 0.18.0-1~1.gbp9cb656, 0.18.0-1~2.gbp646619 and
> so on) that won't conflict between themselves or with the official
> Debian ones, and that will provide sane upgrade paths.

Cool... I may need to look into this.

Thanks,
- Chris




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

Bug#657697: [debian/debian-sid] Remove suhosin patch from description (Closes: #657697)

[Ondřej Surý]

tag 657697 pending
thanks

Date: Sat Jan 28 08:39:25 2012 +0100
Author: Ondřej Surý 
Commit ID: e66d14fdb85c02e16936ea98a54940acf6073ed7
Commit URL: 
http://git.debian.org/?p=pkg-php/php.git;a=commitdiff;h=e66d14fdb85c02e16936ea98a54940acf6073ed7
Patch URL: 
http://git.debian.org/?p=pkg-php/php.git;a=commitdiff_plain;h=e66d14fdb85c02e16936ea98a54940acf6073ed7

Remove suhosin patch from description (Closes: #657697)

  



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

Bug#657691: [debian/debian-sid] Re-enable firebird extension build on armhf and powerspe (Closes: #657691)

[Ondřej Surý]

tag 657691 pending
thanks

Date: Sat Jan 28 08:50:39 2012 +0100
Author: Ondřej Surý 
Commit ID: 006e95de02e8fb90ea9cbdf25c6604de6eb211b3
Commit URL: 
http://git.debian.org/?p=pkg-php/php.git;a=commitdiff;h=006e95de02e8fb90ea9cbdf25c6604de6eb211b3
Patch URL: 
http://git.debian.org/?p=pkg-php/php.git;a=commitdiff_plain;h=006e95de02e8fb90ea9cbdf25c6604de6eb211b3

Re-enable firebird extension build on armhf and powerspe (Closes: #657691)

  



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

Bug#657707: [initramfs-tools] modules for initrd are not stripped

[Michał Mirosław]

Package: initramfs-tools
Version: 0.99
Severity: normal

--- Please enter the report below this line. ---

Please add an option (possibly defaulted to on) to strip kernel modules and 
binaries put in initrd. When using kernel with debugging enables the 
unstripped modules are available in /lib/modules. Unneeded copy of the symbols 
in initrd image take over 80% of its size.

-rw-r--r-- 1 root root  5112330 Jan 17 23:50 initrd.img-3.2.1mq+ (stripped 
modules)
-rw-r--r-- 1 root root 32283567 Jan 28 08:06 initrd.img-3.2.2mq+ (unstripped 
modules)

(rebase from 3.2.1 to 3.2.2 is insignificant).

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.2.1mq+

Debian Release: wheezy/sid
  500 testing security.debian.org 
  500 testing ftp.uni-kl.de 
  500 testing ftp.pl.debian.org 
  500 stable  security.debian.org 
  500 stable  ftp.pl.debian.org 
  500 stable  deb.opera.com 

--- Package information. ---
Depends  (Version) | Installed
==-+-=
klibc-utils   (>= 1.5.9-1) | 1.5.25-1.1
cpio   | 2.11-7
module-init-tools  | 3.16-1
udev  (>= 0.086-1) | 175-3
findutils  (>= 4.2.24) | 4.4.2-4


Recommends (Version) | Installed
-+-===
busybox   (>= 1:1.01-3)  | 1:1.19.3-5
 OR busybox-initramfs| 


Suggests (Version) | Installed
==-+-===
bash-completion| 1:1.99-3



--- Output from package bug script ---
-- initramfs sizes
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.1mq+ root=/dev/mapper/rabbit-root ro 
libata.ignore_hpa=1 disable_mtrr_cleanup

-- /proc/filesystems
ext4
ext2
fuseblk

-- lsmod
Module  Size  Used by
cpufreq_powersave  12454  0 
bnep   17567  2 
autofs431688  2 
cpufreq_userspace  12576  0 
cpufreq_stats  12907  0 
rfcomm 45914  14 
cpufreq_conservative13147  0 
snd_hrtimer12604  1 
pci_stub   12429  1 
vboxpci19021  0 
vboxnetadp 13155  0 
vboxnetflt 23571  0 
vboxdrv   185832  3 vboxpci,vboxnetadp,vboxnetflt
binfmt_misc12957  1 
deflate12551  0 
zlib_deflate   25600  1 deflate
ctr12979  0 
twofish_generic16569  0 
twofish_x86_64_3way25167  0 
twofish_x86_64 12501  1 twofish_x86_64_3way
twofish_common 20505  3 
twofish_generic,twofish_x86_64_3way,twofish_x86_64
camellia   29068  0 
serpent29015  0 
blowfish_generic   12464  0 
blowfish_x86_6421201  0 
blowfish_common16447  2 blowfish_generic,blowfish_x86_64
cast5  24829  0 
des_generic20851  0 
xcbc   12709  0 
rmd160 16640  0 
sha512_generic 12625  0 
sha1_ssse3 16950  0 
sha1_generic   12539  1 sha1_ssse3
hmac   12835  0 
crypto_null12732  0 
af_key 31759  0 
fuse   61893  1 
nfsd  211858  13 
nfs   252501  0 
lockd  67328  2 nfsd,nfs
auth_rpcgss37136  2 nfsd,nfs
nfs_acl12511  2 nfsd,nfs
sunrpc168861  19 nfsd,nfs,lockd,auth_rpcgss,nfs_acl
ext2   59194  1 
loop   22639  0 
firewire_sbp2  17993  0 
btusb  17462  2 
snd_hda_codec_hdmi 30824  1 
snd_hda_codec_realtek45973  1 
pl2303 17262  0 
ftdi_sio   38270  0 
snd_emu10k1_synth  13016  0 
snd_emux_synth 28917  1 snd_emu10k1_synth
snd_seq_virmidi13175  1 snd_emux_synth
snd_seq_midi_emul  12770  1 snd_emux_synth
snd_emu10k1   128039  3 snd_emu10k1_synth
snd_ac97_codec106859  1 snd_emu10k1
ac97_bus   12510  1 snd_ac97_codec
snd_hda_intel  26305  4 
snd_hda_codec  68801  3 
snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
usbserial  32061  2 pl2303,ftdi_sio
i915  355716  2 
ath3k  12671  0 
snd_pcm_oss36899  0 
bluetooth 164414  24 bnep,rfcomm,btusb,ath3k
snd_mixer_oss  17881  1 snd_pcm_oss
snd_pcm63678  7 
snd_hda_codec_hdmi,snd_emu10k1,snd_ac97_codec,snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_util_mem   12704  2 snd_emux_synth,snd_emu10k1
snd_hwdep  13150  3 snd_emux_synth,snd_emu10k1,snd_hda_codec
snd_seq_midi   12848  0 
snd_rawmidi22984  3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi
snd_seq_midi_event 13316  2 snd_seq_virmidi,snd_seq_midi
snd_seq45015  6 
snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emu

Bug#648890: [xul-ext-firetray] Incompatible with Icedove

[Sascha Girrulat]

Package: xul-ext-firetray
Version: 0.3.1-3
Severity: important

The possible reason for the firetray compatibility problem between the
icedove/iceweasel version is a build against xulrunner-dev x.x
and icedove-dev(3.1.16) so we get a lib for both. The icedove package
brings an own "xulrunner-dev" with it. But for this there is some work
to do. I will do this asap.

Cheers
Sascha



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

Bug#657679: Minor typo in debconf template

[Christian PERRIER]

Quoting Francesca Ciceri (madame...@debian.org):
> Package: namazu2
> Severity: minor
> 
> 
> Hi,
> 
> while translating it into Italian, I've found a little typo in namazu2
> debconf template:
> 
> #: ../templates:1001
> msgid ""
> "Namazu package will be installed in /usr/lib/cgi-bin/namazu.cgi by
> default. "
> "But for VirtualHost, you may also need copy the cgi scripts to another "
> "location. The cgi will be copied automaticaly on upgrade or
> installation."
> 
> s/automaticaly/automatically/


To maintainer: fixing this and only this will fuzzy all translations
in debian/po.

Indeed, those have to be unfuzzied *before* applying the patch (or
before running "debconf-updatepo", or before building the package):

for i in debian/*po ; do sed -i 's/automaticaly/automatically/g' $i ; done

I attached a full tarball of the resulting debian/po directory.




namazu-po.tar.gz
Description: Binary data


signature.asc
Description: Digital signature

Bug#657706: texworks: Syntax Coloring not working

[Douglas F. Calvert]

Package: texworks
Version: 0.5~svn952-1
Severity: normal


Hello,
 I have texworks configured to do syntax coloring however my .tex files are all 
black text on white background. 

I am running texworks under xfce if it makes a difference. 

I apologize that I can not provide more information. Please let me know what 
else you need to know...



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

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

Versions of packages texworks depends on:
ii  libc6   2.13-24
ii  libgcc1 1:4.6.2-12
ii  libhunspell-1.3-0   1.3.2-4
ii  libpoppler-qt4-30.16.7-2+b1
ii  libqt4-dbus 4:4.7.4-2
ii  libqt4-script   4:4.7.4-2
ii  libqt4-scripttools  4:4.7.4-2
ii  libqt4-xml  4:4.7.4-2
ii  libqtcore4  4:4.7.4-2
ii  libqtgui4   4:4.7.4-2
ii  libstdc++6  4.6.2-12
ii  zlib1g  1:1.2.3.4.dfsg-3

Versions of packages texworks recommends:
ii  texlive-local [texlive-latex-base]  2011-1~1
ii  texworks-help-en0.5~svn952-1

Versions of packages texworks suggests:
ii  texlive-local [texlive-xetex]  2011-1~1
ii  texworks-scripting-lua 0.5~svn952-1
ii  texworks-scripting-python  0.5~svn952-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#657646: Update alternative priority for surf is too high

[Vasudev Kamath]

>>I grepped through the lintian laboratory looking for all browser 
>>registering x-www-browser alternative. Here are the results: 
>>
>>netsurf 100
>>konqueror   100
>>epiphany-browser85
>>iceape  80
>>iceweasel   70
>>links2  69
>>surf50
>>midori  50
>>dillo   50
>>rekonq  40
>>chromium-browser40
>>chimera230
>>conkeror20
>>uzbl10
>>luakit  10
>>
>>Priority 50 for this browser doesn't look completely crazy: there are 
>>other niche browser with equal or even higher priority. The only 
>>"mainstream" browser with lower priority is Chromium. Perhaps Chromium 
>>priority should be bumped instead.

>>Thoughts? See also bug #630390.

Yes you are right! I'm surprised to see some weird browsers getting
higher priority than actually used browsers! And chromium at 40!! So
what do you suggest? Shall I reduce the alternative to 30 or leave as
is?

Best Regards
-- 
Vasudev Kamath
http://blog.copyninja.info
http://identi.ca/vasudev
vasu...@joindiaspora.com (Ostatus)


signature.asc
Description: Digital signature

Bug#636669: Fixed version is ready in mentors

[Hideki Yamane]

Hi,

 Updated version is already prepared by maintainer in mentors, it fixes 
 this issue. See http://mentors.debian.net/package/notify-osd

 It seems to be good shape, however, is there any reason not to upload 
 to repository? 

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane



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

Bug#655151: No module named _snack

[Curtis Maloney]

Can confirm that Kris' change gives me a usable module.

--
Curtis



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

Bug#657705: cacti: [INTL:ru] Russian debconf templates translation update

[Yuri Kozlov]

Package: cacti
Version: 0.8.7g-3
Severity: wishlist
Tags: l10n patch


Russian debconf templates translation update is attached.

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

Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
# translation of ru.po to Russian
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the cacti package.
#
# Yuri Kozlov , 2009, 2011, 2012.
msgid ""
msgstr ""
"Project-Id-Version: cacti 0.8.7g-3\n"
"Report-Msgid-Bugs-To: ca...@packages.debian.org\n"
"POT-Creation-Date: 2012-01-25 07:09+0100\n"
"PO-Revision-Date: 2012-01-28 09:35+0400\n"
"Last-Translator: Yuri Kozlov \n"
"Language-Team: Russian \n"
"Language: ru\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 1.0\n"
"Plural-Forms:  nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && "
"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"

#. Type: select
#. Choices
#: ../cacti.templates:2001
msgid "Apache2"
msgstr "Apache2"

#. Type: select
#. Choices
#: ../cacti.templates:2001
msgid "None"
msgstr "не настраивать"

#. Type: select
#. Description
#: ../cacti.templates:2002
#| msgid "Webserver type"
msgid "Web server:"
msgstr "Веб-сервер:"

#. Type: select
#. Description
#: ../cacti.templates:2002
#| msgid ""
#| "Please select the webserver type for which cacti should be automatically "
#| "configured."
msgid ""
"Please select the web server for which Cacti should be automatically "
"configured."
msgstr ""
"Выберите веб-сервер, который нужно автоматически настроить для запуска Cacti."

#. Type: select
#. Description
#: ../cacti.templates:2002
#| msgid ""
#| "Select \"None\" if you would like to configure your webserver by hand."
msgid "Select \"None\" if you would like to configure the web server manually."
msgstr "Выберите «не настраивать», если хотите настроить веб-сервер вручную."

#~ msgid "Which kind of web server should be used by cacti?"
#~ msgstr "Тип используемого cacti веб-сервера"

#~ msgid "Apache, Apache-SSL, Apache2, All, None"
#~ msgstr "Apache, Apache-SSL, Apache2, все, ни одного"

Bug#657678: ITP: simplelxc -- Minimalist package to create LXC guests and then manage them simply.

[Daniel Baumann]

On 01/27/2012 11:15 PM, Bekir Dogan wrote:
> Main objective is to make testing of any program easy on personal computers
> (for now it works only for Debian systems) without losing time for these:
> * does not require to manually configure networking on host system,
> * does not require to manually create template,
> * does not require to manually determining IP addresses,
> * does not require to manually configuring any other parameters needed.
> 
> Just install simplelxc, create a guest and go.

i would rather much prefere if those little bits would be incorporated
into lxc-debconf in lxc itself. there's only minimal effort needed, as
lxc-debconf already determines all the defaults anyway and just needs
the one or other update to determine them better.

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



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

Bug#634537: Open RC bug in gtkterm

[Hideki Yamane]

tags 634537 pending
thanks

Hi,

>  As Zach suggested, newer upstream version (0.99.7-rc1) is built fine.
>  If Sebastien wouldn't upload it, I want to upload it as NMU.

 I've prepared it as 
http://www.mithril-linux.org/~henrich/debian/package/temp/gtkterm_0.99.7~rc1-0.1.dsc

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane



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

Bug#656792: linux-image-3.2.0-1-amd64: kernel does not boot since 3.1 under a (strange) Xen anymore

[Ben Hutchings]

On Sat, 2012-01-28 at 00:29 +0100, Christoph Anton Mitterer wrote:
> Hi.
> 
> Perhaps this helps. According to the ISP the exakt version of the dom0
> kernel is:
> 2.6.32.12-0.7.1.xs6.0.0.529.170661xen
> 
> Also they claim there is not Microsoft HyperV or so used at all.

But they probably enabled 'Viridian compatibility mode' which makes
XenServer look more like HyperV, probably to make Windows guests behave
btter.  Linux 3.1 now checks for Xen before HyperV, to avoid being
fooled by this.  That might be a problem if it causes the kernel to
detect different emulated devices.  (I don't know whether it could have
this effect.)

Which drivers are in the initramfs?  Does
/etc/initramfs-tools/initramfs.conf have MODULES=dep (which is
vulnerable to configuration changes) or MODULES=most (which is safer)?

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.


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

Bug#657428: RFS: surf -- simple web browser (QA upload)

[Vasudev Kamath]

On 22:40 Fri 27 Jan , Jakub Wilk wrote:
 
> For the record, the bug number is #657646.
> 
> As I commented there, I'm not convinced that reducing priority is
> necessary. That said, it won't do (much) harm either, so I don't
> really mind.
> 
> Please consider applying the attached patch, which fixes some minor
> whitespace issues.

Applied. Thanks for the patch :) (That reminds me I'm always bad at
cosmetics )

> I see you added patch header to debian/patches/X11.diff, which is
> great, but if it was meant to follow DEP-3:
> - "Last-Updated" should be spelled "Last-Update" and should use
> -MM-DD format.
> - You could add Bug-Debian field.
> 
> Oh, my remark about Last-Update(ed) also applies to
> dpkg-buildflags.patch. :)

So much for trying to write dep3 header without looking at DEP3 page
;). Fixed it and added Bug-Debian too.

New version is already uploaded to mentors. Thanks for the reviews

Best Regards
-- 
Vasudev Kamath


signature.asc
Description: Digital signature

Bug#657497: nfs-common: Exec permission denied

[dE .]

What about the server exports?



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

Bug#657704: [snowballz] snowballz is unable to start due to missing font

[Dean Evans]

Package: snowballz
Version: 0.9.5.1-2.1
Severity: serious

snowballz linked to the TSCu_Comic.ttf from the ttf-tamil-fonts package
which has since removed the TSCu* fonts from their package [0] causing
snowballz to refuse to start with the traceback below.

[0] 
http://packages.debian.org/changelogs/pool/main/t/ttf-indic-fonts/current/changelog#version1:0.5.13

 * Removed TSCu and TAMu family of fonts from package. These fonts use legacy
 encoding. (Closes: #428025, #441901)


TraceBack:

dean@sidspace:/usr/share/games/snowballz/data% snowballz
/usr/share/games/snowballz/font.py:3: UserWarning: 
***
The rabbyt.fonts module is deprecated and will be removed in a future
version of rabbyt.  I recommend using pyglet for font rendering.

If you still want to use pygame fonts, check out the ``pygame_font.py``
example included with rabbyt.
***

  import rabbyt.fonts
/usr/share/games/snowballz/font.py:3: UserWarning: 
The rabbyt.vertexarrays module is deprecated and will be removed in a
  future version of rabbyt.

  import rabbyt.fonts
Traceback (most recent call last):
  File "snowballz.py", line 614, in 
data.load_font()
  File "/usr/share/games/snowballz/data.py", line 431, in load_font
chat_font = font.Font("data/TSCu_Comic.ttf", 20)
  File "/usr/share/games/snowballz/font.py", line 14, in __init__
f = pygame.font.Font(facename, pixel_height)
IOError: unable to read font filename


--- System information. ---
Architecture: amd64
Kernel:   Linux 3.1.0-1-amd64

Debian Release: wheezy/sid
  500 unstableftp.au.debian.org 
  500 stable  deb.opera.com 

--- Package information. ---
Depends  (Version) | Installed
==-+-===
python(>= 2.4) | 2.7.2-10
python-pygame  | 1.9.1release+dfsg-5
python-opengl  | 3.0.1~b2-1
python-numpy   | 1:1.5.1-3
python-imaging | 1.1.7-4
python-rabbyt  | 0.8.1-1+b2
ttf-tamil-fonts| 1:0.5.14


Package's Recommends field is empty.

Package's Suggests field is empty.







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

Bug#657702: texworks: Cannot use hunspell dictionaries for spellcheck

[Hongzheng Wang]

Package: texworks
Version: 0.5~svn952-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
   My texworks cannot perform spell check if hunspell dictionaries are
   installed.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   Install hunspell dictionaries (e.g., hunspell-en-us) and observe
   whether texworks can perform spekk check.
   In contrast, install myspell dictionaries (e.g., myspell-en-us) and
   repeat the experiment.
   * What was the outcome of this action?
   Only myspell dictionaries can be used.
   * What outcome did you expect instead?
   Should myspell dictionaries be equivalent to hunspell dictionaries in
   function in this scenario?


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

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

Versions of packages texworks depends on:
ii  libc6   2.13-24
ii  libgcc1 1:4.6.2-12
ii  libhunspell-1.3-0   1.3.2-4
ii  libpoppler-qt4-30.16.7-2+b1
ii  libqt4-dbus 4:4.8.0-1
ii  libqt4-script   4:4.8.0-1
ii  libqt4-scripttools  4:4.8.0-1
ii  libqt4-xml  4:4.8.0-1
ii  libqtcore4  4:4.8.0-1
ii  libqtgui4   4:4.8.0-1
ii  libstdc++6  4.6.2-12
ii  zlib1g  1:1.2.5.dfsg-1

Versions of packages texworks recommends:
ii  texlive-latex-base  2009-15
ii  texworks-help-en0.5~svn952-1

Versions of packages texworks suggests:
pn  texlive-xetex   2009-15
pn  texworks-scripting-lua 
pn  texworks-scripting-python  

-- 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#657092: Upstream Bug Report

[Soren Stoutner]

A bug report has been opened upstream at 
http://trac.roundcube.net/ticket/1488332

-- 
Soren Stoutner
Small Business Tech Solutions
623-262-6169
so...@smallbusinesstech.net
www.smallbusinesstech.net


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

Bug#656947: __size_t issue affecting soundcard.h remains

[Steven Chamberlain]

Hi,

On 28/01/12 03:35, Steven Chamberlain wrote:
> $ g++-4.6 /usr/include/sys/soundcard.h
> In file included from /usr/include/machine/_types.h:8:0,
>  from /usr/include/sys/_types.h:33,
>  from /usr/include/machine-i386/endian.h:37,
>  from /usr/include/machine/endian.h:8,
>  from /usr/include/sys/soundcard.h:110:
> /usr/include/machine-i386/_types.h:94:9: error: declaration does not
> declare anything [-fpermissive]

> $ g++ /usr/include/sys/soundcard.h -E | grep segsz -C 2
> typedef __int32_t __ptrdiff_t;
> typedef __int32_t __register_t;
> typedef __int32_t __segsz_t;
> typedef __uint32_t ;
> typedef __int32_t __ssize_t;

Found it!

I did 'cpp -dD /usr/include/sys/soundcard.h' which led me to this:

/usr/lib/gcc/i486-kfreebsd-gnu/4.6/include/stddef.h:
> 203 #if defined (__FreeBSD__) && (__FreeBSD__ >= 5)
> 204 /* __size_t is a typedef on FreeBSD 5!, must not trash it. */
> 205 #else
> 206 #define __size_t
> 207 #endif

Not sure of the right way to fix it so I've CC'd the Debian GCC Maintainers.

Maybe just like this?  It fixes the issue for me.

--- stddef.h.orig   2012-01-28 04:13:06.0 +
+++ stddef.h2012-01-28 04:14:05.0 +
@@ -200,7 +200,7 @@
 #define ___int_size_t_h
 #define _GCC_SIZE_T
 #define _SIZET_
-#if defined (__FreeBSD__) && (__FreeBSD__ >= 5)
+#if defined (__FreeBSD__) && (__FreeBSD__ >= 5) || (__FreeBSD_kernel__)
 /* __size_t is a typedef on FreeBSD 5!, must not trash it. */
 #else
 #define __size_t


While here, I noticed similar stuff in the same file and wondered if it
may have been causing other problems on kFreeBSD, such as:

> /* On FreeBSD 5, machine/ansi.h does not exist anymore... */
> #if defined (__FreeBSD__) && (__FreeBSD__ >= 5)
> #include 
> #endif

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



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

Bug#653501: libfreenect : pull request and issues raised

[Yaroslav Halchenko]

just 1 minor addition toward better python-freenect
https://github.com/yarikoptic/libfreenect/tree/debian-0.1.2

ideally we could also update pre-generated freenect.c and patch on older
systems to not re-cython it... but as far as noone complaints -- I am
just ok with how it is now

so -- make up your mind about outstanding high level problems and then
we could upload

-- 
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic



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

Bug#657422: How can I replace the downloader of aptitude with another downloader such as axel?

[Frank]

? 2012?01?28? 00:08, Julian Andres Klode ??:

On Fri, Jan 27, 2012 at 10:58:52AM +0800, Frank wrote:

Thanks. In debian, aptitude is strongly suggested.

Who told you this? Given that aptitude was/is in a fairly
bad state, and only now seems to recover with a new
maintainer team, I don't see how aptitude is strongly
suggested anywhere.



In Debian Reference, it makes a comparison between apt-get / apt-cache 
and aptitude. It tells about the advantage of aptitude. For example, it 
says '|aptitude| is most suitable for the *daily interactive package 
management* such as inspecting installed packages and searching 
available packages.'


And, another reason is that in most pages of Debian Reference, it uses 
aptitude instead of apt-get / apt-cache.

Bug#656947: __size_t issue affecting soundcard.h remains

[Steven Chamberlain]

Hi,

I think something is still wrong with soundcard.h or the __size_t
definition, because the GNU C++ compiler does not seem to like it:

$ g++-4.6 /usr/include/sys/soundcard.h
In file included from /usr/include/machine/_types.h:8:0,
 from /usr/include/sys/_types.h:33,
 from /usr/include/machine-i386/endian.h:37,
 from /usr/include/machine/endian.h:8,
 from /usr/include/sys/soundcard.h:110:
/usr/include/machine-i386/_types.h:94:9: error: declaration does not
declare anything [-fpermissive]

/usr/include/machine-i386/_types.h:94:
typedef __uint32_t  __size_t;   /* sizeof() */

$ g++ /usr/include/sys/soundcard.h -E | grep segsz -C 2
typedef __int32_t __ptrdiff_t;
typedef __int32_t __register_t;
typedef __int32_t __segsz_t;
typedef __uint32_t ;
typedef __int32_t __ssize_t;


I've observed this bug causing configure to fail during an attempted
build of hamfax;  its conftest is attached.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org
/* confdefs.h */
#define PACKAGE_NAME "hamfax"
#define PACKAGE_TARNAME "hamfax"
#define PACKAGE_VERSION "0.8.1"
#define PACKAGE_STRING "hamfax 0.8.1"
#define PACKAGE_BUGREPORT "cschm...@users.sourceforge.net"
#define PACKAGE_URL ""
#define PACKAGE "hamfax"
#define VERSION "0.8.1"
#define USE_FILE 1
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
/* end confdefs.h.  */
#include 
#ifdef HAVE_SYS_TYPES_H
# include 
#endif
#ifdef HAVE_SYS_STAT_H
# include 
#endif
#ifdef STDC_HEADERS
# include 
# include 
#else
# ifdef HAVE_STDLIB_H
#  include 
# endif
#endif
#ifdef HAVE_STRING_H
# if !defined STDC_HEADERS && defined HAVE_MEMORY_H
#  include 
# endif
# include 
#endif
#ifdef HAVE_STRINGS_H
# include 
#endif
#ifdef HAVE_INTTYPES_H
# include 
#endif
#ifdef HAVE_STDINT_H
# include 
#endif
#ifdef HAVE_UNISTD_H
# include 
#endif
#include 
/* g++ -E  conftest.cpp */

Bug#653501: libfreenect : pull request and issues raised

[Yaroslav Halchenko]

my .1 cents on you questions

On Fri, 27 Jan 2012, Nicolas Bourdaud wrote:
>   The udev rules were broken, so I needed to update them, especially, the
> permission of "all" is updated by another udev rule that I have not yet
> identified but anyways, I am not sure it was a good practice to grant
> access to any user.

yeap -- doesn't sound ideal ;-)

> Instead I set the group to plugdev, so that any user
> of plugdev (normal desktop user are usually) can access and this is not
> altered by any other rule. My question is now: do you think it make
> sense? If so does the plugdev group make sense as well? If you don't
> know, I can ask on mentor mailing list to have the opinion of the community.

'plugdev' group makes total sense to me -- even more than
allocating a new group solely for kinect -- but sure thing do not
hesitate to seek further advice on -mentors or even -dev mailing list.

> ...
> (the one that entered in testing today). Now I have 3 solutions but none
> are good:
> - solution 1: installing libfreenect0.1 package installs a modprobe rule
> >...<
> - solution 2: write a patch to libfreenect which detaches the kernel
> >...<
> - solution 3: Status quo. We don't do anything, just inform users in the
> >...<

Arne's suggestion is right to the point imho.  Lazy guy like me would
have just reverted to 3. in one form or another ;-)  suggesting admin to
decide via debconf (with 'high' priority for the question) sounds the
best but would require a bit more work, especially since i18n will be on
your back quite soon -- get ready to incorporate their patches ;-)

Cheers,

-- 
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic



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

Bug#657701: ITP: python-mongokit -- structured schema and validation layer on top of the pymongo driver

[Clint Byrum]

Package: wnpp
Severity: wishlist
Owner: Clint Byrum 

* Package name: python-mongokit
  Version : 0.7.2
  Upstream Author :   Nicolas Clairon (Namlook) 
* URL : http://namlook.github.com/mongokit/
* License : BSD
  Programming Lang: Python
  Description : structured schema and validation layer on top of the 
pymongo driver

 MongoDB is a schema-less document oriented database. It has a lot of
 drivers for many langages (python, ruby, perl, java, php...).
 .
 MongoKit is a python module that brings structured schema and validation
 layer on top of the pymongo driver. It has been written to be as simple
 and light as possible with the KISS and DRY principles in mind.
 .
 Features
 .
 * schema validation (wich use simple python type for the declaration)
 * schema less feature
 * doted notation
 * nested and complex schema declaration
 * untyped field support
 * required fields validation
 * default values
 * custom validators
 * cross database document reference
 * random query support (which returns a random document from the database)
 * inheritance and polymorphisme support
 * versionized document support (in beta stage)
 * partial auth support (it brings a simple User model)
 * operator for validation (currently : OR, NOT and IS)
 * simple web framework integration
 * import/export to json
 * i18n support
 * GridFS support
 * document migration support



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

Bug#650976: bug#10552: Emacs build failure on GNU/Hurd i386 caused by signal

[Chong Yidong]

Rob Browning  writes:

> (If possible, please preserve the 650976-forwarded address in any replies.)
>
> We've had a report of a build failure on GNU/Hurd when a long write is
> interrupted by a signal (since Emacs hasn't set SA_RESTART).
>
> One proposed solution is to add
>
>   #define POSIX_SIGNALS 1
>
> to src/s/gnu.h.
>
> See: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650976

Thanks.  Committed to trunk.



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

Bug#657700: sweethome3d: Export to SVG doesn't work

[Gabriele Giacone]

Package: sweethome3d
Version: 3.4+dfsg-1
Severity: normal

To reproduce, menu "Plan - Export to SVG format". It produces a broken SVG
image.

java.lang.ExceptionInInitializerError
at
org.freehep.graphicsio.svg.SVGGraphics2D.writeImage(SVGGraphics2D.java:569)
at
org.freehep.graphicsio.AbstractVectorGraphicsIO.drawImage(AbstractVectorGraphicsIO.java:482)
at
org.freehep.graphicsio.AbstractVectorGraphicsIO.drawImage(AbstractVectorGraphicsIO.java:371)
at org.freehep.graphics2d.VectorGraphics.fill(VectorGraphics.java:287)
at org.freehep.graphicsio.svg.SVGGraphics2D.fill(SVGGraphics2D.java:467)
at com.eteks.sweethome3d.swing.PlanComponent.fillAndDrawArea(Unknown
Source)
at com.eteks.sweethome3d.swing.PlanComponent.paintWalls(Unknown Source)
at com.eteks.sweethome3d.swing.PlanComponent.paintHomeItems(Unknown
Source)
at com.eteks.sweethome3d.swing.PlanComponent.paintContent(Unknown
Source)
at com.eteks.sweethome3d.swing.PlanComponent.access$1800(Unknown Source)
at
com.eteks.sweethome3d.swing.PlanComponent$SVGSupport.exportToSVG(Unknown Source)
at com.eteks.sweethome3d.swing.PlanComponent.exportToSVG(Unknown Source)
at com.eteks.sweethome3d.swing.HomePane.exportToSVG(Unknown Source)
at com.eteks.sweethome3d.viewcontroller.HomeController$34.call(Unknown
Source)
at com.eteks.sweethome3d.viewcontroller.HomeController$34.call(Unknown
Source)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
com.eteks.sweethome3d.viewcontroller.ThreadedTaskController$1.run(Unknown
Source)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.NullPointerException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.freehep.graphics2d.PixelGraphics2D.(PixelGraphics2D.java:101)
... 24 more


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

Kernel: Linux 3.2.0-1-amd64 (SMP w/3 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 sweethome3d depends on:
ii  icedtea-netx-common 1.1.4-1
ii  java-wrappers   0.1.24
ii  java3ds-fileloader  1.2+dfsg-1
ii  libbatik-java   1.7-8
ii  libfreehep-graphicsio-svg-java  2.1.1-3
ii  libitext-java   2.1.7-2
ii  libjava3d-java  1.5.2+dfsg-5
ii  libsunflow-java 0.07.2.svn396+dfsg-9
ii  openjdk-6-jre   6b24~pre2-1

sweethome3d recommends no packages.

sweethome3d 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#657689: e1000e Detected Hardware Unit Hang:

[Ben Hutchings]

On Sat, 2012-01-28 at 01:53 +0100, ubik pl wrote:
> Package: linux-2.6
> Version: 2.6.32-38
> Linux version 2.6.32-5-xen-amd64
> RAM 8GB
> 
> Bug seems the same as #518182 and occurs on high traffic load.
> System automatically recovered after aprox. 50
> minutes([1782786.812335] e1000e :00:19.0: eth0: Reset adapter)
[...]

Why do say 50 minutes?  These messages cover a span of only 7 seconds.
Were they repeated?

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.


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

Bug#657687: dspam: FTBFS(kfreebsd): configure: error: Unable to determine how to compile with pthreads

[Cyril Brulebois]

Christoph Egger  (28/01/2012):
> Package: src:dspam
> Version: 3.10.1+dfsg-3+b1
> Severity: serious
> Tags: sid wheezy
> User: debian-...@lists.debian.org
> Usertags: kfreebsd
> X-Debbugs-Cc: debian-...@lists.debian.org
> Justification: fails to build from source (but built successfully in the past)
> 
> checking how you like your pthreads... unknown
> configure: error: Unable to determine how to compile with pthreads
> 
> Full build log at
> https://buildd.debian.org/status/fetch.php?pkg=dspam&arch=kfreebsd-amd64&ver=3.10.1%2Bdfsg-3%2Bb1&stamp=1327287208

For reference:
  lists.debian.org/201201240019.45717.robo...@celest.fr

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#656562: some __aligned issues remain

[Steven Chamberlain]

On 21/01/12 00:36, Debian Bug Tracking System wrote:
> In file included from ../../../tools/ipod-usb.c:1:0:
> /usr/include/libusb.h:254:43: error: expected '=', ',', ';', 'asm' or 
> '__attribute__' before '__aligned'

Hi,

This problem still affects a few other header files, where the parameter
to __aligned was a macro and not a bare number, e.g.:

> /usr/include/dev/usb/usb_device.h:} __aligned(USB_HOST_ALIGN);
> /usr/include/dev/usb/usb_device.h:} __aligned(USB_HOST_ALIGN);
> /usr/include/netinet/in_pcb.h:} __aligned(CACHE_LINE_SIZE);
> /usr/include/sys/pcpu.h:} __aligned(CACHE_LINE_SIZE);
> /usr/include/vm/uma_int.h:#define UMA_ALIGN   __aligned(CACHE_LINE_SIZE)
> /usr/include/vm/vm_page.h:} __aligned(CACHE_LINE_SIZE);

Packages with build failures due to this so far:
* php5 --
https://buildd.debian.org/status/fetch.php?pkg=php5&arch=kfreebsd-i386&ver=5.3.9-3&stamp=1327716668
* zabbix --
https://buildd.debian.org/status/fetch.php?pkg=zabbix&arch=kfreebsd-i386&ver=1%3A1.8.10-1&stamp=1327712644
* cups --
https://buildd.debian.org/status/fetch.php?pkg=cups&arch=kfreebsd-i386&ver=1.5.0-15&stamp=1327718267

Please consider my attached diff for kfreebsd-kernel-headers.  The regex
\([0-9A-Z_]*\) covers these remaining cases.

Something more generic, like \([^)]*\?\) might seem better, but then it
would have wrongly modified this also:

./usr/include/osreldate.h:#define __aligned(x)
__attribute__((__aligned__(x)))

Thanks,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org
Index: debian/rules
===
--- debian/rules	(revision 4012)
+++ debian/rules	(working copy)
@@ -53,7 +53,7 @@
 		-e 's/#\s*ifndef\s*__GNUCLIKE_[A-Z_]\+\(\s\|$$\)/#if 0/g' \
 		\
 		-e 's/__packed\(\s\|;\)/ __attribute__((__packed__))\1/g' \
-		-e 's/__aligned(\([0-9]*\))/ __attribute__((aligned(\1)))/g' \
+		-e 's/__aligned(\([0-9A-Z_]*\))/ __attribute__((aligned(\1)))/g' \
 		-e 's/\(\s\|^\|(\)u_\(char\|int\|short\|long\)\(\s\)/\1unsigned \2\3/g' \
 		\
 		-e 's/defined\s*(\s*_SYS_CDEFS_H_\s*)/defined(_SYS_CDEFS_H)/g' \

Bug#653501: libfreenect : pull request and issues raised

[Yaroslav Halchenko]

On Sat, 28 Jan 2012, Nicolas Bourdaud wrote:
> >> > we might alternatively start libfreenect-maint team on alioth which
> >> > would be listed as the maintainer while we all stay in uploaders... what
> >> > you think?
> If everybody in the neurodebian project, we can stay in it, that what
> you prefer. I am not sure, it is wise to open a project on its own for
> one package but I might be wrong. What do you prefer.
ok -- let's make it
NeuroDebian Team 
;-)

> (off topic question: there is a neurodebian project on Alioth, and
> pkg-exppsy which has more people... which one should be used?)

sorry for the confusion -- originally we founded pkg-exppsy project,
which grew up into NeuroDebian.  Since repositories were setup etc under
pkg-exppsy -- we just kept it alive while
http://alioth.debian.org/projects/pkg-exppsy
says that it was superseeded by NeuroDebian.  I just found that
http://pkg-exppsy.alioth.debian.org/ still redirects to dated
http://wiki.debian.org/DebianSciencePsychology ... both now fixed to
point to NeuroDebian

so, you are welcome to join both if you wish, but since we use alioth
only for hosting our repositories, then pkg-exppsy should be sufficient
(for libfreenect anyways we might just keep using github straight)

-- 
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic



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

Bug#657699: lintian: check pkgconfig files for stray hardening flags

[Russ Allbery]

Package: lintian
Version: 2.5.4
Severity: wishlist

I modified a package today to enable hardening, and was surprised to
discover -Wl,-z,relro in the Libs field of the resulting *.pc file,
and -D_FORTIFY_SOURCE=2 in the Cflags field.  This obviously isn't
correct; the hardening flags aren't required to build clients of the
library.

I don't think that copying CPPFLAGS and LDFLAGS directly into the *.pc
file is the right thing to do upstream (and will be talking to them
about that), but it would be good to have a Lintian check for this as
well, since I suspect this is a mistake that more than one upstream
will make.

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

Kernel: Linux 3.1.0-1-686-pae (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 lintian depends on:
ii  binutils   2.22-4
ii  bzip2  1.0.6-1
ii  diffstat   1.55-2
ii  file   5.09-2
ii  gettext0.18.1.1-5
ii  intltool-debian0.35.0+20060710.1
ii  libapt-pkg-perl0.1.25+b1
ii  libclass-accessor-perl 0.34-1
ii  libclone-perl  0.31-1+b2
ii  libdpkg-perl   1.16.1.2
ii  libemail-valid-perl0.185-1
ii  libipc-run-perl0.90-1
ii  libparse-debianchangelog-perl  1.2.0-1
ii  libtimedate-perl   1.2000-1
ii  liburi-perl1.59-1
ii  locales2.13-24
ii  man-db 2.6.0.2-3
ii  patchutils 0.3.2-1.1
ii  perl [libdigest-sha-perl]  5.14.2-6
ii  unzip  6.0-5

lintian recommends no packages.

Versions of packages lintian suggests:
ii  binutils-multiarch 
ii  dpkg-dev   1.16.1.2
ii  libhtml-parser-perl3.69-1+b1
ii  libtext-template-perl  1.45-2
ii  man-db 2.6.0.2-3
ii  xz-utils   5.1.1alpha+20110809-3

-- 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#657698: php5: re-enable suhosin patch or add separate packages with suhosin patch enabled per default

[Christoph Anton Mitterer]

Package: php5
Version: 5.3.9-3
Severity: wishlist


Hi.

Having the suhosin patch enabled per default used to be a very good thing
and probably greatly increased security of PHP installations.

In this versions, it seems you've disabled the patch.

I don't know the reasons but I'm very sad about it.
Even though you've added that PHP5_SUHOSIN=no/yes option to the rules file
it would mean some effort for people to reactivate this (manually making
packages and so on).

Could you:
a) Just re-enable it per default (for security reasons); if some people have 
problems
with it, they should rather try to fix this upstream... or such people could 
manually
build their packages and disable suhosin in it.

b) Provide packages for both, which conflict each other, and provide the same 
names.
One could have e.g.
php5, php5-cgi, php5-cli, etc. => suhosin enabled
php5-nosuhosin, php5-cgi-nosuhosin, php5-cli-nosuhosin, etc. => suhosin disabled
That way, per default packages with suhosin enabled (which should be the sane 
default)
would get installed, but people have still the possibility to take the other 
packages
if they like; without any manual compilations.


Cheers,
Chris.



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

Bug#657697: php5: suhosin silently disabled

[Christoph Anton Mitterer]

Package: php5
Version: 5.3.9-3
Severity: important


Hi.

Actually this should be marked critical, as an important security feature
was apparently silently disabled.

a) The package descriptions still all claim, that suhosion patch would be 
enabled.

b) There should be NEWS.Debian entry about it's removal.


Cheers,
Chris.



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

Bug#657696: gnome-commander: opening smb share 'domain' field not works

[Andrey]

Package: gnome-commander
Version: 1.2.8.15-2
Severity: normal

Dear Maintainer,

When I opening win xp share in Active Directory enviroment field domain 
doesnt works correctly.

Works only combination domain\username in field username.


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

Kernel: Linux 3.1.0-1-amd64 (SMP w/8 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 gnome-commander depends on:
ii  gnome-commander-data  1.2.8.15-2
ii  libart-2.0-2  2.3.21-1
ii  libatk1.0-0   2.2.0-2
ii  libbonobo2-0  2.24.3-1
ii  libbonoboui2-02.24.3-1
ii  libc6 2.13-24
ii  libcairo2 1.10.2-6.2
ii  libexiv2-90.20-2.1
ii  libfontconfig12.8.0-3
ii  libfreetype6  2.4.8-1
ii  libgcc1   1:4.6.2-11
ii  libgconf2-4   2.32.4-1
ii  libgdk-pixbuf2.0-02.24.0-2
ii  libglib2.0-0  2.30.2-4
ii  libgnome2-0   2.32.1-2
ii  libgnomecanvas2-0 2.30.3-1
ii  libgnomeui-0  2.24.5-2
ii  libgnomevfs2-01:2.24.4-1
ii  libgtk2.0-0   2.24.8-3
ii  libice6   2:1.0.7-2
ii  liborbit2 1:2.14.19-0.1
ii  libpango1.0-0 1.29.4-2
ii  libpoppler13  0.16.7-2+b1
ii  libpopt0  1.16-3
ii  libpython2.7  2.7.2-8
ii  libsm62:1.2.0-2
ii  libssl1.0.0   1.0.0g-1
ii  libstdc++64.6.2-11
ii  libtag1c2a1.7-1
ii  python2.7.2-9
ii  python2.7 2.7.2-8
ii  zlib1g1:1.2.3.4.dfsg-3

gnome-commander recommends no packages.

Versions of packages gnome-commander suggests:
pn  libgnomevfs2-extra  1:2.24.4-1
pn  meld 

-- 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#657695: apt: gives up too easily when resolving Breaks of virtual packages

[Colin Watson]

Package: apt
Version: 0.8.16~exp9
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch precise

If a package Breaks a virtual package with many providers, and the
appropriate resolver action is to remove several of those providers,
then the resolver goes round one iteration of its master loop - which
has a hard limit of 10 iterations, so they are in short supply - per
provider.  This is not the case for Conflicts, where it deals with all
the providers in a single iteration of the master loop.

There seems no obvious reason for this discrepancy, and I think it was
an oversight when Breaks support was introduced in apt.

An example of a failed upgrade resolution due to this bug is here:

  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/922485

You can see it working its way through xserver-xorg-core's Breaks on
xserver-xorg-video-6 one package at a time and eventually running out of
iterations, when it would have succeeded if it had got round to
processing all the providers.

The following patch fixes this:

=== modified file 'apt-pkg/algorithms.cc'
--- apt-pkg/algorithms.cc   2011-11-10 15:56:21 +
+++ apt-pkg/algorithms.cc   2012-01-28 01:44:53 +
@@ -1098,8 +1098,7 @@ bool pkgProblemResolver::ResolveInternal
  LEnd->Dep = End;
  LEnd++;
  
- if (Start->Type != pkgCache::Dep::Conflicts &&
- Start->Type != pkgCache::Dep::Obsoletes)
+ if (Start.IsNegative() == false)
 break;
   }
}

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#657694: portmap: init script uses /lib/init/rw

[Francesco Potortì]

Package: portmap
Version: 6.0.0-3
Severity: normal

As the subject says: it should use /run instead, as noted in sysvinit
(2.88dsf-17) NEWS file.

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

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

Versions of packages portmap depends on:
ii  debconf [debconf-2.0]  1.5.41
ii  libc6  2.13-24
ii  libwrap0   7.6.q-22
ii  lsb-base   3.2-28

portmap recommends no packages.

portmap suggests no packages.



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

Bug#656348: iptables-persistent: fails to install in chroot

[Hideki Yamane]

tags 656348 patch
thanks

Hi,

 Just adding kmod would fix this issue, see attached patch.
 I tested it with piuparts and works fine.

 Thanks.


-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane
diff -Nru iptables-persistent-0.5.3/debian/changelog iptables-persistent-0.5.3+nmu1/debian/changelog
--- iptables-persistent-0.5.3/debian/changelog	2011-11-29 09:14:42.0 +0900
+++ iptables-persistent-0.5.3+nmu1/debian/changelog	2012-01-28 11:02:01.0 +0900
@@ -1,3 +1,12 @@
+iptables-persistent (0.5.3+nmu1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/control
+- add "Depends: kmod" to properly call modprobe in postinst
+  (Closes: #656348)
+
+ -- Hideki Yamane   Sat, 28 Jan 2012 11:00:31 +0900
+
 iptables-persistent (0.5.3) unstable; urgency=low
 
   * [09d9ae] Check for loaded modules in postinst (Closes: #637852)
diff -Nru iptables-persistent-0.5.3/debian/control iptables-persistent-0.5.3+nmu1/debian/control
--- iptables-persistent-0.5.3/debian/control	2011-11-29 09:14:42.0 +0900
+++ iptables-persistent-0.5.3+nmu1/debian/control	2012-01-28 11:00:28.0 +0900
@@ -9,7 +9,7 @@
 
 Package: iptables-persistent
 Architecture: all
-Depends: iptables, lsb-base, ${misc:Depends}
+Depends: iptables, lsb-base, ${misc:Depends}, kmod
 Description: boot-time loader for iptables rules
  This package provides a system startup script that restores iptables
  rules from a configuration file.

Bug#657693: vsftpd FTBFS on armhf (and maybe amd64)

[peter green]

package: vsftpd
version: 2.3.5-2
severity: important

vsftpd fails to build on armhf with the following error. This initially 
happened on the buildd

and I have also reproduced locally.

gcc -o vsftpd main.o utility.o prelogin.o ftpcmdio.o postlogin.o privsock.o 
tunables.o ftpdataio.o secbuf.o ls.o postprivparent.o logging.o str.o netstr.o 
sysstr.o strlist.o banner.o filestr.o parseconf.o secutil.o ascii.o 
oneprocess.o twoprocess.o privops.o standalone.o hash.o tcpwrap.o ipaddrparse.o 
access.o features.o readwrite.o opts.o ssl.o sslslave.o ptracesandbox.o 
ftppolicy.o sysutil.o sysdeputil.o  -lwrap -lpam -lssl -lcrypto -lcap -fPIE 
-pie -Wl,-z,relro -Wl,-z,now
/usr/bin/ld: utility.o: relocation R_ARM_THM_MOVW_ABS_NC against `a local 
symbol' can not be used when making a shared object; recompile with -fPIC
utility.o: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[2]: *** [vsftpd] Error 1


It also failed on the amd64 buildd in the same way but I was unable to 
reproduce that.


I think the problem is that you are passing -fPIE to the linker but not 
passing -fPIC

to the compiler but i'm not an expert on this.



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

Bug#401219: close 401219

[Stéphane Aulery]

Thunderbird/9.0.1

close 401219 2.07-6
stop

-

Hi,

After testing the procedure described the latest stable package, I see
that this bug has been fixed a long time.

Regards,

-- 
Stéphane Aulery



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

Bug#657644: [Debian-med-packaging] Bug#657644: wcstools and emboss: error when trying to install together

[Charles Plessy]

Le Fri, Jan 27, 2012 at 07:13:18PM +0100, Andreas Tille a écrit :
> 
> Usually we do handle this by a first come, first served policy and
> according to this in a new package like wcstools the binary should be
> renamed (and properly documented to inform the users about this change).
> 
> I'd suggest smething like wgs-remap or alternatively you can provide a
> /usr/lib/wgstools/remap and ask users to set their PATH accordingly to
> not break existing scripts or things like this.

Hi all,

emboss also has some programs already renamed, so one more would not hurt too
much.  Would there be a project-wide black list of common names, I would be
willing to add /usr/bin/remap there and rename it in emboss in addition to
wgstools.

Have a nice day,

-- 
Charles



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

Bug#651216: python-whisper: Please package new upstream version

[Elliot Murphy]

Yes, that is fine with me. Thank you for your work on this package.

On Friday, January 27, 2012, Jonas Genannt 
wrote:
> Hello Elliot,
>
>> Thank you for preparing a new upstream version. I don't have rights to
>> upload myself (not yet a debian maintainer), so feel free to ask
>> python team for a sponsored upload.
>
> I have changed the maintainer to Python Module Team, and added you and
> me as Uploader for python-whisper
>
>
http://anonscm.debian.org/viewvc/python-modules/packages/python-whisper/trunk/debian/control?revision=20155&view=markup
>
> Is that change ok for you?
>
> Thanks,
>Jonas
>

-- 
Elliot Murphy | https://launchpad.net/~statik/

Bug#645401: Nice, but… wasn’t enough ☹

[Thorsten Glaser]

Dixi quod…

>Your line is wrong:
>
>ifneq ($(DEB_HOST_ARCH_OS), $(findstring $(DEB_HOST_ARCH_OS), hurd m68k hppa 
>ppc64 armhf powerpcspe))

I’m retrying with:

ifeq (,$(findstring $(DEB_HOST_ARCH),hurd-i386 m68k hppa ppc64 armhf 
powerpcspe))

Looking good so far. Please use that in your next upload, and make one soon ;)

HTH & HAND,
//mirabilos
-- 
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.  -- Coywolf Qi Hunt



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

Bug#657643: dictionaries-common: update-default-ispell fails to find a dictionary during update from squeeze to wheezy

[Agustin Martin]

reassign 657643 irussian
retitle 657643 irussian: Changes info-ispell->language for no good
reason causing upgrade problems.
found 657643 irussian/0.99g5-15
found 657643 irussian/0.99g5-16
tag 657643 +patch
thanks

2012/1/27 Andreas Beckmann :
> Package: dictionaries-common
> Version: 1.12.3
> Severity: important
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'squeeze'.
> It installed fine in 'squeeze', then the upgrade to 'wheezy' fails.

Thanks for the test,

This is actually a problem with irussian, thus reassigning this bug report.

All ispell dictionaries and wordlists identification is done through a
unique identifier,  given at info-ispell->language, that must match
one of the entries in debconf template. That identifier must not be
changed across versions, so system knows that same dict is available,
although is possible to change the displayed string associated to that
identifier.

Seems that this unique identifier was changed in irussian/0.99g5-15,
causing this problem. Users upgrading to that version should have
found an extra debconf question. I am attaching a patch reverting that
change and putting new string in elanguages field, so old string is
used as identifier, but new string is displayed. irussian users
upgrading to this version will find yet another debconf question for
reverting things, but squeeze->wheezy upgrade should now work
seamlessly again.

Patch also removes irussian versioned ispell dependency. Since
autobuildhash is used, package should work well with old and new
ispell (that is one of the reasons of the autobuildhash stuff)

Regards,

-- 
Agustin
diff -Nru rus-ispell-0.99g5/debian/control rus-ispell-0.99g5/debian/control
--- rus-ispell-0.99g5/debian/control	2011-10-28 07:52:45.0 +0200
+++ rus-ispell-0.99g5/debian/control	2012-01-28 02:04:49.0 +0100
@@ -10,7 +10,7 @@
 
 Package: irussian
 Architecture: all
-Depends: dictionaries-common (>= 0.49.2), ispell (>= 3.3.02), debconf | debconf-2.0, ${misc:Depends}
+Depends: dictionaries-common (>= 0.49.2), ispell , debconf | debconf-2.0, ${misc:Depends}
 Provides: ispell-dictionary
 Description: Russian dictionary for Ispell
  This dictionary contains Russian wordlists for the Ispell spellchecker.
diff -Nru rus-ispell-0.99g5/debian/irussian.info-ispell rus-ispell-0.99g5/debian/irussian.info-ispell
--- rus-ispell-0.99g5/debian/irussian.info-ispell	2011-10-23 01:07:25.0 +0200
+++ rus-ispell-0.99g5/debian/irussian.info-ispell	2012-01-28 01:50:39.0 +0100
@@ -1,4 +1,5 @@
-Language: russki (Russian)
+Language: russian (Russian koi8-r)
+Elanguage: russki (Russian)
 Hash-Name: russian
 Emacsen-Name: russian
 Casechars: [АБВГДЕЁЖЗИЙКЛМНОПРСТУФХЦЧШЩЬЫЪЭЮЯабвгдеёжзийклмнопрстуфхцчшщьыъэюя]

Bug#657692: actionaz uses unacceptable build flags -mmmx -msse -msse2 -mfpmath=sse

[peter green]

package: actionaz
version: 3.2.1.1+dfsg-1
severity: serious

Actionaz builds with the following flags (among others)

-mmmx -msse -msse2 -mfpmath=sse

These flags are unacceptable in debian on CPU architectures other than 
amd64*. On i386 they cause the compiler to produce binaries that are 
incompatible with much of the hardware that debian supports. On other 
architectures they cause the build to fail with "unrecognized command 
line option" errors.


* on amd64 they are acceptable but pointless



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

Bug#656762: gnome-shell: after "something went wrong" no chance to save any data at all

[G. Chris Hofmann]

I started having this problem recently and to lend some credibility to
the PackageKit theory, it started about the same time I installed
PackageKit.  I set the key as noted above and have not experienced the
issue as of yet.  I set the key last evening though, so probably not
long enough time has passed to make any drastic proclamations yet.




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

Bug#651216: python-whisper: Please package new upstream version

[Jonas Genannt]

Hello Elliot,

> Thank you for preparing a new upstream version. I don't have rights to
> upload myself (not yet a debian maintainer), so feel free to ask
> python team for a sponsored upload.

I have changed the maintainer to Python Module Team, and added you and
me as Uploader for python-whisper

http://anonscm.debian.org/viewvc/python-modules/packages/python-whisper/trunk/debian/control?revision=20155&view=markup

Is that change ok for you?

Thanks,
Jonas



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

Bug#657691: php5 FTBFS on armhf, dependency on firebird-dev is negated but configure script still looks for it.

[peter green]

package: php5
severity: important

php5 failed to build on armhf with the following errors.

checking for InterBase support... yes, shared
checking for isc_detach_database in -lfbclient... no
checking for isc_detach_database in -lgds... no
configure: error: libgds, libib_util or libfbclient not found! Check config.log 
for more information.
checking for isc_detach_database in -lib_util... no
make: *** [configure-apache2-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Doing some investigating it looks like the configure script is still 
looking for libaries from firebird-dev even though armhf has been 
negated in the build-depends. The changelog of the package says "Don't 
build firebird extension on hurd, m68k, hppa, ppc64, armhf and 
powerpcspe (Closes: #651070)". However looking at bug 651070 it only 
seems to discuss hurd issues, it does not discuss any reasoning for 
disabling it on other architectures.


I haven't personally done a build test of php5 on armhf with 
firebird-dev installed (because it would take a bloody long time) but 
given that the previous version built fine I'd expect it to build 
successfully. Why did you attempt to disable the firebird extension on 
armhf in the first place?




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

Bug#657690: General protection fault in xfs_vm_releasepage

[Will Aoki]

Package: linux-image-2.6.32-5-amd64
Version: 2.6.32-39squeeze1

My backup server has begun crashing in the XFS code within two minutes
of the start of about one of every six AMANDA runs. The first crash,
twelve days ago, appears to be XFS bug 15516 and will be reported
separately (as I don't see an existing bug report). This morning's crash
follows:

Jan 27 00:11:22 chickenadventurous kernel: [811024.687095] general protection 
fault:  [#1] SMP
Jan 27 00:11:22 chickenadventurous kernel: [811024.687142] last sysfs file: 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input7/event1/uevent
Jan 27 00:11:22 chickenadventurous kernel: [811024.687198] CPU 0
Jan 27 00:11:22 chickenadventurous kernel: [811024.687220] Modules linked in: 
rpcsec_gss_krb5 nfsd nfs lockd fscache nfs_acl auth_rpcgss sunrpc 8021q garp 
stp ext3 jbd mbcache loop snd_hda_codec_intelhdmi snd_hda_codec_realtek 
snd_hda_intel snd_hda_codec i915 snd_hwdep snd_pcm snd_timer snd drm_kms_helper 
drm psmouse i2c_algo_bit i2c_i801 pcspkr evdev soundcore video serio_raw 
snd_page_alloc i2c_core output button processor xfs exportfs dm_mod raid1 
md_mod sg sr_mod cdrom osst sd_mod crc_t10dif st usbhid usb_storage hid 
ata_piix ata_generic sym53c8xx scsi_transport_spi e1000e libata ehci_hcd 
scsi_mod thermal usbcore nls_base thermal_sys [last unloaded: scsi_wait_scan]
Jan 27 00:11:22 chickenadventurous kernel: [811024.687541] Pid: 47, comm: 
kswapd0 Not tainted 2.6.32-5-amd64 #1
Jan 27 00:11:22 chickenadventurous kernel: [811024.687580] RIP: 
0010:[]  [] xfs_count_page_state+0x25/0x66 
[xfs]
Jan 27 00:11:22 chickenadventurous kernel: [811024.687657] RSP: 
0018:880124867b78  EFLAGS: 00010203
Jan 27 00:11:22 chickenadventurous kernel: [811024.687692] RAX: 
880100b0 RBX: ea0001728008 RCX: 880124867bd4
Jan 27 00:11:22 chickenadventurous kernel: [811024.687750] RDX: 
880124867bd8 RSI: 880124867bdc RDI: ea0001728008
Jan 27 00:11:22 chickenadventurous kernel: [811024.687809] RBP: 
 R08: 7a5da831f7287f78 R09: 6bc7c2d2d83dc935
Jan 27 00:11:22 chickenadventurous kernel: [811024.687869] R10: 
 R11: a0207a03 R12: 8800257a0d90
Jan 27 00:11:22 chickenadventurous kernel: [811024.687928] R13: 
00019e57 R14: 00012805 R15: 880124867c40
Jan 27 00:11:22 chickenadventurous kernel: [811024.687988] FS:  
() GS:88000520() knlGS:
Jan 27 00:11:22 chickenadventurous kernel: [811024.688048] CS:  0010 DS: 0018 
ES: 0018 CR0: 8005003b
Jan 27 00:11:22 chickenadventurous kernel: [811024.688084] CR2: 
7fff89ae8a60 CR3: 01001000 CR4: 06f0
Jan 27 00:11:22 chickenadventurous kernel: [811024.688142] DR0: 
 DR1:  DR2: 
Jan 27 00:11:22 chickenadventurous kernel: [811024.688202] DR3: 
 DR6: 0ff0 DR7: 0400
Jan 27 00:11:22 chickenadventurous kernel: [811024.688258] Process kswapd0 
(pid: 47, threadinfo 880124866000, task 880127b9dbd0)
Jan 27 00:11:22 chickenadventurous kernel: [811024.688320] Stack:
Jan 27 00:11:22 chickenadventurous kernel: [811024.688346]  a0207a53 
  0001
Jan 27 00:11:22 chickenadventurous kernel: [811024.688384] <0>  
0001  
Jan 27 00:11:22 chickenadventurous kernel: [811024.688448] <0>  
 ea0001728040 000101728040
Jan 27 00:11:22 chickenadventurous kernel: [811024.690605] Call Trace:
Jan 27 00:11:22 chickenadventurous kernel: [811024.690639]  
[] ? xfs_vm_releasepage+0x50/0xa5 [xfs]
Jan 27 00:11:22 chickenadventurous kernel: [811024.690683]  
[] ? invalidate_inode_page+0x5c/0x87
Jan 27 00:11:22 chickenadventurous kernel: [811024.690721]  
[] ? invalidate_mapping_pages+0x69/0xdb
Jan 27 00:11:22 chickenadventurous kernel: [811024.690759]  
[] ? shrink_icache_memory+0xfc/0x228
Jan 27 00:11:22 chickenadventurous kernel: [811024.690797]  
[] ? shrink_slab+0xe0/0x153
Jan 27 00:11:22 chickenadventurous kernel: [811024.690833]  
[] ? kswapd+0x4d9/0x686
Jan 27 00:11:22 chickenadventurous kernel: [811024.690867]  
[] ? isolate_pages_global+0x0/0x20f
Jan 27 00:11:22 chickenadventurous kernel: [811024.690907]  
[] ? autoremove_wake_function+0x0/0x2e
Jan 27 00:11:22 chickenadventurous kernel: [811024.690947]  
[] ? __wake_up_common+0x44/0x72
Jan 27 00:11:22 chickenadventurous kernel: [811024.690985]  
[] ? kswapd+0x0/0x686
Jan 27 00:11:22 chickenadventurous kernel: [811024.691017]  
[] ? kthread+0x79/0x81
Jan 27 00:11:22 chickenadventurous kernel: [811024.691052]  
[] ? child_rip+0xa/0x20
Jan 27 00:11:22 chickenadventurous kernel: [811024.691087]  
[] ? kthread+0x0/0x81
Jan 27 00:11:22 chickenadventurous kernel: [811024.691119]  
[] ? child_rip+0x0/0x20
Jan 27 00:11:22 chickenadventurous kernel: [811024.691153] Code: 49 89 1f eb ef 
90 c7 01 00

Bug#656712: hylafax-server.postinst: still no luck

[Giuseppe Sacco]

Il giorno dom, 22/01/2012 alle 23.11 +0100, Matthias Urlichs ha scritto:
[...]
> Setting up hylafax-server (2:6.1~20111227-7) ...
> cp: `/etc/hylafax/hyla.conf' and `/var/spool/hylafax/etc/hyla.conf' are the 
> same file
> dpkg: error processing hylafax-server (--install):
>  subprocess installed post-installation script returned error exit status 1
> Errors were encountered while processing:
>   hylafax-server
> 
> You are excessively blind this weekend. ;-)
> (The copy is in line 20, you don't test for bindount until line 30 or so)

You are right again: I did not see a couple of problmes. This bug report
is about an error about line 120 and you spotted a second one about line
20.

Could you try again? I updated all binary packages in
http://centrum.lixper.it/~giuseppe/debian/hylafax/

Thanks,
Giuseppe




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

Bug#657689: e1000e Detected Hardware Unit Hang:

[ubik pl]

Package: linux-2.6
Version: 2.6.32-38
Linux version 2.6.32-5-xen-amd64
RAM 8GB

Bug seems the same as #518182 and occurs on high traffic load.
System automatically recovered after aprox. 50
minutes([1782786.812335] e1000e :00:19.0: eth0: Reset adapter)


[1782779.812239] e1000e :00:19.0: eth0: Detected Hardware Unit Hang:
[1782779.812241]   TDH  <46>
[1782779.812242]   TDT  <4a>
[1782779.812243]   next_to_use  <4a>
[1782779.812244]   next_to_clean<46>
[1782779.812245] buffer_info[next_to_clean]:
[1782779.812247]   time_stamp   <11a8f9df5>
[1782779.812248]   next_to_watch<46>
[1782779.812249]   jiffies  <11a8f9ef2>
[1782779.812250]   next_to_watch.status <0>
[1782779.812251] MAC Status <80280>
[1782779.812252] PHY Status 
[1782779.812253] PHY 1000BASE-T Status  
[1782779.812254] PHY Extended Status
[1782779.812256] PCI Status <10>
[1782781.812247] e1000e :00:19.0: eth0: Detected Hardware Unit Hang:
[1782781.812249]   TDH  <46>
[1782781.812250]   TDT  <4a>
[1782781.812251]   next_to_use  <4a>
[1782781.812252]   next_to_clean<46>
[1782781.812253] buffer_info[next_to_clean]:
[1782781.812254]   time_stamp   <11a8f9df5>
[1782781.812255]   next_to_watch<46>
[1782781.812256]   jiffies  <11a8fa0e6>
[1782781.812258]   next_to_watch.status <0>
[1782781.812259] MAC Status <80280>
[1782781.812260] PHY Status 
[1782781.812261] PHY 1000BASE-T Status  
[1782781.812262] PHY Extended Status
[1782781.812263] PCI Status <10>
[1782783.812250] e1000e :00:19.0: eth0: Detected Hardware Unit Hang:
[1782783.812252]   TDH  <46>
[1782783.812253]   TDT  <4a>
[1782783.812254]   next_to_use  <4a>
[1782783.812255]   next_to_clean<46>
[1782783.812256] buffer_info[next_to_clean]:
[1782783.812257]   time_stamp   <11a8f9df5>
[1782783.812259]   next_to_watch<46>
[1782783.812260]   jiffies  <11a8fa2da>
[1782783.812261]   next_to_watch.status <0>
[1782783.812262] MAC Status <80280>
[1782783.812263] PHY Status 
[1782783.812264] PHY 1000BASE-T Status  
[1782783.812265] PHY Extended Status
[1782783.812266] PCI Status <10>
[1782785.812687] e1000e :00:19.0: eth0: Detected Hardware Unit Hang:
[1782785.812689]   TDH  <46>
[1782785.812690]   TDT  <4a>
[1782785.812691]   next_to_use  <4a>
[1782785.812692]   next_to_clean<46>
[1782785.812693] buffer_info[next_to_clean]:
[1782785.812694]   time_stamp   <11a8f9df5>
[1782785.812695]   next_to_watch<46>
[1782785.812696]   jiffies  <11a8fa4ce>
[1782785.812698]   next_to_watch.status <0>
[1782785.812699] MAC Status <80280>
[1782785.812700] PHY Status 
[1782785.812701] PHY 1000BASE-T Status  
[1782785.812702] PHY Extended Status
[1782785.812703] PCI Status <10>
[1782786.812020] [ cut here ]
[1782786.812032] WARNING: at
/build/buildd-linux-2.6_2.6.32-38-amd64-bk66e4/linu


x-2.6-2.6.32/debian/build/source_amd64_xen/net/sched/sch_generic.c:261
dev_watch

dog+0xe2/0x194()
[1782786.812037] Hardware name: OptiPlex 755
[1782786.812040] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out
[1782786.812043] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4
xt_state nf
   _conntrack
xt_physdev xt_multiport iptable_filter ip_tables x_tables xen_evtchn

  xenfs bridge stp loop
i915 drm_kms_helper drm i2c_algo_bit snd_pcm snd_timer snd

processor video soundcore
snd_page_alloc button i2c_i801 psmouse pcspkr serio_r

  aw acpi_processor dcdbas i2c_core evdev
output ext3 jbd mbcache dm_mod raid1 md_

 mod sg sr_mod sd_mod cdrom crc_t10dif uhci_hcd
8139too ata_generic 8139cp mii at

  a_piix thermal thermal_sys e1000e libata ehci_hcd scsi_mod
usbcore nls_base [las
 t
unloaded: scsi_wait_scan]
[1782786.812138] Pid: 0, comm: swapper Not tainted 2.6.32-5-xen-amd64 #1
[1782786.812141] Call Trace:
[1782786.812144][] ? dev_watchdog+0xe2/0x194
[1782786.812154]  [] ? dev_watchdog+0xe2/0x194
[1782786.812160]  [] ? warn_slowpath_common+0x77/0xa3
[1782786.812165]  [] ? dev_watchdog+0x0/0x194
[1782786.812170]  [] ? warn_slowpath_fmt+0x51/0x59
[1782786.812176]  [] ? xen_vcpuop_set_next_event+0x4c/0x60
[1782786.812181]  [] ? xen_vcpuop_set_next_event+0x0/0x60
[1782786.812186]  [] ? xen_force_evtchn_callback+0x9/0xa
[1782786.812191]  [] ? check_events+0x12/0x20
[1782786.812196]  [] ? netif_tx_lock+0x3d/0x69
[1782786.812202]  [] ? netdev_drivername+0x3b/0x40
[1782786.812207]  [] ? 

Bug#657687: dspam: FTBFS(kfreebsd): configure: error: Unable to determine how to compile with pthreads

[Steven Chamberlain]

Hi,

This issue led to the discussion here on debian-bsd:
http://lists.debian.org/debian-bsd/2012/01/msg00148.html

Awaiting a fix in eglibc for this testcase (reassign bug there?):

|  #include 
|  #include 
|
|  int main() {
|
|pthread_mutex_t m;
|pthread_mutex_init(&m, NULL);
|pthread_exit(0);
|exit(EXIT_FAILURE);
|  }

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



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

Bug#657092: Reassign

[Soren Stoutner]

Vincent,

On Friday, January 27, 2012 05:18:38 PM Vincent Bernat wrote:
> OoO  En cette  soirée bien  amorcée du  vendredi 27  janvier  2012, vers
> 
> I have  reassigned and  raised the priority.  Unless someone  comes with
> some patch to make Roundcube compatible with SQLite 3.x, this means that
> support for SQLite will just be dropped.

You are correct.  I'm not holding out hope that this gets fixed anytime soon, 
although I am going to file a bug with upstream.  It looks like in the meantime 
I am going to have to migrate all of my current installations to roundcube-
mysql.

I also raised the severity level to grave as this is more appropriate for this 
situation given that the package is completely unusable.

Soren

-- 
Soren Stoutner
Small Business Tech Solutions
623-262-6169
so...@smallbusinesstech.net
www.smallbusinesstech.net


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

Bug#645401: Nice, but… wasn’t enough ☹

[Thorsten Glaser]

Source: php5
Version: 5.3.9-3

[…]
checking whether rfc822_output_address_list function present... yes
checking whether build with IMAP works... yes
checking for InterBase support... yes, shared
checking for isc_detach_database in -lfbclient... no
checking for isc_detach_database in -lgds... no
checking for isc_detach_database in -lib_util... no
configure: error: libgds, libib_util or libfbclient not found! Check config.log 
for more information.
make: *** [configure-apache2-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package

Your line is wrong:

ifneq ($(DEB_HOST_ARCH_OS), $(findstring $(DEB_HOST_ARCH_OS), hurd m68k hppa 
ppc64 armhf powerpcspe))

Because:

(pbuild1831)root@ara5:~/php5-5.3.9 # dpkg-architecture -qDEB_HOST_ARCH_OS
linux

I think you want DEB_HOST_ARCH. According to the arches file,
it’s got DEB_HOST_ARCH=hurd-i386 on the Hurd.

bye,
//mirabilos
-- 
  “Having a smoking section in a restaurant is like having
  a peeing section in a swimming pool.”
-- Edward Burr



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

Bug#657556: X.org crash all the time unexpected

[Michelle Konzack]

OK, now after some testing I have encountered a weird problem:

I have 8 Workstains base on the AsusTek A7V600-X Mainboard with  CPUs of
AMD Sempron, Athlon and Geode.  All Workstations running with  2/3 GByte
DDR400 memory.

I use mainly the Matrox G45+MDHA16D/OE6 (VGA Dual-Head, AGP) which works
perfectly on all machines runing Lenny.

Now some machines are upgraded to Squeeze and I have  encountered  tonns
of XTerm bugs.  I have several 100 cores laying around inm my ${HOME}.

OK, since mainly xterm aps are closing (xterm  crashs)  and  X  restarts
unexpected, I now have  have  removed  the  Matrox  G45+MDHA16D/OE6  und
inserted an Matrox G45FMDVP32DB (DVI/VGA Dual-Head, PCI) and now X  does
not more crash.

Hmm, broken grafikcard?

I am wondering, since I have bought 10 of them original NEW!

Checed the Card in another Workstation (same Mainboard Type,  Soundcard)
and it works perfectly without crashing under Lenny and Squeeze.

Can someone of you Guys and Girls explain this?

More weird stuff:

FOr 2 years I had bougth 20 mainboards, 80 1 GByte  memory  modules,  20
graficcards, 20 2"5 SATA drives and 20 DVD-RW drives.   When  assembled,
some of the graficcards wont work with Debian Lenny and if  I  put  them
into another Computer it just works...

It is NOT THE FIRST TIME, I have such sick fault which droved  my  crazy
for more then one week!

Thanks, Greetings and nice Day/Evening
Michelle Konzack

-- 
# Debian GNU/Linux Consultant ##
   Development of Intranet and Embedded Systems with Debian GNU/Linux

itsystems@tdnet Tel: +49-176-86004575 office
Owner Michelle Konzack  Tel: +49-177-9351947  mobil Germany
Tel: +33-6-61925193   mobil France
Gewerbe Strasse 3
77694 Kehl/Germany  Jabber: linux4miche...@jabber.ccc.de



Linux-User #280138 with the Linux Counter, http://counter.li.org/


signature.pgp
Description: Digital signature

Bug#657418: libpgpool0: fails to upgrade from squeeze - trying to overwrite ...

[Hideki Yamane]

tags 657418 patch
tags 657418 pending
thanks

Hi,

 I've prepared an NMU for pgpool2 (versioned as 3.1.1-1.1) and uploaded it 
 to DELAYED/5. Please feel free to tell me if I should delay it longer.

 Thanks.

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane
diff -Nru pgpool2-3.1.1/debian/changelog pgpool2-3.1.1/debian/changelog
--- pgpool2-3.1.1/debian/changelog	2011-12-23 03:06:50.0 +0900
+++ pgpool2-3.1.1/debian/changelog	2012-01-28 09:17:58.0 +0900
@@ -1,3 +1,12 @@
+pgpool2 (3.1.1-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/control.in
+- libpgpool0: set Breaks to solve "fails to upgrade from squeeze"
+  (Closes: #657418) 
+
+ -- Hideki Yamane   Sat, 28 Jan 2012 09:16:51 +0900
+
 pgpool2 (3.1.1-1) unstable; urgency=low
 
   * New upstream release.  Closes: #646116.
diff -Nru pgpool2-3.1.1/debian/control pgpool2-3.1.1/debian/control
--- pgpool2-3.1.1/debian/control	2011-12-23 04:01:52.0 +0900
+++ pgpool2-3.1.1/debian/control	2012-01-28 09:18:03.0 +0900
@@ -37,6 +37,7 @@
 Package: libpgpool0
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
+Breaks: pgpool2 (<< 3.1.1-1)
 Description: pgpool control protocol library
  pgpool-II is a middleware that works between PostgreSQL servers and a
  PostgreSQL database client.  This package contains the pgpool control
diff -Nru pgpool2-3.1.1/debian/control.in pgpool2-3.1.1/debian/control.in
--- pgpool2-3.1.1/debian/control.in	2011-12-23 03:54:47.0 +0900
+++ pgpool2-3.1.1/debian/control.in	2012-01-28 09:11:09.0 +0900
@@ -37,6 +37,7 @@
 Package: libpgpool0
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
+Breaks: pgpool2 (<< 3.1.1-1)
 Description: pgpool control protocol library
  pgpool-II is a middleware that works between PostgreSQL servers and a
  PostgreSQL database client.  This package contains the pgpool control

Bug#653501: libfreenect : pull request and issues raised

[Nicolas Bourdaud]

Hello Arne!

On 27/01/2012 18:26, Yaroslav Halchenko wrote:
> Hi Arne -- thanks a lot for following up!
> So Nicolas -- ready to take the blame? ;)

If it is ok for all of you, I am fine with taking the blame! :-)


On 27/01/2012 17:32, Yaroslav Halchenko wrote:
> I guess you do have a
> beast (kinect) to enjoy, right? ;)

To answer you question Yaroslav, we bought a kinect few month ago in the
lab to test few things and it was on my office mate's desk since then. I
was curious about it and started to see how this beast could perform...


On 27/01/2012 17:35, Yaroslav Halchenko wrote:
> or may be just bluntly under NeuroDebian Team, since you are pretty much
> a part of it now ;-) )
> 
> On Fri, 27 Jan 2012, Yaroslav Halchenko wrote:
>> > we might alternatively start libfreenect-maint team on alioth which
>> > would be listed as the maintainer while we all stay in uploaders... what
>> > you think?

If everybody in the neurodebian project, we can stay in it, that what
you prefer. I am not sure, it is wise to open a project on its own for
one package but I might be wrong. What do you prefer.
(off topic question: there is a neurodebian project on Alioth, and
pkg-exppsy which has more people... which one should be used?)


On 27/01/2012 18:25, Arne Bernin wrote:
>> - solution 1: installing libfreenect0.1 package installs a modprobe rule
>> > which blacklist the module gspca_kinect. But it makes the v4l2 interface
>> > unavailable which is bad for those who want to use it.
> What about asking the user via debconf what he wants and make the
> blacklisting as an option? Seems the easiest solution for me...

Actually, I had forgot this possibility... It is actually better than
the statu quo but it still remains the question of the default action.
What surprises me the most is that issue of userspace driver and kernel
space driver seems not to have been raised earlier with other devices...

Cheers,

Nicolas



signature.asc
Description: OpenPGP digital signature

Bug#657092: Reassign

[Vincent Bernat]

OoO  En cette  soirée bien  amorcée du  vendredi 27  janvier  2012, vers
22:24, Soren Stoutner  disait :

> It seems to me this bug should be moved to roundcube-sqlite and upgraded to 
> serious because it completely breaks all roundcube installations that rely on 
> sqlite.

I have  reassigned and  raised the priority.  Unless someone  comes with
some patch to make Roundcube compatible with SQLite 3.x, this means that
support for SQLite will just be dropped.
-- 
Vincent Bernat ☯ http://vincent.bernat.im

Make sure your code "does nothing" gracefully.
- The Elements of Programming Style (Kernighan & Plauger)


pgpddGnHqyo04.pgp
Description: PGP signature

Bug#657688: juman: FTBFS: cp: target `debian/juman-dic/usr/share/juman/dic' is not a directory

[Christoph Egger]

Package: src:juman
Version: 7.0-1
Severity: serious
Tags: sid wheezy
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the buildds:

make[3]: Leaving directory 
`/build/buildd-juman_7.0-1-kfreebsd-amd64-LWznjZ/juman-7.0'
make[2]: Leaving directory 
`/build/buildd-juman_7.0-1-kfreebsd-amd64-LWznjZ/juman-7.0'
rm -rf debian/tmp/usr/lib/juman/doc
dh_link -pjuman usr/share/doc/juman usr/lib/juman/doc
cp -p dic/*.dic debian/juman-dic/usr/share/juman/dic
cp: target `debian/juman-dic/usr/share/juman/dic' is not a directory
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory 
`/build/buildd-juman_7.0-1-kfreebsd-amd64-LWznjZ/juman-7.0'
make: *** [binary-arch] Error 2

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=juman&arch=kfreebsd-i386&ver=7.0-1&stamp=1327301199

Regards

Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer



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

Bug#657687: dspam: FTBFS(kfreebsd): configure: error: Unable to determine how to compile with pthreads

[Christoph Egger]

Package: src:dspam
Version: 3.10.1+dfsg-3+b1
Severity: serious
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the kfreebsd-* buildds:

checking for netinet/in.h... yes
checking for arpa/inet.h... yes
checking for inet_ntoa_r... no
checking if inet_ntoa_r might be used... no
checking for strcasestr... yes
checking whether to enable daemon mode... yes
checking how you like your pthreads... unknown
configure: error: Unable to determine how to compile with pthreads

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=dspam&arch=kfreebsd-amd64&ver=3.10.1%2Bdfsg-3%2Bb1&stamp=1327287208

Regards

Christoph

If you have further questions please mail debian-...@lists.debian.org

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer



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

Bug#657393: RFS: skstream/0.3.6-1 [ITA] -- IOStream C++ socket Library

[Jakub Wilk]

* Stephen M. Webb , 2012-01-27, 18:20:

  * debian/rules: add --with autoreconf to regenerate autoconfigury


A typo, though I'm not sure which word you had in mind. :P


  * debian/control: tweaked for multi-arch


Could you be more explicit about how it was tweaked?

BTW, you could add "Multi-Arch: same" field to all 3 packages, so that 
there's an actual benefit from installing stuff into multi-arch 
directories. :)


I see test failures in my build log:

| make  check-TESTS
| make[3]: Entering directory `/build/skstream-hivd_N/skstream-0.3.8/test'
| ...F.F.F.F
|
|
| !!!FAILURES!!!
| Test Results:
| Run:  22   Failures: 4   Errors: 0
|
|
| 1) test: tcpskstreamtest::testConstructor_2 (F) line: 141 childskstreamtest.h
| assertion failed
| - Expression: sks->is_open()
| - Check that echo service is running on local machine
|
|
| 2) test: tcpskstreamtest::testOpen (F) line: 160 childskstreamtest.h
| assertion failed
| - Expression: skstream->is_open()
| - Check that echo service is running on local machine
|
|
| 3) test: tcpskstreamtest::testOpenNonblock (F) line: 189 childskstreamtest.h
| assertion failed
| - Expression: skstream->is_open()
|
|
| 4) test: rawskstreamtest::testConstructor_1 (F) line: 262 childskstreamtest.h
| assertion failed
| - Expression: skstream.is_open()
| - Raw only works on GNU/Linux and you must be root
|
|
| PASS: skstreamtestrunner
| =
| 1 test passed
| =

...but then the build process continues. :/

--
Jakub Wilk



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

Bug#622395: Bug#389258: Request for permission to NMU memtest86

[Yann Dirson]

On Fri, Jan 27, 2012 at 11:50:24PM +0100, Aurelien Jarno wrote:
> The current version of memtest86 in unstable is 3 years old, and doesn't
> really support machines with >= 4GB of RAM. Given this kind of machine
> is quite common nowadays, memtest86 is not really usable anymore.
> 
> Version 4.0a supports 4GB of RAM, and is also able to use multiple CPUs
> for faster and better testing.
> 
> The patch below is the diff of the debian/ directory necessary to bring
> the version to 4.0a. It can be used directly with the upstream tarball.
> Would it be possible to upload it as an NMU?

OK, please do.  Thanks!

> --- memtest86-3.5/debian/changelog2012-01-27 11:36:16.0 +0100
> +++ memtest86-4.0a/debian/changelog   2012-01-27 11:34:08.590168321 +0100
> @@ -1,3 +1,13 @@
> +memtest86 (4.0a-0.1) unstable; urgency=low
> +
> +  * Non-maintainer upload.
> +  * New upstream version (Closes: #622395):
> +- Support machines with >= 4GB of RAM.  Closes: #522525, #572347, 
> #582610,
> +  #647756.
> +- Fix build with -O3.  Closes: #389258.
> +
> + -- Aurelien Jarno   Fri, 27 Jan 2012 23:49:59 +0100
> +
>  memtest86 (3.5-2.3) unstable; urgency=low
>  
>* Non-maintainer upload.
> 
> -- 
> Aurelien Jarno  GPG: 1024D/F1BCDB73
> aurel...@aurel32.net http://www.aurel32.net





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

Bug#657686: cricket: fails to install - postinst calls useradd incorrectly

[Andreas Beckmann]

Package: cricket
Version: 1.0.5-16
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package cricket.
  (Reading database ... 8848 files and directories currently installed.)
  Unpacking cricket (from .../cricket_1.0.5-16_amd64.deb) ...
  Setting up cricket (1.0.5-16) ...
  useradd: unrecognized option '--quiet'
  Usage: useradd [options] LOGIN
  [...]
  dpkg: error processing cricket (--configure):
   subprocess installed post-installation script returned error exit status 2


cheers,

Andreas


cricket_1.0.5-16.log.gz
Description: GNU Zip compressed data

Bug#657685: gmime2.4 FTBFS on armhf assembler errors from gcc

[peter green]

package: gmime2.4
severity: important
tags: patch

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../util -DGMIME_VERSION=\"2.4.31\" 
-DGMIME_MAJOR_VERSION=2 -DGMIME_MINOR_VERSION=4 -DGMIME_MICRO_VERSION=31 
-DG_LOG_DOMAIN=\"gmime\" -DG_DISABLE_DEPRECATED -D_LARGEFILE64_SOURCE 
-D_FILE_OFFSET_BITS=64 -pthread -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -g -O2 -fno-strict-aliasing -c gmime-param.c  -fPIC 
-DPIC -o .libs/gmime-param.o
/tmp/cc1SBNmj.s: Assembler messages:
/tmp/cc1SBNmj.s:2152: Error: can't resolve `.rodata' {.rodata section} - 
`.LPIC18' {*UND* section}
make[5]: *** [gmime-param.lo] Error 1

I have produced a somewhat reduced (though not as much as i'd like) testcase 
and sent it as a bug report on gcc-4.6[1] but I don't expect a fast response
from them and it's important for the armhf to keep things in sync as much as 
possible as we aim towards becoming a release architecture.


The bug is only reproducable with -O2 and higher, it is not reproducable
with -O1.

Therefore could I ask you to apple the attatched patch which reduces the
optmisation level on armhf to -O1 to your next upload (please don't upload
right now though unless you have rc issues to fix, getting the mono
transition through is more important than helping us out). 


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

--- gmime2.4-2.4.31/debian/rules	2012-01-28 00:01:37.0 +
+++ gmime2.4-2.4.31.new/debian/rules	2012-01-27 23:48:59.0 +
@@ -16,6 +16,13 @@
 include /usr/share/quilt/quilt.make
 include /usr/share/gnome-pkg-tools/1/rules/uploaders.mk
 
+DEB_HOST_ARCH ?=$(shell dpkg-architecture -qDEB_HOST_ARCH)
+
+#use -01 on armhf to avoid assembler errors
+ifeq ($(DEB_HOST_ARCH),armhf)
+  export CFLAGS += -O1
+endif
+
 autoreconf: autoreconf-stamp
 autoreconf-stamp: $(QUILT_STAMPFN)
 	autoreconf -f -i -s

Bug#657684: wrong path in man page

[jidanni]

Package: debtags
Version: 1.8.0
Severity: minor
File: /usr/share/man/man1/debtags.1.gz

   The update command can be used to download  extra  tags  as  listed  in
   /etc/debtags/sources/list:  see  the  contents  of  that  file for more
   information.

Don't you mean . instead of /?

And all of
/etc/debtags/sources.list
/etc/debtags/sources.list.d/*

P.S., for update, mention something about how it is there in
/etc/cron.daily/debtags and what to do for users who don't have their
computer connected to the net 24 hours a day etc.



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

Bug#657676: sysvinit: FTBFS on kfreebsd due to missing sys/signalfd.h

[Steven Chamberlain]

On 27/01/12 23:10, Roger Leigh wrote:
> Looking at the source, I see no evidence of actual signalfd usage,
> so just not including the header may fix this universally.  Certainly
> removing it on Linux does not break compilation.

Hi,

Seems you're right, I just tried building on kfreebsd-i386 and simply
removing the #include  allowed it to build successfully.

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



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

Bug#657676: sysvinit: FTBFS on kfreebsd due to missing sys/signalfd.h

[Roger Leigh]

tags 657676 + pending
thanks

On Fri, Jan 27, 2012 at 11:50:15PM +0100, Guillem Jover wrote:
> Hi!
> 
> On Fri, 2012-01-27 at 21:42:17 +, Roger Leigh wrote:
> > Package: sysvinit
> > Version: 2.88dsf-19
> > Severity: normal
> > 
> > This needs a kfreebsd workaround (also fails on kfreebsd-i386).
> 
> signalfd is a Linux only interface (see [0]), BSD based systems can use

It turns out it was including the header but not using it, so was
basically redundant.  Removing the include fixes the issue for
all platforms.


Regards,
Roger

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



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

Bug#657393: RFS: skstream/0.3.6-1 [ITA] -- IOStream C++ socket Library

[Paul Tagliamonte]

On Fri, Jan 27, 2012 at 6:20 PM, Stephen M. Webb
 wrote:
> On 01/27/2012 01:45 PM, Jakub Wilk wrote:
>> * Stephen M. Webb , 2012-01-26, 12:05:
>>
>>> since the library is a part of an MMORPG stack, and I anticipate a
>>> newer client app revision getting in to Debian long before a new
>>> server app, so the coexistence of both old and new SONAMEs will be
>>> required, at least for a little while.
>>
>> Could elaborate more of this? What is "client app" and "server app" in
>> this context?
>
> The MMORPG server and client both use this library.  While both are
> actively developed upstream, the server has been removed from Debian
> because it has been unmaintained for too long and will require going
> through the ITP process (I believe, please correct me if I'm wrong).
> The client has merely been orphaned, and I currently have an ITA on it.
>
> The server package is still available in derivates (like Ubuntu) as a

If a package has been removed in Debian, don't count on Ubuntu keeping
it around :)

It's after the part in the cycle where we sync with Debian, so it'll
be in the next release (unless someone removes it, which is not out of
the question), but not the next.

*If* it was removed in Debian. I've not checked on any of this.

> binary package and will continue to depend on the older libraries until
> a newer upstream is available.  Mean time, the newer client is
> wire-protocol compatible with older servers, so it's more important to
> focus on that.
>
>> Please bear in mind that having multiple versions of the same source
>> package in a single suite is not really a desired state.
>>
>> As far as unstable is concerned, you don't have control over when the
>> old package will be removed. While I think ftp-masters usually wait
>> until the old version don't have rdepeds anymore, they can also do it
>> whenever they see fit (possibly rendering not-yet-rebuilt packages
>> uninstallable).
>>
>> Until very recently, it wasn't even possible (unless some dirty hacks
>> were involved) to keep multiple versions of a library in testing. It's
>> doable now, but such a state certainly doesn't make the Release Team happy.
>
> Assuming the remaining packages in the WorldForge stack get uploaded, it
> does not matter to me that the older libraries are available.  I am just
> starting at the bottom of the dependency stack wit this package.
>
>> Did you build in unstable? I just did (with DEB_BUILD_OPTIONS=noopt),
>> and saw this in the build log:
>>
>> /bin/bash ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H
>> -I.. -I..   -g -O2 -Wall -DNDEBUG -c -o sksocket.lo sksocket.cpp
>
> OK, this is the famous noppt bug in dh.  Fixed by bumping up to compat
> level 9.  Seems someone changed the default behind my back while I
> wasn't looking.  Unfortunately this bump pulls in the magic of
> multi-arch, but fortunately that does not harm and dependent packages
> continue to build OK.
>
>>> I would appreciate an explicit list of any apparent regressions, since
>>> they aren't apparent to me from the build logs or runtime testing of
>>> the package.
>>
>> I didn't have anything specific in mind (except noopt support). Looking
>> at old debian/rules there are some things that dh certainly doesn't do:
>> - setting LDFLAGS=-lstdc++;
>> - passing --disable-debug to configure.
>> Maybe these were no-ops or simply wrong. Maybe not. I didn't check. :)
>
> The GCC c++ compiler links with its library now, since version 3.0.  The
> default config is --disable-default.  Yes, these are noops.
>
>> Now some things I didn't catch in my initial review:
>>
>> The package descriptions were modified, but this is not documented in
>> the changelog.
>
> Nice catch.  Remediated.
>
>> The .orig.tar is compressed with bz2, but uscan would download a
>> .tar.gz. I see the upstream provides bzip2ed tarballs too, so it should
>> be a matter of fixing debian/watch.
>
> OK, done.
>
> New package uploaded to
> http://mentors.debian.net/debian/pool/main/s/skstream/skstream_0.3.8-1.dsc
>
> Changes:
>  skstream (0.3.8-1) unstable; urgency=low
>  .
>   * new maintainer: Debian games team (closes: #653977)
>     - added myself as uploader
>   * new upstream release
>   * changed package description (iostream, not isostream)
>   * renamed binary packages due to SONAME change
>   * converted packaging to use dh sequenceer
>   * converted packaging to 3.0 (quilt) format
>   * updated Standards-Version to 3.9.2 (no changes required)
>   * added debian/symbols file
>   * added VCs- fields to debian/control
>   * debian/copyright: convert to DEP-5 format
>   * debian/compat: set to compatibility level 9
>   * debian/rules: add --with autoreconf to regenerate autoconfigury
>   * debian/control: tweaked for multi-arch
>
> --
> Stephen M. Webb  
>
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/4f23313a.6020...@bregmas

Bug#654728: mysql-5.1: non-standard gcc/g++ used for build (gcc-4.5)

[Thorsten Glaser]

Hi,

I’ve just found the upstream bug for this, which says that
gcc 4.4 should work just as fine.

Please switch mysql-5.1 (and, when uploaded to unstable,
mysql-5.5) to using gcc-4.4 on m68k, as we never ported
gcc-4.5 to it since gcc-4.5 will not be released with
wheezy, and having two compilers (plus testing gcc-4.7
every once in a while) is work enough.

Thanks,
//mirabilos
-- 
  “Having a smoking section in a restaurant is like having
  a peeing section in a swimming pool.”
-- Edward Burr



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

Bug#636968: fim: diff for NMU version 0.3-beta-prerelease-1.3

[gregor herrmann]

On Fri, 27 Jan 2012 20:24:00 +0100, Jakub Wilk wrote:

> >+#if PNG_LIBPNG_VER_MAJOR >= 1 && PNG_LIBPNG_VER_MINOR >= 4
> >+png_set_expand_gray_1_2_4_to_8(h->png);
> >+#else
> > png_set_gray_1_2_4_to_8(h->png);
> >+#endif
> 
> Won't that break with libpng 2.0? I think it the condition should be
> rather:
> (PNG_LIBPNG_VER_MAJOR == 1 && PNG_LIBPNG_VER_MINOR >= 4) || 
> PNG_LIBPNG_VER_MAJOR > 1

Good question.

Let's ask the sumbitter/libpng maintainer:
Nobuhiro, what dou think?
 
Cheers,
gregor
 
-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Vic Chesnutt: Thumbtack


signature.asc
Description: Digital signature

Bug#656792: linux-image-3.2.0-1-amd64: kernel does not boot since 3.1 under a (strange) Xen anymore

[Christoph Anton Mitterer]

Hi.

Perhaps this helps. According to the ISP the exakt version of the dom0
kernel is:
2.6.32.12-0.7.1.xs6.0.0.529.170661xen

Also they claim there is not Microsoft HyperV or so used at all.


Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Bug#656384: gdm3 is shipping a gnome-power-manager.desktop

[Francois Marier]

reopen 656384
reassign 656384 gdm3
thanks

I think I might have found the culprit: 

  $ dpkg -S /usr/share/gdm/autostart/LoginWindow/gnome-power-manager.desktop
  gdm3: /usr/share/gdm/autostart/LoginWindow/gnome-power-manager.desktop

Since the gnome-power-manager binary was removed, this autostart desktop
file should be removed.

Cheers,
Francois

-- 
Francois Marier identi.ca/fmarier
http://fmarier.orgtwitter.com/fmarier



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

Bug#621692: Status of 1.7 packaging

[Peter Samuelson]

[Diego Fernández Durán]
>   What's the state of Subversion 1.7 packaging for Debian?
>   Is there any way in which I can help?

I've just been really really short on time.  I hope I can find time to
get a 1.7 package uploaded this weekend.  I will probably disable serf
support on kFreeBSD until I can find time to fix that.

That would be a useful thing to do, anyone looking for things to do:
figure out why the serf 1.0 testsuite hangs on FreeBSD:

https://buildd.debian.org/status/fetch.php?pkg=serf&arch=kfreebsd-amd64&ver=1.0.0-2&stamp=1313651587

It is not Debian-specific; this same issue has been reported on other
FreeBSD systems as well.  I notice the FreeBSD Ports tree has serf 1.0,
and did not patch for this issue, so either they don't run the
testsuite at all, or it doesn't fail for them.

Peter



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

Bug#657393: RFS: skstream/0.3.6-1 [ITA] -- IOStream C++ socket Library

[Stephen M. Webb]

On 01/27/2012 01:45 PM, Jakub Wilk wrote:
> * Stephen M. Webb , 2012-01-26, 12:05:
> 
>> since the library is a part of an MMORPG stack, and I anticipate a
>> newer client app revision getting in to Debian long before a new
>> server app, so the coexistence of both old and new SONAMEs will be
>> required, at least for a little while.
> 
> Could elaborate more of this? What is "client app" and "server app" in
> this context?

The MMORPG server and client both use this library.  While both are
actively developed upstream, the server has been removed from Debian
because it has been unmaintained for too long and will require going
through the ITP process (I believe, please correct me if I'm wrong).
The client has merely been orphaned, and I currently have an ITA on it.

The server package is still available in derivates (like Ubuntu) as a
binary package and will continue to depend on the older libraries until
a newer upstream is available.  Mean time, the newer client is
wire-protocol compatible with older servers, so it's more important to
focus on that.

> Please bear in mind that having multiple versions of the same source
> package in a single suite is not really a desired state.
> 
> As far as unstable is concerned, you don't have control over when the
> old package will be removed. While I think ftp-masters usually wait
> until the old version don't have rdepeds anymore, they can also do it
> whenever they see fit (possibly rendering not-yet-rebuilt packages
> uninstallable).
> 
> Until very recently, it wasn't even possible (unless some dirty hacks
> were involved) to keep multiple versions of a library in testing. It's
> doable now, but such a state certainly doesn't make the Release Team happy.

Assuming the remaining packages in the WorldForge stack get uploaded, it
does not matter to me that the older libraries are available.  I am just
starting at the bottom of the dependency stack wit this package.

> Did you build in unstable? I just did (with DEB_BUILD_OPTIONS=noopt),
> and saw this in the build log:
> 
> /bin/bash ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H  
> -I.. -I..   -g -O2 -Wall -DNDEBUG -c -o sksocket.lo sksocket.cpp

OK, this is the famous noppt bug in dh.  Fixed by bumping up to compat
level 9.  Seems someone changed the default behind my back while I
wasn't looking.  Unfortunately this bump pulls in the magic of
multi-arch, but fortunately that does not harm and dependent packages
continue to build OK.

>> I would appreciate an explicit list of any apparent regressions, since
>> they aren't apparent to me from the build logs or runtime testing of
>> the package.
> 
> I didn't have anything specific in mind (except noopt support). Looking
> at old debian/rules there are some things that dh certainly doesn't do:
> - setting LDFLAGS=-lstdc++;
> - passing --disable-debug to configure.
> Maybe these were no-ops or simply wrong. Maybe not. I didn't check. :)

The GCC c++ compiler links with its library now, since version 3.0.  The
default config is --disable-default.  Yes, these are noops.

> Now some things I didn't catch in my initial review:
> 
> The package descriptions were modified, but this is not documented in
> the changelog.

Nice catch.  Remediated.

> The .orig.tar is compressed with bz2, but uscan would download a
> .tar.gz. I see the upstream provides bzip2ed tarballs too, so it should
> be a matter of fixing debian/watch.

OK, done.

New package uploaded to
http://mentors.debian.net/debian/pool/main/s/skstream/skstream_0.3.8-1.dsc

Changes:
 skstream (0.3.8-1) unstable; urgency=low
 .
   * new maintainer: Debian games team (closes: #653977)
 - added myself as uploader
   * new upstream release
   * changed package description (iostream, not isostream)
   * renamed binary packages due to SONAME change
   * converted packaging to use dh sequenceer
   * converted packaging to 3.0 (quilt) format
   * updated Standards-Version to 3.9.2 (no changes required)
   * added debian/symbols file
   * added VCs- fields to debian/control
   * debian/copyright: convert to DEP-5 format
   * debian/compat: set to compatibility level 9
   * debian/rules: add --with autoreconf to regenerate autoconfigury
   * debian/control: tweaked for multi-arch

-- 
Stephen M. Webb  



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

Bug#657529: Patch for stable version

[Michael Tokarev]

On 28.01.2012 03:04, Matt Kraai wrote:
> Hi,
> 
> I've attached a patch that should fix this problem to this message.
> It's based on the patch used to fix this problem in unstable, which
> doesn't apply cleanly to the stable version.  I wasn't sure what do to
> about the patch headers, so I left them unchanged.  Should I upload a
> fixed package somewhere?

See DSA 2396-1 which were issued about 5 hours ago.  The fixed
stable version is already available in debian security archives.

Also,

http://anonscm.debian.org/gitweb/?p=collab-maint/qemu-kvm.git;a=shortlog;h=refs/heads/squeeze

and in particular,

http://anonscm.debian.org/gitweb/?p=collab-maint/qemu-kvm.git;a=blob;f=debian/patches/e1000-bounds-packet-size-against-buffer-size-CVE-2012-0029.diff;h=91ab34c2ee49499706aedc70618139ccc9d95923;hb=59e1ee22261dbc793282f61c9ed12bfd56d7c056

The difference between 1.0 and 0.12 version is cpu_physical_memory_read
that's used in 0.12 vs pci_dma_read() used in later version, and 13-line
offset.

Thanks,

/mjt



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

Bug#650654: wine: FTBFS on amd64: asm/errno.h: No such file or directory

[Michael Gilbert]

Here is a new patch that fixes the lintian autoreject as well.

Best wishes,
Mike
diff -u wine-1.0.1/debian/changelog wine-1.0.1/debian/changelog
--- wine-1.0.1/debian/changelog
+++ wine-1.0.1/debian/changelog
@@ -1,3 +1,11 @@
+wine (1.0.1-3.5) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Build-depend on gcc-multilib (closes: bug #650654).
+  * Fix statically-linked-binary wine-preloader lintian override.
+
+ -- Michael Gilbert   Sun, 01 Jan 2012 13:01:50 -0500
+
 wine (1.0.1-3.4) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u wine-1.0.1/debian/control wine-1.0.1/debian/control
--- wine-1.0.1/debian/control
+++ wine-1.0.1/debian/control
@@ -30,7 +30,8 @@
  ia32-libs (>= 1.19) [amd64 kfreebsd-amd64],
  ia32-libs-dev [amd64 kfreebsd-amd64],
  lib32ncurses5-dev [amd64 kfreebsd-amd64], lib32asound2-dev [amd64],
- lib32z1-dev [amd64 kfreebsd-amd64]
+ lib32z1-dev [amd64 kfreebsd-amd64],
+ gcc-multilib
 Standards-Version: 3.7.3
 Homepage: http://www.winehq.org/
 Vcs-Browser: http://git.debian.org/?p=pkg-wine/wine.git
diff -u wine-1.0.1/debian/libwine.lintian-overrides wine-1.0.1/debian/libwine.lintian-overrides
--- wine-1.0.1/debian/libwine.lintian-overrides
+++ wine-1.0.1/debian/libwine.lintian-overrides
@@ -1,5 +1,5 @@
 # the preloader is a self-contained binary on purpose
-libwine binary: statically-linked-binary ./usr/lib/wine/wine-preloader
+libwine binary: statically-linked-binary usr/lib/wine/wine-preloader
 # specially linked binaries, leaving them unstripped for now,
 # as dh_strip is currently unable to handle them properly
 libwine binary: unstripped-binary-or-object ./usr/lib/wine/wine-preloader

Bug#644438: Fwd: Re: Add OSGi metadata to the java binding

[Peter Samuelson]

[Jakub Adam]

> upstream accepted my OSGi metadata patch for JavaHL and commited to
> trunk.  Until this version is released and packaged, could you please
> add the attached file to debian/patches?

Ah, yeah, I see, r1234864 upstream.  Sure, I'll do the equivalent in my
next upload, which I really really hope to have time to do this weekend
(I've tried to find time for months, maybe I finally can).

Peter



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

Bug#657682: gcc-4.6: assembler error on armhf Error: can't resolve `.rodata' {.rodata section} - `.LPIC10' {*UND* section}

[peter green]

I have reduced this to the attatched testcase
sorry, screwed up trying to attatch the file in reportbug, here's the 
testcase.
/* -*- Mode: C; tab-width: 8; indent-tabs-mode: t; c-basic-offset: 8 -*- */
/*  GMime
 *  Copyright (C) 2000-2010 Jeffrey Stedfast
 *
 *  This library is free software; you can redistribute it and/or
 *  modify it under the terms of the GNU Lesser General Public License
 *  as published by the Free Software Foundation; either version 2.1
 *  of the License, or (at your option) any later version.
 *
 *  This library is distributed in the hope that it will be useful,
 *  but WITHOUT ANY WARRANTY; without even the implied warranty of
 *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 *  Lesser General Public License for more details.
 *
 *  You should have received a copy of the GNU Lesser General Public
 *  License along with this library; if not, write to the Free
 *  Software Foundation, 51 Franklin Street, Fifth Floor, Boston, MA
 *  02110-1301, USA.
 */


#include 
#include 
#include 
#include 

typedef struct _GMimeParam GMimeParam;


/**
 * GMimeParam:
 * @next: Pointer to the next param.
 * @name: Parameter name.
 * @value: Parameter value.
 *
 * A parameter name/value pair as used for some Content header fields.
 **/
struct _GMimeParam {
	GMimeParam *next;
	char *name;
	char *value;
};

#include 
static unsigned short gmime_special_table[256] = {1029};

enum {
	IS_CTRL = (1 << 0),
	IS_LWSP = (1 << 1),
	IS_TSPECIAL = (1 << 2),
	IS_SPECIAL  = (1 << 3),
	IS_SPACE= (1 << 4),
	IS_DSPECIAL = (1 << 5),
	IS_QPSAFE   = (1 << 6),
	IS_ESAFE= (1 << 7),  /* encoded word safe */
	IS_PSAFE= (1 << 8),  /* encode word in phrase safe */
	IS_ATTRCHAR = (1 << 9),  /* attribute-char from rfc2184 */
	
	/* ctype replacements */
	IS_ASCII= (1 << 10), /* ascii */
	IS_BLANK= (1 << 11), /* space or tab */
};

#define is_ctrl(x) ((gmime_special_table[(unsigned char)(x)] & IS_CTRL) != 0)
#define is_lwsp(x) ((gmime_special_table[(unsigned char)(x)] & IS_LWSP) != 0)
#define is_tspecial(x) ((gmime_special_table[(unsigned char)(x)] & IS_TSPECIAL) != 0)
#define is_type(x, t) ((gmime_special_table[(unsigned char)(x)] & (t)) != 0)
#define is_ttoken(x) ((gmime_special_table[(unsigned char)(x)] & (IS_TSPECIAL|IS_LWSP|IS_CTRL)) == 0)
#define is_atom(x) ((gmime_special_table[(unsigned char)(x)] & (IS_SPECIAL|IS_SPACE|IS_CTRL)) == 0)
#define is_dtext(x) ((gmime_special_table[(unsigned char)(x)] & IS_DSPECIAL) == 0)
#define is_fieldname(x) ((gmime_special_table[(unsigned char)(x)] & (IS_CTRL|IS_SPACE)) == 0)
#define is_qpsafe(x) ((gmime_special_table[(unsigned char)(x)] & IS_QPSAFE) != 0)
#define is_especial(x) ((gmime_special_table[(unsigned char)(x)] & IS_ESAFE) != 0)
#define is_psafe(x) ((gmime_special_table[(unsigned char)(x)] & IS_PSAFE) != 0)
#define is_attrchar(x) ((gmime_special_table[(unsigned char)(x)] & IS_ATTRCHAR) != 0)

/* ctype replacements */
#define is_ascii(x) ((gmime_special_table[(unsigned char)(x)] & IS_ASCII) != 0)
#define is_blank(x) ((gmime_special_table[(unsigned char)(x)] & IS_BLANK) != 0)

#define CHARS_LWSP " \t\n\r"   /* linear whitespace chars */
#define CHARS_TSPECIAL "()<>@,;:\\\"/[]?="
#define CHARS_SPECIAL "()<>@,;:\\\".[]"
#define CHARS_CSPECIAL "()\\\r"	   /* not in comments */
#define CHARS_DSPECIAL "[]\\\r \t" /* not in domains */
#define CHARS_ESPECIAL "()<>@,;:\"/[]?.=_" /* encoded word specials (rfc2047 5.1) */
#define CHARS_PSPECIAL "!*+-/=_"   /* encoded phrase specials (rfc2047 5.3) */
#define CHARS_ATTRCHAR "*'% "  /* attribute-char from rfc2184 */

#define GMIME_FOLD_LEN 76

#define w(x)
#define d(x)



static char *
decode_value (const char **in)
{
	const char *inptr = *in;
	
	
	if (*inptr == '"') {
		return decode_quoted_string (in);
	} else if (is_ttoken (*inptr)) {
		return decode_token (in);
	}
	

	return decode_token (in);

}

static char *
decode_param_token (const char **in)
{
	const char *inptr = *in;
	while (is_ttoken (*inptr) && *inptr != '*')
		inptr++;
}

static gboolean
decode_rfc2184_param (const char **in, char **paramp, int *part, gboolean *encoded)
{
	
	const char *inptr = *in;
	decode_param_token (&inptr);
	
}

static gboolean
decode_param (const char **in, char **paramp, char **valuep, int *id, gboolean *encoded)
{
	gboolean is_rfc2184 = FALSE;
	const char *inptr = *in;
	char *param, *value = NULL;
	char *val;
	
	is_rfc2184 = decode_rfc2184_param (&inptr, ¶m, id, encoded);
	
	if (*inptr == '=') {
		inptr++;
		value = decode_value (&inptr);
		
		if (!is_rfc2184 && value) {
			if (strstr (value, "=?") != NULL) {
/* We (may) have a broken param value that is rfc2047
 * encoded. Since both Outlook and Netscape/Mozilla do
 * this, we should handle this case.
 */

if ((val = g_mime_utils_header_decode_text (value))) {
	g_free (value);
	value = val;
}
			}
			
			if (!g_utf8_validate (value, -1, NULL)) {
/* A (broken) mail

Bug#657676: sysvinit: FTBFS on kfreebsd due to missing sys/signalfd.h

[Roger Leigh]

severity 657676 serious
thanks

On Fri, Jan 27, 2012 at 11:50:15PM +0100, Guillem Jover wrote:
> On Fri, 2012-01-27 at 21:42:17 +, Roger Leigh wrote:
> > startpar.c:45:26: fatal error: sys/signalfd.h: No such file or directory
> > This needs a kfreebsd workaround (also fails on kfreebsd-i386).
> 
> signalfd is a Linux only interface (see [0]), BSD based systems can use
> kqueue instead, also Solaris through libkqueue, for GNU/Hurd I'm not sure
> what's the equivalent. In any case this worked fine with -18, so given
> the extent of this regression wouldn't reverting back to the previous
> startpar be the ideal solution for now? Or does the new code base give
> significant improvements?

Unsure.  We were on 0.53.1, and the new version is 0.58.  It merged
all of the existing Debian patchset, so is desirable from this POV.
The lack of upstream version control or changelog (that I'm aware of)
does not help matters.  Possibly we can back out just the signalfd
change, or add kfreebsd/hurd-specific ifdefs for its use.

Looking at the source, I see no evidence of actual signalfd usage,
so just not including the header may fix this universally.  Certainly
removing it on Linux does not break compilation.

> Also this seems should be of serious severity instead?

Yes, I set this with reportbug, not sure why it's normal.  Setting
appropriately.


Regards,
Roger

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



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

Bug#657672: chromium: Dialog to upload files does not show up

[Jonathan Nieder]

Frederik Schwarzer wrote:

> for about two weeks now, the dialog for uploading files to websites does
> not show up anymore.
> E.g. if I go to http://imagebin.org/index.php?page=add, the "Choose
> file" button does nothing. Same goes for every website I tried.

In other words, '' tags produce a button that doesn't
work for you.  Very odd.  Works for me™.

Does downgrading to some previous version from testing or
http://snapshot.debian.org/ help?  Do you use GNOME, KDE, or some other
environment?  Does "dmesg" reveal anything having segfaulted?

Puzzled,
Jonathan



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

Bug#657598: freebsd-libs: FTBFS on kfreebsd-i386

[Christoph Egger]

Hi!

Steven Chamberlain  writes:
> kfreebsd-kernel-headers 0.67 already fixed that for #656947 -- how often
> do the buildd's upgrade packages?

  For normal packages, they are used on the buildds even before they hit
the normal archive (get used once they're in incoming). For everything
that's part of build-essential only on manual action.

Regards

Christoph (upgrading buildds now)

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer



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

Bug#657683: haveged: new version 1.3a available

[Sven Hartge]

Package: haveged
Version: 1.1-2
Severity: wishlist

Hi!

A new version 1.3a is available from
http://www.issihosts.com/haveged/downloads.html, please update the package.

Grüße,
Sven.

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

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

Versions of packages haveged depends on:
ii  libc6 2.13-24
ii  lsb-base  3.2-28.1

haveged recommends no packages.

haveged 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#657682: gcc-4.6: assembler error on armhf Error: can't resolve `.rodata' {.rodata section} - `.LPIC10' {*UND* section}

[Peter Green]

Package: gcc-4.6
Version: 4.6.2-12
Severity: important

Gmime failed to build on armhf with the following error

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../util 
-DGMIME_VERSION=\"2.4.31\" -DGMIME_MAJOR_VERSION=2 -DGMIME_MINOR_VERSION=4 
-DGMIME_MICRO_VERSION=31 -DG_LOG_DOMAIN=\"gmime\" -DG_DISABLE_DEPRECATED 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pthread -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -g -O2 -fno-strict-aliasing -c 
gmime-param.c  -fPIC -DPIC -o .libs/gmime-param.o
/tmp/cc1SBNmj.s: Assembler messages:
/tmp/cc1SBNmj.s:2152: Error: can't resolve `.rodata' {.rodata section} - 
`.LPIC18' {*UND* section}
make[5]: *** [gmime-param.lo] Error 1

I have reduced this to the attatched testcase, to build the testcase use the
following command.

gcc -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -O2 
-c test.c  -fPIC

I attempted to reduce it further but any further significant code removals
I did made the error go away.

removing -fPIC makes the error go away as does reducing the optimisation level
to -O1

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

Kernel: Linux 2.6.39.2-x2 (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 gcc-4.6 depends on:
ii  binutils  2.22-4
ii  cpp-4.6   4.6.2-12
ii  gcc-4.6-base  4.6.2-12
ii  libc6 2.13-24
ii  libgcc1   1:4.6.2-12
ii  libgmp10  2:5.0.2+dfsg-2+b1
ii  libgomp1  4.6.2-12
ii  libmpc2   0.9-4+b1
ii  libmpfr4  3.1.0-3+b1
ii  zlib1g1:1.2.3.4.dfsg-3+b1

Versions of packages gcc-4.6 recommends:
ii  libc6-dev  2.13-24

Versions of packages gcc-4.6 suggests:
pn  binutils-gold
pn  gcc-4.6-doc  
pn  gcc-4.6-locales  
pn  libgcc1-dbg  
pn  libgomp1-dbg 
pn  libmudflap0-4.6-dev  
pn  libmudflap0-dbg  
pn  libquadmath-dbg  

-- no debconf information



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

Bug#657598: freebsd-libs: FTBFS on kfreebsd-i386

[Steven Chamberlain]

On 27/01/12 23:00, Christoph Egger wrote:
> /build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/sys/cam/cam.h:228:5:
>  note: expected 'const u_int8_t *' but argument is of type 'char *'
> cc -Wall -g -pipe -fPIC -I. 
> -I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/sys
>  -D_GNU_SOURCE -isystem /usr/include/bsd -DLIBBSD_OVERLAY   
> -D__va_list=__builtin_va_list -O2 -isystem /usr/include/freebsd 
> -I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/debian/local/include
>   
> -I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam
>  
> -I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam/../../sys
>  -std=gnu99 -fstack-protector  -c 
> /build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam/../../sys/cam/scsi/scsi_da.c
> cc -Wall -g -pipe -fPIC -I. 
> -I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/sys
>  -D_GNU_SOURCE -isystem /usr/include/bsd -DLIBBSD_OVERLAY   
> -D__va_list=__builtin_va_list -O2 -isystem /usr/include/freebsd 
> -I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/debian/local/include
>   
> -I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam
>  
> -I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam/../../sys
>  -std=gnu99 -fstack-protector  -c 
> /build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam/../../sys/cam/scsi/scsi_sa.c
> In file included from /usr/include/machine/_types.h:8:0,
>  from /usr/include/sys/_types.h:33,
>  from /usr/include/sys/devicestat.h:36,
>  from 
> /build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam/../../sys/cam/scsi/scsi_sa.c:48:
> /usr/include/machine-i386/_types.h:96:19: error: conflicting types for 
> '__time_t'
> /usr/include/i386-kfreebsd-gnu/bits/types.h:149:26: note: previous 
> declaration of '__time_t' was here

Hi Christoph,

kfreebsd-kernel-headers 0.67 already fixed that for #656947 -- how often
do the buildd's upgrade packages?

On 25/01/12 21:41, Debian Bug Tracking System wrote:
> Changes:
>  kfreebsd-kernel-headers (0.67) unstable; urgency=low
>  .
>* s/time_t/__time_t/ in struct bintime.


After the buildd's have kfreebsd-kernel-headers 0.67, php5 could also be
rebuilt because it failed to build with the same error.

From
https://buildd.debian.org/status/fetch.php?pkg=php5&arch=kfreebsd-i386&ver=5.3.9-3&stamp=1327684719
:
> libtool: compile:  i486-kfreebsd-gnu-gcc -IZend/ 
> -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/Zend/ 
> -DPHP_ATOM_INC 
> -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/apache2filter-build/include
>  
> -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/apache2filter-build/main
>  -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9 
> -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/apache2filter-build/ext/date/lib
>  -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/ext/date/lib 
> -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/ext/ereg/regex 
> -I/usr/include/libxml2 
> -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/ext/mbstring/libmbfl
>  
> -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/apache2filter-build/ext/mbstring/libmbfl
>  
> -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/ext/mbstring/libmbfl/mbfl
>  
> -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/apache2filter-build/ex
t/mbstring/libmbfl/mbfl 
-I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/apache2filter-build/TSRM
 
-I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/apache2filter-build/Zend
 -I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/main 
-I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/Zend 
-I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/TSRM 
-I/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/apache2filter-build/
 -I/usr/include -O2 -Wall -fsigned-char -fno-strict-aliasing 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -gstabs -fvisibility=hidden -c 
/build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/Zend/zend_stream.c  
-fPIC -DPIC -o Zend/.libs/zend_stream.o
> In file included from /usr/include/machine/_types.h:8:0,
>  from /usr/include/sys/_types.h:33,
>  from /usr/include/net-snmp/system/kfreebsd.h:8,
>  from /usr/include/net-snmp/net-snmp-config.h:1766,
>  from 
> /build/buildd-php5_5.3.9-3-kfreebsd-i386-_gR1b0/php5-5.3.9/ext/snmp/snmp.c:73:
> /usr/include/machin

Bug#657529: Patch for stable version

[Matt Kraai]

Hi,

I've attached a patch that should fix this problem to this message.
It's based on the patch used to fix this problem in unstable, which
doesn't apply cleanly to the stable version.  I wasn't sure what do to
about the patch headers, so I left them unchanged.  Should I upload a
fixed package somewhere?

-- 
Matt Kraai
https://ftbfs.org/kraai
commit 65f82df0d7a71ce1b10cd4c5ab0d176ac840
Author: Anthony Liguori 
Date:   Mon Jan 23 07:30:43 2012 -0600

e1000: bounds packet size against buffer size

Otherwise we can write beyond the buffer and corrupt memory.  This is tracked
as CVE-2012-0029.

Signed-off-by: Anthony Liguori 

Index: qemu-kvm-0.12.5+dfsg/hw/e1000.c
===
--- qemu-kvm-0.12.5+dfsg.orig/hw/e1000.c	2010-07-26 17:43:53.0 -0700
+++ qemu-kvm-0.12.5+dfsg/hw/e1000.c	2012-01-27 14:57:35.0 -0800
@@ -453,6 +453,8 @@
 bytes = split_size;
 if (tp->size + bytes > msh)
 bytes = msh - tp->size;
+
+bytes = MIN(sizeof(tp->data) - tp->size, bytes);
 cpu_physical_memory_read(addr, tp->data + tp->size, bytes);
 if ((sz = tp->size + bytes) >= hdr && tp->size < hdr)
 memmove(tp->header, tp->data, hdr);
@@ -468,6 +470,7 @@
 // context descriptor TSE is not set, while data descriptor TSE is set
 DBGOUT(TXERR, "TCP segmentaion Error\n");
 } else {
+split_size = MIN(sizeof(tp->data) - tp->size, split_size);
 cpu_physical_memory_read(addr, tp->data + tp->size, split_size);
 tp->size += split_size;
 }

Bug#657598: freebsd-libs: FTBFS on kfreebsd-i386

[Christoph Egger]

Hi all!

Steven Chamberlain  writes:
>> Steven Chamberlain  writes:
>>> On 27/01/12 10:57, Niels Thykier wrote:
>>> Bug#657602 was filed right after #657598 and is a duplicate of this issue.
>> It just needs the buildd maintainer (me in this case) being aware of
>> it. You can mail kfreebsd-i...@buildd.debian.org for these
>> cases.
>
> Thanks!  I was still trying to figure out who to mail about this...

  Now failing a few lines further down there (reassigning to 
kfreebsd-kernel-headers?):

/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/sys/cam/cam.h:228:5:
 note: expected 'const u_int8_t *' but argument is of type 'char *'
cc -Wall -g -pipe -fPIC -I. 
-I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/sys
 -D_GNU_SOURCE -isystem /usr/include/bsd -DLIBBSD_OVERLAY   
-D__va_list=__builtin_va_list -O2 -isystem /usr/include/freebsd 
-I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/debian/local/include
  
-I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam
 
-I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam/../../sys
 -std=gnu99 -fstack-protector  -c 
/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam/../../sys/cam/scsi/scsi_da.c
cc -Wall -g -pipe -fPIC -I. 
-I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/sys
 -D_GNU_SOURCE -isystem /usr/include/bsd -DLIBBSD_OVERLAY   
-D__va_list=__builtin_va_list -O2 -isystem /usr/include/freebsd 
-I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/debian/local/include
  
-I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam
 
-I/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam/../../sys
 -std=gnu99 -fstack-protector  -c 
/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam/../../sys/cam/scsi/scsi_sa.c
In file included from /usr/include/machine/_types.h:8:0,
 from /usr/include/sys/_types.h:33,
 from /usr/include/sys/devicestat.h:36,
 from 
/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam/../../sys/cam/scsi/scsi_sa.c:48:
/usr/include/machine-i386/_types.h:96:19: error: conflicting types for 
'__time_t'
/usr/include/i386-kfreebsd-gnu/bits/types.h:149:26: note: previous declaration 
of '__time_t' was here
*** Error code 1

Stop in 
/build/buildd-freebsd-libs_8.3~svn229725-3-kfreebsd-i386-U78vkA/freebsd-libs-8.3~svn229725/lib/libcam.
make: *** [build-cam-stamp] Error 1

Regards

Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer



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

Bug#657425: mozjs FTBFS on Alpha: symbol files need update

[Michael Cree]

tags 657425 patch
thanks

patch for updating debian/libmozjs185-1.0.symbols to be correct for
Alpha attached.

Cheers
Michael.
--- mozjs-1.8.5-1.0.0+dfsg.orig/debian/libmozjs185-1.0.symbols	2012-01-25 12:11:56.0 +1300
+++ mozjs-1.8.5-1.0.0+dfsg/debian/libmozjs185-1.0.symbols	2012-01-28 11:25:00.0 +1300
@@ -529,16 +529,16 @@
  (arch=armhf)JaegerThrowpoline@Base 1.8.5-1.0.0+dfsg
  (arch=armhf)JaegerTrampoline@Base 1.8.5-1.0.0+dfsg
  (arch=armhf)JaegerTrampolineReturn@Base 1.8.5-1.0.0+dfsg
- (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPi@Base 1.8.5-1.0.0+dfsg
- (arch=amd64 ia64 kfreebsd-amd64 s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPl@Base 1.8.5-1.0.0+dfsg
+ (arch=!alpha !amd64 !ia64 !kfreebsd-amd64 !s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPi@Base 1.8.5-1.0.0+dfsg
+ (arch=alpha amd64 ia64 kfreebsd-amd64 s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPl@Base 1.8.5-1.0.0+dfsg
  _Z14js_DateGetDateP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
  _Z14js_DateGetYearP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
  _Z14js_DateIsValidP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
  _Z14js_IntervalNowv@Base 1.8.5-1.0.0+dfsg
  _Z15js_DateGetHoursP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
  _Z15js_DateGetMonthP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
- (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x)_Z15js_FindPropertyP9JSContextiPP8JSObjectS3_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
- (arch=amd64 ia64 kfreebsd-amd64 s390x)_Z15js_FindPropertyP9JSContextlPP8JSObjectS3_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
+ (arch=!alpha !amd64 !ia64 !kfreebsd-amd64 !s390x)_Z15js_FindPropertyP9JSContextiPP8JSObjectS3_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
+ (arch=alpha amd64 ia64 kfreebsd-amd64 s390x)_Z15js_FindPropertyP9JSContextlPP8JSObjectS3_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
  _Z15js_IsTypedArrayP8JSObject@Base 1.8.5-1.0.0+dfsg
  _Z16js_CloseIteratorP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
  _Z16js_IsArrayBufferP8JSObject@Base 1.8.5-1.0.0+dfsg
@@ -546,8 +546,8 @@
  _Z16js_ValueToSourceP9JSContextRKN2js5ValueE@Base 1.8.5-1.0.0+dfsg
  _Z17js_DateGetMinutesP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
  _Z17js_DateGetSecondsP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
- (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x)_Z17js_LookupPropertyP9JSContextP8JSObjectiPS2_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
- (arch=amd64 ia64 kfreebsd-amd64 s390x)_Z17js_LookupPropertyP9JSContextP8JSObjectlPS2_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
+ (arch=!alpha !amd64 !ia64 !kfreebsd-amd64 !s390x)_Z17js_LookupPropertyP9JSContextP8JSObjectiPS2_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
+ (arch=alpha amd64 ia64 kfreebsd-amd64 s390x)_Z17js_LookupPropertyP9JSContextP8JSObjectlPS2_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
  _Z17js_ObjectIsRegExpP8JSObject@Base 1.8.5-1.0.0+dfsg
  (subst)_Z18JS_StructuredCloneP9JSContext{uint64_t}P{uint64_t}PFP8JSObjectS0_P23JSStructuredCloneReaderjjPvEPK26JSStructuredCloneCallbacksS6_@Base 1.8.5-1.0.0+dfsg
  _Z18js_ConsumeJSONTextP9JSContextP10JSONParserPKtj12DecodingMode@Base 1.8.5-1.0.0+dfsg
@@ -571,11 +571,11 @@
  _Z24js_DateGetMsecSinceEpochP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
  (arch=!s390 !s390x)_Z24js_InitTypedArrayClassesP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
  _Z24js_IsDensePrimitiveArrayP8JSObject@Base 1.8.5-1.0.0+dfsg
- (subst|arch=!amd64 !ia64 !kfreebsd-amd64 !s390x)_Z25js_GetterOnlyPropertyStubP9JSContextP8JSObjectiiP{uint64_t}@Base 1.8.5-1.0.0+dfsg
- (subst|arch=amd64 ia64 kfreebsd-amd64 s390x)_Z25js_GetterOnlyPropertyStubP9JSContextP8JSObjectliP{uint64_t}@Base 1.8.5-1.0.0+dfsg
+ (subst|arch=!alpha !amd64 !ia64 !kfreebsd-amd64 !s390x)_Z25js_GetterOnlyPropertyStubP9JSContextP8JSObjectiiP{uint64_t}@Base 1.8.5-1.0.0+dfsg
+ (subst|arch=alpha amd64 ia64 kfreebsd-amd64 s390x)_Z25js_GetterOnlyPropertyStubP9JSContextP8JSObjectliP{uint64_t}@Base 1.8.5-1.0.0+dfsg
  _Z27js_CloneDensePrimitiveArrayP9JSContextP8JSObjectPS2_@Base 1.8.5-1.0.0+dfsg
  _Z27js_ReportAllocationOverflowP9JSContext@Base 1.8.5-1.0.0+dfsg
- (arch=!ia64 !mips !mipsel !powerpc !s390 !s390x)_Z27js_SetTraceableNativeFailedP9JSContext@Base 1.8.5-1.0.0+dfsg
+ (arch=!alpha !ia64 !mips !mipsel !powerpc !s390 !s390x)_Z27js_SetTraceableNativeFailedP9JSContext@Base 1.8.5-1.0.0+dfsg
  _Z28js_CreateTypedArrayWithArrayP9JSContextiP8JSObject@Base 1.8.5-1.0.0+dfsg
  _Z28js_ReparentTypedArrayToScopeP9JSContextP8JSObjectS2_@Base 1.8.5-1.0.0+dfsg
  _Z29js_CreateTypedArrayWithBufferP9JSContextiP8JSObjectii@Base 1.8.5-1.0.0+dfsg
@@ -597,15 +597,15 @@
  _ZN13JSCompartment4wrapEP9JSContextPN2js5ValueE@Base 1.8.5-1.0.0+dfsg
  _ZN13JSCompartment4wrapEP9JSContextPP8JSObject@Base 1.8.5-1.0.0+dfsg
  _ZN13JSCompartment4wrapEP9JSContextPP8JSString@Base 1.8.5-1.0.0+dfsg
- (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x)_ZN13JSCompartment4wrapEP9JSContextPPFiS1_P8JSObjectiPN2js5ValueEE@Base 1.8.5-1.0.0+dfsg
- (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x)_ZN13JSCompartment4wr

Bug#657676: sysvinit: FTBFS on kfreebsd due to missing sys/signalfd.h

[Guillem Jover]

Hi!

On Fri, 2012-01-27 at 21:42:17 +, Roger Leigh wrote:
> Package: sysvinit
> Version: 2.88dsf-19
> Severity: normal
> 
> cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Wformat-security -Werror=format-security -W -Wall -D_GNU_SOURCE  
> -DACCTON_OFF  -c -o last.o last.c
> cc -Wl,-z,relro  last.o oldutmp.h   -o last
> cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Wformat-security -Werror=format-security -W -Wall -D_GNU_SOURCE  
> -DACCTON_OFF  -c -o mesg.o mesg.c
> cc -Wl,-z,relro  mesg.o   -o mesg
> make[2]: Leaving directory 
> `/build/buildd-sysvinit_2.88dsf-19-kfreebsd-amd64-q08mr8/sysvinit-2.88dsf/src'
> /usr/bin/make  -C startpar
> make[2]: Entering directory 
> `/build/buildd-sysvinit_2.88dsf-19-kfreebsd-amd64-q08mr8/sysvinit-2.88dsf/startpar'
> gcc   -D_GNU_SOURCE  -Wall -W -pipe -DVERSION=\"0.58\" -DNOTSUSE -c startpar.c
> startpar.c:45:26: fatal error: sys/signalfd.h: No such file or directory
> compilation terminated.
> make[2]: *** [startpar.o] Error 1
> make[2]: Leaving directory 
> `/build/buildd-sysvinit_2.88dsf-19-kfreebsd-amd64-q08mr8/sysvinit-2.88dsf/startpar'
> make[1]: *** [override_dh_auto_build] Error 2
> make[1]: Leaving directory 
> `/build/buildd-sysvinit_2.88dsf-19-kfreebsd-amd64-q08mr8/sysvinit-2.88dsf'
> make: *** [build] Error 2
> 
> This needs a kfreebsd workaround (also fails on kfreebsd-i386).

signalfd is a Linux only interface (see [0]), BSD based systems can use
kqueue instead, also Solaris through libkqueue, for GNU/Hurd I'm not sure
what's the equivalent. In any case this worked fine with -18, so given
the extent of this regression wouldn't reverting back to the previous
startpar be the ideal solution for now? Or does the new code base give
significant improvements?

Also this seems should be of serious severity instead?

[0] 

thanks,
guillem



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

Bug#389258: Request for permission to NMU memtest86

[Aurelien Jarno]

The current version of memtest86 in unstable is 3 years old, and doesn't
really support machines with >= 4GB of RAM. Given this kind of machine
is quite common nowadays, memtest86 is not really usable anymore.

Version 4.0a supports 4GB of RAM, and is also able to use multiple CPUs
for faster and better testing.

The patch below is the diff of the debian/ directory necessary to bring
the version to 4.0a. It can be used directly with the upstream tarball.
Would it be possible to upload it as an NMU?

--- memtest86-3.5/debian/changelog  2012-01-27 11:36:16.0 +0100
+++ memtest86-4.0a/debian/changelog 2012-01-27 11:34:08.590168321 +0100
@@ -1,3 +1,13 @@
+memtest86 (4.0a-0.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * New upstream version (Closes: #622395):
+- Support machines with >= 4GB of RAM.  Closes: #522525, #572347, #582610,
+  #647756.
+- Fix build with -O3.  Closes: #389258.
+
+ -- Aurelien Jarno   Fri, 27 Jan 2012 23:49:59 +0100
+
 memtest86 (3.5-2.3) unstable; urgency=low
 
   * Non-maintainer upload.

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: Digital signature

Bug#657681: htop: Nevative CPU usage time shown

[micham]

Package: htop
Version: 0.8.3-1
Severity: normal
Tags: patch



htop shows negative cpu usage time:

  PID USER  PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command
 9785  user  20   0  325M  236M  1860 S  0.0  1.5  0:00.12 ./mprime
 9792  user  39  19  325M  236M  1860 R  0.0  1.5 -596523h-14:-8 ./mprime
 9796  user  39  19  325M  236M  1860 R  0.0  1.5 -596523h-14:-8 ./mprime
 9797  user  39  19  325M  236M  1860 R  0.0  1.5 -596523h-14:-8 ./mprime
 9798  user  39  19  325M  236M  1860 R  0.0  1.5 -596523h-14:-8 ./mprime
 9781  user  30  10  325M  236M  1860 S  0.0  1.5 -596523h-14:-8 ./mprime

This is caused by an integer overflow. The high number is comming from the 
Kernel: (e.g.)
 user@kvm:~$ cat /proc/9781/task/9798/stat
9798 (mprime) R 4413 9781 4413 34824 9781 4202560 46384 0 4 0 13739580949 
918902298809 0 0 39 19 6 0 46913565 341078016 60514 18446744073709551615 
4194304 29585884 140735277536320 139701526982104 17369198 0 0 0 16386 0 0 0 -1 
3 0 0 9183 0 0

918902298809 + 13739580949 is quite a large number (>2^31-1)

Int should actually be enough at that place.


>From 1f5d6f44731482f76262ee71179a1ded3a0bf737 Mon Sep 17 00:00:00 2001
From: Micha M. 
Date: Fri, 27 Jan 2012 22:00:43 +0100
Subject: [PATCH] Fix integer overflow

Without this fix I get something like:

  PID USER  PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command
 9785  user  20   0  325M  236M  1860 S  0.0  1.5  0:00.12 ./mprime
 9792  user  39  19  325M  236M  1860 R  0.0  1.5 -596523h-14:-8 ./mprime
 9796  user  39  19  325M  236M  1860 R  0.0  1.5 -596523h-14:-8 ./mprime
 9797  user  39  19  325M  236M  1860 R  0.0  1.5 -596523h-14:-8 ./mprime
 9798  user  39  19  325M  236M  1860 R  0.0  1.5 -596523h-14:-8 ./mprime
 9781  user  30  10  325M  236M  1860 S  0.0  1.5 -596523h-14:-8 ./mprime

After:

  PID USER PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command
 9781  user 30  10  325M  236M  1860 S  0.0  1.5  0:00.01 ./mprime
 9785  user 20   0  325M  236M  1860 S  0.0  1.5  0:00.12 ./mprime
 9792  user 39  19  325M  236M  1860 R  0.0  1.5 2590671h22:11 ./mprime
 9796  user 39  19  325M  236M  1860 R  0.0  1.5 2581130h26:17 ./mprime
 9797  user 39  19  325M  236M  1860 R  0.0  1.5 2562047h47:16 ./mprime
 9798  user 39  19  325M  236M  1860 R  0.0  1.5 2590671h53:17 ./mprime

It looks like that there is a bug in the Linux Kernel:

 user@kvm:~$ cat /proc/9781/task/9798/stat
9798 (mprime) R 4413 9781 4413 34824 9781 4202560 46384 0 4 0 13739580949 
918902298809 0 0 39 19 6 0 46913565 341078016 60514 18446744073709551615 
4194304 29585884 140735277536320 139701526982104 17369198 0 0 0 16386 0 0 0 -1 
3 0 0 9183 0 0
 user@kvm:~$ uname -a
Linux kvm 2.6.32-5-amd64 #1 SMP Thu Nov 3 03:41:26 UTC 2011 x86_64 GNU/Linux
 user@kvm:~$

Signed-off-by: Micha M. 
---
 Process.c |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Process.c b/Process.c
index 8f3762c..0cc990f 100644
--- a/Process.c
+++ b/Process.c
@@ -236,7 +236,7 @@ static void Process_printTime(RichString* str, unsigned 
long t) {
double jiffytime = 1.0 / jiffy;
 
double realTime = t * jiffytime;
-   int iRealTime = (int) realTime;
+   long long iRealTime = (long long) realTime;
 
int hours = iRealTime / 3600;
int minutes = (iRealTime / 60) % 60;
-- 
1.7.0.4




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

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

Versions of packages htop depends on:
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib
ii  libncurses5   5.7+20100313-5 shared libraries for terminal hand

htop recommends no packages.

Versions of packages htop suggests:
pn  ltrace (no description available)
pn  strace (no description available)

-- no debconf information



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

Bug#657680: realtime support for followme is underdocumented

[Clint Adams]

Package: asterisk
Version: 1:1.6.2.9-2+squeeze4

I am trying to enable a Realtime config for FollowMe, but asterisk
either complains or crashes.  I suspect that I am doing something
wrong, but there isn't much to go on beyond doc/followme.txt and
the source.



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

Bug#657579: usb-modeswitch: usb_modeswitch_dispatcher Segmentation fault on armhf

[Josua Dietze]

Am 27.01.2012 08:46, schrieb Belousow Makc:

Package: usb-modeswitch
Version: 1.2.2+repack0-1
Severity: important

Dear Maintainer,
usb_modeswitch_dispatcher have Segmentation fault on Debian armhf:

#1  0xb6eea8cc in _IO_vfprintf_internal (s=, format=, ap=...) at vfprintf.c:1620


I think this is the known bug 656688:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656688

Can you try the patched source pack provided there?

Josua Dietze



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

Bug#657659: pcalendar: Cannot set the duration of menstruation

[Andreas Tille]

Hi Maryan,

as you might know (and hopefully like) your pcalendar application is
included into Debian distrubution.  This was done thanks to Miriam who
has done the actual packaging and it maintained in the Debian Med team
which tries to support any application which is relevant to some extand
to health care.

As you can read below a user has reported a bug in pcalendar and
there is another one available here:

   http://bugs.debian.org/pcalendar

Do you see any chance to fix these two reported problems and keep us
informed?

Kind regards and thanks for providing pcalendar as Free Software

 Andreas.

- Forwarded message from Mikolaj Menke  -

Date: Fri, 27 Jan 2012 20:03:08 +0100
From: Mikolaj Menke 
To: Debian Bug Tracking System 
Subject: Bug#657659: pcalendar: Cannot set the
duration of menstruation

Package: pcalendar
Version: 3.2.0-2
Severity: wishlist


One cannot set the duration of menstruation so that it would be visible
on the dashboard. Only the first day of a period and the ovulation can be set.

-- System Information:
Debian Release: 6.0.3
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (100, 'unstable'), 
(100, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash

Versions of packages pcalendar depends on:
ii  libxerces2-java2.9.1-4.1 Validating XML parser for Java wit
ii  openjdk-6-jre [jav 6b18-1.8.7-2~squeeze1 OpenJDK Java runtime, using Hotspo
ii  sun-java5-jre [jav 1.5.0-19-1Sun Java(TM) Runtime Environment (
ii  sun-java6-jre [jav 6.26-0squeeze1Sun Java(TM) Runtime Environment (

pcalendar recommends no packages.

pcalendar suggests no packages.

-- no debconf information



___
Debian-med-packaging mailing list
debian-med-packag...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging


- End forwarded message -

-- 
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#657598: freebsd-libs: FTBFS on kfreebsd-i386

[Steven Chamberlain]

> Steven Chamberlain  writes:
>> On 27/01/12 10:57, Niels Thykier wrote:
>> Bug#657602 was filed right after #657598 and is a duplicate of this issue.
> 
>   Jep didn't look carefully enough before filling. I've merged them
> however seconds after they both were visible

Hi,

They don't look merged in the web-based BTS?  Maybe because Package of
#657598 was wrong?

> It just needs the buildd maintainer (me in this case) being aware of
> it. You can mail kfreebsd-i...@buildd.debian.org for these
> cases.

Thanks!  I was still trying to figure out who to mail about this...

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



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

Bug#657679: Minor typo in debconf template

[Francesca Ciceri]

Package: namazu2
Severity: minor


Hi,

while translating it into Italian, I've found a little typo in namazu2
debconf template:

#: ../templates:1001
msgid ""
"Namazu package will be installed in /usr/lib/cgi-bin/namazu.cgi by
default. "
"But for VirtualHost, you may also need copy the cgi scripts to another "
"location. The cgi will be copied automaticaly on upgrade or
installation."

s/automaticaly/automatically/

Thanks,
Francesca
-- 
"People assume that time is a strict progression of cause to effect,
but actually from a non-linear, non-subjective viewpoint is more 
like a big ball of wibbly wobbly, timey wimey... stuff."
The Doctor


signature.asc
Description: Digital signature

Bug#657678: ITP: simplelxc -- Minimalist package to create LXC guests and then manage them simply.

[Bekir Dogan]

Package: wnpp
Severity: wishlist
Owner: Bekir Dogan 

* Package name: simplelxc
  Version : 0.1
  Upstream Author : Bekir Dogan 
* URL : https://github.com/bergerx/simplelxc#readme
* License : GPL
  Programming Lang: Shell script
  Description : Minimalist package to create LXC guests and then manage 
them simply.

Main objective is to make testing of any program easy on personal computers
(for now it works only for Debian systems) without losing time for these:
* does not require to manually configure networking on host system,
* does not require to manually create template,
* does not require to manually determining IP addresses,
* does not require to manually configuring any other parameters needed.

Just install simplelxc, create a guest and go.

Main purpose of this project is to handle only simple tasks, so if you want to
manage production lxc installation, you should consider using plain lxc
userspace control tool (http://lxc.sourceforge.net/) or projects like lxctl
(http://lxc.tl/).

Bekir Dogan



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

Bug#657598: freebsd-libs: FTBFS on kfreebsd-i386

[Christoph Egger]

Hi!

Steven Chamberlain  writes:
> On 27/01/12 10:57, Niels Thykier wrote:
> Bug#657602 was filed right after #657598 and is a duplicate of this issue.

  Jep didn't look carefully enough before filling. I've merged them
however seconds after they both were visible

>> /usr/include/sys/callout.h:43:26: fatal error: sys/_callout.h: No such file 
>> or directory
>
> This should be fixed in kfreebsd-kernel-headers 0.65
>
> freebsd-libs just needs a rebuild requested by a maintainer I think?

  It just needs the buildd maintainer (me in this case) being aware of
it. You can mail kfreebsd-i...@buildd.debian.org for these
cases. Doesn't need to be the maintainer to request it.

Regards

Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer



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

Bug#657677: tex-common: missing files in /usr/share/doc/tex-common

[Brenda J . Butler]

Package: tex-common
Version: 2.08.1
Severity: minor


I went to look at http://localhost/doc/tex-common/README.Debian.html,
which exists, but every link from that page is broken.  And the page
consists mostly of links.

Those links point to things like:

localhost/doc/tex-common/ch1.html
localhost/doc/tex-common/ch2.html#s-sec-texmf-trees
localhost/doc/tex-common/ch5.html

And those documents do not exist in my filesystem.

apt-search file does not find a(nother) package in which those files
belong.



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

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

Versions of packages tex-common depends on:
ii  debconf [debconf-2.0]1.5.36.1Debian configuration management sy
ii  dpkg 1.15.8.11   Debian package management system
ii  ucf  3.0025+nmu1 Update Configuration File: preserv

tex-common recommends no packages.

Versions of packages tex-common suggests:
ii  debhelper 8.0.0  helper programs for debian/rules

Versions of packages texlive-base depends on:
ii  dpkg  1.15.8.11  Debian package management system
ii  install-info  4.13a.dfsg.1-6 Manage installed documentation in 
ii  luatex0.60.2-1   next generation TeX engine
ii  mime-support  3.48-1 MIME files 'mime.types' & 'mailcap
ii  texlive-binaries  2009-8 Binaries for TeX Live
ii  texlive-common2009-11TeX Live: Base component
ii  texlive-doc-base  2009-2 TeX Live: TeX Live documentation

-- debconf information:
  tex-common/check_texmf_wrong:
  tex-common/check_texmf_missing:



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

Bug#657598: freebsd-libs: FTBFS on kfreebsd-i386

[Steven Chamberlain]

On 27/01/12 10:57, Niels Thykier wrote:
> Package: freebsd-libs

Should have been src:freebsd-libs

Bug#657602 was filed right after #657598 and is a duplicate of this issue.

> /usr/include/sys/callout.h:43:26: fatal error: sys/_callout.h: No such file 
> or directory

This should be fixed in kfreebsd-kernel-headers 0.65

freebsd-libs just needs a rebuild requested by a maintainer I think?

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



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