Bug#771719: tcplay: does not support discs with 4k sectors

[GCS]

Hi Ralf,

On Mon, Dec 1, 2014 at 10:10 PM, Ralf Jung  wrote:
> tcplay does not properly support discs with 4k sectors: They are opened, but
> reading from the disc produces wrong results, and writing to the discs results
> in data the official TrueCrypt cannot read. This can lead to irrecoverable
> data loss if any writes are performed on the disk.
>
> This was reported and fixed upstream a while ago already [1], so I assume
> version 2.0 (released more than half a year ago) fixed the problem.
 Yes, it seems it was fixed in 2.0, but it has a somewhat unclear
license. I've backported the fix for 1.1. But don't have any 4k discs
nearby, can you test it for me? You should build it for yourself[1]
and only in the last chance use my own binary packages for amd64[2] or
i386[3].

Thanks,
Laszlo/GCS
[1] dget -x http://www.barcikacomp.hu/gcs/tcplay_1.1-2.dsc
[2] http://www.barcikacomp.hu/gcs/tcplay_1.1-2_amd64.deb
[3] http://www.barcikacomp.hu/gcs/tcplay_1.1-2_i386.deb


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

Bug#750521: problems with scim and pin-entry

[Rolf Leggewie]

note to self: bug 712823 and bug 750521 sound surprisingly related


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

Processed: acknowledgement of reception RC bug report in scim from Debian maintainer

[Debian Bug Tracking System]

Processing control commands:

> tags 750521 + help
Bug #750521 [scim-gtk-immodule] scim-gtk-immodule breaks pinentry-gtk2 and 
impairs gnome-keyring
Ignoring request to alter tags of bug #750521 to the same tags previously set
> found 750521 1.4.14-6
Bug #750521 [scim-gtk-immodule] scim-gtk-immodule breaks pinentry-gtk2 and 
impairs gnome-keyring
Ignoring request to alter found versions of bug #750521 to the same values 
previously set

-- 
750521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: acknowledgement of reception RC bug report in scim from Debian maintainer

[Debian Bug Tracking System]

Processing control commands:

> tags 750521 + help
Bug #750521 [scim-gtk-immodule] scim-gtk-immodule breaks pinentry-gtk2 and 
impairs gnome-keyring
Added tag(s) help.
> found 750521 1.4.14-6
Bug #750521 [scim-gtk-immodule] scim-gtk-immodule breaks pinentry-gtk2 and 
impairs gnome-keyring
Marked as found in versions scim/1.4.14-6.

-- 
750521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#771768: antiword: CVE-2014-8123: buffer overflow of of atPPSlist[].szName[]

[Salvatore Bonaccorso]

Source: antiword
Version: 0.37-6
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerability was published for antiword.

CVE-2014-8123[0]:
buffer overflow of atPPSlist[].szName[] 

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2014-8123
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1169665
[2] http://seclists.org/oss-sec/2014/q4/870

Regards,
Salvatore


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

Bug#750521: acknowledgement of reception RC bug report in scim from Debian maintainer

[Rolf Leggewie]

Control: tags 750521 + help
Control: found 750521 1.4.14-6

On 27.11.2014 02:04, Daniel Kahn Gillmor wrote:
> On Wed 2014-11-26 12:49:47 -0500, Daniel Kahn Gillmor wrote:
>> I think i'm able to reproduce the problem (no keyboard input accepted in
>> pinentry-gtk-2) from a minimal gnome setup with just:

>   apt install im-config scim --no-recommends


Hello Lina, Ximin and Daniel,

thank you for the report and triage of this problem.  Much appreciated.
I apologize for the delay in response, I was offline on a remote island
for what was the Thanksgiving Weekend in the US.

I am sorry about the problems this issue has been causing you.  I am
still trying to verify the problem locally.  I'm downloading a live CD
now and will follow the steps that Daniel has generously provided to
test in a clean environment.

These kind of problems are usually the domain of my co-maintainer and
main upstream dev, Tz-Huan Huang.  I will CC him on this mail, but I do
not expect him to be able to respond for a while since he informed me
that he would be offline until about middle of December.  I am tagging
this ticket as "help" to indicate that I am hoping for other users and
devs to help with code inspection and coming up with a patch for jessie
to ensure a minimal delay.

Since this ticket was opened in June it means that at least 1.4.14-6 up
to 1.4.15-3 of scim would be affected.  Did anybody ever try the version
in stable which is 1.4.13-5?  It would be good to know what versions of
scim are known as affected and unaffected to speed up the remaining triage.

This is a quick heads-up to let everyone know that I am looking into
this as well as to kindly request help from others.  I shall write more
as I progress with this ticket.

Regards

Rolf


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

Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

[Didier Roche]

Control: severity -1 important
Control: tag -1 moreinfo

Hey,

I tried this morning on a vm (with multiple dms installed: lightdm, xdm, 
gdm and kdm) and when choosing kdm as the alternative to choose in the 
postinst and checking the status, all seems fine:

- all other units are disabled,
- display-manager.service is masked (as the default dm is an init script)
- generated kdm.service is chosen

Do you mind showing the output (as root) of:
systemctl status kdm.service
systemctl status display-manger.service

Thanks!


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

Processed: Re: Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #771653 [systemd] systemd 217 breaks X11 (not more kdm and loggin and using 
startx gives me no mouse)
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #771653 [systemd] systemd 217 breaks X11 (not more kdm and loggin and using 
startx gives me no mouse)
Ignoring request to alter tags of bug #771653 to the same tags previously set

-- 
771653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#771684: marked as done (/var/lib/dpkg/tmp.ci/preinst: 6: /var/lib/dpkg/tmp.ci/preinst: upgrade: not found)

[Debian Bug Tracking System]

Your message dated Tue, 02 Dec 2014 06:37:34 +
with message-id 
and subject line Bug#771684: fixed in chromium-browser 39.0.2171.71-2
has caused the Debian Bug report #771684,
regarding /var/lib/dpkg/tmp.ci/preinst: 6: /var/lib/dpkg/tmp.ci/preinst: 
upgrade: not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 39.0.2171.71-1
Severity: normal


Hi.

During upgrade the following error occurs:
Preparing to unpack .../chromium_39.0.2171.71-1_amd64.deb ...
/var/lib/dpkg/tmp.ci/preinst: 6: /var/lib/dpkg/tmp.ci/preinst: upgrade: not 
found
Unpacking chromium (39.0.2171.71-1) over (38.0.2125.101-3) ...


Cheers,
Chris.


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

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

Versions of packages chromium depends on:
ii  libasound2   1.0.28-1
ii  libc62.19-13
ii  libcairo21.14.0-2.1
ii  libcap2  1:2.24-6
ii  libcups2 1.7.5-9
ii  libdbus-1-3  1.8.12-1
ii  libexpat12.1.0-6+b3
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-2
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.25-1
ii  libharfbuzz0b0.9.35-2
ii  libjpeg62-turbo  1:1.3.1-11
ii  libnspr4 2:4.10.7-1
ii  libnspr4-0d  2:4.10.7-1
ii  libnss3  2:3.17.2-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpci3  1:3.2.1-3
ii  libspeechd2  0.8-6
ii  libspeex11.2~rc1.2-1
ii  libsrtp0 1.4.5~20130609~dfsg-1.1
ii  libstdc++6   4.9.2-4
ii  libudev1 215-7
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b1
ii  libxi6   2:1.7.4-1+b1
ii  libxml2  2.9.2+dfsg1-1
ii  libxrandr2   2:1.4.2-1+b1
ii  libxrender1  1:0.9.8-1+b1
ii  libxslt1.1   1.1.28-2+b2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+2
ii  xdg-utils1.1.0~rc1+git20111210-7.1

chromium recommends no packages.

Versions of packages chromium suggests:
ii  chromium-inspector  39.0.2171.71-1
ii  chromium-l10n   39.0.2171.71-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 39.0.2171.71-2

We believe that the bug you reported is fixed in the latest version of
chromium-browser, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 771...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium-browser 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 02 Dec 2014 01:30:33 +
Source: chromium-browser
Binary: chromium chromium-dbg chromium-l10n chromium-inspector chromedriver
Architecture: source i386 all
Version: 39.0.2171.71-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Maintainers 

Changed-By: Michael Gilbert 
Description:
 chromedriver - web browser - WebDriver support
 chromium   - web browser
 chromium-dbg - web browser - debugging symbols
 chromium-inspector - web browser - page inspection support
 chromium-l10n - web browser - language packs
Closes: 771684
Changes:
 chromium-browser (39.0.2171.71-2) unstable; urgency=medium
 .
   * Add missing test to chromium.preinst (closes: #771684).
Checksums-Sha1:
 01c245aa5798ed76039f14501c2ca34c620baef8 4032 
chromium-browser_39.0.2171.71-2.dsc
 fa41e682efc273b0f7463aae1ffbc95ae15e8c73 177736 
chromium-browser_39.0.2171.71-2.debian.tar.xz
 72fbcd826281e26f434c5727fd28b48f209eca42 3705933

Bug#771730: dpkg: yet another trigger cycle, involving initramfs-tools and libc-bin

[Guillem Jover]

Hi!

On Mon, 2014-12-01 at 23:26:32 +0100, Andreas Beckmann wrote:
> Package: dpkg
> Version: 1.17.22
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts

> with the latest dpkg I still get a trigger cycle error on a wheezy->sid
> piuparts upgrade test:
> 
>   Setting up libdevmapper1.02.1:amd64 (2:1.02.90-2) ...
>   Setting up dmsetup (2:1.02.90-2) ...
>   update-initramfs: deferring update (trigger activated)
>   dpkg: cycle found while processing triggers:
>chain of packages whose triggers are or may be responsible:
> initramfs-tools -> libc-bin
>packages' pending triggers which are or may be unresolvable:
> libc-bin: ldconfig
> initramfs-tools: update-initramfs
>   dpkg: error processing package libc-bin (--configure):
>triggers looping, abandoned
>   Errors were encountered while processing:
>libc-bin
> 
> Just verified that this is repeatable in piuparts and not a one-off
> failure.
> 
> The new dpkg was long installed and configured before this happened.
> Full log attached: nvidia-kernel-amd64_340.46+3.16.0+2.log.gz
> 
> I could not reproduce this in an upgrade from wheezy->jessie (i.e. with
> dpkg 1.17.21), full log: nvidia-kernel-amd64=340.46+3.16.0+1.log.gz
> but of course there are more package versions different ...

> If you need more debug information, tell me how to aquire it.
>
> I'm rather opening a new bug than messing with the ones that are supposed
> to be fixed in 1.17.22. This could be an independent issue or needs to be
> reassigned to another package ... Feel free to downgrade the severity to
> not block 1.17.22 from migrating - which should be a good improvement
> over 1.17.21.

I'll take a proper look once I wake up, if I need more info I'll ask
for it, thanks!

Regards,
Guillem


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

Bug#771739: could not start nodm with systemd 217-1 or 217-2

[Martin Pitt]

積丹尼 Dan Jacobson [2014-12-02 13:36 +0800]:
> # cat /etc/X11/default-display-manager
> cat: /etc/X11/default-display-manager: No such file or directory

Indeed, nodm doesn't use this file at all, nor does it conflict with
any other window manager. So installing nodm together with gdm,
lightdm, kdm, etc. will just result in a disaster :-(

Didier, I'm afraid we have to exclude nodm from your DM masking -- I
don't see a way how we can fix this without actually fixing nodm.

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


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

Bug#771739: could not start nodm with systemd 217-1 or 217-2

[積丹尼 Dan Jacobson]

Using 217-2 says nodm is masked.
Had to revert to 215-7 to get it to work.
Give it a try and tell me what happens.
# nodm configuration

# Set NODM_ENABLED to something different than 'false' to enable nodm
NODM_ENABLED=true

# User to autologin for
NODM_USER=jidanni

# First vt to try when looking for free VTs
NODM_FIRST_VT=7

# X session
NODM_XSESSION=/etc/X11/Xsession

# Options for the X server
NODM_X_OPTIONS='-nolisten tcp'

# If an X session will run for less than this time in seconds, nodm will wait an
# increasing bit of time before restarting the session.
NODM_MIN_SESSION_TIME=60
# cat /etc/X11/default-display-manager
cat: /etc/X11/default-display-manager: No such file or directory
#  systemctl status nodm 
● nodm.service - LSB: No Display Manager
   Loaded: loaded (/etc/init.d/nodm)
  Drop-In: /run/systemd/generator/nodm.service.d
   └─50-nodm-$x-display-manager.conf
   Active: active (running) since 二 2014-12-02 13:22:22 CST; 2min 26s ago
  Process: 17940 ExecStart=/etc/init.d/nodm start (code=exited, 
status=0/SUCCESS)
   CGroup: /system.slice/nodm.service
   ├─17947 /usr/sbin/nodm
   └─17948 /usr/bin/X :0 -nolisten tcp vt7

12月 02 13:22:22 jidanni2 systemd[1]: Started LSB: No Display Manager.
12月 02 13:22:22 jidanni2 nodm[17947]: starting nodm
12月 02 13:22:24 jidanni2 nodm[17951]: Successful su on ??? for jidanni by root

But that is when it is working. When it is not there is also some other
output but that is not as easy to copy because I wasn't running
typescript outside of X...

Processed: forcibly merging 771652 771723

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 771652 771723
Bug #771652 {Done: Martin Pitt } [systemd] systemd: system 
217 breaks config not using initrd and /usr and / different
Bug #771723 {Done: Martin Pitt } [systemd] systemd:  systemd: 
kernel panic as /sbin/init cannot load libapparmor1.so
Marked as fixed in versions systemd/217-2.
Merged 771652 771723
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771652
771723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#771739: could not start nodm with systemd 217-1 or 217-2

[Martin Pitt]

Hello Dan,

積丹尼 Dan Jacobson [2014-12-02  7:49 +0800]:
> Could not start nodm with systemd 217-1 or 217-2.

Please show the output of

  cat /etc/X11/default-display-manager
  systemctl status nodm  # as root!

Thanks!

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature

Bug#771723: marked as done (systemd: systemd: kernel panic as /sbin/init cannot load libapparmor1.so)

[Debian Bug Tracking System]

Your message dated Tue, 2 Dec 2014 06:06:58 +0100
with message-id <20141202050658.gb2...@piware.de>
and subject line Re: Bug#771723: systemd: systemd: kernel panic as /sbin/init 
cannot load libapparmor1.so
has caused the Debian Bug report #771723,
regarding systemd:  systemd: kernel panic as /sbin/init cannot load 
libapparmor1.so
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 217-1
Severity: critical
Justification: breaks the whole system

Somehow I eneded up with an unusable system due to /sbin/init was not booting.
After installing sysvinit-core the system booted normal. Sorry, but I did not
get reportbug to report bugs from the console when I booted with
“init=/bin/bash”.

The problem is related to libapparmor1, which cannot be found as it seems to be
installed in /usr/lib and not in /lib. And /usr is mounted after starting init
as usual.
So trying to load systemd the kornel is not able to load the shared libraries
and crashes with a kernel panic.

I might be out of date, but as far as I know no files that are needed at boot
must occur below /usr.




-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-58
ii  libacl1 2.2.52-2
ii  libapparmor12.9.0-2
ii  libaudit1   1:2.4-1
ii  libblkid1   2.25.2-3
ii  libc6   2.19-13
ii  libcap2 1:2.24-6
ii  libcap2-bin 1:2.24-6
ii  libcryptsetup4  2:1.6.6-3
ii  libgcrypt20 1.6.2-4
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 217-1
ii  mount   2.25.2-3
ii  sysv-rc 2.88dsf-58
ii  udev215-7
ii  util-linux  2.25.2-3

Versions of packages systemd recommends:
ii  dbus1.8.12-1
ii  libpam-systemd  217-1

Versions of packages systemd suggests:
pn  systemd-ui  

-- Configuration Files:
/etc/systemd/resolved.conf 886b81674c4697d8949d0fba0e21907d [Errno 2] Datei 
oder Verzeichnis nicht gefunden: u'/etc/systemd/resolved.conf 
886b81674c4697d8949d0fba0e21907d'

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: forcemerge 771652 -1

Hello Tobias,

Tobias Schlemmer [2014-12-01 22:33 +0100]:
> The problem is related to libapparmor1, which cannot be found as it seems to 
> be
> installed in /usr/lib and not in /lib. And /usr is mounted after starting init
> as usual.

This was fixed yesterday in 172-2, see #771652.

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature
--- End Message ---

Bug#771744: marked as done (Cannot reject invalid SSL certificate for IMAP server as dialog keeps appearing)

[Debian Bug Tracking System]

Your message dated Tue, 02 Dec 2014 04:35:09 +
with message-id 
and subject line Bug#771744: fixed in kde4libs 4:4.14.2-4
has caused the Debian Bug report #771744,
regarding Cannot reject invalid SSL certificate for IMAP server as dialog keeps 
appearing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmail
Version: 4:4.11.5-1
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

Configure an outgoing SMTP server with (Start)TLS in kmail. If the
server presents an invalid or self-signed certificate to the agent,
KDE will show a warning dialog offering three choices: details,
continue and cancel (not sure about translation from fr_FR locale).

The "details" button works as expected, showing certificate infos,
then returning to the previous dialog.

The "cancel" button has no effects other than to bring the same dialog
almost instantly back in an infinite loop. 

The "continue" button yields another dialog letting the user choose how
long to accept the certificate, either forever, or only for the current
session. If the dialog is closed without answer, Kmail assumes forever.
At that point, the mail feeder will happily send user credentials over
to the untrusted server.


So basically, there are no ways to reject an invalid certificate, other
than to kill the mail feeder or take the system offline.




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

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

Versions of packages kmail depends on:
ii  kde-runtime   4:4.11.5-1
ii  kdepim-runtime4:4.11.5-1
ii  kdepimlibs-kio-plugins4:4.11.5-4+b1
ii  libakonadi-calendar4  4:4.11.5-4+b1
ii  libakonadi-contact4   4:4.11.5-4+b1
ii  libakonadi-kde4   4:4.11.5-4+b1
ii  libakonadi-kmime4 4:4.11.5-4+b1
ii  libakonadiprotocolinternals1  1.11.0-1
ii  libc6 2.18-4
ii  libcalendarsupport4   4:4.11.5-1
ii  libgcc1   1:4.9-20140411-2
ii  libgpgme++2   4:4.11.5-4+b1
ii  libgrantlee-core0 0.3.0-5
ii  libincidenceeditorsng44:4.11.5-1
ii  libkabc4  4:4.11.5-4+b1
ii  libkalarmcal2 4:4.11.5-4+b1
ii  libkcalcore4  4:4.11.5-4+b1
ii  libkcalutils4 4:4.11.5-4+b1
ii  libkcmutils4  4:4.11.5-3
ii  libkdecore5   4:4.11.5-3
ii  libkdepim44:4.11.5-1
ii  libkdeui5 4:4.11.5-3
ii  libkio5   4:4.11.5-3
ii  libkleo4  4:4.11.5-1
ii  libkmime4 4:4.11.5-4+b1
ii  libknewstuff3-4   4:4.11.5-3
ii  libknotifyconfig4 4:4.11.5-3
ii  libkontactinterface4  4:4.11.5-4+b1
ii  libkparts44:4.11.5-3
ii  libkpgp4  4:4.11.5-1
ii  libkpimidentities44:4.11.5-4+b1
ii  libkpimtextedit4  4:4.11.5-4+b1
ii  libkpimutils4 4:4.11.5-4+b1
ii  libkprintutils4   4:4.11.5-3
ii  libksieveui4  4:4.11.5-1
ii  libktnef4 4:4.11.5-4+b1
ii  libmailcommon44:4.11.5-1
ii  libmailimporter4  4:4.11.5-1
ii  libmailtransport4 4:4.11.5-4+b1
ii  libmessagecomposer4   4:4.11.5-1
ii  libmessagecore4   4:4.11.5-1
ii  libmessagelist4   4:4.11.5-1
ii  libmessageviewer4 4:4.11.5-1
ii  libnepomukcore4   4:4.11.5-2+b1
ii  libpimcommon4 4:4.11.5-1
ii  libqt4-dbus   4:4.8.5+git242-g0315971+dfsg-2
ii  libqt4-network4:4.8.5+git242-g0315971+dfsg-2
ii  libqt4-xml4:4.8.5+git242-g0315971+dfsg-2
ii  libqtcore44:4.8.5+git242-g0315971+dfsg-2
ii  libqtgui4 4:4.8.5+git242-g0315971+dfsg-2
ii  libqtwebkit4  2.2.1-7
ii  libsendlater4 4:4.11.5-1
ii  libsolid4 4:4.11.5-3
ii  libsoprano4   2.9.4+dfsg-1
ii  libstdc++64.9-20140411-2
ii  libtemplateparser44:4.11.5-1
ii  perl   

Processed: tagging 771684

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 771684 + patch
Bug #771684 [chromium] /var/lib/dpkg/tmp.ci/preinst: 6: 
/var/lib/dpkg/tmp.ci/preinst: upgrade: not found
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#754219: xdg-utils: new upstream version available

[Michael Gilbert]

control: severity -1 important

mate lacking xdg-open is not release critical.

Best wishes,
Mike


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

Processed: re: xdg-utils: new upstream version available

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #754219 [xdg-utils] several breakages in xdg-utils 1.1.0~rc1 (esp. MATE)
Severity set to 'important' from 'grave'

-- 
754219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 728113 src:binutils
Bug #728113 {Done: Matthias Klose } [libc6] 
_dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
Bug #728507 {Done: Matthias Klose } [libc6] 
_dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
Bug #728529 {Done: Matthias Klose } [libc6] 
_dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
Bug reassigned from package 'libc6' to 'src:binutils'.
Bug reassigned from package 'libc6' to 'src:binutils'.
Bug reassigned from package 'libc6' to 'src:binutils'.
No longer marked as found in versions eglibc/2.17-93.
No longer marked as found in versions eglibc/2.17-93.
No longer marked as found in versions eglibc/2.17-93.
No longer marked as fixed in versions binutils/2.24.90.20141201-1.
No longer marked as fixed in versions binutils/2.24.90.20141201-1.
No longer marked as fixed in versions binutils/2.24.90.20141201-1.
> fixed 728113 2.24.90.20141201-1
Bug #728113 {Done: Matthias Klose } [src:binutils] 
_dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
Bug #728507 {Done: Matthias Klose } [src:binutils] 
_dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
Bug #728529 {Done: Matthias Klose } [src:binutils] 
_dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
Marked as fixed in versions binutils/2.24.90.20141201-1.
Marked as fixed in versions binutils/2.24.90.20141201-1.
Marked as fixed in versions binutils/2.24.90.20141201-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
728113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728113
728507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728507
728529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#771032: marked as done (monkeysign: Crash due to encoding error)

[Debian Bug Tracking System]

Your message dated Tue, 02 Dec 2014 03:19:37 +
with message-id 
and subject line Bug#771032: fixed in monkeysign 2.0.2
has caused the Debian Bug report #771032,
regarding monkeysign: Crash due to encoding error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: monkeysign
Version: 2.0.1
Severity: grave
Tags: upstream
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

Signing a key fails right after the "Signer toutes les identités? [y/N]"
prompt, with the following error message :

Traceback (most recent call last):
  File "/usr/bin/monkeysign", line 41, in 
u.main()
  File "/usr/lib/python2.7/dist-packages/monkeysign/cli.py", line 69, in main
self.sign_key()
  File "/usr/lib/python2.7/dist-packages/monkeysign/ui.py", line 293, in
sign_key
pattern = self.choose_uid(_('Choose the identity to sign'), keys[key])
  File "/usr/lib/python2.7/dist-packages/monkeysign/cli.py", line 102, in
choose_uid
pattern = raw_input(prompt)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position
17: ordinal not in range(128)

My system's locale is "fr_CA.utf8"

Thanks,

- -- Jerome



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

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

Versions of packages monkeysign depends on:
ii  gnupg 1.4.18-4
ii  gnupg-agent   2.0.26-3
ii  python2.7.8-2
ii  python-pkg-resources  5.5.1-1

Versions of packages monkeysign recommends:
ii  python-gtk2   2.24.0-4
ii  python-qrencode   1.01-4
ii  python-zbar   0.10+doc-10
ii  python-zbarpygtk  0.10+doc-10

monkeysign suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJUdUgpAAoJEK/ZGpI6kvtMt4AIAI1z5AM/eEasl64W/9IMlLl2
rze7ms/SZQ4pIz8/hygOcCa8dfIjMkG0GN28pxRGfq4Sc/gSpaxKB4L3oTFaCGse
CKwYVtGr41eKOE+lmhK8H5rl3RF1cXxkQyaEpLmVImsrYkuAiZ2YpySWWwUx4qZA
qdwb7TPAPLTf6XjcnNxjQAIOnA/Gk5Cebkbt+jyJz6Po0ZF5zttfZ9MaUZdlZLr5
NTqKVkl8xK6aHFdhZ3O7WZLzYbQ1RLbEXe69zq6aUMTyDwNyWygKx/tA2lDPbSZ/
R8p6C+iVMaojI2y6cj9oN/H1EvU+gD1hpRdaNpVwE4LGmkklnpx4YyFwyoKUI+M=
=eJ43
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: monkeysign
Source-Version: 2.0.2

We believe that the bug you reported is fixed in the latest version of
monkeysign, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 771...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated monkeysign package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Dec 2014 21:03:56 -0500
Source: monkeysign
Binary: monkeysign
Architecture: source all
Version: 2.0.2
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Description:
 monkeysign - OpenPGP key signing and exchange for humans
Closes: 770900 771032 771034
Changes:
 monkeysign (2.0.2) unstable; urgency=medium
 .
   * this patch releases fixes critical issues...
   * reported in the Debian BTS:
 * encode prompt properly before prompting (closes: #771032)
 * try to handle error when import actually works in GTK UI
   (closes: #770900)
 * improve debugging by wrapping all writes to gnupg in debug
 * use the proper index when selecting key to sign
   (closes: #771034)
   * reported on the Monkeysphere mailing list:
 * hotfix: properly verify the image signature file
 * hotfix: disable scrolling in qrcode window
 * don't try to remove non-existent video device, and clarify error
   message
 * output --version to stdout and don't make it an error
   * those fix FTBS issues:
 * fix tests after cd4e18c: guess encoding properly
 * update zack's key so t

Bug#770900: marked as done (monkeysign: 'MonkeysignScan' object has no attribute 'dialog')

[Debian Bug Tracking System]

Your message dated Tue, 02 Dec 2014 03:19:37 +
with message-id 
and subject line Bug#770900: fixed in monkeysign 2.0.2
has caused the Debian Bug report #770900,
regarding monkeysign: 'MonkeysignScan' object has no attribute 'dialog'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
770900: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grave
Version: 2.0.1
Severity: normal

Dear Maintainer,

When i scan my own QR code with monkeyscan, i get the following
failure:

0 dkg@alice:~$ monkeyscan 
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/monkeysign/gtkui.py", line 518, in 
decoded
self.process_scan(data)
  File "/usr/lib/python2.7/dist-packages/monkeysign/gtkui.py", line 539, in 
process_scan
self.watch_out_callback(0, 0) # XXX: hack, the callback should call a 
cleaner function
  File "/usr/lib/python2.7/dist-packages/monkeysign/gtkui.py", line 477, in 
watch_out_callback
self.dialog.destroy()
AttributeError: 'MonkeysignScan' object has no attribute 'dialog'
0 dkg@alice:~$ 

The result is that the camera feed stops (though the menus are still
active), and i need to quit the application and restart it.

Note that gnupg2 is version 2.1.0 on this system -- i don't know if
that's relevant for monkeyscan.

   --dkg

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

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

Versions of packages monkeysign depends on:
ii  gnupg 1.4.18-4
ii  gnupg-agent   2.1.0-1
ii  python2.7.8-2
ii  python-pkg-resources  5.5.1-1

Versions of packages monkeysign recommends:
ii  python-gtk2   2.24.0-4
ii  python-qrencode   1.01-4
ii  python-zbar   0.10+doc-10
ii  python-zbarpygtk  0.10+doc-10

monkeysign suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: monkeysign
Source-Version: 2.0.2

We believe that the bug you reported is fixed in the latest version of
monkeysign, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 770...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated monkeysign package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Dec 2014 21:03:56 -0500
Source: monkeysign
Binary: monkeysign
Architecture: source all
Version: 2.0.2
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Description:
 monkeysign - OpenPGP key signing and exchange for humans
Closes: 770900 771032 771034
Changes:
 monkeysign (2.0.2) unstable; urgency=medium
 .
   * this patch releases fixes critical issues...
   * reported in the Debian BTS:
 * encode prompt properly before prompting (closes: #771032)
 * try to handle error when import actually works in GTK UI
   (closes: #770900)
 * improve debugging by wrapping all writes to gnupg in debug
 * use the proper index when selecting key to sign
   (closes: #771034)
   * reported on the Monkeysphere mailing list:
 * hotfix: properly verify the image signature file
 * hotfix: disable scrolling in qrcode window
 * don't try to remove non-existent video device, and clarify error
   message
 * output --version to stdout and don't make it an error
   * those fix FTBS issues:
 * fix tests after cd4e18c: guess encoding properly
 * update zack's key so tests succeed again
 .
   * and this makes sure this package will be easier to support for the
 lifetime of jessie
 * improve error handling again: distinguish different failure cases
   and clearly transmit GPG errors
Checksums-Sha1:
 73294370e11e98093650ac90cab72b8a96b3974d 1613 monkeysign_2.0.2.dsc
 2df8e528ac13c20135746a4e2257c7084b594e66 1006592 monkeysign_2.0.2.tar.xz
 edf9731a3c36c5c0d0f24f336928b054c9375d9d 534

Bug#771034: marked as done (monkeysign: Attempts to sign wrong uid)

[Debian Bug Tracking System]

Your message dated Tue, 02 Dec 2014 03:19:37 +
with message-id 
and subject line Bug#771034: fixed in monkeysign 2.0.2
has caused the Debian Bug report #771034,
regarding monkeysign: Attempts to sign wrong uid
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: monkeysign
Version: 2.0.1
Severity: grave
Tags: upstream
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

I am unable to sign a single uid (not all) using monkeysign. Upon close
inspection, it appears that monkeysign attempts to sign the wrong uid. See line
506 in gpg.py (why the increment?).

Thanks,

- -- Jerome



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

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

Versions of packages monkeysign depends on:
ii  gnupg 1.4.18-4
ii  gnupg-agent   2.0.26-3
ii  python2.7.8-2
ii  python-pkg-resources  5.5.1-1

Versions of packages monkeysign recommends:
ii  python-gtk2   2.24.0-4
ii  python-qrencode   1.01-4
ii  python-zbar   0.10+doc-10
ii  python-zbarpygtk  0.10+doc-10

monkeysign suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJUdVQKAAoJEK/ZGpI6kvtM3kYIAJb2gw5LLUI6tz/U82jZ/CoO
j8cf1krIHy1cU5SL3EhXGgn0W6c+S7udqboBLiYc7dtficROImXm3TD5JeRGMRrQ
LyFqNQeVC+z7Xo6h9tzz5jvHjfB6BDteT5TNe3nNTK7O1aq1/xCLqc9NUk4+rVu9
mIF+6mLY8zp/YoqAps6zJwVWHVBgtXtaUoRxWaMiRBRcKbo2sX4C8KqQjlL5Mv+P
K02o0OiYH+1BRw5jHS431ISrO64U7wABqcL9zfjxbRoaNegbsdAQ/eZjR/jIeHbY
QPFrkZWo/vzZzEuw1Bv1/tTfIXe/Z7jOPeI91lJUSXsw2V1LbzI7Ijl2FCmUDcI=
=hp6C
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: monkeysign
Source-Version: 2.0.2

We believe that the bug you reported is fixed in the latest version of
monkeysign, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 771...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated monkeysign package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Dec 2014 21:03:56 -0500
Source: monkeysign
Binary: monkeysign
Architecture: source all
Version: 2.0.2
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Description:
 monkeysign - OpenPGP key signing and exchange for humans
Closes: 770900 771032 771034
Changes:
 monkeysign (2.0.2) unstable; urgency=medium
 .
   * this patch releases fixes critical issues...
   * reported in the Debian BTS:
 * encode prompt properly before prompting (closes: #771032)
 * try to handle error when import actually works in GTK UI
   (closes: #770900)
 * improve debugging by wrapping all writes to gnupg in debug
 * use the proper index when selecting key to sign
   (closes: #771034)
   * reported on the Monkeysphere mailing list:
 * hotfix: properly verify the image signature file
 * hotfix: disable scrolling in qrcode window
 * don't try to remove non-existent video device, and clarify error
   message
 * output --version to stdout and don't make it an error
   * those fix FTBS issues:
 * fix tests after cd4e18c: guess encoding properly
 * update zack's key so tests succeed again
 .
   * and this makes sure this package will be easier to support for the
 lifetime of jessie
 * improve error handling again: distinguish different failure cases
   and clearly transmit GPG errors
Checksums-Sha1:
 73294370e11e98093650ac90cab72b8a96b3974d 1613 monkeysign_2.0.2.dsc
 2df8e528ac13c20135746a4e2257c7084b594e66 1006592 monkeysign_2.0.2.tar.xz
 edf9731a3c36c5c0d0f24f336928b054c9375d9d 53478 monkeysign_2.0.2_all.deb
Checksums-Sha256:
 1d3e83176a24372c35d541629de5610c32f3dd575e10b115ebdb3055

Processed: Re: Bug#771452: Duplicate object check

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 771452 normal
Bug #771452 [s3ql] s3ql: fsck.s3ql on crashed file system results in uncaught 
exception
Severity set to 'normal' from 'critical'
> clone 771452 -1
Bug #771452 [s3ql] s3ql: fsck.s3ql on crashed file system results in uncaught 
exception
Bug 771452 cloned as bug 771756
> retitle 771452 fsck.s3ql sporadically crashes when checking objects
Bug #771452 [s3ql] s3ql: fsck.s3ql on crashed file system results in uncaught 
exception
Changed Bug title to 'fsck.s3ql sporadically crashes when checking objects' 
from 's3ql: fsck.s3ql on crashed file system results in uncaught exception'
> retitle -1 "No route to host" not recognized as temporary network issue
Bug #771756 [s3ql] s3ql: fsck.s3ql on crashed file system results in uncaught 
exception
Changed Bug title to '"No route to host" not recognized as temporary network 
issue' from 's3ql: fsck.s3ql on crashed file system results in uncaught 
exception'
> reassign -1 python-dugong
Bug #771756 [s3ql] "No route to host" not recognized as temporary network issue
Bug reassigned from package 's3ql' to 'python-dugong'.
No longer marked as found in versions s3ql/2.11.1+dfsg-1.
Ignoring request to alter fixed versions of bug #771756 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771452
771756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#771452: Duplicate object check

[Nikolaus Rath]

severity -1 normal
retitle -1 fsck.s3ql sporadically crashes when checking objects
thanks

Retitling this bug and lowering severity for now. I don't think that the
mount.s3ql crash is related to the fsck.s3ql crashes, or that there is
any data corruption.


Best,
-Nikolaus
-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«


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

Processed: gnustep-dl2-postgresql-adaptor: unhandled symlink to directory conversion: /usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + gnustep-dl2
Bug #771755 [gnustep-dl2-postgresql-adaptor] gnustep-dl2-postgresql-adaptor: 
unhandled symlink to directory conversion: 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources
Added indication that 771755 affects gnustep-dl2

-- 
771755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#771755: gnustep-dl2-postgresql-adaptor: unhandled symlink to directory conversion: /usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources

[Andreas Beckmann]

Package: gnustep-dl2-postgresql-adaptor
Version: 0.12.0-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + gnustep-dl2

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  wheezy -> sid

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

3m8.5s INFO: dirname part contains a symlink:
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle
 (?)
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle/LoginPanel
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle/LoginPanel
 (?)
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle/Resources
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle/Resources
 (?)
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle/Resources/Info-gnustep.plist
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle/Resources/Info-gnustep.plist
 (?)
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle/Resources/postgreslogo.tif
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle/Resources/postgreslogo.tif
 (?)
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle/stamp.make
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle/stamp.make
 (?)


cheers,

Andreas


gnustep-dl2_0.12.0-13.log.gz
Description: application/gzip

Bug#771753: libavifile-0.7-dev, libavifile-0.7-bin: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: libavifile-0.7-dev,libavifile-0.7-bin
Version: 1:0.7.48~20090503.ds-16.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  wheezy -> sid

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

2m18.0s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libavifile-0.7-bin/changelog.Debian.gz (libavifile-0.7-bin) != 
/usr/share/doc/libavifile-0.7-common/changelog.Debian.gz (libavifile-0.7-common)
  /usr/share/doc/libavifile-0.7-bin/changelog.gz (libavifile-0.7-bin) != 
/usr/share/doc/libavifile-0.7-common/changelog.gz (libavifile-0.7-common)
  /usr/share/doc/libavifile-0.7-bin/copyright (libavifile-0.7-bin) != 
/usr/share/doc/libavifile-0.7-common/copyright (libavifile-0.7-common)

2m13.4s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libavifile-0.7-dev/changelog.Debian.gz (libavifile-0.7-dev) != 
/usr/share/doc/libavifile-0.7-common/changelog.Debian.gz (libavifile-0.7-common)
  /usr/share/doc/libavifile-0.7-dev/changelog.gz (libavifile-0.7-dev) != 
/usr/share/doc/libavifile-0.7-common/changelog.gz (libavifile-0.7-common)
  /usr/share/doc/libavifile-0.7-dev/copyright (libavifile-0.7-dev) != 
/usr/share/doc/libavifile-0.7-common/copyright (libavifile-0.7-common)


There are .maintscript files in the package that should do this, but they fail 
beause
the PATHNAME argument is given with a trailing slash, also '-- $@' is 
superfluous.


cheers,

Andreas


libavifile-0.7-dev_1:0.7.48~20090503.ds-16.1.log.gz
Description: application/gzip

Bug#771744: cloning 769852

[Scott Kitterman]

On Mon, 01 Dec 2014 20:26:19 -0500 Scott Kitterman  
wrote:
> clone 769852 -1
> reassign -1 kde4libs
> thanks

There's a kde4libs piece to fixing this as well.

Scott K


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

Bug#771612: marked as done (python-txzookeeper: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Tue, 02 Dec 2014 02:18:45 +
with message-id <547d2185.3050...@nirgal.com>
and subject line python-txzookeeper: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
has caused the Debian Bug report #771612,
regarding python-txzookeeper: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-txzookeeper
Version: 0.9.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  wheezy -> jessie

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

0m57.9s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python-zookeeper/changelog.Debian.gz (python-zookeeper) != 
/usr/share/doc/libzookeeper-mt2/changelog.Debian.gz (libzookeeper-mt2:amd64)
  /usr/share/doc/python-zookeeper/changelog.gz (python-zookeeper) != 
/usr/share/doc/libzookeeper-mt2/changelog.gz (libzookeeper-mt2:amd64)
  /usr/share/doc/python-zookeeper/copyright (python-zookeeper) != 
/usr/share/doc/libzookeeper-mt2/copyright (libzookeeper-mt2:amd64)


cheers,

Andreas


python-txzookeeper_0.9.8-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 3.4.5+dfsg-2

The bug was introduced here:
https://anonscm.debian.org/cgit/pkg-java/zookeeper.git/commit/debian/rules?id=c451bc993cd055b7480e8ca17b8384e33759a7d9
where /usr/share/doc/python-zookeeper is no longer a link to
/usr/share/doc/libzookeeper-mt2.

A fix was commited here:
https://anonscm.debian.org/cgit/pkg-java/zookeeper.git/commit/?id=c3c6a7f026a41676c4e9b12e7cc6213d501869cd

and is available in version 3.4.5+dfsg-2 currently in Jessie. :)

Therefore I'm closing that RC bug.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#771749: cyrus-{common, imapd}-2.4: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: cyrus-imapd-2.4,cyrus-common-2.4
Version: 2.4.17+caldav~beta10-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  wheezy -> jessie (2.4.17+caldav~beta10-8)
  wheezy -> sid (2.4.17+caldav~beta10-9)

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

4m16.8s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/cyrus-common-2.4/changelog.Debian.gz (cyrus-common-2.4) != 
/usr/share/doc/cyrus-common/changelog.Debian.gz (cyrus-common)
  /usr/share/doc/cyrus-common-2.4/copyright (cyrus-common-2.4) != 
/usr/share/doc/cyrus-common/copyright (cyrus-common)
  /usr/share/doc/cyrus-imapd-2.4/copyright (cyrus-imapd-2.4) != 
/usr/share/doc/cyrus-common/copyright (cyrus-common)


There may be more packages failing, but these cannot be tested by piuparts
due to cyrus-common-2.4 already failing ...

cheers,

Andreas


cyrus-imapd-2.4_2.4.17+caldav~beta10-8.log.gz
Description: application/gzip

Processed: reopening 771744

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 771744
Bug #771744 {Done: Scott Kitterman } [kde4libs] Cannot 
reject invalid SSL certificate for IMAP server as dialog keeps appearing
Bug reopened
Ignoring request to alter fixed versions of bug #771744 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: Marking stuff

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 769852 -1
Bug #769852 {Done: Scott Kitterman } [kdepimlibs] Cannot 
reject invalid SSL certificate for IMAP server as dialog keeps appearing
Bug 769852 cloned as bug 771748
> reassign -1 kde4libs
Bug #771748 {Done: Scott Kitterman } [kdepimlibs] Cannot 
reject invalid SSL certificate for IMAP server as dialog keeps appearing
Bug reassigned from package 'kdepimlibs' to 'kde4libs'.
Ignoring request to alter found versions of bug #771748 to the same values 
previously set
No longer marked as fixed in versions kdepimlibs/4:4.14.2-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
769852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769852
771748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: found 771744 in 4:4.14.2-3wq

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 771744 4:4.14.2-3wq
Bug #771744 [kde4libs] Cannot reject invalid SSL certificate for IMAP server as 
dialog keeps appearing
There is no source info for the package 'kde4libs' at version '4:4.14.2-3wq' 
with architecture ''
Unable to make a source version for version '4:4.14.2-3wq'
Marked as found in versions 4:4.14.2-3wq.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: found 771744 in 4:4.14.2-3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 771744 4:4.14.2-3
Bug #771744 [kde4libs] Cannot reject invalid SSL certificate for IMAP server as 
dialog keeps appearing
There is no source info for the package 'kde4libs' at version '4:4.14.2-3' with 
architecture ''
Unable to make a source version for version '4:4.14.2-3'
Marked as found in versions 4:4.14.2-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#771745: python*-greenlet*: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: python3-greenlet,python-greenlet-dbg,python-greenlet-dev
Version: 0.4.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  testing -> sid

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

1m28.4s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python3-greenlet/changelog.Debian.gz (python3-greenlet) != 
/usr/share/doc/python-greenlet/changelog.Debian.gz (python-greenlet)
  /usr/share/doc/python3-greenlet/copyright (python3-greenlet) != 
/usr/share/doc/python-greenlet/copyright (python-greenlet)

1m13.0s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python-greenlet-dbg/changelog.Debian.gz (python-greenlet-dbg) 
!= /usr/share/doc/python-greenlet/changelog.Debian.gz (python-greenlet)
  /usr/share/doc/python-greenlet-dbg/copyright (python-greenlet-dbg) != 
/usr/share/doc/python-greenlet/copyright (python-greenlet)

1m18.7s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python-greenlet-dev/changelog.Debian.gz (python-greenlet-dev) 
!= /usr/share/doc/python-greenlet/changelog.Debian.gz (python-greenlet)
  /usr/share/doc/python-greenlet-dev/copyright (python-greenlet-dev) != 
/usr/share/doc/python-greenlet/copyright (python-greenlet)

There may be more packages affected, but these were not tested by
piuparts due to failing dependencies.


cheers,

Andreas


python3-greenlet_0.4.5-1.log.gz
Description: application/gzip

Processed: cloning 769852

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 769852 -1
Bug #769852 {Done: Scott Kitterman } [kdepimlibs] Cannot 
reject invalid SSL certificate for IMAP server as dialog keeps appearing
Bug 769852 cloned as bug 771744
> reassign -1 kde4libs
Bug #771744 {Done: Scott Kitterman } [kdepimlibs] Cannot 
reject invalid SSL certificate for IMAP server as dialog keeps appearing
Bug reassigned from package 'kdepimlibs' to 'kde4libs'.
Ignoring request to alter found versions of bug #771744 to the same values 
previously set
No longer marked as fixed in versions kdepimlibs/4:4.14.2-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
769852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769852
771744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#769836: marked as done ([chromium-browser] Please use -fexcess-precision=standard or -ffloat-store instead of enabling sse2)

[Debian Bug Tracking System]

Your message dated Mon, 1 Dec 2014 19:38:56 -0500
with message-id 

and subject line Re: Bug#769836: closed by Michael Gilbert 
 (Bug#769836: fixed in chromium-browser 39.0.2171.71-1)
has caused the Debian Bug report #769836,
regarding [chromium-browser] Please use -fexcess-precision=standard or 
-ffloat-store instead of enabling sse2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
769836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium-browser
Severity: serious
version: 38.0.2125.101-4
justification: i386 package must be compiled for i586

According to gcc documentation and my experience [1]:

>The following options control compiler behavior regarding floating-point 
>arithmetic. These options trade off between speed and >correctness. All must 
>be specifically enabled.
>
>-ffloat-store
>Do not store floating-point variables in registers, and inhibit other 
> options that might change whether a floating-point value is taken from a 
> register or memory.
>
>This option prevents undesirable excess precision on machines such as the 
> 68000 where the floating registers (of the 68881) keep more precision than a 
> double is supposed to have. Similarly for the x86 architecture. For most 
> programs, the excess precision does only good, but a few programs rely on the 
> precise definition of IEEE floating point. Use -ffloat-store for such 
> programs, after modifying them to store all pertinent intermediate 
> computations into variables.
>-fexcess-precision=style
>This option allows further control over excess precision on machines where 
> floating-point registers have more precision than the IEEE float and double 
> types and the processor does not support operations rounding to those types. 
> By default, -fexcess-precision=fast is in effect; this means that operations 
> are carried out in the precision of the registers and that it is 
> unpredictable when rounding to the types specified in the source code takes 
> place. When compiling C, if -fexcess-precision=standard is specified then 
> excess precision follows the rules specified in ISO C99; in particular, both 
> casts and assignments cause values to be rounded to their semantic types 
> (whereas -ffloat-store only affects assignments). This option is enabled by 
> default for C if a strict conformance option such as -std=c99 is used.

>-fexcess-precision=standard is not implemented for languages other than C, 
> and has no effect if -funsafe-math-optimizations or -ffast-math is specified. 
> On the x86, it also has no effect if -mfpmath=sse or -mfpmath=sse+387 is 
> specified; in the former case, IEEE semantics apply without excess precision, 
> and in the latter, rounding is unpredictable. 

 [1] 
https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Disappointments.html#Disappointments

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
version: 39.0.2171.71-1

On Mon, Dec 1, 2014 at 11:03 AM, roucaries bastien:
> I am sorry but it work on sse but not on i387 is the sign of huge
> problem in the floating point computation.

Upsteam dropped support for < sse2.  I do not have time to fight
against that.  If someone is willing to step up with a patch set that
reverts that and can clearly continue to update those patches for the
entire jessie release cycle, I will consider it.

Until then, I consider detecting and documenting the situation as the
only sane solution.

Best wishes,
Mike--- End Message ---

Processed: #771461

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 771461 + patch
Bug #771461 [samhain] /var/state/samhain/
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: Re: iceweasel: WebM loading crashes iceweasel

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 770490 fixed-upstream
Bug #770490 [iceweasel] iceweasel: WebM loading crashes iceweasel
Bug #770499 [iceweasel] conkeror: WebM loading crashes conkeror
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
770490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770490
770499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#771461: /var/state/samhain/

[Andrea Claudi]

Hi,
This patch should fix the problem, moving the non-volatile state for the 
samhain package to /var/lib/samhain.

Please, tell me if I need to fix something to make this acceptable.

Cheers,
Andrea

bts tags 771461 + patch
thanksdiff -u samhain-3.1.0/debian/changelog samhain-3.1.0/debian/changelog
--- samhain-3.1.0/debian/changelog
+++ samhain-3.1.0/debian/changelog
@@ -1,3 +1,11 @@
+samhain (3.1.0-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Move all non-volatile package state in /var/lib/, according
+to the FHS (Closes: #771461)
+
+ -- Andrea Claudi   Tue, 02 Dec 2014 00:36:33 +0100
+
 samhain (3.1.0-6) unstable; urgency=medium
 
   * debian/rules: Add an option to disable the ASM code when building
diff -u samhain-3.1.0/debian/dirs samhain-3.1.0/debian/dirs
--- samhain-3.1.0/debian/dirs
+++ samhain-3.1.0/debian/dirs
@@ -5,3 +5,3 @@
 var/log/samhain
-var/state/samhain
+var/lib/samhain
 etc/logrotate.d
diff -u samhain-3.1.0/debian/postrm samhain-3.1.0/debian/postrm
--- samhain-3.1.0/debian/postrm
+++ samhain-3.1.0/debian/postrm
@@ -7,7 +7,7 @@
 
 case "$1" in
 	purge)
-		for dir in /var/log/samhain/supervise /var/log/samhain /var/state/samhain /var/run/samhain
+		for dir in /var/log/samhain/supervise /var/log/samhain /var/lib/samhain /var/run/samhain
 		do
 			[ -d "$dir" ] &&  {
 			 	find $dir -type f -exec rm -f {} \;
diff -u samhain-3.1.0/debian/rules samhain-3.1.0/debian/rules
--- samhain-3.1.0/debian/rules
+++ samhain-3.1.0/debian/rules
@@ -51,7 +51,7 @@
 endif
 	./configure --prefix=/usr --mandir=\$${prefix}/share/man \
 		--with-config-file=/etc/samhain/samhainrc \
-		--with-state-dir=/var/state/samhain  \
+		--with-state-dir=/var/lib/samhain  \
 		--with-prelude \
 		$(DNMALLOC) \
 		$(DISABLE_ASM) \
@@ -69,7 +69,7 @@
 #	dh_autoreconf
 	./configure --prefix=/usr --mandir=\$${prefix}/share/man \
 		--with-config-file=/etc/yule/yulerc \
-		--with-state-dir=/var/state/yule  \
+		--with-state-dir=/var/lib/yule  \
 		--with-prelude \
 		$(DNMALLOC) \
 		--enable-network=server  \
@@ -85,7 +85,7 @@
 #	dh_autoreconf
 	./configure --prefix=/usr --mandir=\$${prefix}/share/man \
 		--with-config-file=/etc/samhain/samhainrc \
-		--with-state-dir=/var/state/samhain  \
+		--with-state-dir=/var/lib/samhain  \
 		--with-prelude \
 		$(DNMALLOC) \
 		--enable-network=client \
@@ -112,7 +112,7 @@
 	dh_installdirs
 	# Fix the permissions
 	chmod o-rX `pwd`/debian/samhain/var/log/samhain \
-		`pwd`/debian/samhain/var/state/samhain \
+		`pwd`/debian/samhain/var/lib/samhain \
 		`pwd`/debian/samhain/etc/samhain
 
 	$(MAKE) install install-boot DESTDIR=`pwd`/debian/samhain
diff -u samhain-3.1.0/debian/samhain.init samhain-3.1.0/debian/samhain.init
--- samhain-3.1.0/debian/samhain.init
+++ samhain-3.1.0/debian/samhain.init
@@ -49,10 +49,10 @@
 {
 # Initialize the database only if does not exist yet, abort if
 # it cannot be created
- [  -f /var/state/samhain/samhain_file ] && return
+ [  -f /var/lib/samhain/samhain_file ] && return
  log_progress_msg "Creating integrity database (this can take some minutes)."
  samhain -t init >/var/log/samhain/samhain-init.log 2>&1
- if [  ! -f /var/state/samhain/samhain_file ] ; then
+ if [  ! -f /var/lib/samhain/samhain_file ] ; then
 log_failure_msg "Database could not be created. Review /var/log/samhain/samhain-init.log"
 log_end_msg 1
 exit 1
only in patch2:
unchanged:
--- samhain-3.1.0.orig/rules.deb.in
+++ samhain-3.1.0/rules.deb.in
@@ -51,7 +51,7 @@
 	# Fix the permissions
 	#chmod o-rX `pwd`/debian/tmp/var/log/samhain \
 	#	`pwd`/debian/tmp/var/run/samhain \
-	#	`pwd`/debian/tmp/var/state/samhain \
+	#	`pwd`/debian/tmp/var/lib/samhain \
 	#	`pwd`/debian/tmp/etc/samhain
 
 	# $(MAKE) install install-boot DESTDIR=`pwd`/debian/tmp

Bug#771739: could not start nodm with systemd 217-1 or 217-2

[積丹尼 Dan Jacobson]

Package: systemd
Version: 217-2
Severity: grave

Could not start nodm with systemd 217-1 or 217-2.


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

Bug#771728: marked as done (ltsp-client-core: hooks in /etc/kernel/postrm.d/ break linux-image package removal on arm)

[Debian Bug Tracking System]

Your message dated Mon, 01 Dec 2014 23:49:12 +
with message-id 
and subject line Bug#771728: fixed in ltsp 5.5.4-2
has caused the Debian Bug report #771728,
regarding ltsp-client-core: hooks in /etc/kernel/postrm.d/ break linux-image 
package removal on arm
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ltsp-client-core
Version: 5.5.4-1
Severity: serious
Tags: patch

When removing a linux-image package on an armhf system (and presumably
armel as well), mkimage is called in the ltsp-client hook
/etc/kernel/postrm.d/update-kernels, and generates output that causes
the package removal to fail...


Removing symbolic link initrd.img.old
You may need to re-run your boot loader
Purging configuration files for linux-image-3.16.0-4-armmp-lpae (3.16.7-2) ...
dpkg: error processing package linux-image-3.16.0-4-armmp-lpae (--purge):
 subprocess installed post-removal script returned error exit status 128
 Errors were encountered while processing:
  linux-image-3.16.0-4-armmp-lpae

E: Sub-process /usr/bin/dpkg returned an error code (1)

The following patch fixes this by redirecting the mkimage output to
/dev/null.

I plan to upload a fixed package today.

 client/share/ltsp/update-kernels | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/client/share/ltsp/update-kernels b/client/share/ltsp/update-kernels
index 5e079be..1a75103 100755
--- a/client/share/ltsp/update-kernels
+++ b/client/share/ltsp/update-kernels
@@ -352,7 +352,8 @@ tftpboot \${kernel_addr_r} \${serverip}:${kernel_file} \\
 EOF
 
 mkimage -A arm -O Linux -T script -C none -a 0x0 -e 0x0 \
--n 'LTSP boot script' -d $BOOT/boot.ltsp $BOOT/boot.scr
+-n 'LTSP boot script' -d $BOOT/boot.ltsp $BOOT/boot.scr \
+> /dev/null

 # Copy .dtb files to boot dir.
 dtb_dirs="/usr/lib/linux-image-${version}/"


live well,
  vagrant


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ltsp
Source-Version: 5.5.4-2

We believe that the bug you reported is fixed in the latest version of
ltsp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 771...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated ltsp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Dec 2014 15:22:01 -0800
Source: ltsp
Binary: ltsp-server ltsp-server-standalone ltsp-client-core ltsp-client 
ltsp-client-builder
Architecture: source all
Version: 5.5.4-2
Distribution: unstable
Urgency: medium
Maintainer: LTSP Debian Maintainers 
Changed-By: Vagrant Cascadian 
Description:
 ltsp-client - complete LTSP client environment
 ltsp-client-builder - build an LTSP environment in the installer target (udeb)
 ltsp-client-core - basic LTSP client environment
 ltsp-server - basic LTSP server environment
 ltsp-server-standalone - complete LTSP server environment
Closes: 771470 771728
Changes:
 ltsp (5.5.4-2) unstable; urgency=medium
 .
   * ltsp-update-kernels/update-kernels: Fix kernel version sorting that
 results in clients booting obsolete kernels (Closes: #771470).
 .
   * update-kernels: Suppress mkimage output, as it prevents linux-image
 packages from being removed successfully (Closes: #771728).
 .
   * ltsp-build-client: Remove plugin that needlessly modifies pulseaudio
 configuration files.
 .
   * ltsp-update-kernels: Remove dtb files when corresponding kernel
 version is no longer present.
 .
   * debian/copyright: Remove outdated VCS information.
Checksums-Sha1:
 4cc1977ad532fdcd385273a34d698be61ca595b0 2285 ltsp_5.5.4-2.dsc
 33f630fd423b3d764ec11b46d2cb26baf7497754 76920 ltsp_5.5.4-2.debian.tar.xz
 8457fbb1e74131c30e978369b0b3833484d13e55 265926 ltsp-server_5.5.4-2_all.deb
 358f6ee428d5b6e3c25ec0d5fa6b6fe4309f6a02 146034 
ltsp-server-standalone_5.5.4-2_all.deb
 3201b1c37eb2e946b65d7d4dd9ccf1efa4a81df4 11124 
ltsp-client-builder_5.5.4-2_all.udeb
Checksums-Sha256:
 5ad0f843e0fa19fb1f49110f3ca

Bug#771470: marked as done (ltsp-client-core: Kernel version sorting may result in booting obsolete kernel)

[Debian Bug Tracking System]

Your message dated Mon, 01 Dec 2014 23:49:12 +
with message-id 
and subject line Bug#771470: fixed in ltsp 5.5.4-2
has caused the Debian Bug report #771470,
regarding ltsp-client-core: Kernel version sorting may result in booting 
obsolete kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ltsp-client-core
Version: 5.5.4-1
Severity: serious
Tags: patch

When upgrading an LTSP environment from Wheezy, LTSP's kernel sorting
rules generate a pxelinux.cfg/ltsp file that defaults to the -486
Wheezy kernel variant, instead of the -586 variant present in Jessie.
This results in clients booting an old kernel and quite possibly
missing security updates.

Additionally, if the configures IFCPU64=true in
/etc/ltsp/update-kernels.conf which should set up pxelinux entries to
boot the appropriate kernel based 32-bit, PAE or 64-bit machines, the
rules always pick the lowest common denominator for all the kernels
(and adding insult to injury, the lowest possible version).

I plan to upload a fixed version shortly...

The following patches were committed upstream, and should resolve this
issue:

From: Alkis Georgopoulos 
Date: Sat, 29 Nov 2014 17:51:04 +0200
Subject: [PATCH 15/17] Correctly sort kernel FLAVOR in increasing order and
 VERSION in decreasing.

---
 client/Debian/etc/ltsp/update-kernels.conf| 2 +-
 client/Debian/share/ltsp/cleanup.d/50-vmlinuz | 2 +-
 client/Ubuntu/etc/ltsp/update-kernels.conf| 2 +-
 client/share/ltsp/update-kernels  | 4 ++--
 server/ltsp-update-kernels| 2 +-
 5 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/client/Debian/etc/ltsp/update-kernels.conf 
b/client/Debian/etc/ltsp/update-kernels.conf
index b22e0a6..97131b5 100644
--- a/client/Debian/etc/ltsp/update-kernels.conf
+++ b/client/Debian/etc/ltsp/update-kernels.conf
@@ -28,7 +28,7 @@ CMDLINE_NBD="root=/dev/nbd0"
 CMDLINE_AOE="root=/dev/etherd/e0.0"
 
 # A sed expression that matches all kernels and returns $FILE $NAME $VERSION 
$FLAVOR
-# Example: ls /boot | sed -n "$KERNEL_NAMES" | sort -V -k 4,4  | sort -r -k 3,3
+# Example: ls /boot | sed -n "$KERNEL_NAMES" | sort -k 4,4V -k 3,3rV
 KERNEL_NAMES='s/\(vmlinu[xz]-\)\([^-]*-[^-]*-\)\(.*\)/& \1 \2 \3/p'
 
 # A sed expression that maps from a kernel name to an initrd name
diff --git a/client/Debian/share/ltsp/cleanup.d/50-vmlinuz 
b/client/Debian/share/ltsp/cleanup.d/50-vmlinuz
index 3a88d30..82fb818 100644
--- a/client/Debian/share/ltsp/cleanup.d/50-vmlinuz
+++ b/client/Debian/share/ltsp/cleanup.d/50-vmlinuz
@@ -14,7 +14,7 @@ INITRD_NAME=${INITRD_NAME:-'s/vmlinu[xz]/initrd.img/p'}
 
 read file name version flavor <
Date: Sat, 29 Nov 2014 10:57:26 -0800
Subject: [PATCH 16/17] update-kernels: Fix issues with kernel version variant
 sorting by first looping on the preferred variants, and using the keyword
 "ALL" instead of "*" to avoid shell globbing issues.

---
 client/share/ltsp/update-kernels | 13 +
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/client/share/ltsp/update-kernels b/client/share/ltsp/update-kernels
index 96310fb..5e079be 100755
--- a/client/share/ltsp/update-kernels
+++ b/client/share/ltsp/update-kernels
@@ -59,6 +59,9 @@ kernel_split() {
 set -f
 for kernel in $(find "/boot/" -type f -name "$KERNEL_PREFIX$KERNEL_SUFFIX" 
-printf "%f\n"); do
 # Validate the "arch"
+if [ "${LIST_KERNELS}" = "ALL" ]; then
+LIST_KERNELS="*"
+fi
 for arch in ${LIST_KERNELS:-*}; do
 case "$kernel" in
 $KERNEL_PREFIX$arch$KERNEL_SUFFIX)
@@ -73,7 +76,9 @@ kernel_split() {
 }
 
 kernel_versions(){
-kernel_split | awk '{print $3$4}'
+for arch in ${LIST_KERNELS:-"ALL"} ; do
+LIST_KERNELS="$arch" kernel_split | awk '{print $3$4}'
+done
 }
 
 kernel_variants(){
@@ -205,7 +210,7 @@ EOF
 pxelinux_include_files="$pxelinux_include_files ltsp-$method"
 # Get the preferred default kernel, preferred 32-bit kernel, or any 
 # kernel.
-version=$(LIST_KERNELS="$LIST_KERNELS_DEFAULT $LIST_KERNELS_32 *" 
kernel_versions | head -n 1)
+version=$(LIST_KERNELS="$LIST_KERNELS_DEFAULT $LIST_KERNELS_32 ALL" 
kernel_versions | head -n 1)
cat > $PXECFG/ltsp-$method <> $PXECFG/ltsp-ifcpu64-$method 

Bug#771729: Depends: gcc-4.9-arm-linux-gnueabihf (>= 4.9.2-2) but it is not installable

[Wookey]

+++ Guido Seifert [2014-12-01 23:23 +0100]:
> Subject: Depends: gcc-4.9-arm-linux-gnueabihf (>= 4.9.2-2) but it is not 
> installable
> Package: gcc-arm-linux-gnueabihf
> Version: Version: 4.9.2-2
> Justification: renders package unusable
> Severity: grave
> 
> Dear Maintainer,
> 
>* What led up to the situation?
>   -> apt-get install gcc-arm-linux-gnueabihf
> 
>I did an apt-get update/upgrade/dist-upgrade, but no effect.   
>It seems gcc-4.9-arm-linux-gnueabihf does not even exists.

It does exist and is installable:
https://packages.debian.org/unstable/gcc-4.9-arm-linux-gnueabihf
I just checked.

Did you do 
dpkg --add-architecture armhf
before the update?

That is needed to have the dependencies available.
 
Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


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

Bug#771132: (no subject)

[Séverin Lemaignan]

Ok.
After further investigation, the 2 bugs you reported are indeed fixed, but in 
master only ([1], [2])

I've open a bug in MORSE [3] to quickly do a new upstream release so that the 
package can be adequately updated in Debian.

Thanks a lot for the report!

Séverin

[1] 
https://github.com/morse-simulator/morse/commit/db937ea839121cd44762342c6833d4e8610a1911
[2] 
https://github.com/morse-simulator/morse/commit/35c9b53d03b5df6c1c66e0d3265235092774c225
[3] https://github.com/morse-simulator/morse/issues/582


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

Bug#728113: marked as done (_dl_check_map_versions: Assertion `needed != ((void *)0)' failed!)

[Debian Bug Tracking System]

Your message dated Mon, 01 Dec 2014 23:04:18 +
with message-id 
and subject line Bug#728529: fixed in binutils 2.24.90.20141201-1
has caused the Debian Bug report #728529,
regarding _dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
728529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: smartmontools
Version: 6.2+svn3841-1
Severity: normal





$ sudo /etc/init.d/smartmontools start
[] Starting S.M.A.R.T. daemon: smartdInconsistency detected by ld.so: 
dl-version.c: 224: _dl_check_map_versions: Assertion `needed != ((void *)0)' 
failed!

$ sudo smartctl -a /dev/sda
Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: 
Assertion `needed != ((void *)0)' failed!






All the dependencies seem to be satisfied. Maybe they are not stated
correctly/strictly enough?



--- System information. ---
Architecture: amd64
Kernel:   Linux 3.10.13-rm2+

Debian Release: 7.2
  990 testing www.emdebian.org 
  990 stable  approx.home.romanrm.net 
  500 testing approx.home.romanrm.net 
  100 wheezy-backports approx.home.romanrm.net 

--- Package information. ---
Depends(Version) | Installed
-+-=
libc6  (>= 2.17) | 2.17-93
libcap-ng0   | 0.6.6-2
libgcc1 (>= 1:4.1.1) | 1:4.7.2-5
libselinux1(>= 1.32) | 2.1.9-5
libstdc++6(>= 4.1.1) | 4.8.1-10
debianutils (>= 2.2) | 4.3.2
lsb-base (>= 3.2-14) | 4.1+Debian8+deb7u1


Recommends  (Version) | Installed
=-+-===
mailx | 
 OR mailutils | 


Suggests(Version) | Installed
=-+-===
gsmartcontrol | 
smart-notifier| 



--- Output from package bug script ---
Output of /usr/share/bug/smartmontools:



-- 
With respect,
Roman


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: binutils
Source-Version: 2.24.90.20141201-1

We believe that the bug you reported is fixed in the latest version of
binutils, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 728...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated binutils package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 01 Dec 2014 21:53:10 +0100
Source: binutils
Binary: binutils binutils-dev binutils-multiarch binutils-multiarch-dev 
binutils-hppa64 binutils-doc binutils-source
Architecture: source all amd64
Version: 2.24.90.20141201-1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 binutils   - GNU assembler, linker and binary utilities
 binutils-dev - GNU binary utilities (BFD development files)
 binutils-doc - Documentation for the GNU assembler, linker and binary utilities
 binutils-hppa64 - GNU assembler, linker and binary utilities targeted for 
hppa64-li
 binutils-multiarch - Binary utilities that support multi-arch targets
 binutils-multiarch-dev - GNU binary utilities that support multi-arch targets 
(BFD develop
 binutils-source - GNU assembler, linker and binary utilities (source)
Closes: 728529
Changes:
 binutils (2.24.90.20141201-1) unstable; urgency=medium
 .
   * Snapshot, taken from the 2.25 branch 20141201.
 - Fix PR ld/16452, PR/ld/16457: Don't output symbol version
   requirement for non-DT_NEEDED libs. Closes: #728529.
Checksums-Sha1:
 e4a8f165e2dd2edc954f516c74fc397e610d6d03 1810 binutils_2.24.90.20141201-1.dsc
 6158a8b3677c1efccb9d714f651a660ed6aa43a3 29908914 
binutils_2.24.90.20141201.orig.tar.gz
 1049426e96767348486c86d90f02e9882bcbfbc6 120863 
binutils_2.24.90.20141201-1.diff.gz
 794401fdd621d0fd1aaf57c71baec134cf1a0f90 501628 
binutils-doc_2.24.90.20141201-1_all.deb
 86657d7b033151d66290e73379e81c14904c70ac 17149330 
binutils-source_2.24.90.20141201-1_all.deb
 d9092c50f3

Bug#728529: marked as done (_dl_check_map_versions: Assertion `needed != ((void *)0)' failed!)

[Debian Bug Tracking System]

Your message dated Mon, 01 Dec 2014 23:04:18 +
with message-id 
and subject line Bug#728529: fixed in binutils 2.24.90.20141201-1
has caused the Debian Bug report #728529,
regarding _dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
728529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libselinux1
Version: 2.2-1
Severity: critical
Justification: breaks unrelated software

Hi!

The recent upgrade auf libselinux1 to version 2.2-1 in unstable causes
smartctl and smartd to fail with the following message:

system:~# smartctl
Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: 
Assertion `needed != ((void *)0)' failed!

Downgrading libselinux1 to 2.1.13-3 solves the problem.

So far only smartctl/smartd is affected, but since this bug affects an
unrelated package, the severity of critical seems correct.

Please also see and maybe merge bug #728507 against smartmontools.

Grüße,
Sven.

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

Kernel: Linux 3.11-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: binutils
Source-Version: 2.24.90.20141201-1

We believe that the bug you reported is fixed in the latest version of
binutils, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 728...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated binutils package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 01 Dec 2014 21:53:10 +0100
Source: binutils
Binary: binutils binutils-dev binutils-multiarch binutils-multiarch-dev 
binutils-hppa64 binutils-doc binutils-source
Architecture: source all amd64
Version: 2.24.90.20141201-1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 binutils   - GNU assembler, linker and binary utilities
 binutils-dev - GNU binary utilities (BFD development files)
 binutils-doc - Documentation for the GNU assembler, linker and binary utilities
 binutils-hppa64 - GNU assembler, linker and binary utilities targeted for 
hppa64-li
 binutils-multiarch - Binary utilities that support multi-arch targets
 binutils-multiarch-dev - GNU binary utilities that support multi-arch targets 
(BFD develop
 binutils-source - GNU assembler, linker and binary utilities (source)
Closes: 728529
Changes:
 binutils (2.24.90.20141201-1) unstable; urgency=medium
 .
   * Snapshot, taken from the 2.25 branch 20141201.
 - Fix PR ld/16452, PR/ld/16457: Don't output symbol version
   requirement for non-DT_NEEDED libs. Closes: #728529.
Checksums-Sha1:
 e4a8f165e2dd2edc954f516c74fc397e610d6d03 1810 binutils_2.24.90.20141201-1.dsc
 6158a8b3677c1efccb9d714f651a660ed6aa43a3 29908914 
binutils_2.24.90.20141201.orig.tar.gz
 1049426e96767348486c86d90f02e9882bcbfbc6 120863 
binutils_2.24.90.20141201-1.diff.gz
 794401fdd621d0fd1aaf57c71baec134cf1a0f90 501628 
binutils-doc_2.24.90.20141201-1_all.deb
 86657d7b033151d66290e73379e81c14904c70ac 17149330 
binutils-source_2.24.90.20141201-1_all.deb
 d9092c50f341cb0640b824905589c008a2d056ee 3493698 
binutils_2.24.90.20141201-1_amd64.deb
 8728a4da0ac5293a740d44fef36bf0bd88c1d67f 1916170 
binutils-dev_2.24.90.20141201-1_amd64.deb
 758d907ab2500df27510ed8da888d78b6cf74f43 1649002 
binutils-multiarch_2.24.90.20141201-1_amd64.deb
 df6ac7e1f8c46d87016cb913be3c4b94e38acf40 1376 
binutils-multiarch-dev_2.24.90.20141201-1_amd64.deb
Checksums-Sha256:
 bb6fb865a7152cae304880b8fe02f5ca96bec014dbc29a20ee8a366be33b4ca3 1810 
binutils_2.24.90.20141201-1.dsc
 9b5f20f12c13147930224dea96d029c103dd3a0910da1a218d00e6b47e791508 29908914 
binutils_2.24.90.20141201.orig.tar.gz
 45cd4645143bae0be9a905ad480dfbb87b0ec91ac992500c14e890bae0d0d21

Bug#728507: marked as done (_dl_check_map_versions: Assertion `needed != ((void *)0)' failed!)

[Debian Bug Tracking System]

Your message dated Mon, 01 Dec 2014 23:04:18 +
with message-id 
and subject line Bug#728529: fixed in binutils 2.24.90.20141201-1
has caused the Debian Bug report #728529,
regarding _dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
728529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: smartmontools
Version: 6.2+svn3841-1
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?

some recent upgrades in Debian unstable

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

tried to manually restart smartd

   * What was the outcome of this action?

# /etc/init.d/smartmontools restart
[] Restarting S.M.A.R.T. daemon: smartdInconsistency detected by ld.so: 
dl-version.c: 224: _dl_check_map_versions: 
Assertion `needed != ((void *)0)' failed!

   * What outcome did you expect instead?

the smartd to start

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


-- Package-specific info:
Output of /usr/share/bug/smartmontools:

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

Kernel: Linux 3.12.0-rc7+ (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages smartmontools depends on:
ii  debianutils  4.4
ii  libc62.17-93
ii  libcap-ng0   0.7.3-1
ii  libgcc1  1:4.8.2-1
ii  libselinux1  2.2-1
ii  libstdc++6   4.8.2-1
ii  lsb-base 4.1+Debian12

Versions of packages smartmontools recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20131005cvs-1

Versions of packages smartmontools suggests:
ii  gsmartcontrol   0.8.7-1
pn  smart-notifier  

-- Configuration Files:
/etc/default/smartmontools changed:
start_smartd=yes

/etc/smartd.conf changed:
/dev/disk/by-id/ata-WDC_WD3200AAJB-00WGA0_WD-WCARW6960348 -a -I 194 -W 4,49,55 
-R 5
/dev/disk/by-id/ata-SAMSUNG_SP4002H_0462J1FT349824 -a -I 194 -W 4,49,55 -R 5


-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: binutils
Source-Version: 2.24.90.20141201-1

We believe that the bug you reported is fixed in the latest version of
binutils, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 728...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated binutils package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 01 Dec 2014 21:53:10 +0100
Source: binutils
Binary: binutils binutils-dev binutils-multiarch binutils-multiarch-dev 
binutils-hppa64 binutils-doc binutils-source
Architecture: source all amd64
Version: 2.24.90.20141201-1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 binutils   - GNU assembler, linker and binary utilities
 binutils-dev - GNU binary utilities (BFD development files)
 binutils-doc - Documentation for the GNU assembler, linker and binary utilities
 binutils-hppa64 - GNU assembler, linker and binary utilities targeted for 
hppa64-li
 binutils-multiarch - Binary utilities that support multi-arch targets
 binutils-multiarch-dev - GNU binary utilities that support multi-arch targets 
(BFD develop
 binutils-source - GNU assembler, linker and binary utilities (source)
Closes: 728529
Changes:
 binutils (2.24.90.20141201-1) unstable; urgency=medium
 .
   * Snapshot, taken from the 2.25 branch 20141201.
 - Fix PR ld/16452, PR/ld/16457: Don't output symbol version
   requirement for non-DT_NEEDED libs. Closes: #728529.
Checksums-Sha1:
 e4a8f165e2dd2edc954f516c74fc397e610d6d03 1810 binutils_2.24.90.20141201-1.dsc
 6158a8b3677c1efccb9d714f651a660ed6aa43a3 29908914 
binutils_2.24.90.20141201.orig.tar.gz
 1049426e96767348486c86d90f02e9882bcbfbc6 120863 
binutils_2.24.90.20141201-1.d

Bug#771452: Duplicate object check

[Nikolaus Rath]

On 12/01/2014 02:31 PM, Shannon Dealy wrote:
> On Mon, 1 Dec 2014, Nikolaus Rath wrote:
> 
> [snip]
>> I think at this point I can probably write you a patch to get the file
>> system functional again, but I'd very much like to find out what's
>> happening here.
>>
>> Would you be able to run fsck with --backend-options no-ssl, and capture
>> the traffic using Wireshark?
> 
> Hi Nikolaus,
> 
> I performed several runs of fsck.s3ql while experimenting with wireshark
> (it has been years since I've used it or tcpdump) to get the settings
> right.  Each time, fsck.s3ql failed in the same manner.  Then when I did
> what was to be the final run/capture, it ran to completion without errors.
> 
> Given the behavior above, the first thing that leaps to mind is possibly
> a race condition.  I would usually expect more inconsistency (such as
> failing at different objects each time) if it was simply uninitialized
> data or corruption, though those may be possibilities too.

That's interesting, but it actually fits my hypothesis. fsck.s3ql is
single-threaded, so it's not a race condition. However, when retrieving
the object list from S3, S3QL has to do several requests because S3
forces to "paginize" the list to at most 1 entries per request. I
suspect there might be a bug in the pagination handling that causes an
object to be listed twice.

Most likely, this is only triggered when S3 does something
uncommon-but-legal in its responses. But the only way to check this is
to get a dump of the raw server response. So if you could try this again
a few more times (use the --force option to force an fsck), that would
be fantastic.

> I still have the bucket that was copied using the aws command line
> tools, and am in the process of copying that to a new bucket for testing
> so we don't lose the corrupt version, but won't get to testing it
> tonight.  I have not tried to use the original file system since
> fsck.s3ql succeeded and am not entirely sure if it trust it without
> knowing what was wrong with fsck.s3ql

At this point, I am pretty confident that this is a bug related to
object listing. Object listing is only used by fsck.s3ql, so I think
that using the file system normally (aka with mount.s3ql) should not
result in any problems.

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«


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

Bug#771452: Duplicate object check

[Shannon Dealy]

On Mon, 1 Dec 2014, Nikolaus Rath wrote:

[snip]

I think at this point I can probably write you a patch to get the file
system functional again, but I'd very much like to find out what's
happening here.

Would you be able to run fsck with --backend-options no-ssl, and capture
the traffic using Wireshark?


Hi Nikolaus,

I performed several runs of fsck.s3ql while experimenting with wireshark 
(it has been years since I've used it or tcpdump) to get the settings 
right.  Each time, fsck.s3ql failed in the same manner.  Then when I did 
what was to be the final run/capture, it ran to completion without 
errors.


Given the behavior above, the first thing that leaps to mind is possibly a 
race condition.  I would usually expect more inconsistency (such as 
failing at different objects each time) if it was simply uninitialized 
data or corruption, though those may be possibilities too.


I still have the bucket that was copied using the aws command line tools, 
and am in the process of copying that to a new bucket for testing so we 
don't lose the corrupt version, but won't get to testing it tonight.  I 
have not tried to use the original file system since fsck.s3ql succeeded 
and am not entirely sure if it trust it without knowing what was wrong 
with fsck.s3ql


Something more for you to ponder.  FWIW.

Regards,

Shannon C. Dealy   | DeaTech Research Inc.
de...@deatech.com  |- Custom Software Development -
USA Phone: +1 800-467-5820 |- Natural Building Instruction -
numbers  : +1 541-929-4089 |www.deatech.com


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

Bug#771730: dpkg: yet another trigger cycle, involving initramfs-tools and libc-bin

[Andreas Beckmann]

Package: dpkg
Version: 1.17.22
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts


Hi Guillem,

with the latest dpkg I still get a trigger cycle error on a wheezy->sid
piuparts upgrade test:

  Setting up libdevmapper1.02.1:amd64 (2:1.02.90-2) ...
  Setting up dmsetup (2:1.02.90-2) ...
  update-initramfs: deferring update (trigger activated)
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
initramfs-tools -> libc-bin
   packages' pending triggers which are or may be unresolvable:
libc-bin: ldconfig
initramfs-tools: update-initramfs
  dpkg: error processing package libc-bin (--configure):
   triggers looping, abandoned
  Errors were encountered while processing:
   libc-bin

Just verified that this is repeatable in piuparts and not a one-off
failure.

The new dpkg was long installed and configured before this happened.
Full log attached: nvidia-kernel-amd64_340.46+3.16.0+2.log.gz

I could not reproduce this in an upgrade from wheezy->jessie (i.e. with
dpkg 1.17.21), full log: nvidia-kernel-amd64=340.46+3.16.0+1.log.gz
but of course there are more package versions different ...


If you need more debug information, tell me how to aquire it.


I'm rather opening a new bug than messing with the ones that are supposed
to be fixed in 1.17.22. This could be an independent issue or needs to be
reassigned to another package ... Feel free to downgrade the severity to
not block 1.17.22 from migrating - which should be a good improvement
over 1.17.21.


Andreas


nvidia-kernel-amd64_340.46+3.16.0+2.log.gz
Description: application/gzip


nvidia-kernel-amd64=340.46+3.16.0+1.log.gz
Description: application/gzip

Bug#771729: Depends: gcc-4.9-arm-linux-gnueabihf (>= 4.9.2-2) but it is not installable

[Guido Seifert]

Subject: Depends: gcc-4.9-arm-linux-gnueabihf (>= 4.9.2-2) but it is not 
installable
Package: gcc-arm-linux-gnueabihf
Version: Version: 4.9.2-2
Justification: renders package unusable
Severity: grave

Dear Maintainer,

   * What led up to the situation?
  -> apt-get install gcc-arm-linux-gnueabihf

   I did an apt-get update/upgrade/dist-upgrade, but no effect. 
   It seems gcc-4.9-arm-linux-gnueabihf does not even exists.

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

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


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

Bug#768998: Bug#767010: kadu-dev: KaduTargets.cmake hardcodes amd64 path

[Mateusz Łukasik]

On 01.12.2014 11:57 Julien Cristau wrote:

On Sun, Nov 30, 2014 at 15:58:42 +0100, gregor herrmann wrote:


On Sun, 30 Nov 2014 11:41:11 +0100, Mateusz Łukasik wrote:


kadu-mime-tex should be rebuild by bin-nmu with kadu >= 1.2-2 it fix that
bug. For example now is build fine on armhf:

dpkg-gencontrol: warning: File::FcntlLock not available; using flock which
is not NFS-safe
dpkg-gencontrol: warning: package kadu-mime-tex: unused substitution
variable ${misc:Pre-Depends}
dh_md5sums
dh_builddeb
dpkg-deb: building package `kadu-mime-tex' in
`../kadu-mime-tex_1.0-2_armhf.deb'.
  dpkg-genchanges  >../kadu-mime-tex_1.0-2_armhf.changes
dpkg-genchanges: not including original source code in upload
  dpkg-source --after-build kadu-mime-tex-1.0
dpkg-buildpackage: binary and diff upload (original source NOT included)



So, let's request a giveback on all arches except amd64 (where the
package built):

gb kadu-mime-tex_1.0-2 . ALL -amd64


Given back.

Cheers,
Julien



It looks fine:

https://buildd.debian.org/status/package.php?p=kadu-mime-tex&suite=sid

Mateusz


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

Processed: tagging 761306

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 761306 + pending
Bug #761306 [systemd] v208 -> v215 upgrade fails to re-open notification socket
Bug #771101 [systemd] wheezy -> jessie dist-upgrade failure when systemd is the 
active PID1
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
761306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761306
771101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#771728: ltsp-client-core: hooks in /etc/kernel/postrm.d/ break linux-image package removal on arm

[Vagrant Cascadian]

Package: ltsp-client-core
Version: 5.5.4-1
Severity: serious
Tags: patch

When removing a linux-image package on an armhf system (and presumably
armel as well), mkimage is called in the ltsp-client hook
/etc/kernel/postrm.d/update-kernels, and generates output that causes
the package removal to fail...


Removing symbolic link initrd.img.old
You may need to re-run your boot loader
Purging configuration files for linux-image-3.16.0-4-armmp-lpae (3.16.7-2) ...
dpkg: error processing package linux-image-3.16.0-4-armmp-lpae (--purge):
 subprocess installed post-removal script returned error exit status 128
 Errors were encountered while processing:
  linux-image-3.16.0-4-armmp-lpae

E: Sub-process /usr/bin/dpkg returned an error code (1)

The following patch fixes this by redirecting the mkimage output to
/dev/null.

I plan to upload a fixed package today.

 client/share/ltsp/update-kernels | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/client/share/ltsp/update-kernels b/client/share/ltsp/update-kernels
index 5e079be..1a75103 100755
--- a/client/share/ltsp/update-kernels
+++ b/client/share/ltsp/update-kernels
@@ -352,7 +352,8 @@ tftpboot \${kernel_addr_r} \${serverip}:${kernel_file} \\
 EOF
 
 mkimage -A arm -O Linux -T script -C none -a 0x0 -e 0x0 \
--n 'LTSP boot script' -d $BOOT/boot.ltsp $BOOT/boot.scr
+-n 'LTSP boot script' -d $BOOT/boot.ltsp $BOOT/boot.scr \
+> /dev/null

 # Copy .dtb files to boot dir.
 dtb_dirs="/usr/lib/linux-image-${version}/"


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#771132: morse-simulator is not usable with the current version of blender

[Pablo Oliveira]

Hi Séverin,

Séverin Lemaignan  wrote:
> For sanity check, can you post the output of `morse --version`?

Sure:

morse 1.2.1

> Thanks for your report. MORSE 1.2.1 is indeed expected to support Blender 
> 2.72.

>From my tests, MORSE 1.2.1 does not work out of the box with Blender 2.72. I
relaxed the version check at morse:48 and ran into another problem. Apparently,
Blender 2.72 has substituded the link_append method by two separate link and 
append
methods 
(http://blender.stackexchange.com/questions/17876/import-object-without-bpy-ops-wm-link-append).
To make morse work on my system I had to patch line 63 of
/usr/lib/python3/dist-packages/morse/builder/bpymorse.py with "link_append = 
bpy.ops.wm.link"

Thanks,

Pablo Oliveira


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

Bug#771727: fex: postinst uses /usr/share/doc content (Policy 12.3)

[Andreas Beckmann]

Package: fex
Version: 20140917-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
https://www.debian.org/doc/debian-policy/ch-docs.html#s12.3

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

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

  Selecting previously unselected package fex.
  (Reading database ... 9826 files and directories currently installed.)
  Preparing to unpack .../fex_20140917-1_all.deb ...
  Unpacking fex (20140917-1) ...
  Setting up fex (20140917-1) ...
  Adding group `fex' (GID 152) ...
  Done.
  Adding system user `fex' (UID 151) ...
  Adding new user `fex' (UID 151) with group `fex' ...
  Not creating home directory `/usr/share/fex'.
  Installing initial copy of htdocs into /var/lib/fex/htdocs ...
  Initializing /etc/fex/fex.ph with correcting hostname (using: 
myhost.domain.example.com)
  gzip: /usr/share/doc/fex/examples/fex.ph.gz: No such file or directory
  Logdir still pointing to $spooldir. Please update to /var/log/fex
  in order to take full advantage of logrotate settings.
  Once you have updated your configfiles just run:
 dpkg-reconfigure fex
  To have the logfiles moved into their new location
  Error: The new file /usr/share/doc/fex/examples/xinetd_fex does not exist!
  dpkg: error processing package fex (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   fex


Cheers,

Andreas


fex_20140917-1.log.gz
Description: application/gzip

Bug#770534: marked as done (icinga2-common: fails to install: icinga2-common.postinst: icinga2: not found)

[Debian Bug Tracking System]

Your message dated Mon, 01 Dec 2014 21:49:23 +
with message-id 
and subject line Bug#770534: fixed in icinga2 2.2.1-1
has caused the Debian Bug report #770534,
regarding icinga2-common: fails to install: icinga2-common.postinst: icinga2: 
not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
770534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icinga2-common
Version: 2.2.0-1
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 icinga2-common.
  (Reading database ... 8297 files and directories currently installed.)
  Preparing to unpack .../icinga2-common_2.2.0-1_all.deb ...
  Unpacking icinga2-common (2.2.0-1) ...
  Setting up icinga2-common (2.2.0-1) ...
  Adding system-user for nagios
  enabling default icinga2 features
  /var/lib/dpkg/info/icinga2-common.postinst: 32: 
/var/lib/dpkg/info/icinga2-common.postinst: icinga2: not found
  dpkg: error processing package icinga2-common (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   icinga2-common


cheers,

Andreas


icinga2-common_2.2.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: icinga2
Source-Version: 2.2.1-1

We believe that the bug you reported is fixed in the latest version of
icinga2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 770...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Wirt  (supplier of updated icinga2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 01 Dec 2014 20:48:59 +0100
Source: icinga2
Binary: icinga2 icinga2-common icinga2-bin icinga2-doc icinga2-classicui 
icinga2-ido-mysql icinga2-ido-pgsql icinga2-dbg
Architecture: source amd64 all
Version: 2.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Alexander Wirt 
Description:
 icinga2- host and network monitoring system
 icinga2-bin - host and network monitoring system - daemon
 icinga2-classicui - host and network monitoring system - classic UI
 icinga2-common - host and network monitoring system - common files
 icinga2-dbg - host and network monitoring system - debug symbols
 icinga2-doc - host and network monitoring system - documentation
 icinga2-ido-mysql - host and network monitoring system - MySQL support
 icinga2-ido-pgsql - host and network monitoring system - PostgreSQL support
Closes: 770534 770743
Changes:
 icinga2 (2.2.1-1) unstable; urgency=medium
 .
   [ Alexander Wirt ]
   * [e73d057] Links are tested with -L
   * [d605522] Just to be safe, use -e to check for the old apache configfile.
 (Closes: #770743)
   * [05f8f54] Move enable-feature to icinga2-bin (Closes: #770534)
   * [c6fd841] Imported Upstream version 2.2.1
   * [1135583] Add is_fresh_install to icinga2-bin postinst
   * [1deb08b] icinga2-prepare-dirs was renamed to prepare-dirs
 .
   [ Gunnar Beutner ]
   * [c3d13b5] Fix support for Apache 2.4
Checksums-Sha1:
 e9bdd117eff414c0b87a677c04bee92b1d42dfa4 2636 icinga2_2.2.1-1.dsc
 215f6f5eb85cb997b006960e1d636d59b6d7e352 683579 icinga2_2.2.1.orig.tar.gz
 010c7a2d8a7dd54bce71187bda056e27ff0fe0bb 26260 icinga2_2.2.1-1.debian.tar.xz
 b98ce84a77c6232388af917d74b78a2304967cc9 17940 icinga2_2.2.1-1_amd64.deb
 0c092c4bc13a455df0b8ea6269499f9abfaeedc1 34916 icinga2-common_2.2.1-1_all.deb
 899813cfd4994de266a646950bb9ec7e29d09575 2243330 icinga2-bin_2.2.1-1_amd64.deb
 1161bb3dc10758d02cfacca19e2eb794ba7fdfdb 144026 icinga2-doc_2.2.1-1_all.deb
 afe6c39d125d3789d7f7097bb0627a7ba6596200 28960 
icinga2-classicui_2.2.1-1_all.deb
 c5a29c0399a70970163b2aedbab2309e239ba80c 119976 
icinga2-ido-mysql_2.2.1-1_amd64.deb
 d16f39d9eee9e95c47970613641cdff6540e64fa 122640 
icinga2-ido-pgsql_2.2.1-1_am

Bug#771723: systemd: systemd: kernel panic as /sbin/init cannot load libapparmor1.so

[Tobias Schlemmer]

Package: systemd
Version: 217-1
Severity: critical
Justification: breaks the whole system

Somehow I eneded up with an unusable system due to /sbin/init was not booting.
After installing sysvinit-core the system booted normal. Sorry, but I did not
get reportbug to report bugs from the console when I booted with
“init=/bin/bash”.

The problem is related to libapparmor1, which cannot be found as it seems to be
installed in /usr/lib and not in /lib. And /usr is mounted after starting init
as usual.
So trying to load systemd the kornel is not able to load the shared libraries
and crashes with a kernel panic.

I might be out of date, but as far as I know no files that are needed at boot
must occur below /usr.




-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-58
ii  libacl1 2.2.52-2
ii  libapparmor12.9.0-2
ii  libaudit1   1:2.4-1
ii  libblkid1   2.25.2-3
ii  libc6   2.19-13
ii  libcap2 1:2.24-6
ii  libcap2-bin 1:2.24-6
ii  libcryptsetup4  2:1.6.6-3
ii  libgcrypt20 1.6.2-4
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 217-1
ii  mount   2.25.2-3
ii  sysv-rc 2.88dsf-58
ii  udev215-7
ii  util-linux  2.25.2-3

Versions of packages systemd recommends:
ii  dbus1.8.12-1
ii  libpam-systemd  217-1

Versions of packages systemd suggests:
pn  systemd-ui  

-- Configuration Files:
/etc/systemd/resolved.conf 886b81674c4697d8949d0fba0e21907d [Errno 2] Datei 
oder Verzeichnis nicht gefunden: u'/etc/systemd/resolved.conf 
886b81674c4697d8949d0fba0e21907d'

-- no debconf information


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

Bug#771700: marked as done ([freecol] freecol freezes on intro)

[Debian Bug Tracking System]

Your message dated Mon, 01 Dec 2014 21:34:31 +
with message-id 
and subject line Bug#771700: fixed in freecol 0.10.7+dfsg-3
has caused the Debian Bug report #771700,
regarding [freecol] freecol freezes on intro
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: freecol
Version: 0.10.7+dfsg-2
Severity: grave

--- Please enter the report below this line. ---
On startup in the into movie, freecol freezes. No interaction is 
possible.
I had tested it with Oracle JDK 1.7.0_72 and openjdk7. The same behavior 
on both.


Problem is known upstream: https://sourceforge.net/p/freecol/bugs/2703/.
I had added log to the upstream bug report.

A possible workaround is, to disable the intro.
Add "--no-intro" in /usr/games/freecol to the excecution command.


regards,
Sascha

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16.0-4-amd64

Debian Release: jessie/sid
  995 testing ftp.de.debian.org
   950 jessie-backports ftp.de.debian.org
 1000 testing-updates ftp.de.debian.org
 1000 testing-proposed-updates ftp.de.debian.org

--- Package information. ---
Depends  (Version) | Installed
==-+-===
openjdk-6-jre  |
 OR java6-runtime  |
java-wrappers  (>= 0.1.13) | 0.1.28
libcommons-cli-java| 1.2-3
libcortado-java| 0.6.0-2
libmiglayout-java  | 4.2-1
fonts-liberation(>= 1.07.0-2~) | 1.07.4-1


Package's Recommends field is empty.

Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Source: freecol
Source-Version: 0.10.7+dfsg-3

We believe that the bug you reported is fixed in the latest version of
freecol, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 771...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vincent Fourmond  (supplier of updated freecol package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 01 Dec 2014 21:30:25 +0100
Source: freecol
Binary: freecol
Architecture: source all
Version: 0.10.7+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Vincent Fourmond 
Description:
 freecol- open source remake of the old Colonization
Closes: 771700
Changes:
 freecol (0.10.7+dfsg-3) unstable; urgency=medium
 .
   * Disable intro video to avoid hanging at startup (closes: #771700)
Checksums-Sha1:
 8db972f3a3ddb9c2a03ea357a0f5f63a98e11c92 1821 freecol_0.10.7+dfsg-3.dsc
 439b5d9ca42e4867c60f9345b85321853079c875 9264 
freecol_0.10.7+dfsg-3.debian.tar.xz
 b7af8907e28ade2b7b1b21ec502f0357a45be387 35463044 freecol_0.10.7+dfsg-3_all.deb
Checksums-Sha256:
 67b04fe3a15eab3389daf9eb0cf2c483b25531178177cd947d2948fab94a57dd 1821 
freecol_0.10.7+dfsg-3.dsc
 b8b9042c5156260bb9f8dbd7e5cf96e3023d6a935948e39c3bd1abb8545f892e 9264 
freecol_0.10.7+dfsg-3.debian.tar.xz
 6a74acfddb5d379d59e67d0d7046e67a0a0ade0ece952bfab9b4c721ef65d256 35463044 
freecol_0.10.7+dfsg-3_all.deb
Files:
 4feaeb40e0f6ee28f7452420bc7365e7 1821 games optional freecol_0.10.7+dfsg-3.dsc
 81b220e92659069212cf7081173f2086 9264 games optional 
freecol_0.10.7+dfsg-3.debian.tar.xz
 eaa14048f70b52dfc2a0c734958479f3 35463044 games optional 
freecol_0.10.7+dfsg-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJUfNnJAAoJEO3GeJm/E8RX9/kH/2bc9b2R+lpthKDdf7OK66+b
ZyWqF/76UeOjO//OREIk4akqCxPRT7w+7khq+4bUQ8T6NvPlyHEAgWZNBiqb8+iL
6CRr13SeUT+HpXeM47GqAy0RZyf5xZ8+BgfHinVlKbQNP4d6c0lLH/9K46Syi7Ju
QLZMZk0bd+KWOEhXI84yutTilMDtofUzuz1Z4XqQRzH28EwQ//xkH2rxWiGLBJHY
OO1dWvi4WimJkv4xhyFL4gafXUQKNMm0LXP7FY//i9RUl9HQrPcJm04hh30PD7xU
oJksz8qOMGs5cwqWuhZ8iPPImjfqcngE7obwaiYFaMTIBPIVHeAqZCtR5Fm0PX0=
=vEs4
-END PGP SIGNATURE End Message ---

Processed: tagging 770194

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 770194 - jessie
Bug #770194 [src:ruby-stringex] ruby-stringex: FTBFS: Test failures
Ignoring request to alter tags of bug #770194 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
770194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: tagging 765124

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 765124 - jessie
Bug #765124 [ruby-i18n] ruby-stringex: FTBFS: ERROR: Test "ruby2.1" failed: 
Running tests for ruby2.1 using debian/ruby-tests.rake ...
Removed tag(s) jessie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
765124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#771177: marked as done (develock-el: breaks c++ mode in sid and jessie)

[Debian Bug Tracking System]

Your message dated Mon, 01 Dec 2014 21:19:13 +
with message-id 
and subject line Bug#771177: fixed in develock-el 0.39-2
has caused the Debian Bug report #771177,
regarding develock-el: breaks c++ mode in sid and jessie
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: develock-el
Version: 0.39-1
Severity: grave
Justification: renders package unusable

This package completely breaks the standard emacs c++ mode.

To reproduce: open the attached .cpp file and try to indent the
second line using tab.

This was fixed upstream and updating the package to 0.45 fixes
this problem.

I suggest doing this as soon as possible so that a freeze
exception can be requested for jessie. I'm happy to do an
NMU for it if you don't have time. Let me know if you need
my help.

Francois

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

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

Versions of packages develock-el depends on:
ii  emacs  46.1
ii  emacs24 [emacsen]  24.4+1-4

develock-el recommends no packages.

develock-el suggests no packages.

-- no debconf information
int main() {
return 0;
}
--- End Message ---
--- Begin Message ---
Source: develock-el
Source-Version: 0.39-2

We believe that the bug you reported is fixed in the latest version of
develock-el, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 771...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mehdi Dogguy  (supplier of updated develock-el package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Dec 2014 20:59:57 +0100
Source: develock-el
Binary: develock-el
Architecture: source all
Version: 0.39-2
Distribution: unstable
Urgency: medium
Maintainer: Mehdi Dogguy 
Changed-By: Mehdi Dogguy 
Description:
 develock-el - additional font-lock keywords for the developers on Emacs
Closes: 771177
Changes:
 develock-el (0.39-2) unstable; urgency=medium
 .
   * Fix compatibility with Emacs's C++ mode (Closes: #771177).
Checksums-Sha1:
 9e373bd2492de15c402a55081d0ded063e505043 1831 develock-el_0.39-2.dsc
 751bda56a70d1cb08ec6bba2010e5c59e27b6930 6008 develock-el_0.39-2.debian.tar.xz
 15c463167e63e15c2e637fab4b5976392b192cf7 17690 develock-el_0.39-2_all.deb
Checksums-Sha256:
 296f3f649b452fdc3695dcbba9a59dfa7409075ac6540e3474cef57aef00decd 1831 
develock-el_0.39-2.dsc
 616891977e1c24acc02b26bde5c38a22a9b30466744269db30dadf092dd04a2c 6008 
develock-el_0.39-2.debian.tar.xz
 0549b34c647a71b06fb262ed86db4af658126d996cc4ebb2290dd4f243626e9e 17690 
develock-el_0.39-2_all.deb
Files:
 fe76c8e9f9c117c86015d6913e5d39fc 1831 editors optional develock-el_0.39-2.dsc
 b3d15d9e00fc210a4126ac19b9ff0976 6008 editors optional 
develock-el_0.39-2.debian.tar.xz
 26f418674e26efdca70641c4c3071510 17690 editors optional 
develock-el_0.39-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJUfMs1AAoJEDO+GgqMLtj/ZD8QAMF3au2ODicrL+HGe4GJnTPH
6FPICxcb9KqoSvs1jkZcIUaAflEsj41zURzcXzZWynKX46i1xVrkPB87IvRaiMly
OjgYHhixYaiZdE9x8mfuCq6ihZs3SVMkyFLrqatJN9yBt4xPMiVyWuUbvHrhzfwZ
2zjWVJvlq/kdhdnR0Z2YLwY+qwBCXxb3yrmu26LHOAq4OrLv8RuLm45/jRWndX9U
/ipavuZBxESFxzGxCUHL1cJ0Z7Z5OG59lER6H3udsY8oJBk0WysjbXlqrupKWVRl
4S5YNuauT/JDFMLybFs+4f/Z4LiDnqG/SyUi9aOY6Abf6thhoIkbm6boa672VL3K
86Cf+hyRkpfyUYzk9paaOrpyicJIon4OQItHwo6ecdLSkbDeWqRxSDtOL+/5ZDKD
vr9+Mkz8nbP3mV+NK/tB7RJ1R8dNBklERz6x+6OmOEPZniC0rXi9vxaEkXwjOTGk
aNTHiqJD3sfB2tH+6ndAW8fusxa409LwtqFZ2+wlGlJylac38TZijtVopcszPxUi
xXIYDseiA8UU+jaMMrignwQx/GeceugQjzTn+6xpM9PjGy6yuzG8VGk0XRIh7r5y
PhRlY0wJiZ3vmh/u8sz8MW9aS6P4YnEX35YqA5jUCuI9iSMOUoCHcFjzt3MMkG6u
IxkJ6V31GjGUl4Lqnv52
=hkaQ
-END PGP SIGNATURE End Message ---

Bug#771719: tcplay: does not support discs with 4k sectors

[Ralf Jung]

Package: tcplay
Version: 1.1-1+b1
Severity: critical
Tags: upstream
Justification: causes serious data loss

Dear Maintainer,

tcplay does not properly support discs with 4k sectors: They are opened, but
reading from the disc produces wrong results, and writing to the discs results
in data the official TrueCrypt cannot read. This can lead to irrecoverable
data loss if any writes are performed on the disk.

This was reported and fixed upstream a while ago already [1], so I assume
version 2.0 (released more than half a year ago) fixed the problem.

Kind regards,
Ralf


[1] 

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

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

Versions of packages tcplay depends on:
ii  libc6   2.19-13
ii  libdevmapper1.02.1  2:1.02.90-2
ii  libgcrypt20 1.6.2-4
ii  libgpg-error0   1.17-2
ii  libuuid12.25.2-3

tcplay recommends no packages.

tcplay suggests no packages.

-- no debconf information


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

Bug#761306: Bug#771101: Bug#761306: Bug#771101: wheezy -> jessie dist-upgrade failure when systemd is the active PID1

[Sjoerd Simons]

On Thu, Nov 27, 2014 at 05:48:45PM +0100, Michael Biebl wrote:
> Am 27.11.2014 um 16:41 schrieb Michael Biebl:
> > Am 27.11.2014 um 15:59 schrieb Michael Biebl:
> >> I would have expected, that the socket does *not* exist before systemd
> >> is re-execd, but apparently I had a file there:
> >>
> >>  srw-rw-rw- 1 root root 0 Oct 10 10:41 /run/systemd/notify
> >>
> >> and no process listening on it.
> >> (don't worry about the date, it was run in a VM with a busted clock).
> >>
> >> *Some* process is triggering the creation of the notification socket and
> >> it also seems to have the wrong permissions (should be srwxrwxrwx).
> > 
> > It's actually a bit simpler: v44 *did* already use /run/systemd/notify
> > (with permissions srw-rw-rw-), then it was changed to use an abstract
> > namespace and it was changed back and forth a couple of times.
> > Maybe a simple chmod will do when upgrading from v44. Will test.
> 
> Sjoerd, you mentioned in your bug report, that you upgraded from v208->v215
> 
> v208 uses an abstract socket though, so I'm not sure if it's actually
> the same issue.
> Did you maybe first upgrade from v44 to v208 and then did the
> dist-upgrade to v215?

No pretty sure it was from v208 directly. I was just re-reading the code of
upstream system again it it looks like upstream now removes the old socket file
right before calling bind:
  f0e62e89970b8c38eb07a9beebd277ce13a5fcc2

We probably should backport that one, which should solve both issues.


-- 
Fill what's empty, empty what's full, scratch where it itches.
-- Alice Roosevelt Longworth


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

Bug#771700: [freecol] freecol freezes on intro

[Vincent Fourmond]

On Mon, Dec 1, 2014 at 8:27 PM, Vincent Fourmond  wrote:
> On Mon, Dec 1, 2014 at 8:20 PM, Markus Koschany  wrote:
>> On 01.12.2014 19:42, Sascha Kühndel (InuSasha) wrote:
>>> Package: freecol
>>> Version: 0.10.7+dfsg-2
>>> Severity: grave
>>>
>>> --- Please enter the report below this line. ---
>>> On startup in the into movie, freecol freezes. No interaction is possible.
>>> I had tested it with Oracle JDK 1.7.0_72 and openjdk7. The same behavior
>>> on both.
>>>
>>> Problem is known upstream: https://sourceforge.net/p/freecol/bugs/2703/.
>>> I had added log to the upstream bug report.
>>>
>>> A possible workaround is, to disable the intro.
>>> Add "--no-intro" in /usr/games/freecol to the excecution command.
>>
>>
>> Hi,
>>
>> thanks for the report. It seems upstream hasn't found a real solution
>> for this issue yet but the workaround seems to work. Adding --no-intro
>> to our wrapper script would be a good idea.
>
>   Reading through the whole report, there seems to be problems further
> down (game doesn't start). I'll check that right now.

  As far as I can tell, running with the --no-intro works for me, so
I'll upload that workaround tonight.

  Regards,

  Vincent


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

Processed: Re: Bug#770672: gnome-packagekit: FTBFS without docbook: reference to entity "REFENTRY" for which no system identifier could be generated

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #770672 [src:gnome-packagekit] gnome-packagekit: FTBFS without docbook: 
reference to entity "REFENTRY" for which no system identifier could be generated
Severity set to 'important' from 'serious'

-- 
770672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#770672: gnome-packagekit: FTBFS without docbook: reference to entity "REFENTRY" for which no system identifier could be generated

[Matthias Klumpp]

Control: severity -1 important

Hi!

2014-12-01 20:14 GMT+01:00 gregor herrmann :
> On Sun, 23 Nov 2014 00:25:39 -0800, Daniel Schepler wrote:
>
>> Source: gnome-packagekit
>> Version: 3.14.0-1
>> Severity: serious
>>
>> From my pbuilder build log, using an archive of locally rebuilt packages:
> [..]
>> It would seem that with this archive,
>
> I'm a bit confused by your local archive and how it differes from the
> offical one.
>
>> docbook doesn't automatically get pulled
>> in as a dependency of the Build-Depends; and this is valid because only
>> docbook-dsssl brings it in, and its dependency is actually on
>> "docbook (>= 3.1) | docbook-xml".
>
> FWIW, I built 3.14.0-1 in a jessie and sid chroot (amd64 cowbuilder),
> and in both cases docbook gets installed and the builds succeed.
I agree. I also tried to reproduce this several times, using pbuilder,
sbuild with a Debian Sid and Tanglu Bartholomea chroot, and it never
FTBFS due to a missing docbook.
Daniel, can you maybe provide more information about this?
Reducing severity to important, since I doubt this bug is RC (the
Debian builders also seem to be able to build it).
Cheers,
Matthias

-- 
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/


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

Bug#771700: [freecol] freecol freezes on intro

[Vincent Fourmond]

  Heya,

On Mon, Dec 1, 2014 at 8:20 PM, Markus Koschany  wrote:
> On 01.12.2014 19:42, Sascha Kühndel (InuSasha) wrote:
>> Package: freecol
>> Version: 0.10.7+dfsg-2
>> Severity: grave
>>
>> --- Please enter the report below this line. ---
>> On startup in the into movie, freecol freezes. No interaction is possible.
>> I had tested it with Oracle JDK 1.7.0_72 and openjdk7. The same behavior
>> on both.
>>
>> Problem is known upstream: https://sourceforge.net/p/freecol/bugs/2703/.
>> I had added log to the upstream bug report.
>>
>> A possible workaround is, to disable the intro.
>> Add "--no-intro" in /usr/games/freecol to the excecution command.
>
>
> Hi,
>
> thanks for the report. It seems upstream hasn't found a real solution
> for this issue yet but the workaround seems to work. Adding --no-intro
> to our wrapper script would be a good idea.

  Reading through the whole report, there seems to be problems further
down (game doesn't start). I'll check that right now.

  Regards,

  Vincent


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

Bug#771700: [freecol] freecol freezes on intro

[Markus Koschany]

On 01.12.2014 19:42, Sascha Kühndel (InuSasha) wrote:
> Package: freecol
> Version: 0.10.7+dfsg-2
> Severity: grave
> 
> --- Please enter the report below this line. ---
> On startup in the into movie, freecol freezes. No interaction is possible.
> I had tested it with Oracle JDK 1.7.0_72 and openjdk7. The same behavior
> on both.
> 
> Problem is known upstream: https://sourceforge.net/p/freecol/bugs/2703/.
> I had added log to the upstream bug report.
> 
> A possible workaround is, to disable the intro.
> Add "--no-intro" in /usr/games/freecol to the excecution command.


Hi,

thanks for the report. It seems upstream hasn't found a real solution
for this issue yet but the workaround seems to work. Adding --no-intro
to our wrapper script would be a good idea.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#770672: gnome-packagekit: FTBFS without docbook: reference to entity "REFENTRY" for which no system identifier could be generated

[gregor herrmann]

On Sun, 23 Nov 2014 00:25:39 -0800, Daniel Schepler wrote:

> Source: gnome-packagekit
> Version: 3.14.0-1
> Severity: serious
> 
> From my pbuilder build log, using an archive of locally rebuilt packages:
[..]
> It would seem that with this archive, 

I'm a bit confused by your local archive and how it differes from the
offical one.

> docbook doesn't automatically get pulled
> in as a dependency of the Build-Depends; and this is valid because only
> docbook-dsssl brings it in, and its dependency is actually on
> "docbook (>= 3.1) | docbook-xml".

FWIW, I built 3.14.0-1 in a jessie and sid chroot (amd64 cowbuilder),
and in both cases docbook gets installed and the builds succeed.

Therefore I'm a bit skeptical that we actually have a serious bug
here.


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: Status Quo: Rollin' Home


signature.asc
Description: Digital Signature

Bug#771700: [freecol] freecol freezes on intro

[InuSasha]

Package: freecol
Version: 0.10.7+dfsg-2
Severity: grave

--- Please enter the report below this line. ---
On startup in the into movie, freecol freezes. No interaction is 
possible.
I had tested it with Oracle JDK 1.7.0_72 and openjdk7. The same behavior 
on both.


Problem is known upstream: https://sourceforge.net/p/freecol/bugs/2703/.
I had added log to the upstream bug report.

A possible workaround is, to disable the intro.
Add "--no-intro" in /usr/games/freecol to the excecution command.


regards,
Sascha

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16.0-4-amd64

Debian Release: jessie/sid
  995 testing ftp.de.debian.org
   950 jessie-backports ftp.de.debian.org
 1000 testing-updates ftp.de.debian.org
 1000 testing-proposed-updates ftp.de.debian.org

--- Package information. ---
Depends  (Version) | Installed
==-+-===
openjdk-6-jre  |
 OR java6-runtime  |
java-wrappers  (>= 0.1.13) | 0.1.28
libcommons-cli-java| 1.2-3
libcortado-java| 0.6.0-2
libmiglayout-java  | 4.2-1
fonts-liberation(>= 1.07.0-2~) | 1.07.4-1


Package's Recommends field is empty.

Package's Suggests field is empty.


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

Processed: Re: /var/lib/dpkg/tmp.ci/preinst: 6: /var/lib/dpkg/tmp.ci/preinst: upgrade: not found

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 771684 serious
Bug #771684 [chromium] /var/lib/dpkg/tmp.ci/preinst: 6: 
/var/lib/dpkg/tmp.ci/preinst: upgrade: not found
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: tagging 754219

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # the patch for the watchfile does not fix the actual issues of this bug 
> report
> tags 754219 - patch
Bug #754219 [xdg-utils] several breakages in xdg-utils 1.1.0~rc1 (esp. MATE)
Removed tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
754219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#769214: marked as done (dmtcp: FTBFS in jessie: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 01 Dec 2014 17:48:47 +
with message-id 
and subject line Bug#769214: fixed in dmtcp 2.3.1-6
has caused the Debian Bug report #769214,
regarding dmtcp: FTBFS in jessie: test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
769214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dmtcp
Version: 2.3.1-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-2014-11-11 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»/contrib'
> make[2]: Nothing to be done for 'default'.
> make[2]: Leaving directory '/«PKGBUILDDIR»/contrib'
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> env PWD=`pwd` ./test/autotest.py --retry-once --slow
> Making all in mtcp
> Making all in plugin
> /tmp/ccJfpFuf.o: In function `xtmpnam':
> /«PKGBUILDDIR»/test/syscall-tester.c:208: warning: the use of `tmpnam' is 
> dangerous, better use `mkstemp'
> dmtcp1 Verifying there is enough disk space ...
> == Tests ==
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp2 
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp3 
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp4 
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp5 
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsyscall-tester 
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDfile1  
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcpaware1
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDplugin-sleep2  
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDplugin-example-db
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDgettimeofday   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsigchild   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDshared-fd  
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDstale-fd   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpoll   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDforkexec   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDwaitpid
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDclient-server  
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDfrisbee
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDshared-memory  
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-shm1  
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-shm2  
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-sem   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-msg   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDposix-mq1  
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDposix-mq2  
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpty2   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDtimer  
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDclock  
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdlopen1
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread1   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread2   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread3   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread4   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread5   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDgzip   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDperl   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpython 
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDbash   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdash   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDscript 
> ckpt:   FAILED
> script root-pids: [23184] msg: checkpoint error, 4 expected, 0 found, 
> running=0
> Trying once again
> ckpt:   FAILED
> openmp-1   root-pids: [23208] msg: checkpoint error, 4 expected, 0 found, 
> running=0
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDopenmp-2   
> ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSED
> == Summary ==
> ip-172-31-15-17: 42 of 43 tests passed
> make: *** [build-stamp] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014-11-11/dmtcp_2.3.1-5_jessie.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/F

Bug#768245: marked as done (opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Mon, 01 Dec 2014 17:34:16 +
with message-id 
and subject line Bug#768245: fixed in opendnssec 1:1.4.6-5
has caused the Debian Bug report #768245,
regarding opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory 
conversion: /usr/share/doc/PACKAGE
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
768245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opendnssec-enforcer-sqlite3,opendnssec-enforcer-mysql
Version: 1:1.4.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  wheezy -> jessie

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

1m5.2s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/opendnssec-enforcer-sqlite3/NEWS.Debian.gz 
(opendnssec-enforcer-sqlite3) != 
/usr/share/doc/opendnssec-enforcer/NEWS.Debian.gz (opendnssec-enforcer)
  /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.Debian.gz 
(opendnssec-enforcer-sqlite3) != 
/usr/share/doc/opendnssec-enforcer/changelog.Debian.gz (opendnssec-enforcer)
  /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.gz 
(opendnssec-enforcer-sqlite3) != 
/usr/share/doc/opendnssec-enforcer/changelog.gz (opendnssec-enforcer)
  /usr/share/doc/opendnssec-enforcer-sqlite3/copyright 
(opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-enforcer/copyright 
(opendnssec-enforcer)

1m9.5s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/opendnssec-enforcer-mysql/NEWS.Debian.gz 
(opendnssec-enforcer-mysql) != 
/usr/share/doc/opendnssec-enforcer/NEWS.Debian.gz (opendnssec-enforcer)
  /usr/share/doc/opendnssec-enforcer-mysql/changelog.Debian.gz 
(opendnssec-enforcer-mysql) != 
/usr/share/doc/opendnssec-enforcer/changelog.Debian.gz (opendnssec-enforcer)
  /usr/share/doc/opendnssec-enforcer-mysql/changelog.gz 
(opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-enforcer/changelog.gz 
(opendnssec-enforcer)
  /usr/share/doc/opendnssec-enforcer-mysql/copyright 
(opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-enforcer/copyright 
(opendnssec-enforcer)


cheers,

Andreas


opendnssec-enforcer-sqlite3_1:1.4.6-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: opendnssec
Source-Version: 1:1.4.6-5

We believe that the bug you reported is fixed in the latest version of
opendnssec, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 768...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated opendnssec package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Dec 2014 17:56:04 +0100
Source: opendnssec
Binary: opendnssec-c

Bug#768245: opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Ondřej Surý]

Andreas,

many thanks. I have just uploaded fixed package, and I really hope this
is the last update :).

Cheers,
Ondrej

On Mon, Dec 1, 2014, at 01:58, Andreas Beckmann wrote:
> Control: found -1 1:1.4.6-4
> Control: severity -1 serious
> Control: tag -1 - moreinfo
> 
> On 2014-11-06 10:40, Andreas Beckmann wrote:
> > On 2014-11-06 08:50, Ondřej Surý wrote:
> >> both opendnssec-enforcer-sqlite3 and opendnssec-enforcer-mysql uses
> >> dpkg-maintscript-helper to replace the symlink with directory:
> >>
> >> ondrej@lettie:~/Projects/pkg-nlnetlabs/opendnssec/debian (master)$ cat
> >> opendnssec-enforcer-mysql.maintscript 
> >> symlink_to_dir /usr/share/doc/opendnssec-enforcer-mysql/
> >> /usr/share/doc/opendnssec-common/ 1:1.4.6-2~ -- "$@"
> 
> > But probably it's the old-target. IMO this should be what
> > $(readlink $pathname) returns. You used $(readlink -f $pathname) plus a
> > trailing slash. Also you have a trailing slash on $pathname.
> 
> Yes, it is the old target. And it is so obvious that we overlooked it
> completely:
> 
> The error is:
> 
> /usr/share/doc/opendnssec-enforcer-sqlite3/NEWS.Debian.gz
> (opendnssec-enforcer-sqlite3) !=
> /usr/share/doc/opendnssec-enforcer/NEWS.Debian.gz (opendnssec-enforcer)
> 
> the scripts have:
> 
> dpkg-maintscript-helper symlink_to_dir
> /usr/share/doc/opendnssec-enforcer-sqlite3
> /usr/share/doc/opendnssec-common 1:1.4.6-2~ -- "$@"
> 
> 
> The old target must be "-enforcer", not "-common".
> 
> Don't forget to bump the LASTVERSION to 1:1.4.6-5~ to also attempt to
> clean up failed cleanup.
> 
> 
> Andreas


-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


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

Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

[Eric Valette]

On 01/12/2014 15:08, Martin Pitt wrote:

Hello again,

Eric Valette [2014-12-01 10:11 +0100]:

After fixing the libapparmor in /usr bug, I managed to boot but kdm was
not started.


This is most likely due to Didier's new generator to read
/etc/X11/default-display-manager and only start that one. What does
that file contain on your system?


more /etc/X11/default-display-manager
/usr/bin/kdm

--eric


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

Bug#769106: python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook.

[Matthias Klose]

On 11/21/2014 03:02 PM, Scott Kitterman wrote:

On IRC, an alternate solution was suggested.

What about moving the rtinstall call from the python2.7-minimal postinst to
python2.7's and then have python2.7 depend on python-minimal?

That would resolve this issue and not create a dependency loop.  Would it
cause any other 'bad' things?


I don't think this solves the issue. The idea is to have everything about 
byte-compilation in the -minimal packages. Whoever said that, I think the 
pre-dependency is the least invasive solution



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

Bug#771685: lvm2: system fails to boot when using lvm2 with upstart

[ewew]

Package: lvm2
Version: 2.02.95-8
Severity: grave
Justification: renders package unusable



Hello

Recently i haved tested upstart on debian jessie with lvm, but problem with
boot has appeared. The system is unable to boot when lvm volume is created.
It seems that boot can continue if no lvm volume is created, but needed library
can by present in the system. Other solutions on this problem has not been 
effective. Even lvm2.conf file from debian does not work.
Debug indicates that upstart is stuck on some kind of signal or something.
Attempt to mount desired lvm volumes from command line was successfull with 
init replaced with bash.

Thank You

Have a nice day

ewew


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

Bug#768876: unblock: busybox/1:1.22.0-14

[Cyril Brulebois]

Michael Tokarev  (2014-12-01):
> So, can someone please tell me what's wrong with this unblock request?

I did write in my first reply:

  “At this stage, I'd rather see the security fix only.”

> I can try to fix built-using generation adding gcc to the mix but I'm
> afraid to do that this late in the release cycle, especially after it
> required so many iterations to get the most important in this context
> part of built-using.  Note that this most important part - which
> prompted the original bug report wrt built-using - is here with proper
> value (it is glibc which had bug in several versions, producing buggy
> static binaries).

Since these versions are (AFAICT) history now, having complex b-depends
and/or b-conflicts looks like a thing we would like to avoid, which
leads us back to the quote above.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processed: Re: Bug#769836 closed by Michael Gilbert (Bug#769836: fixed in chromium-browser 39.0.2171.71-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #769836 {Done: Michael Gilbert } [chromium-browser] 
[chromium-browser] Please use -fexcess-precision=standard or -ffloat-store 
instead of enabling sse2
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions chromium-browser/39.0.2171.71-1.

-- 
769836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#769836: closed by Michael Gilbert (Bug#769836: fixed in chromium-browser 39.0.2171.71-1)

[roucaries bastien]

control: reopen -1


On Mon, Dec 1, 2014 at 10:42 AM, Debian Bug Tracking System
 wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the chromium-browser package:

Hi,

I am sorry but it work on sse but not on i387 is the sign of huge
problem in the floating point computation.

Please see with vincent lefevre what it means.

Your computation are totally screwed, and depend on the phase of the
moon of the rounding engine.

Compiling only under sse does not fix this kind of problem it paper only over.

I am see that upstream do previously. It is doing manually that
-ffloat-store do.

Note that i586 is the supported architecture for jessie.

Bastien


>
> #769836: [chromium-browser] Please use -fexcess-precision=standard or 
> -ffloat-store instead of enabling sse2
>
> It has been closed by Michael Gilbert .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Michael Gilbert 
>  by
> replying to this email.
>
>
> --
> 769836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769836
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Michael Gilbert 
> To: 769836-cl...@bugs.debian.org
> Cc:
> Date: Mon, 01 Dec 2014 09:39:20 +
> Subject: Bug#769836: fixed in chromium-browser 39.0.2171.71-1
> Source: chromium-browser
> Source-Version: 39.0.2171.71-1
>
> We believe that the bug you reported is fixed in the latest version of
> chromium-browser, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 769...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Michael Gilbert  (supplier of updated chromium-browser 
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Mon, 01 Dec 2014 01:13:44 +
> Source: chromium-browser
> Binary: chromium chromium-dbg chromium-l10n chromium-inspector chromedriver
> Architecture: source i386 all
> Version: 39.0.2171.71-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Chromium Maintainers 
> 
> Changed-By: Michael Gilbert 
> Description:
>  chromedriver - web browser - WebDriver support
>  chromium   - web browser
>  chromium-dbg - web browser - debugging symbols
>  chromium-inspector - web browser - page inspection support
>  chromium-l10n - web browser - language packs
> Closes: 748867 766420 767697 769836 771640
> Changes:
>  chromium-browser (39.0.2171.71-1) unstable; urgency=medium
>  .
>* New upstream stable release:
>  - CVE-2014-3566: SSLv3 support is now disabled by default.
>  - CVE-2014-7899: Address bar spoofing. Credit to Eli Grey.
>  - CVE-2014-7900: Use-after-free in pdfium. Credit to Atte Kettunen.
>  - CVE-2014-7901: Integer overflow in pdfium. Credit to cloudfuzzer.
>  - CVE-2014-7902: Use-after-free in pdfium. Credit to cloudfuzzer.
>  - CVE-2014-7903: Buffer overflow in pdfium. Credit to cloudfuzzer.
>  - CVE-2014-7904: Buffer overflow in Skia. Credit to Atte Kettunen.
>  - CVE-2014-7905: Flaw allowing navigation to intents that do not have the
>BROWSABLE category. Credit to WangTao(neobyte).
>  - CVE-2014-7906: Use-after-free in pepper plugins. Credit to Chen Zhang.
>  - CVE-2014-0574: Double-free in Flash. Credit to biloulehibou.
>  - CVE-2014-7907: Use-after-free in blink. Credit to Chen Zhang.
>  - CVE-2014-7908: Integer overflow in media. Credit to Christoph Diehl.
>  - CVE-2014-7909: Uninitialized memory read in Skia. Credit to miaubiz.
>* Display info about upstream ending support for non-sse2 (closes: 
> #769836).
>* Remove non-free RFCs from the upstream tarball (closes: #771640).
>* Include a conf file for Google's API keys (closes: #748867).
>* Handle dangling chromium icon directory (closes: #766420).
>* Install icons into the correct path (closes: #767697).
> Checksums-Sha1:
>  be6d6105502cfae932f42522716295ce39c09904 4032 
> chromium-browser_39.0.2171.71-1.dsc
>  4d1ca0f62cf15d21e7116e181bcf1b4ca7d39da1 273337552 
> chromium-browser_39.0.2171.71.orig.tar.xz
>  f9304c8bf7ed6f5ea3eddc6804532a2274733be8 177604 
> chromium-browser_39.0.2171.71-1.debian.tar.xz
>  06b99a874e5d868dbb28d4f4095442279cae6019 37053310 
> chromium_39.0.2171.71-1_i386.deb
>  1adc89b125b1969f69f63eeec6df56ccef31dcf0 592742752 
> chromium-dbg_39.0.2171.71-1_i386.deb
>  03a832115f617a1f91672fab4c7113419

Bug#767037: Grub EFI fallback - patches for review

[Holger Levsen]

On Montag, 1. Dezember 2014, Cyril Brulebois wrote:
> Looking at the EFI/UEFI history, I hope nobody will think EFI is the
> deprecated, pre-UEFI implementation.

I wouldn't be so sure. Up until this very moment I thought EFI was something 
different than UEFI...

> With that in mind, and with all EFI
> occurrences we already have (including “mandatory” names), it looks to
> my non-expert eye that EFI might be the name to standardize over. Maybe
> Colin could confirm that.

this sounds fine to me, with the above in mind however, I would suggest to 
explain this (at least in the manual) once. 


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

Bug#768876: unblock: busybox/1:1.22.0-14

[Michael Tokarev]

So, can someone please tell me what's wrong with
this unblock request?

I can try to fix built-using generation adding gcc
to the mix but I'm afraid to do that this late in
the release cycle, especially after it required so
many iterations to get the most important in this
context part of built-using.  Note that this most
important part - which prompted the original bug
report wrt built-using - is here with proper
value (it is glibc which had bug in several
versions, producing buggy static binaries).

Thanks,

/mjt

28.11.2014 18:33, Thorsten Glaser wrote:
> On Fri, 28 Nov 2014, Michael Tokarev wrote:
> 
>> Um.  Maybe we should assume exact versions of software running in
>> buildds too?
> 
> No, only things that end up in the binaries.
> 
>> BTW, how about somethig like gcc -v (I'm not sure it is the right
>> option actually) which shows all libs it actually used for linking -
> 
> Yes, except that is not parsable, and varies by compiler.
> 
>> run it once, find out all actual libs and go from there, translating
>> the list to debian package names.  I think _that_ will be the only
>> real thing.
> 
> I agree. Maybe -Wl,-v or -Wl,-t instead. We always use binutils…
> but these options also have their shortcomings.
> 
>> Besides, this process should be automated with some helper, something
>> like dh_built-using, I dunno.  Or else, due to the fact that it is
> 
> No, this requires intimate knowledge of the build system in use;
> autoconf will break during the configure phase if you use some
> compiler flags (like -Werror) for example, so you have to inject
> that flag somewhere.
> 
> Also, not everything is always static, and if you build multiple
> binary packages, you need to track what is what anyway.
> 
> I think that, for B-U, we can’t find a generic solution.
> 
>> Oh well.  Do you think I should reopen this bugreport?
> 
> I think you probably only should add the libgcc.a provider
> and cross fingers for now. B-U are not unimportant, but a
> real PITA anyway right now.
> 
> bye,
> //mirabilos
> 


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

Bug#767037: Grub EFI fallback - patches for review

[Cyril Brulebois]

Steve McIntyre  (2014-12-01):
> Hmmm, you're right. There's some existing inconsistencies already,
> which don't help. In various places we already use "EFI" (e.g. in the
> GRUB package names, EFI System Partition etc.) but in others it's
> UEFI. Maybe we'd be better with just EFI everywhere...?

Looking at the EFI/UEFI history, I hope nobody will think EFI is the
deprecated, pre-UEFI implementation. With that in mind, and with all EFI
occurrences we already have (including “mandatory” names), it looks to
my non-expert eye that EFI might be the name to standardize over. Maybe
Colin could confirm that.

> >Did you send the templates for review through debian-l10n-english?
> 
> Nope. They're currently entirely my own set of mistakes written in the
> early hours... :-)

:p

> 
> 
> >> +@@ -846,6 +876,7 @@ main (int argc, char *argv[])
> >> +   char *relative_grubdir;
> >> +   char **efidir_device_names = NULL;
> >> +   grub_device_t efidir_grub_dev = NULL;
> >> ++  char *base_efidir = NULL;
> >> +   char *efidir_grub_devname;
> >> +   int efidir_is_mac = 0;
> >> +   int is_prep = 0;
> >> +@@ -878,6 +909,9 @@ main (int argc, char *argv[])
> >> +   bootloader_id = xstrdup ("grub");
> >> + }
> >> + 
> >> ++  if (removable && force_extra_removable)
> >> ++grub_util_error (_("Invalid to use both --removable and 
> >> --force_extra_removable"));
> >> ++
> >> +   if (!grub_install_source_directory)
> >> + {
> >> +   if (!target)
> >> +@@ -1087,6 +1121,8 @@ main (int argc, char *argv[])
> >> +   if (!efidir_is_mac && grub_strcmp (fs->name, "fat") != 0)
> >> +  grub_util_error (_("%s doesn't look like an EFI partition.\n"), efidir);
> >> + 
> >> ++  base_efidir = xstrdup(efidir);
> 
> >Needs a matching free()?
> 
> I wish it was that easy - the code in grub-install.c is a mix of
> styles here. Some allocations are freed immediately, while some stay
> around for the life of the program. This needs to be one of the
> latter, I think.

OK. I suspected that way after having looked a bit, but thought asking
wouldn't hurt.

> 
> 
> >> diff --git a/rescue.d/81grub-efi-force-removable 
> >> b/rescue.d/81grub-efi-force-removable
> >> new file mode 100644
> >> index 000..b35b724
> >> --- /dev/null
> >> +++ b/rescue.d/81grub-efi-force-removable
> >> @@ -0,0 +1,91 @@
> >> +#! /bin/sh -e
> >> +
> >> +. /usr/share/debconf/confmodule
> >> +
> >> +. /usr/share/grub-installer/functions.sh
> >> +
> >> +log () {
> >> +  logger -t grub-installer "grub-efi-force-removable $@"
> >> +}
> >> +
> >> +error () {
> >> +  log "error: $@"
> >> +}
> >> +
> >> +die () {
> >> +  local template="$1"
> >> +  shift
> >> +
> >> +  error "$@"
> >> +  db_input critical "$template" || [ $? -eq 30 ]
> >> +  db_go || true
> >> +  exit 1
> >> +}
> >> +
> >> +mountvirtfs () {
> >> +  fstype="$1"
> >> +  path="$2"
> >> +  if grep -q "[[:space:]]$fstype\$" /proc/filesystems && \
> >> + ! grep -q "^[^ ]\+ \+$path " /proc/mounts; then
> >> +  mkdir -p "$path" || \
> >> +  die grub-installer/mounterr "Error creating $path"
> >> +  mount -t "$fstype" "$fstype" "$path" || \
> >> +  die grub-installer/mounterr "Error mounting $path"
> >> +  trap "umount $path" HUP INT QUIT KILL PIPE TERM EXIT
> >> +  fi
> >> +}
> >> +
> >> +db_progress START 0 3 grub-installer/progress/title
> >> +db_progress INFO grub-installer/progress/step_force_efi
> >> +
> >> +# Should we also install grub-efi to the removable media path?
> >> +# Ask the user
> >> +log "Prompting user about removable media path"
> >> +db_input high grub-installer/force-efi-extra-removable
> >> +if ! db_go; then
> >> +  # back up to menu
> >> +  db_progress STOP
> >> +  exit 10
> >> +fi
> >> +db_get grub-installer/force-efi-extra-removable
> >> +if [ "$RET" != true ]; then
> >> +  db_progress STOP
> >> +  exit 0
> >> +fi
> >> +
> >> +db_progress STEP 1
> >> +db_progress INFO grub-installer/progress/step_mount_filesystems
> >> +
> >> +log "Mounting filesystems"
> >> +# If we're installing grub-efi, it wants /sys mounted in the
> >> +# target. Maybe /proc too?
> >> +mountvirtfs proc /target/proc
> >> +mountvirtfs sysfs /target/sys
> >> +chroot /target mount /boot/efi || true
> >> +
> >> +db_progress STEP 1
> >> +db_progress INFO grub-installer/progress/step_install_loader
> >> +# Do the installation now
> >> +log "Running grub-install"
> >> +if ! chroot /target grub-install --force-extra-removable; then
> >
> >in-target?
> 
> Hmmm, maybe. I saw a lot of calls to chroot directly in the
> grub-installer code, and almost none using in-target. There aren't any
> other uses of in-target in the rescue scripts either. I was just
> following existing convention, but I'm happy to switch if it makes
> sense.

Nah, matching the surrounding code looks like a good idea.

> 
> 
> Thanks for the review!

You're very welcome.

> Are you happy with the general approach I'm using?

Well, given a few bug reports and (ISTR) some feedback from
us

Bug#767037: Grub EFI fallback - patches for review

[Steve McIntyre]

On Mon, Dec 01, 2014 at 03:52:51PM +0100, Cyril Brulebois wrote:
>Steve McIntyre  (2014-12-01):
>> Control: severity 767037 serious
>> Control: tag 767037 +patch
>> 
>> [ Raising severity to serious as I've heard more and more reports of
>>   the problems here recently. ]
>> 
>> Hi folks,
>> 
>> i have two patches attached here, one for grub and one for
>> grub-installer. They implement the logic I described below and are
>> reasonably self-contained and non-intrusive. Please check them over
>> and give feedback, I'd like to get these in ASAP.
>
>Some comments inline + there seems to be little to no consistency as far
>as “{U,}EFI removable path” is concerned. Maybe make that uniform across
>the patches to reduce user bewilderment?

Hmmm, you're right. There's some existing inconsistencies already,
which don't help. In various places we already use "EFI" (e.g. in the
GRUB package names, EFI System Partition etc.) but in others it's
UEFI. Maybe we'd be better with just EFI everywhere...?

>Did you send the templates for review through debian-l10n-english?

Nope. They're currently entirely my own set of mistakes written in the
early hours... :-)



>> +@@ -846,6 +876,7 @@ main (int argc, char *argv[])
>> +   char *relative_grubdir;
>> +   char **efidir_device_names = NULL;
>> +   grub_device_t efidir_grub_dev = NULL;
>> ++  char *base_efidir = NULL;
>> +   char *efidir_grub_devname;
>> +   int efidir_is_mac = 0;
>> +   int is_prep = 0;
>> +@@ -878,6 +909,9 @@ main (int argc, char *argv[])
>> +   bootloader_id = xstrdup ("grub");
>> + }
>> + 
>> ++  if (removable && force_extra_removable)
>> ++grub_util_error (_("Invalid to use both --removable and 
>> --force_extra_removable"));
>> ++
>> +   if (!grub_install_source_directory)
>> + {
>> +   if (!target)
>> +@@ -1087,6 +1121,8 @@ main (int argc, char *argv[])
>> +   if (!efidir_is_mac && grub_strcmp (fs->name, "fat") != 0)
>> +grub_util_error (_("%s doesn't look like an EFI partition.\n"), efidir);
>> + 
>> ++  base_efidir = xstrdup(efidir);

>Needs a matching free()?

I wish it was that easy - the code in grub-install.c is a mix of
styles here. Some allocations are freed immediately, while some stay
around for the life of the program. This needs to be one of the
latter, I think.



>> --- a/debian/templates.in
>> +++ b/debian/templates.in
>> @@ -12,6 +12,17 @@ _Description: Linux default command line:
>>   The following string will be used as Linux parameters for the default menu
>>   entry but not for the recovery mode.
>>  
>> +Template: grub2/force_efi_extra_removable
>> +Type: boolean
>> +Default: false
>> +_Description: Force extra installation to the EFI removable path?
>> + Some UEFI-based systems are buggy and do not handle new bootloaders 
>> correctly.
>> + If you force extra installation of GRUB to the EFI removable path, it 
>> should
>> + make sure that this system will boot Debian correctly despite such a 
>> problem.
>> + However, this may remove the ability to boot any other operating systems 
>> that
>> + also depend on this path. If so, uou will need to ensure that GRUB is
>
>you

ACK, good catch.



>> diff --git a/rescue.d/81grub-efi-force-removable 
>> b/rescue.d/81grub-efi-force-removable
>> new file mode 100644
>> index 000..b35b724
>> --- /dev/null
>> +++ b/rescue.d/81grub-efi-force-removable
>> @@ -0,0 +1,91 @@
>> +#! /bin/sh -e
>> +
>> +. /usr/share/debconf/confmodule
>> +
>> +. /usr/share/grub-installer/functions.sh
>> +
>> +log () {
>> +logger -t grub-installer "grub-efi-force-removable $@"
>> +}
>> +
>> +error () {
>> +log "error: $@"
>> +}
>> +
>> +die () {
>> +local template="$1"
>> +shift
>> +
>> +error "$@"
>> +db_input critical "$template" || [ $? -eq 30 ]
>> +db_go || true
>> +exit 1
>> +}
>> +
>> +mountvirtfs () {
>> +fstype="$1"
>> +path="$2"
>> +if grep -q "[[:space:]]$fstype\$" /proc/filesystems && \
>> +   ! grep -q "^[^ ]\+ \+$path " /proc/mounts; then
>> +mkdir -p "$path" || \
>> +die grub-installer/mounterr "Error creating $path"
>> +mount -t "$fstype" "$fstype" "$path" || \
>> +die grub-installer/mounterr "Error mounting $path"
>> +trap "umount $path" HUP INT QUIT KILL PIPE TERM EXIT
>> +fi
>> +}
>> +
>> +db_progress START 0 3 grub-installer/progress/title
>> +db_progress INFO grub-installer/progress/step_force_efi
>> +
>> +# Should we also install grub-efi to the removable media path?
>> +# Ask the user
>> +log "Prompting user about removable media path"
>> +db_input high grub-installer/force-efi-extra-removable
>> +if ! db_go; then
>> +# back up to menu
>> +db_progress STOP
>> +exit 10
>> +fi
>> +db_get grub-installer/force-efi-extra-removable
>> +if [ "$RET" != true ]; then
>> +db_progress STOP
>> +exit 0
>> +fi
>> +
>> +db_progress STEP 1
>> +db_progress INFO grub-installer/progress/step_mount_filesystems
>> +
>> +log "Mounting fi

Bug#770608:

[Mathieu Malaterre]

tags -1 pending

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770608#17


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

Bug#771452: Duplicate object check

[Nikolaus Rath]

On 12/01/2014 02:04 AM, Shannon Dealy wrote:
> On Sun, 30 Nov 2014, Nikolaus Rath wrote:
> 
>> On 11/30/2014 07:07 PM, Nikolaus Rath wrote:
>>> On 11/30/2014 01:07 AM, Shannon Dealy wrote:

 Attached is the object_list.txt file from running fsck using your
 patch.

 Seems a little peculiar that the exception occurs at the 10 object
 mark, though it may simply be chance and mean nothing:

 "..processed 10 objects so far.."
>>>
>>> That does not make sense to me. The file that you attached has only
>>> 99540 lines.
>>>
>>> As far as I can tell, there is no way for the above message to be
>>> emitted before 10 lines have been written to the file.
>>>
>>> Could you post the complete output of fsck.s3ql again, just to be sure?
> 
> It is in fact happening that way, however, since it only updates in
> increments of 500, if this is a bug, it is effectively an "off by one"
> error.

Well, not really. It just prints the current status *every 500* objects,
so it really can't be off by 500.

The only explanation that I have is that for some reason Python did not
flush the file system buffer cache when it encountered the exception, so
we're just seeing part of the while. But that really should happen
automatically.


>> If it really is failing with this message, please try the attached
>> patch, run fsck.s3ql with "--debug-modules s3ql.fsck" and attach
>> ~/.s3ql/fsck.log* (depending on the bucket size, there may be several
>> log files).
> 
> It maxed out your log file limit (see attached .tgz file), but this was
> interesting as it occurs at the point of the exception:
> 
>i=10, obj_name=s3ql_data_1, obj_id=1
> 
> since the previous object was object_id=190092, following the pattern of
> object listing, the above obj_id should probably be 190093 not 1.

Not necessarily 190093, but probably not 1 (because that should have
been the first object, but unfortunately that's missing from the logs).

I think at this point I can probably write you a patch to get the file
system functional again, but I'd very much like to find out what's
happening here.

Would you be able to run fsck with --backend-options no-ssl, and capture
the traffic using Wireshark?

Best,
-Nikolaus
-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«


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

Bug#771652: marked as done (systemd: system 217 breaks config not using initrd and /usr and / different)

[Debian Bug Tracking System]

Your message dated Mon, 01 Dec 2014 15:20:34 +
with message-id 
and subject line Bug#771652: fixed in systemd 217-2
has caused the Debian Bug report #771652,
regarding systemd: system 217 breaks config not using initrd and /usr and / 
different
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 217-1
Severity: critical
Justification: breaks the whole system

After upgrading to 217, I had a crash because init was unable to load
libapparmor1. After seraching it is located in /usr that in my system
is not yet mounted.

copying manually libraries to /lib solves the boot problem (but still breaks
X11/kde)



-- Package-specific info:

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

Kernel: Linux 3.17.4 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-58
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1
ii  libblkid1   2.25.2-3
ii  libc6   2.19-13
ii  libcap2 1:2.24-6
ii  libcap2-bin 1:2.24-6
ii  libcryptsetup4  2:1.6.6-3
ii  libgcrypt20 1.6.2-4
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b2
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-7
ii  mount   2.25.2-3
ii  sysv-rc 2.88dsf-58
ii  udev217-1
ii  util-linux  2.25.2-3

Versions of packages systemd recommends:
ii  dbus1.9.4-1
ii  libpam-systemd  215-7

Versions of packages systemd suggests:
pn  systemd-ui  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 217-2

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 771...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt  (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Dec 2014 15:09:09 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev 
libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev 
libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 
libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb 
libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg
Architecture: source amd64
Version: 217-2
Distribution: experimental
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Martin Pitt 
Description:
 gir1.2-gudev-1.0 - libgudev-1.0 introspection data
 libgudev-1.0-0 - GObject-based wrapper library for libudev
 libgudev-1.0-dev - libgudev-1.0 development files
 libpam-systemd - system and service manager - PAM module
 libsystemd-daemon-dev - systemd utility library (transitional package)
 libsystemd-daemon0 - systemd utility library (deprecated)
 libsystemd-dev - systemd utility library - development files
 libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated)
 libsystemd-id128-dev - systemd 128 bit ID utility library (transitional 
package)
 libsystemd-journal-dev - systemd journal utility library (transitional package)
 libsystemd-journal0 - systemd journal utility library (deprecated)
 libsystemd-login-dev - systemd login utility library (transitional package)
 libsystemd-login0 - systemd login utility library (deprecated)
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 python3-systemd - Python 3 bindings for systemd
 systemd- system and service manager
 systemd-dbg - system and service manager (debug symbols)
 systemd-sysv - system and service manager - SysV links
 udev   - /dev/ and hotpl

Bug#771573: cups: Millions of symlinks to .ppd file created in /tmp

[Carl Worth]

On Mon, Dec 01 2014, Brian Potkin wrote:
> On Sun 30 Nov 2014 at 12:03:17 -0800, Carl Worth wrote:
>
>> I looked through the bugs in cups and didn't see any talking about
>> "symlinks" or "/tmp" so I hope this isn't a duplicate bug entry.
>
> It is. :) But not to worry.

Ah, well.

>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764253
>
> Updating and testing would be good.

Thanks for that information, I will certainly let you know if I see any
future problems, (and I'll also try to do that in bug reports for the
affected package).

I appreciate your quick response,

-Carl


pgpW1A1KMwpdY.pgp
Description: PGP signature

Bug#768741: phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5'

[Peter Pentchev]

On Sun, Nov 30, 2014 at 05:39:09PM -0500, Vincent Legout wrote:
> Miriam Ruiz  writes:
> 
> > I thought I had already uploaded it yeah, go ahead if I didn't
> 
> Uploaded.

Thanks to you both!

> Peter, can you please request an unblock?

Yep, the release team unblocked it in #771665.

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@freebsd.org p.penc...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: Digital signature

Bug#767037: Grub EFI fallback - patches for review

[Cyril Brulebois]

Steve McIntyre  (2014-12-01):
> Control: severity 767037 serious
> Control: tag 767037 +patch
> 
> [ Raising severity to serious as I've heard more and more reports of
>   the problems here recently. ]
> 
> Hi folks,
> 
> i have two patches attached here, one for grub and one for
> grub-installer. They implement the logic I described below and are
> reasonably self-contained and non-intrusive. Please check them over
> and give feedback, I'd like to get these in ASAP.

Some comments inline + there seems to be little to no consistency as far
as “{U,}EFI removable path” is concerned. Maybe make that uniform across
the patches to reduce user bewilderment?

Did you send the templates for review through debian-l10n-english?

> I saw almost zero response to my previous mail... :-/
> 
> For this to work sensibly, we will need both patches applying.
> 
> On Thu, Nov 20, 2014 at 01:49:55AM +, Steve McIntyre wrote:
> >
> >Hi folks,
> >
> >All of these bugs look to be the same issue: dealing with broken UEFI
> >implementations that don't find/boot a *correctly* installed grub-efi
> >loader in \EFI\debian\grubx64.efi for some reason. There's multiple
> >parts to fixing this for Debian, I think, and I'll spell them out
> >here. Please comment and tell me I'm wrong if you think I am!
> >
> > 1. Add extra support in the grub-efi*(?) packages. When we
> >install/update a grub-efi boot image (grub*.efi), add the option
> >of *also* installing that image to the removable media path:
> >\EFI\boot\boot$ARCH.efi. This code should *not* be enabled by
> >default (as correctly-functioning UEFI implementations will not
> >need it), but we should add a debconf variable to enable it. Thus,
> >this can be configured elsewhere or even pre-seeded at
> >installation time if desired. As newer, future versions of grub
> >are installed, we should ensure that the copy of grub in the
> >removable media path is updated in sync.
> >
> >(Why do we need to update the removable media path copy? To ensure
> >that the loader portion there and the rest of the grub modules,
> >config etc. remain in sync. Otherwise, badness...)
> >
> > 2. Add support (question, template, etc.) in grub-installer to set
> >the new debconf variable. This should be at low priority so most
> >people won't see it, but it's available in expert mode or (again)
> >for pre-seed use.
> >
> > 3. Add an extra path through the grub-installer code for *rescue*
> >mode: "Did you install a UEFI system but your Debian system did
> >not boot?" which can set the new debconf variable and then call
> >the normal "reinstall grub" code. We'll need to make sure we warn
> >people that this will over-write any existing UEFI bootloaders on
> >their system, so if they still want to use their old Windows
> >install dual-boot etc. they need to make sure it's configured for
> >booting via Grub.
> >
> >Ideally, it would be lovely if we can somehow guess/determine
> >automatically that there is a Debian UEFI installation on the
> >system and offer this new rescue option automatically only where
> >it makes sense. Not sure how hard/easy that would be right now,
> >before investigating the code further.
> >
> > 4. Add documentation to the installation guide to take people through
> >this process: "If you have a broken UEFI implementation on your
> >computer, then here's how to recognise it and here's what to do to
> >work around it.."
> >
> >Go on, what have I missed / misunderstood / got wrong?
> >
> >-- 
> >Steve McIntyre, Cambridge, UK.
> >st...@einval.com
> >  Armed with "Valor": "Centurion" represents quality of Discipline,
> >  Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
> >  concord the digital world while feeling safe and proud.
> >
> >
> >-- 
> >To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
> >with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> >Archive: https://lists.debian.org/20141120014955.ga28...@einval.com
> >
> >
> -- 
> Steve McIntyre, Cambridge, UK.st...@einval.com
> "...In the UNIX world, people tend to interpret `non-technical user'
>  as meaning someone who's only ever written one device driver." -- Daniel Pead

> >From e384e597914b6e1b1dcbf96ef6782cf9bcc2313b Mon Sep 17 00:00:00 2001
> From: Steve McIntyre 
> Date: Mon, 1 Dec 2014 11:37:06 +
> Subject: [PATCH] Add support for forcing EFI installation to the removable
>  media path
> 
> Add an extra option to grub-install "--force-extra-removable". On EFI
> platforms, this will cause an extra copy of the grub-efi image to be
> written to the appropriate removable media patch
> /boot/efi/EFI/BOOT/BOOT$ARCH.EFI as well. This will help with broken
> UEFI implementations where the firmware does not work when configured
> with new boot paths.
> 
> Also added new debconf logic to a

Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

[Martin Pitt]

Hello again,

Eric Valette [2014-12-01 10:11 +0100]:
> After fixing the libapparmor in /usr bug, I managed to boot but kdm was
> not started.

This is most likely due to Didier's new generator to read
/etc/X11/default-display-manager and only start that one. What does
that file contain on your system?

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


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

Processed: Re: Bug#767103: irssi-plugin-otr needs rebuild on new uploads of irssi

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 767103 important
Bug #767103 [irssi-plugin-otr] irssi-plugin-otr doesn't work with irssi 0.8.17
Severity set to 'important' from 'grave'
> retitle 767103 irssi-plugin-otr needs rebuild on new uploads of irssi
Bug #767103 [irssi-plugin-otr] irssi-plugin-otr doesn't work with irssi 0.8.17
Changed Bug title to 'irssi-plugin-otr needs rebuild on new uploads of irssi' 
from 'irssi-plugin-otr doesn't work with irssi 0.8.17'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
767103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#771669: marked as forwarded (segfault on SQLPrepare SELECT with expression result column)

[Debian Bug Tracking System]

Your message dated Mon, 1 Dec 2014 14:38:26 +0100
with message-id <20141201133826.gb19...@capsaicin.mamane.lu>
has caused the   report #771669,
regarding segfault on SQLPrepare SELECT with expression result column
to be marked as having been forwarded to the upstream software
author(s) c...@ch-werner.de

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Hi Christian,

May I draw your attention on Debian bug number 771669, which I quote
below and which can be read in full at http://bugs.debian.org/771669 ?

It was reported against 0.992, but I have reproduced it with 0.999
(which I'm shortly going to upload to Debian).

I also attach a backtrace with sqliteodbc and libsqlite3 compiled in
full debug mode. The trigger for this segfault seems to me to be that
a column in the result of the select is an expression, as opposed to a
"straight" column reference from a table, leading to
sqlite3_column_(database|table|origin)_name to return NULL, which is
then passed to sqlite3_table_column_metadata. I'm not 100% sure if
that is to be considered a bug in sqliteodbc or in libsqlite3; even if
a bug in libsqlite3, it would probably be good to work around it in
sqliteodbc, additionally to having it fixed in libsqlite3.


Please keep 771...@bugs.debian.org in CC of your replies, so that they
are filed by our bug tracking system and forwarded to the right
people.

Best Regards and Thanks,

Lionel Mamane

On Mon, Dec 01, 2014 at 02:31:22PM +0200, Enrico Zini wrote:
> Package: libsqliteodbc
> Version: 0.992-2
> Severity: grave
> 
> Hello,
> 
> sqlite3+odbc segfaults with this simple test case, which as far as I
> understand ODBC is just a standard connect and prepare sequence.
> 
> The segfault happens in the current Jessie and in Fedora 20.
> 
> $ cat sqlite-odbc.c
> #include 
> #include 
> #include 
> #include 
> 
> int main()
> {
> // Allocate ODBC environment handle and register version
> SQLHENV od_env;
> assert(SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &od_env) == 
> SQL_SUCCESS);
> assert(SQLSetEnvAttr(od_env, SQL_ATTR_ODBC_VERSION, (void*)SQL_OV_ODBC3, 
> 0) == SQL_SUCCESS);
> 
> SQLHDBC od_conn;
> assert(SQLAllocHandle(SQL_HANDLE_DBC, od_env, &od_conn) == SQL_SUCCESS);
> 
> // Connect to the DSN
> char sdcout[1024];
> SQLSMALLINT outlen;
> assert(SQLDriverConnect(od_conn, NULL,
> (SQLCHAR*)"Driver=SQLite3;Database=test.sqlite;", SQL_NTS,
> (SQLCHAR*)sdcout, 1024, &outlen,
> SQL_DRIVER_NOPROMPT) == SQL_SUCCESS);
> 
> // Create a statement
> SQLHSTMT stm;
> assert(SQLAllocHandle(SQL_HANDLE_STMT, od_conn, &stm) == SQL_SUCCESS);
> 
> 
> // Prepare a query
> assert(SQLPrepare(stm, (SQLCHAR*)"SELECT COUNT(*) FROM sqlite_master 
> WHERE type='table' AND name=?", SQL_NTS) == SQL_SUCCESS);
> 
> 
> // All good, deallocate things
> SQLFreeHandle(SQL_HANDLE_STMT, stm);
> SQLFreeHandle(SQL_HANDLE_DBC, od_conn);
> SQLFreeHandle(SQL_HANDLE_ENV, od_env);
> }
> $ gcc -g sqlite-odbc.c -o sqlite-odbc -lodbc
> $ rm -f test.sqlite  # Not needed, but it keeps the tests stateless
> $ ./sqlite-odbc
> Segmentation fault
> $ rm -f test.sqlite  # Not needed, but it keeps the tests stateless
> $ gdb ./sqlite-odbc
> GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
> [...]
> (gdb) run
> Starting program: /home/enrico/lavori/arpa/dballe/sqlite-odbc
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x76abc537 in sqlite3_stricmp () from 
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> (gdb) where
> #0  0x76abc537 in sqlite3_stricmp () from 
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #1  0x76abd485 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #2  0x76abecf6 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #3  0x76b29188 in sqlite3_table_column_metadata () from 
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #4  0x76d8180d in ?? () from 
> /usr/lib/x86_64-linux-gnu/odbc/libsqlite3odbc.so
> #5  0x76d882d0 in ?? () from 
> /usr/lib/x86_64-linux-gnu/odbc/libsqlite3odbc.so
> #6  0x76d88965 in ?? () from 
> /usr/lib/x86_64-linux-gnu/odbc/libsqlite3odbc.so
> #7  0x77b94481 in SQLPrepare () from 
> /usr/lib/x86_64-linux-gnu/libodbc.so.2
> #8  0x00400957 in main () at sqlite-odbc.c:30
> (gdb)
> 
> 
> Regards,
> 
> Enrico
> 
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architec

Bug#767103: irssi-plugin-otr needs rebuild on new uploads of irssi

[Holger Levsen]

severity 767103 important
retitle 767103 irssi-plugin-otr needs rebuild on new uploads of irssi

Hi,

irssi-plugin-otr from bpo works for me with irssi from bpo now and I seem to 
recall someone confirmed this for the sid versions too, thus downgrading the 
bug and retitling accordingly.


cheers,
Holger


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

Processed: Grub EFI fallback - patches for review

[Debian Bug Tracking System]

Processing control commands:

> severity 767037 serious
Bug #767037 [grub-efi] grub-efi: add install-time option to place grub-efi in 
removable media path
Bug #708430 [grub-efi] grub-efi: add install-time option to place grub-efi in 
removable media path
Bug #746662 [grub-efi] grub-efi: add install-time option to place grub-efi in 
removable media path
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> tag 767037 +patch
Bug #767037 [grub-efi] grub-efi: add install-time option to place grub-efi in 
removable media path
Bug #708430 [grub-efi] grub-efi: add install-time option to place grub-efi in 
removable media path
Bug #746662 [grub-efi] grub-efi: add install-time option to place grub-efi in 
removable media path
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.

-- 
708430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708430
746662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746662
767037: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#766502: TYPO3 CMS 4.5.37, 4.7.20, 6.1.12 and 6.2.6 released

[Holger Levsen]

Hi,

On Mittwoch, 22. Oktober 2014, typo3.org: Latest News wrote:
> We are announcing the release of the following TYPO3 CMS updates:
> 
>   * TYPO3 CMS 4.5.37 LTS
> 
> **IMPORTANT: These versions include important security fixes to the TYPO3
> core. A security announcement has just been released:
> **[http://typo3.org/teams/security/security-bulletins/typo3-core/typo3-cor
> e-sa-2014-002/](http://typo3.org/teams/security/security-bulletins/typo3-co
> re/typo3-core-sa-2014-002/)

and 4.5.38 is available now too.


cheers,
Holger


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