Processed: severity of 742474 is normal

[Debian Bug Tracking System]

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

> severity 742474 normal
Bug #742474 [xfce4] xfce4: Panel show/hide stops working intermittently
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
742474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742474
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#742114: dependency on tcl not tight enough

[Erwan David]

On Wed, Mar 19, 2014 at 05:59:06PM CET, Christian Hofstaedtler 
 said:
> * Erwan David  [140319 11:30]:
> > /usr/share/tcltk/tcl8.5/init.tcl: version conflict for package "Tcl": have 
> > 8.5.14, need exactly 8.5.15
> > version conflict for package "Tcl": have 8.5.14, need exactly 8.5.15
> > while executing
> > "package require -exact Tcl 8.5.15"
> > (file "/usr/share/tcltk/tcl8.5/init.tcl" line 19)
>  
> 
> This file is shipped by tcl, not by ruby.
> 
> This looks suspiciously, and I doubt this is a dependency or ruby
> problem.
> 
> Please verify that this command works on your system:
> 
> tclsh8.5 /usr/share/tcltk/tcl8.5/init.tcl
> 
> Thanks,
> Christian

Yes, it works...
Sorry for the delay, I switch between 8.15.15 (for testing) and 8.5.14 (for my 
bunytk scripts to work).


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

Bug#742405: zookeeper ftbfs without openjdk

[Ivo De Decker]

Hi Tim,

On Sun, Mar 23, 2014 at 08:42:08PM +, Tim Retout wrote:
> Zookeeper also fails to build on sparc.  These seem to be the
> architectures where openjdk is not the default JDK.
> 
> This would explain why 3.4.5+dfsg-1 built successfully, because
> openjdk was the default on kfreebsd between November and February.
> 
> I'm not actually sure how best to resolve this...

I CC'ed the debian-bsd list. If there is no other option, you could file a
removal bug for the kfreebsd binaries, which would allow the new version to
migrate to testing.

Cheers,

Ivo


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

Processed: Re: doublecmd: FTBFS: install: cannot stat '*.so*': No such file or directory

[Debian Bug Tracking System]

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

> affects 741792 + src:lazarus
Bug #741792 [src:doublecmd] doublecmd: FTBFS: install: cannot stat '*.so*': No 
such file or directory
Added indication that 741792 affects src:lazarus
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
741792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741792
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#742474: xfce4: Panel show/hide stops working intermittently

[David Creelman]

Package: xfce4
Version: 4.10.1
Severity: serious
Justification: fails to build from source

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***
Had been using the system normally day in/day out.
Have not been able to detect what it is that I've done differently to make this 
happen (does seem to happen
more often when running virtual box in seamless mode though?)

When the problem my "main" panel at the bottom stops automatically hiding when 
the mouse is
moved away from it. The panel is set to automatically hide/show.
To fix the issue, I need to log out and in again.
I expected to not have to log out and log in again.


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

Kernel: Linux 3.13-1-686-pae (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/dash

Versions of packages xfce4 depends on:
ii  gtk2-engines-xfce  3.0.1-2
ii  libxfce4ui-utils   4.10.0-5
ii  orage  4.10.0-1+b1
ii  thunar 1.6.3-1
ii  xfce4-appfinder4.10.1-1
ii  xfce4-mixer4.10.0-3
ii  xfce4-panel4.10.1-1
ii  xfce4-session  4.10.1-5
ii  xfce4-settings 4.10.1-2
ii  xfconf 4.10.0-2
ii  xfdesktop4 4.10.2-3
ii  xfwm4  4.10.1-2

Versions of packages xfce4 recommends:
ii  desktop-base  7.0.3
ii  tango-icon-theme  0.8.90-5
ii  thunar-volman 0.8.0-4
ii  xfce4-notifyd 0.2.4-2
pn  xorg  

Versions of packages xfce4 suggests:
pn  gtk3-engines-xfce
ii  xfce4-goodies4.10
ii  xfce4-power-manager  1.2.0-3

-- 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#742442: [Pkg-running-devel] Bug#742442: garmin-ant-downloader: Segfaults on amd64

[Christian PERRIER]

Quoting Christian Perrier (bubu...@debian.org):
> Package: garmin-ant-downloader
> Version: 20110626-1
> Severity: serious
> 
> g-a-t seems unusable on amd64. Apparently, as soon as it is launched
> AND an ANT+ stick is present, it then segfaults:
> 
> 
> $ ./gant
> Erreur de segmentation


Just to be clear. The above is showing a run of a locally compiled
"gant" executablebut the same happens with the binary provided by
the package (/usr/bin/garmin-ant-downloader)

I was actually trying to see if that problem could have been something
induced by builds on autobuilders but apparently not.




signature.asc
Description: Digital signature

Bug#741740: ledger-3 bundles non-dfsg software

[Ben Finney]

On 16-Mar-2014, Jamie Nguyen wrote:

> ledger bundles an SHA-1 C++ implementation by Paul E. Jones which is
> licensed under a "Freeware Public License". This license does not allow
> modification and therefore does not adhere to the DFSG.

The upstream source for ‘ledger’ contains separate files for each license:

* doc/LICENSE.rtf
* doc/LICENSE-utfcpp
* doc/LICENSE-sha1
* doc/LICENSE

Each of these need to be described in ‘debian/copyright’.

As Jamie says, the ‘doc/LICENSE-sha1’ contains a copyright notice and
license text; the license terms are non-free (permission is not granted to
redistribute modified versions, failing DFSG §3).

> There was a similar issue with the "orthanc" package. This was resolved
> when the upstream author switched to a different library with a license
> compatible with the DFSG:

In the case of SHA-1, there are numerous implementations; some of them
(e.g. http://www.tamale.net/sha1/>) are licensed under free software
terms.

The package maintainer could replace the non-free files with a free
equivalent, and changing any relevant function calls to match, thereby
resolving this bug. Then, provide the patch to the ‘ledger’ upstream
maintainer, helping them to resolve the issue in a future version.

-- 
 \“Always code as if the guy who ends up maintaining your code |
  `\ will be a violent psychopath who knows where you live.” —John |
_o__) F. Woods |
Ben Finney 


signature.asc
Description: Digital signature

Bug#741620: upgrade broke starttls?

[John Seymour]

I can confirm that this bug exists. i had to roll back to the previous 
version the get starttls working.

--
*John Seymour*
Research Physicist and IT Manager

National Acoustic Laboratories 
/A Division of Australian Hearing/

Australian Hearing Hub
16 University Avenue
Macquarie University NSW 2109 Australia
P +61 2 9412 6839
F +61 2 9412 6769

Please consider the environment before printing this email

Processed: tagging 688168

[Debian Bug Tracking System]

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

> tags 688168 + upstream
Bug #688168 [src:lldpad] lldpad: Please port to libnl-3.x
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
688168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688168
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#742461: mate-settings-daemon enters a infinite crash/restart loop

[Tom Maneiro]

Package: mate-settings-daemon
Version: 1.8.0-1
Severity: grave
Justification: renders package unusable

After doing a apt dist-update last night, several core components of MATE were
upgraded to 1.8 on my Jessie system.

Normally I use KDE, but from time to time I also use MATE, but since that
update I've been unable to reach a stable desktop. Everything starts to flicker
badly: panels, menus, tray icons, desktop icons. Fonts and dialogs switch font
sizes, menus are hard to use, and in general, the overall desktop feels
extremely unstable and sluggish.

Taking a look at dmesg, I find dozens of these:
[  621.039193] traps: mate-settings-d[12942] trap int3 ip:7ff691c3a3c9
sp:7fff62967f40 error:0
[  621.583086] traps: mate-settings-d[12963] trap int3 ip:7f6cf8dbc3c9
sp:7fff2c45d9e0 error:0
[  622.144056] traps: mate-settings-d[12982] trap int3 ip:7f8023b6d3c9
sp:7fff476512b0 error:0
[  622.717133] traps: mate-settings-d[13009] trap int3 ip:7f1059c9d3c9
sp:7fff96c0a210 error:0
[  623.261964] traps: mate-settings-d[13034] trap int3 ip:7f10dbc413c9
sp:7fffb5473430 error:0
[  623.819512] traps: mate-settings-d[13061] trap int3 ip:7ff2d2bc13c9
sp:7fff21f21640 error:0
[  624.355532] traps: mate-settings-d[13081] trap int3 ip:7f66db7843c9
sp:7fff11fbecc0 error:0
[  624.899599] traps: mate-settings-d[13108] trap int3 ip:7f14966b33c9
sp:7fff2518efc0 error:0
[  625.463491] traps: mate-settings-d[13135] trap int3 ip:7f1f5019b3c9
sp:7fffb9e93260 error:0
[  626.051037] traps: mate-settings-d[13162] trap int3 ip:7f56a6a813c9
sp:7fff9fea4cb0 error:0
[  626.602089] traps: mate-settings-d[13190] trap int3 ip:7f9c52e473c9
sp:7fff8217cf50 error:0
[  627.186409] traps: mate-settings-d[13217] trap int3 ip:7fc7eaa183c9
sp:74926d10 error:0
[  627.725624] traps: mate-settings-d[13236] trap int3 ip:7f426cf153c9
sp:7fffbbfd2bb0 error:0
[  628.295965] traps: mate-settings-d[13262] trap int3 ip:7f6a982823c9
sp:7fff9418ab50 error:0
[  628.829837] traps: mate-settings-d[13289] trap int3 ip:7f8d9cf5c3c9
sp:7fff50c74520 error:0
[  629.450491] traps: mate-settings-d[13308] trap int3 ip:7f8b2c2663c9
sp:7fff4c84fb30 error:0
[  630.016590] traps: mate-settings-d[13331] trap int3 ip:7f43da0fb3c9
sp:7fff38086700 error:0
[  630.555314] traps: mate-settings-d[13358] trap int3 ip:7fd7a9b503c9
sp:7fff73a05c80 error:0
[  631.119840] traps: mate-settings-d[13386] trap int3 ip:7ff4c042a3c9
sp:7fff48037df0 error:0
[  631.707592] traps: mate-settings-d[13413] trap int3 ip:7f0056e3f3c9
sp:7fff8b866740 error:0
[  632.264920] traps: mate-settings-d[13440] trap int3 ip:7f25142ff3c9
sp:7fffb113ab30 error:0
[  632.814582] traps: mate-settings-d[13467] trap int3 ip:7fb5387d03c9
sp:7fff1a405f10 error:0
which matches the frequency of the desktop flickering, which means that
mate-settings-daemon is at fault (it gets killed, desktop loses settings, it
respawns, icons and widgets gets their colors and fonts back, then it gets
killed again... and repated until I manage to logoff. Hence because of this,
MATE is completely broken on my system.

I've tried switching mate-settings-desktop backends (I had GStreamer, tried
switching to Pulse) since the actual mate-settings-daemon binary seems to live
on those, but to no avail - desktop is still unstable.



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

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

Versions of packages mate-settings-daemon depends on:
ii  mate-settings-daemon-gstreamer  1.8.0-1

mate-settings-daemon recommends no packages.

mate-settings-daemon 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

Processed: severity of 685439 is important

[Debian Bug Tracking System]

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

> severity 685439 important
Bug #685439 [apt-show-versions] Use of uninitialized value in hash element
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
685439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685439
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#742064: marked as done (owncloud-client-cmd: Crash when trying to sync remote folder (Segmentation fault))

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 23:33:57 +
with message-id 
and subject line Bug#742064: fixed in owncloud-client 1.5.3+dfsg-1
has caused the Debian Bug report #742064,
regarding owncloud-client-cmd: Crash when trying to sync remote folder 
(Segmentation fault)
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.)


-- 
742064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: owncloud-client-cmd
Version: 1.5.2+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm trying to sync with a remote owncloud folder and it crash with this
output:

>> (meutel@assurancetourix) ~/tmp/oc-test
>> owncloudcmd --confdir $HOME/.local/share/data/ownCloud/ Sync/ 
>> https://cloud.meutel.net/index.php/apps/files?dir=/Sync/ 
[03/18 19:31:41.475866, 9] csync_vio_init:  capabilities: atomar copy support: 
yes
[03/18 19:31:41.475947, 9] csync_vio_init:  capabilities: post copy stat: no
[03/18 19:31:41.475957, 9] csync_vio_init:  capabilities: time sync required: no
[03/18 19:31:41.475965, 9] csync_vio_init:  capabilities: unix extensions: 0
[03/18 19:31:41.475972, 9] csync_vio_init:  capabilities: use send_file: yes
[03/18 19:31:41.475980, 9] csync_vio_init:  capabilities: get support: no
[03/18 19:31:41.475987, 9] csync_vio_init:  capabilities: put support: no
[03/18 19:31:41.475994, 9] csync_init:  Module does not need time 
synchronization.
03-18 19:31:41:476 Passing NO proxy to csync for 
"https://cloud.meutel.net/index.php/apps/files?dir=/Sync/remote.php/webdav/"; 
03-18 19:31:41:476 void Mirall::CSyncThread::startSync() Sync started 
03-18 19:31:41:476 starting to sync  QThread(0xd50250) QThread(0xd50250) 
03-18 19:31:41:478 Transaction Start  "checkConnect" 
03-18 19:31:41:478 Columns in the current journal:  ("phash", "pathlen", 
"path", "inode", "uid", "gid", "mode", "modtime", "type",
 "md5", "fileid") 
03-18 19:31:41:479 =sync DB has only 0 items, enable recursive PROPFIND if 
csync supports it 
03-18 19:31:41:479 void Mirall::CSyncThread::startSync() No default Account 
object, huh? 
03-18 19:31:41:479  Update start 
 >> 
03-18 19:31:41:479 csync_update: Journal: Sync/.csync_journal.db
03-18 19:31:41:541 csync_memstat_check: Memory: 233744K total size, 18620K 
resident, 14480K shared
03-18 19:31:41:541 csync_ftw:  <= Closing walk for Sync with read_from_db 0
03-18 19:31:41:541 csync_update: Update detection for local replica took 0,00 
seconds walking 0 files.
03-18 19:31:41:541 csync_memstat_check: Memory: 233744K total size, 18824K 
resident, 14636K shared
03-18 19:31:41:541 oc_module: opendir method called on 
https://cloud.meutel.net/index.php/apps/files?dir=/Sync/remote.php/webdav
03-18 19:31:41:541 oc_module: * scheme https
03-18 19:31:41:541 oc_module: * host cloud.meutel.net
03-18 19:31:41:541 oc_module: * port 0
03-18 19:31:41:541 oc_module: * path 
/index.php/apps/files?dir=/Sync/remote.php/webdav
03-18 19:31:41:541 oc_module: Invalid scheme https, go outa here!
03-18 19:31:41:541 oc_module: fetch_resource_list_recursive Starting recursive 
propfind https://cloud.meutel.net/index.php/apps/fi
les?dir=/Sync/remote.php/webdav 
/index.php/apps/files%3fdir%3d/Sync/remote.php/webdav
Erreur de segmentation

"Erreur de segmentation" is french for "Segmentation fault". 

This message appears in /var/log/messages:

Mar 18 19:31:41 assurancetourix kernel: [ 3960.685026] owncloudcmd[23118]: 
segfault at 28 ip 7f1c2596e29c sp 7fff6b632370 error 4 in 
libneon-gnutls.so.27.3.0[7f1c25961000+27000]

There is no log on the server side. I can sync the same folder with the desktop 
client without problems.



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

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

Versions of packages owncloud-client-cmd depends on:
ii  libc6 2.18-4
ii  libgcc1   1:4.8.2-16
ii  libneon27-gnutls  0.30.0-1
ii  libowncloudsync0  1.5.2+dfsg-1
ii  libqt4-dbus   4:4.8.5+git242-g0315971+dfsg-2
ii  libqt4-network4:4.8.5+git242-g0315971+dfsg-2
ii  libqt4-sql4:4.8.5+git242-g0315971+dfsg-2
ii  libqt4-sql-sqlite 4:4.8.5+git242-g0315971+dfsg-2
ii  libqt4-xml4:4.8.5+git242-g0315971+dfsg-2
i

Bug#742423: wine-unstable is *still* unusable

[Marc Dequènes (Duck)]

Quoting "Marc Dequènes (Duck)" :

You closed #742021 and #742317 in a hurry, but the logic in  
/usr/bin/wine-unstable is to look for the real 32/64 binaries in the  
same directory while you moved them into /usr/lib/wine-unstable/,  
thus your package is unusable.


Broken analysis due to a workaround. Here is the trace of the current problem:

$ winecfg
+ basename /usr/bin/winecfg .exe
+ appname=winecfg.exe
+ test -z
+ test ! -z
+ WINEPREFIX=/home/duck/.wine
+ test -e /home/duck/.wine/system.reg
+ wine=/usr/bin/wine
+ exec /usr/bin/wine winecfg.exe
/usr/bin/winecfg: 36: exec: /usr/bin/wine: not found

I'm not using wine directly but through playonlinux, thus there is no  
trace of me using wine-unstable in any reg file, this is a broken  
assumption.


Btw you also broke using playonlinux or other tools around because  
they all expect a "wine" binary and not "wine-unstable". Unless there  
is an alternative mechanism for choosing the default version i think  
using wine-unstable remains unusable (but using an alternative would  
probably break your current logic).


--
Marc Dequènes (Duck)



pgpxGTIDekmS9.pgp
Description: PGP Digital Signature

Bug#655969: lirc: prompting due to modified conffiles which where not modified by the user

[Stefan Lippers-Hollmann]

Hi

On Sunday 23 March 2014, Ben Hutchings wrote:
> Some time ago you committed:
> 
> r497 | slh-guest | 2012-02-23 12:20:25 + (Thu, 23 Feb 2012) | 1 line
> 
>   detection stages (Closes: #660956).
> 
> Index: debian/changelog
> ===
> --- debian/changelog(revision 496)
> +++ debian/changelog(revision 497)
> @@ -88,7 +88,7 @@
>  lirc 0.7.1pre2-8, previous versions unconditionally started an 
> interactive
>  non-debconf hardware detection/ selection menu, which always left
>  hardware.conf modified; md5sums for prior versions apply to aborted h/w
> -detection stages.
> +detection stages (Closes: #660956).
>  
>   -- Stefan Lippers-Hollmann   Sat, 28 Jan 2012 20:03:16 +0100
>  
> 
> I think you actually meant to close #655969.

Thanks for noticing this, I didn't match up to the bug closure with the
correct changelog entry when the bug was filed after the actual change
had already been done long before. Given that both bugs will be fixed 
in the same version, the actual effects would have been limited, but 
I've fixed it (and removed a duplicate bug closure) in [1].

> Anyway, as the postinst in wheezy does not appear to modify the config
> file, it appears that further upgrades should not have this problem.
> Given that the bug was tagged squeeze-ignore and wheezy-ignore, perhaps
> it can now be closed?

I certainly won't object against closing this bug, especially as 
neither squeeze nor wheezy will be changed in this regard anymore
(most users actually using lirc, would have needed to adapt their
configuration for kernel >= 2.6.37 anyways[2], when lirc was merged
into the kernel and several modules moved from lirc to RC_CORE). 
However technically speaking, squeeze is still supported until roughly
2014-05-06 (depending on the actual EOL date to be announced by the 
stable release team) - and squeeze to wheezy upgrades also remain 
affected. While technically not correct either, it might make sense to 
drop its severity below the RC threshold though, to avoid bug squashers
from wasting time on this though.

On the other hand there will be an upload, with the afforementioned bug
closures soon (for some value of 'soon', probably before the middle of
the year), which requires some adaptions to these pending changes (in 
order to provide native systemd units, the sysv initscripts will have 
to be split into individual initscripts for lirc, lircmd and irexec, so
the (to be added) systemd units can mask the corresponding initscripts 
properly[3]) - and it's best to avoid needless/ forseeable conffile 
churn until this is settled.

Regards
Stefan Lippers-Hollmann

[1] 
http://anonscm.debian.org/viewvc/pkg-lirc/lirc/trunk/debian/changelog?r1=517&r2=518
[2] https://lists.debian.org/debian-backports/2012/04/msg00076.html
[3] lirc's sysv initscripts are working fine under systemd's sysv 
compatibility mode, but native support needs further changes.


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

Bug#739535: marked as done (uswsusp: FTBFS: Can't locate Switch.pm in @INC)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 23:03:39 +
with message-id 
and subject line Bug#739535: fixed in uswsusp 1.0+20120915-5
has caused the Debian Bug report #739535,
regarding uswsusp: FTBFS: Can't locate Switch.pm in @INC
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.)


-- 
739535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: uswsusp
Version: 1.0+20120915-4
Severity: serious
Tags: patch

Hi there,

Your package uswsusp fails to build in current unstable on amd64.

(Hopefully) Relevant part of the log: 
--

  ^
load.c:459:3: warning: 'gcry_ac_data_new' is deprecated (declared at 
/usr/include/gcrypt.h:1417) [-Wdeprecated-declarations]
   ret = gcry_ac_data_new(&rsa_data_set);
   ^
load.c:476:3: warning: 'gcry_ac_data_set' is deprecated (declared at 
/usr/include/gcrypt.h:1443) [-Wdeprecated-declarations]
   ret = gcry_ac_data_set(rsa_data_set, GCRY_AC_FLAG_COPY,
   ^
load.c:485:3: warning: 'gcry_ac_key_init' is deprecated (declared at 
/usr/include/gcrypt.h:1501) [-Wdeprecated-declarations]
   ret = gcry_ac_key_init(&rsa_priv, rsa_hd,
   ^
load.c:490:2: warning: 'gcry_ac_data_new' is deprecated (declared at 
/usr/include/gcrypt.h:1417) [-Wdeprecated-declarations]
  ret = gcry_ac_data_new(&key_set);
  ^
load.c:496:2: warning: 'gcry_ac_data_set' is deprecated (declared at 
/usr/include/gcrypt.h:1443) [-Wdeprecated-declarations]
  ret = gcry_ac_data_set(key_set, GCRY_AC_FLAG_COPY, "a", mpi);
  ^
load.c:501:2: warning: 'gcry_ac_data_decrypt' is deprecated (declared at 
/usr/include/gcrypt.h:1579) [-Wdeprecated-declarations]
  ret = gcry_ac_data_decrypt(rsa_hd, 0, rsa_priv, &mpi, key_set);
  ^
load.c:518:2: warning: 'gcry_ac_data_destroy' is deprecated (declared at 
/usr/include/gcrypt.h:1421) [-Wdeprecated-declarations]
  gcry_ac_data_destroy(key_set);
  ^
load.c:521:2: warning: 'gcry_ac_key_destroy' is deprecated (declared at 
/usr/include/gcrypt.h:1541) [-Wdeprecated-declarations]
  gcry_ac_key_destroy(rsa_priv);
  ^
load.c:524:2: warning: 'gcry_ac_data_destroy' is deprecated (declared at 
/usr/include/gcrypt.h:1421) [-Wdeprecated-declarations]
  gcry_ac_data_destroy(rsa_data_set);
  ^
load.c:535:2: warning: 'gcry_ac_close' is deprecated (declared at 
/usr/include/gcrypt.h:1497) [-Wdeprecated-declarations]
  gcry_ac_close(rsa_hd);
  ^
gcc -DHAVE_CONFIG_H -I.   -D_FORTIFY_SOURCE=2 -DS2RAM -D_LARGEFILE64_SOURCE 
   -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -c -o s2ram.o s2ram.c
perl wlcsv2c.pl whitelist.csv whitelist.c
Can't locate Switch.pm in @INC (you may need to install the Switch module) 
(@INC contains: /etc/perl /usr/local/lib/perl/5.18.2 
/usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 
/usr/share/perl/5.18 /usr/local/lib/site_perl .) at wlcsv2c.pl line 5.
BEGIN failed--compilation aborted at wlcsv2c.pl line 5.
make[3]: *** [whitelist.c] Error 2
make[3]: Leaving directory `/«BUILDDIR»/uswsusp-1.0+20120915'
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
make[2]: Leaving directory `/«BUILDDIR»/uswsusp-1.0+20120915'
make[1]: Leaving directory `/«BUILDDIR»/uswsusp-1.0+20120915'
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Build finished at 20140219-1954

Finished


E: Build failure (dpkg-buildpackage died)

A full buildlog is available at 
http://www.warperbbs.de/stuff/buildlogs/uswsusp_1.0+20120915-4_amd64.build

As the error suggests, adding libswitch-perl to the Build-Depends fixing this 
build failure.

Thanks for your time!

Regards,
  Andreas

-- 
PGP-encrypted mails preferred
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: uswsusp
Source-Version: 1.0+20120915-5

We believe that the bug you reported is fixed in the latest version of
uswsusp, 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 739...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rodolfo García Peñas (kix)  (supplier of updated uswsusp 
package)

(This

Processed: wine-unstable is *still* unusable

[Debian Bug Tracking System]

Processing control commands:

> severity -1 critical
Bug #742423 [wine-unstable] wine-unstable: wine-wrapper (aka everything) tries 
to call /usr/bin/wine (which is missing)
Severity set to 'critical' from 'important'

-- 
742423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742423
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#711620: marked as done (libthread-queue-any-perl: FTBFS with perl 5.18: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 21:50:52 +
with message-id 
and subject line Bug#711620: fixed in libthread-queue-any-perl 1.14-1
has caused the Debian Bug report #711620,
regarding libthread-queue-any-perl: FTBFS with perl 5.18: 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.)


-- 
711620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libthread-queue-any-perl
Version: 1.12-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.18-transition
Tags: sid jessie

This package FTBFS with perl 5.18 from experimental (in a clean sbuild
session):

   dh_auto_test
make[1]: Entering directory `/build/dom-libthread-queue-any-perl_1.12-1-i386-4yd
gPg/libthread-queue-any-perl-1.12'
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 
'blib/lib', 'blib/arch')" t/*.t
# threads loaded
Not an ARRAY reference at /build/dom-libthread-queue-any-perl_1.12-1-i386-4ydgPg
/libthread-queue-any-perl-1.12/blib/lib/Thread/Queue/Any.pm line 79.
# Tests were run but no plan was declared and done_testing() was not seen.
t/001basic.t ... 
Dubious, test returned 255 (wstat 65280, 0xff00)
All 9 subtests passed 
# threads loaded
Not an ARRAY reference at /build/dom-libthread-queue-any-perl_1.12-1-i386-4ydgPg
/libthread-queue-any-perl-1.12/blib/lib/Thread/Queue/Any.pm line 79.
# Tests were run but no plan was declared and done_testing() was not seen.
t/010serializer.t .. 
Failed 2/2 test programs. 0/15 subtests failed.
Dubious, test returned 255 (wstat 65280, 0xff00)
All 6 subtests passed 

Test Summary Report
---
t/001basic.t (Wstat: 65280 Tests: 9 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
t/010serializer.t (Wstat: 65280 Tests: 6 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
Files=2, Tests=15,  0 wallclock secs ( 0.02 usr  0.02 sys +  0.08 cusr  0.01 
csys =  0.13 CPU)
Result: FAIL

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
--- End Message ---
--- Begin Message ---
Source: libthread-queue-any-perl
Source-Version: 1.14-1

We believe that the bug you reported is fixed in the latest version of
libthread-queue-any-perl, 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 711...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libthread-queue-any-perl 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: Sun, 23 Mar 2014 22:37:02 +0100
Source: libthread-queue-any-perl
Binary: libthread-queue-any-perl
Architecture: source all
Version: 1.14-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Description: 
 libthread-queue-any-perl - module implementing thread-safe queues for any 
data-structure
Closes: 711620
Changes: 
 libthread-queue-any-perl (1.14-1) unstable; urgency=low
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * Change Vcs-Git to canonical URI (git://anonscm.debian.org).
   * Change search.cpan.org based URIs to metacpan.org based URIs.
 .
   [ Florian Schlichting ]
   * Imported Upstream version 1.13.
   * Bumped Standards-Version to 3.9.4 (no change).
   * Email change: Florian Schlichting -> f...@debian.org.
   * Remove workaround, maintblead argument handling was fixed upstream.
 .
   [ gregor herrmann ]
   * Strip trailing slash from metacpan URLs.
   * New upstream release.
 Fixes "FTBFS with perl 5.18: test failures"
 (Closes: #711620)
   * Declare compliance with Debian Policy 3.9.5.
Checksums-Sha1: 
 b5c18ff04ce8e682ca54233a0e2889c9cab976d5 2262 
libthread-queue-any-perl_1.14-1.dsc
 09861b3635639524999e244e731b2f9bc08f4f18 12591 
libthread-queue-any-perl_1.14.orig.tar.gz
 e7fb32af158d2dc1cfa009cc31c42189db397efd 2204 
libthread-queue-any-perl_1.14-1.debian.tar.xz
 9457c5b6581b5897062fe3acecd7390929405501 14518 
libthread-queue-any-perl_1.14-1_all.deb
Checksums-Sha256: 
 30399e2f463b85762dd9591c6e8ab28dbdebedafa63c9871666b68857a7

Bug#711620: Pending fixes for bugs in the libthread-queue-any-perl package

[pkg-perl-maintainers]

tag 711620 + pending
thanks

Some bugs in the libthread-queue-any-perl package are closed in
revision 3214abe1b8ddbb4001db1c20e243216de220fc75 in branch 'master'
by gregor herrmann

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libthread-queue-any-perl.git;a=commitdiff;h=3214abe

Commit message:

New upstream release. Fixes "FTBFS with perl 5.18: test failures" (Closes: 
#711620)


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

Processed: Pending fixes for bugs in the libthread-queue-any-perl package

[Debian Bug Tracking System]

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

> tag 711620 + pending
Bug #711620 [src:libthread-queue-any-perl] libthread-queue-any-perl: FTBFS with 
perl 5.18: test failures
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
711620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711620
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: limit source to lintian, tagging 739671, tagging 739744, tagging 733318, tagging 738175 ...

[Debian Bug Tracking System]

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

> #lintian (2.5.22) UNRELEASED; urgency=medium
> #
> #  * checks/cruft.pm:
> #+ [BR,NT] Optimise the GFDL check considerably in some
> #  cases (e.g. the linux source).  (Closes: #738342)
> #+ [BR] Factorize GFDL detection. Detect non official
> #  wordings of GFDL invariant section.  (Closes: #717916).
> #  Fix some old false positives.
> #  (Closes: #742260, #741212).
> #+ [BR] Add opentoken non official wording for GFDL
> #  invariant section, thanks to Nicolas Boulenguez.
> #  (Closes: #740183).
> #+ [BR] Detect minified js based on line length.
> #  (Closes: #735348).
> #+ [BR] Detect missing sources for minified javascript, flash project,
> #  flash files, and elf binary.
> #  * data/binary/embedded-libs:
> #+ [RG] Detect embedded copies of liblivemedia, libgadu, libssh,
> #  libssh2, freetype, nss, and nspr.
> #+ [RG] Adjust the detection of embedded copies of libmagic.
> #+ [RG] Detect embedded copies of an ancient tinyxml.  Thanks to
> #  Andreas Rönnquist for the report.  (Closes: #733318)
> #  * data/files/privacy*:
> #+ [BR] Improve detection of privacy-breach-google-cse, thanks to
> #  Paul Wise (Closes: #739247).
> #+ [BR] Detect google+, thanks to Paul Wise.
> #  (Closes: #738175).
> #  * lib/Lintian/Collect/Source.pm:
> #+ [NT] Apply patch from Mathieu Parent to make "binaries" return
> #  the package name in the same order as they are listed in the
> #  control file.  (Closes: #739671)
> #  * t/runtests:
> #+ [NT] Cache test artifacts and reuse them in subsequent
> #  runs.  This removes the majority of the runtime
> #  overhead of running the test suite on subsequent runs.
> #  (Closes: #699083)
> #+ [NT,BR] Fix test suite issues caused by a regression
> #  in tar 1.27.  (Closes: #739744)
> #
> limit source lintian
Limiting to bugs with field 'source' containing at least one of 'lintian'
Limit currently set to 'source':'lintian'

> tags 739671 + pending
Bug #739671 [lintian] phppear check randomly checks one binary
Added tag(s) pending.
> tags 739744 + pending
Bug #739744 [lintian] lintian: FTBFS test failures
Added tag(s) pending.
> tags 733318 + pending
Bug #733318 [lintian] lintian doesn't detect an embedded tinyxml
Added tag(s) pending.
> tags 738175 + pending
Bug #738175 [lintian] lintian: please add privacy-breach-googleplus
Added tag(s) pending.
> tags 735348 + pending
Bug #735348 [lintian] [lintian] Detect minified javascript
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
733318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733318
735348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735348
738175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738175
739671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739671
739744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739744
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#742405: zookeeper ftbfs without openjdk

[Tim Retout]

Zookeeper also fails to build on sparc.  These seem to be the
architectures where openjdk is not the default JDK.

This would explain why 3.4.5+dfsg-1 built successfully, because
openjdk was the default on kfreebsd between November and February.

I'm not actually sure how best to resolve this...

-- 
Tim Retout 


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

Processed: unblock 739744 with 740199

[Debian Bug Tracking System]

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

> unblock 739744 with 740199
Bug #739744 [lintian] lintian: FTBFS test failures
739744 was blocked by: 740199
739744 was not blocking any bugs.
Removed blocking bug(s) of 739744: 740199
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
739744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739744
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: bug 740199 is forwarded to http://lists.gnu.org/archive/html/bug-tar/2014-03/msg00001.html

[Debian Bug Tracking System]

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

> forwarded 740199 
> http://lists.gnu.org/archive/html/bug-tar/2014-03/msg1.html
Bug #740199 {Done: Niels Thykier } [tar] [regression] tar 
mess up \ and \\ files
Ignoring request to change the forwarded-to-address of bug#740199 to the same 
value
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
740199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740199
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: bug 740199 is forwarded to http://lists.gnu.org/archive/html/bug-tar/2014-03/msg00001.html

[Debian Bug Tracking System]

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

> forwarded 740199 
> http://lists.gnu.org/archive/html/bug-tar/2014-03/msg1.html
Bug #740199 {Done: Niels Thykier } [tar] [regression] tar 
mess up \ and \\ files
Set Bug forwarded-to-address to 
'http://lists.gnu.org/archive/html/bug-tar/2014-03/msg1.html'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
740199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740199
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#724469: FTBFS on all big-endian architectures

[Adam Conrad]

On Sun, Mar 23, 2014 at 10:33:32AM +0100, intrigeri wrote:
> 
> I'd rather not drop s390x from the list of architectures this package
> is built for, but this RC bug has now been around for 6 months, and at
> some point I'll want to get rid of it.

Not fixing a bug isn't the way to get rid of it.  This isn't s390x
specific, it's incorrect code leading to failure on 64-bit BE arches,
of which there are several, it just happens that s390x is the only
officially-supported one.

I understand that you personally may not have the skills to fix it,
and need input from either a porter or upstream, but that doesn't mean
the bug magically doesn't exist if no one gives you a patch to fix it.

... Adam


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

Bug#742392: hurd: Hang during apt-get upgrade from last image release

[Petter Reinholdtsen]

I got some help from gg0 on IRC to debug this issue.  He proposed to
upgrade everything except hurd first, and this worked:

  apt-get update
  apt-mark hold hurd
  apt-get dist-upgrade
  apt-mark unhold hurd

This reduced the amount of packages to upgrade to the minimum.
Upgrading using apt-get dist-upgrade now also hung, but it was a lot
quicker to test as I had snapshotted the freshly upgraded system.

We tried adding a serial console (adding
GRUB_CMDLINE_GNUMACH="console=com0" in /etc/default/grub and running
update-grub) and see if anything showed up there.  No messages showed
up in the serial console when the system got stuck.  I did however
notice that the hang caused the machine to no longer respond to ping,
and my ssh connections would stop working too.

Last, I tried to upgrade over ssh (instead of the console I had tried
initially, and then I got a bit more text before the machine went
dead:

  root@debian:~# apt-get dist-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
libdb5.1
  The following NEW packages will be installed:
login
  The following packages will be upgraded:
db5.1-util hurd hurd-dev hurd-libs0.3
  4 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
  Need to get 1351 kB/6117 kB of archives.
  After this operation, 2894 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://cdn.debian.net/debian/ sid/main login hurd-i386 1:4.1.5.1-1.1 
[695 kB]
  Get:2 http://cdn.debian.net/debian/ sid/main db5.1-util hurd-i386 5.1.29-8 
[656 kB]
  Fetched 1351 kB in 7s (177 kB/s)  

  Reading changelogs... Done
  (Reading database ... 38608 files and directories currently installed.)
  Preparing to unpack .../hurd-dev_1%3a0.5.git20140320-1_hurd-i386.deb ...
  Unpacking hurd-dev (1:0.5.git20140320-1) over (1:0.5.git20140203-1) ...


  Preparing to unpack .../hurd-libs0.3_1%3a0.5.git20140320-1_hurd-i386.deb ...
  Unpacking hurd-libs0.3:hurd-i386 (1:0.5.git20140320-1) over 
(1:0.5.git20140203-1) ...
  Setting up hurd-libs0.3:hurd-i386 (1:0.5.git20140320-1) ...
  Processing triggers for libc-bin (2.18-3) ...
  (Reading database ... 38608 files and directories currently installed.)
  Preparing to unpack .../hurd_1%3a0.5.git20140320-1_hurd-i386.deb ...
  Unpacking hurd (1:0.5.git20140320-1) over (1:0.5.git20140203-1) ...
  Setting up hurd (1:0.5.git20140320-1) ...
  Installing new version of config file /etc/hurd/rc ...
  Installing new version of config file /etc/init.d/hurd-console ...

Not sure how to continue, as gg0 is not able to reproduce the problem,
but at least here it happen every time.

-- 
Happy hacking
Petter Reinholdtsen


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

Bug#742442: garmin-ant-downloader: Segfaults on amd64

[Christian Perrier]

Package: garmin-ant-downloader
Version: 20110626-1
Severity: serious

g-a-t seems unusable on amd64. Apparently, as soon as it is launched
AND an ANT+ stick is present, it then segfaults:


$ ./gant
Erreur de segmentation


I somehow suspect this might be related to the following warning
during compilation:

cperrier@mykerinos:~/src/debian/running/garmin-ant-downloader(master)
$ make
cc -g -Wall xml2-config --cflags   -c -o gant.o gant.c
gant.c: In function ‘dump_data’:
gant.c:268:7: warning: format ‘%x’ expects argument of type ‘unsigned
int’, but argument 3 has type ‘size_t’ [-Wformat=]
   fprintf(out, "0x%04x:", offset + i);
  ^
  gant.c: In function ‘chevent’:
  gant.c:821:9: warning: variable ‘newdata’ set but not
used [-Wunused-but-set-variable]
uint newdata;
 ^
 cc -g -Wall xml2-config --cflags   -c -o antlib.o antlib.c
 cc   gant.o antlib.o  -lpthread -lm xml2-config --libs -o gant
 
cperrier@mykerinos:~/src/debian/running/garmin-ant-downloader(master)

Sadly, my skills end here and I really need help debugging this...:-|


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

Kernel: Linux 3.13-1-amd64 (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 garmin-ant-downloader depends on:
ii  libc62.18-4
ii  libxml2  2.9.1+dfsg1-3

garmin-ant-downloader recommends no packages.

garmin-ant-downloader 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#725531: aptdaemon: FTBFS: Tests failed

[Julian Andres Klode]

On Sun, Mar 23, 2014 at 7:28 PM, Steve McIntyre  wrote:
> On Sun, Mar 23, 2014 at 06:15:55PM +0100, Julian Andres Klode wrote:
>>On Sun, Mar 23, 2014 at 5:00 PM, Steve McIntyre  wrote:
>>>
>>> Ping?
>>>
>>> Over 5 months later with no response. I have just confirmed the
>>> problem locally with a test build. Should we remove aptdaemon?
>>>
>>
>>The thing is, it runs fine. Some packages just have crazy test suites
>>which start failing at some point. Simply disabling them (for example,
>>by adding  an || true to debian/rules) is better until everyone
>>switched to PackageKit and we remove it or upstream manages to create
>>a new release.
>
> That's fair enough, there was just no response in the bug report here
> to give any clues as to your plans. I'll agree that the test suite
> here looks quite OTT - maybe it's worth either disabling or trimming
> some of it down and doing an upload so this doesn't get removed as RC
> buggy?
>

I did this in the time between my email and yours, in 1.1.1-2, just by
merging the current Ubuntu changes, which make test suite failures not
fail the build. Although the test suite now seems to pass.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.


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

Bug#725531: aptdaemon: FTBFS: Tests failed

[Steve McIntyre]

On Sun, Mar 23, 2014 at 06:15:55PM +0100, Julian Andres Klode wrote:
>On Sun, Mar 23, 2014 at 5:00 PM, Steve McIntyre  wrote:
>>
>> Ping?
>>
>> Over 5 months later with no response. I have just confirmed the
>> problem locally with a test build. Should we remove aptdaemon?
>>
>
>The thing is, it runs fine. Some packages just have crazy test suites
>which start failing at some point. Simply disabling them (for example,
>by adding  an || true to debian/rules) is better until everyone
>switched to PackageKit and we remove it or upstream manages to create
>a new release.

That's fair enough, there was just no response in the bug report here
to give any clues as to your plans. I'll agree that the test suite
here looks quite OTT - maybe it's worth either disabling or trimming
some of it down and doing an upload so this doesn't get removed as RC
buggy?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html


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

Bug#660473: openais seems discontinued upstream

[Ben Hutchings]

Control: severity -1 normal

On Tue, 2013-10-15 at 16:40 +0200, Mathieu Malaterre wrote:
> severity 660473 grave
> thanks
> 
> Marking as grave, I believe that we should not ship openais in jessie,
> since project is dead upstream:
> 
> http://web.archive.org/web/20120227232142/http://www.openais.org/doku.php

I don't disagree, but this does not meet any of the criteria for a
severity of grave.

Ben.

-- 
Ben Hutchings
Computers are not intelligent.  They only think they are.


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

Processed: Re: openais seems discontinued upstream

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #660473 [openais] openais seems discontinued upstream
Severity set to 'normal' from 'grave'

-- 
660473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660473
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#725531: marked as done (aptdaemon: FTBFS: Tests failed)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 18:03:26 +
with message-id 
and subject line Bug#725531: fixed in aptdaemon 1.1.1-2
has caused the Debian Bug report #725531,
regarding aptdaemon: FTBFS: Tests 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.)


-- 
725531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aptdaemon
Version: 1.1.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131006 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully): 
> ==
> ERROR: test (tests.test_pep8.AptDaemonPep8TestCase)
> Check if the source code matches the PEP8 style conventions.
> --
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/tests/test_pep8.py", line 35, in test
> "aptdaemon", "tests"])
>   File "/usr/lib/python3.3/subprocess.py", line 547, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['pep8', '--statistics', 
> '--show-source', '--show-pep8', '--exclude', 'pkenums.py', 'aptdaemon', 
> 'tests']' returned non-zero exit status 1
> 
> ==
> FAIL: test_install_file (tests.test_worker.WorkerTestCase)
> Test the installation of a local package file.
> --
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/tests/test_worker.py", line 342, in test_install_file
> trans.error.details)
> nose.proxy.AssertionError: False is not true : Lintian check results for 
> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:
> 
> 'False is not true : Lintian check results for 
> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n' 
> = self._formatMessage('False is not true : Lintian check results for 
> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n', 
> "%s is not true" % safe_repr(False))
> >>  raise self.failureException('False is not true : Lintian check results 
> >> for 
> >> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n')
> 
> 
> --
> Ran 78 tests in 136.860s
> 
> FAILED (failures=1, errors=1, skipped=4)
> make[1]: *** [test-python3.3] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/10/06/aptdaemon_1.1.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: aptdaemon
Source-Version: 1.1.1-2

We believe that the bug you reported is fixed in the latest version of
aptdaemon, 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 725...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julian Andres Klode  (supplier of updated aptdaemon 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: Sun, 23 Mar 2014 18:44:37 +0100
Source: aptdaemon
Binary: aptdaemon python3-aptdaemon python-aptdaemon python3-aptdaemon.test 
aptdaemon-data python-aptdaemon-gtk python3-aptdaemon.pkcompat 
python-aptdaemon.gtkwidgets python3-aptdaemon.gtk3widgets 
python-aptdaemon.gtk3widgets
Architecture: source all
Version: 1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Julian Andres Klode 
Changed-By: Julian Andres Klode 
Description: 
 aptdaemon  - transaction based package management service
 aptdaemon-data - data files for clients
 python-aptdaemon - Python 2 module for the server and client of aptdaemon
 python-ap

Bug#638760: Removal of grace, pygrace and expeyes

[Evgeny Stambulchik]

On 23/03/14 19:04, Michael Banck wrote:


As soon as the t1lib library package is removed from Debian, it is not
an embedded library anymore, just some code.  It probably makes sense to
link it statically then.


And this is exactly what is going to happen. When an external t1lib is 
not found, configure falls back to using the bundled static library. It 
has been so for many, many years. So all that is needed is removing the 
explicit dependency on t1lib.



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

Bug#742432: Malformed patch results in deletion of already-patched files

[Ben Hutchings]

Package: quilt
Version: 0.61-1
Severity: grave

(git)/home/ben/src/linux-3.2[linux-3.2.y]$ quilt push --fuzz=2
Applying patch 
x86-add-check-for-number-of-available-vectors-before-cpu-down.patch
patching file arch/x86/include/asm/irq.h
patching file arch/x86/kernel/irq.c
Hunk #1 succeeded at 222 (offset -40 lines).
patching file arch/x86/kernel/smpboot.c
patch:  malformed patch at line 220:cpu_disable_common();

Patch x86-add-check-for-number-of-available-vectors-before-cpu-down.patch does 
not apply (enforce with -f)

# Oops, I need to fix diff addresses

(git)/home/ben/src/linux-3.2[linux-3.2.y]$ quilt push --fuzz=2
Applying patch 
x86-add-check-for-number-of-available-vectors-before-cpu-down.patch
can't find file to patch at input line 104
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|From: Prarit Bhargava 
|Date: Mon, 13 Jan 2014 06:51:01 -0500
|Subject: x86: Add check for number of available vectors before CPU down
|
|commit da6139e49c7cb0f4251265cb5243b8d220adb48d upstream.
|
|Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=64791
|
|When a cpu is downed on a system, the irqs on the cpu are assigned to
|other cpus.  It is possible, however, that when a cpu is downed there
|aren't enough free vectors on the remaining cpus to account for the
|vectors from the cpu that is being downed.
|
|This results in an interesting "overflow" condition where irqs are
|"assigned" to a CPU but are not handled.
|
|For example, when downing cpus on a 1-64 logical processor system:
|
|
|[  232.021745] smpboot: CPU 61 is now offline
|[  238.480275] smpboot: CPU 62 is now offline
|[  245.991080] [ cut here ]
|[  245.996270] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 
dev_watchdog+0x246/0x250()
|[  246.005688] NETDEV WATCHDOG: p786p1 (ixgbe): transmit queue 0 timed out
|[  246.013070] Modules linked in: lockd sunrpc iTCO_wdt iTCO_vendor_support 
sb_edac ixgbe microcode e1000e pcspkr joydev edac_core lpc_ich ioatdma ptp mdio 
mfd_core i2c_i801 dca pps_core i2c_core wmi acpi_cpufreq isci libsas 
scsi_transport_sas
|[  246.037633] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.12.0+ #14
|[  246.044451] Hardware name: Intel Corporation S4600LH 
../SVRBD-ROW_T, BIOS SE5C600.86B.01.08.0003.022620131521 02/26/2013
|[  246.057371]  0009 88081fa03d40 8164fbf6 
88081fa0ee48
|[  246.065728]  88081fa03d90 88081fa03d80 81054ecc 
88081fa13040
|[  246.074073]   88200cce 0040 

|[  246.082430] Call Trace:
|[  246.085174][] dump_stack+0x46/0x58
|[  246.091633]  [] warn_slowpath_common+0x8c/0xc0
|[  246.098352]  [] warn_slowpath_fmt+0x46/0x50
|[  246.104786]  [] dev_watchdog+0x246/0x250
|[  246.110923]  [] ? 
dev_deactivate_queue.constprop.31+0x80/0x80
|[  246.119097]  [] call_timer_fn+0x3a/0x110
|[  246.125224]  [] ? update_process_times+0x6f/0x80
|[  246.132137]  [] ? 
dev_deactivate_queue.constprop.31+0x80/0x80
|[  246.140308]  [] run_timer_softirq+0x1f0/0x2a0
|[  246.146933]  [] __do_softirq+0xe0/0x220
|[  246.152976]  [] call_softirq+0x1c/0x30
|[  246.158920]  [] do_softirq+0x55/0x90
|[  246.164670]  [] irq_exit+0xa5/0xb0
|[  246.170227]  [] smp_apic_timer_interrupt+0x4a/0x60
|[  246.177324]  [] apic_timer_interrupt+0x6a/0x70
|[  246.184041][] ? cpuidle_enter_state+0x5b/0xe0
|[  246.191559]  [] ? cpuidle_enter_state+0x57/0xe0
|[  246.198374]  [] cpuidle_idle_call+0xbd/0x200
|[  246.204900]  [] arch_cpu_idle+0xe/0x30
|[  246.210846]  [] cpu_startup_entry+0xd0/0x250
|[  246.217371]  [] rest_init+0x77/0x80
|[  246.223028]  [] start_kernel+0x3ee/0x3fb
|[  246.229165]  [] ? repair_env_string+0x5e/0x5e
|[  246.235787]  [] x86_64_start_reservations+0x2a/0x2c
|[  246.242990]  [] x86_64_start_kernel+0xf8/0xfc
|[  246.249610] ---[ end trace fb74fdef54d79039 ]---
|[  246.254807] ixgbe :c2:00.0 p786p1: initiating reset due to tx timeout
|[  246.262489] ixgbe :c2:00.0 p786p1: Reset adapter
|Last login: Mon Nov 11 08:35:14 from 10.18.17.119
|[root@(none) ~]# [  246.792676] ixgbe :c2:00.0 p786p1: detected SFP+: 5
|[  249.231598] ixgbe :c2:00.0 p786p1: NIC Link is Up 10 Gbps, Flow 
Control: RX/TX
|[  246.792676] ixgbe :c2:00.0 p786p1: detected SFP+: 5
|[  249.231598] ixgbe :c2:00.0 p786p1: NIC Link is Up 10 Gbps, Flow 
Control: RX/TX
|
|(last lines keep repeating.  ixgbe driver is dead until module reload.)
|
|If the downed cpu has more vectors than are free on the remaining cpus on the
|system, it is possible that some vectors are "orphaned" even though they are
|assigned to a cpu.  In this case, since the ixgbe driver had a watchdog, the
|watchdog fired and notified that something was wrong.
|
|This patch adds a function, check_vectors(), to compare the number of vectors
|on the CPU going down and compares it to the number of vectors available on
|the system.  If there aren't enough vectors for the CPU

Bug#655969: lirc: prompting due to modified conffiles which where not modified by the user

[Ben Hutchings]

Some time ago you committed:

r497 | slh-guest | 2012-02-23 12:20:25 + (Thu, 23 Feb 2012) | 1 line

  detection stages (Closes: #660956).

Index: debian/changelog
===
--- debian/changelog(revision 496)
+++ debian/changelog(revision 497)
@@ -88,7 +88,7 @@
 lirc 0.7.1pre2-8, previous versions unconditionally started an interactive
 non-debconf hardware detection/ selection menu, which always left
 hardware.conf modified; md5sums for prior versions apply to aborted h/w
-detection stages.
+detection stages (Closes: #660956).
 
  -- Stefan Lippers-Hollmann   Sat, 28 Jan 2012 20:03:16 +0100
 

I think you actually meant to close #655969.

Anyway, as the postinst in wheezy does not appear to modify the config
file, it appears that further upgrades should not have this problem.
Given that the bug was tagged squeeze-ignore and wheezy-ignore, perhaps
it can now be closed?

Ben.

-- 
Ben Hutchings
Computers are not intelligent.  They only think they are.


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

Bug#725531: aptdaemon: FTBFS: Tests failed

[Julian Andres Klode]

On Sun, Mar 23, 2014 at 5:00 PM, Steve McIntyre  wrote:
> Control: tag -1 +confirmed
>
> On Sun, Oct 06, 2013 at 08:07:49PM +0200, David Suárez wrote:
>>Source: aptdaemon
>>Version: 1.1.1-1
>>Severity: serious
>>Tags: jessie sid
>>User: debian...@lists.debian.org
>>Usertags: qa-ftbfs-20131006 qa-ftbfs
>>Justification: FTBFS on amd64
>>
>>Hi,
>>
>>During a rebuild of all packages in sid, your package failed to build on
>>amd64.
>>
>>Relevant part (hopefully):
>>> ==
>>> ERROR: test (tests.test_pep8.AptDaemonPep8TestCase)
>>> Check if the source code matches the PEP8 style conventions.
>>> --
>>> Traceback (most recent call last):
>>>   File "/«PKGBUILDDIR»/tests/test_pep8.py", line 35, in test
>>> "aptdaemon", "tests"])
>>>   File "/usr/lib/python3.3/subprocess.py", line 547, in check_call
>>> raise CalledProcessError(retcode, cmd)
>>> subprocess.CalledProcessError: Command '['pep8', '--statistics', 
>>> '--show-source', '--show-pep8', '--exclude', 'pkenums.py', 'aptdaemon', 
>>> 'tests']' returned non-zero exit status 1
>>>
>>> ==
>>> FAIL: test_install_file (tests.test_worker.WorkerTestCase)
>>> Test the installation of a local package file.
>>> --
>>> Traceback (most recent call last):
>>>   File "/«PKGBUILDDIR»/tests/test_worker.py", line 342, in test_install_file
>>> trans.error.details)
>>> nose.proxy.AssertionError: False is not true : Lintian check results for 
>>> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:
>>>
>>> 'False is not true : Lintian check results for 
>>> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n'
>>>  = self._formatMessage('False is not true : Lintian check results for 
>>> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n',
>>>  "%s is not true" % safe_repr(False))
>>> >>  raise self.failureException('False is not true : Lintian check results 
>>> >> for 
>>> >> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n')
>>>
>>>
>>> --
>>> Ran 78 tests in 136.860s
>>>
>>> FAILED (failures=1, errors=1, skipped=4)
>>> make[1]: *** [test-python3.3] Error 1
>
> Ping?
>
> Over 5 months later with no response. I have just confirmed the
> problem locally with a test build. Should we remove aptdaemon?
>

The thing is, it runs fine. Some packages just have crazy test suites
which start failing at some point. Simply disabling them (for example,
by adding  an || true to debian/rules) is better until everyone
switched to PackageKit and we remove it or upstream manages to create
a new release.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.


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

Bug#638760: Removal of grace, pygrace and expeyes

[Evgeny Stambulchik]

Hi,

IMHO, this discussion went well out of proportions...

On 23/03/14 18:47, Michael Gilbert wrote:


Embedded libraries are almost always to be avoided due to numerous
reasons listed in the Debian security documentation.


Right, but these reasons are inapplicable when the external library is 
removed from the debian archive and as such, is literally inexistent for 
debian users. From this point on, t1lib is a part of the grace package. 
Its sources should be treated exactly like the rest of C files under the 
grace-x.y.z directory.



You can make the change to internal t1lib, but you should expect an RC
bug and removal from testing after some time.


Why then? I mean, anything may happen, but how is this related to the 
_current_ motion to remove the _t1lib_ package?



That may be a compromise solution.  You get to keep grace in unstable,
and advanced users that need it can figure out how to fetch it there,
and at the same time, the deprecated library is kept out of testing
and stable.


The deprecated library is kept out of testing and stable by removing 
_its_ _own_ package. It is not installed in /usr/[lib,include]. Just 
linked statically in a single executable.


Best,

Evgeny


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

Bug#738384: marked as done (python-repoze.what: FTBFS: cp: not writing through dangling symlink [...]/jquery.js)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 17:03:34 +
with message-id 
and subject line Bug#738384: fixed in python-repoze.what 1.0.9-3
has caused the Debian Bug report #738384,
regarding python-repoze.what: FTBFS: cp: not writing through dangling symlink 
[...]/jquery.js
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.)


-- 
738384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-repoze.what
Version: 1.0.9-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140208 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> running install
> running build
> running build_py
> running egg_info
> writing requirements to repoze.what.egg-info/requires.txt
> writing repoze.what.egg-info/PKG-INFO
> writing namespace_packages to repoze.what.egg-info/namespace_packages.txt
> writing top-level names to repoze.what.egg-info/top_level.txt
> writing dependency_links to repoze.what.egg-info/dependency_links.txt
> writing entry points to repoze.what.egg-info/entry_points.txt
> reading manifest file 'repoze.what.egg-info/SOURCES.txt'
> writing manifest file 'repoze.what.egg-info/SOURCES.txt'
> running install_lib
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/__init__.py
>  (namespace package)
> copying repoze/what/release.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what
> copying repoze/what/predicates.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what
> copying repoze/what/authorize.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what/__init__.py
>  (namespace package)
> copying repoze/what/middleware.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what
> copying repoze/what/adapters/testutil.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what/adapters
> copying repoze/what/adapters/__init__.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what/adapters
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what/plugins/__init__.py
>  (namespace package)
> running install_egg_info
> Copying repoze.what.egg-info to 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze.what-1.0.9-py2.7.egg-info
> Installing 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze.what-1.0.9-py2.7-nspkg.pth
> running install_scripts
> dh_installdocs -ppython-repoze.what 
> cp: not writing through dangling symlink 
> '/«PKGBUILDDIR»/debian/python-repoze.what/usr/share/doc/python-repoze.what/html/_static/jquery.js'
> dh_installdocs: cd 'docs/build/html//..' && find 'html' \( -type f -or -type 
> l \) -and ! -empty -print0 | xargs -0 -I {} cp --parents -dp {} 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/share/doc/python-repoze.what 
> returned exit code 123
> make: *** [binary-install/python-repoze.what] Error 123

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/02/08/python-repoze.what_1.0.9-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-repoze.what
Source-Version: 1.0.9-3

We believe that the bug you reported is fixed in the latest version of
python-repoze.what, 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 738...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Wiltshire  (supplier of updated python-repoze.what 
package)

(This message was generated automatically at their request; if you
believe that 

Bug#638760: Removal of grace, pygrace and expeyes

[Michael Banck]

Hi,

On Sun, Mar 23, 2014 at 12:47:18PM -0400, Michael Gilbert wrote:
> On Sun, Mar 23, 2014 at 10:02 AM, Michael Banck wrote:
> > This is my summary, see below for specific replies to specific points:
> >
> > 1. Grace is not unmaintained, it is maintained in Debian by Nicholas
> > Breen.  It also is not abandoned upstream, its latest stable release
> > being from late 2012.
> >
> > 2. As t1lib is superseded and unmaintained, it should be removed from
> > Debian as a library package.
> >
> > 3. As grace is a useful application, it should remain in Debian.  To
> > this end, with respect to point #2 above, it could start to use the
> > internal copy of t1lib instead of the external package.
> >
> > 4. As soon as grace is switched to the internal copy, t1lib becomes a
> > convenience library of grace, similar to thousands of other convenience
> > libraries in Debian package.  In particular, security concerns should be
> > less pronounced, as grace does not (TTBOMK) run as root, nor does it
> > listen on the network.  Basically, the security concerns should be
> > similar to any other piece of C/C++ code in any other graphical
> > application.
> 
> Embedded libraries are almost always to be avoided due to numerous
> reasons listed in the Debian security documentation.

Please explain how this is different to any other convenience library?

As soon as the t1lib library package is removed from Debian, it is not
an embedded library anymore, just some code.  It probably makes sense to
link it statically then.
 
> You can make the change to internal t1lib, but you should expect an RC
> bug and removal from testing after some time.

Whether or not that situation is RC (I don't think it would be) would be
up to the release team or ultimately the tech-ctte I guess.
 
> That may be a compromise solution.  You get to keep grace in unstable,
> and advanced users that need it can figure out how to fetch it there,
> and at the same time, the deprecated library is kept out of testing
> and stable.

I don't see a reason not to ship it in jessie.


Michael


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

Bug#717928: Package list for transition

[Neil Williams]

For information, the current list of packages blocking the removal of lcms are:

Checking reverse dependencies...
# Broken Depends:
cegui-mk2: libcegui-mk2-dev [amd64 armel armhf i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc s390x sparc]
dcraw: dcraw
devil: libdevil-dev
   libdevil1c2
entangle: entangle [amd64 armel armhf i386 mips mipsel powerpc s390x sparc]
f-spot: f-spot [amd64 armel i386 kfreebsd-amd64 kfreebsd-i386 powerpc s390x]
geeqie: geeqie
gimp: gimp
gimp-plugin-registry: gimp-plugin-registry [amd64 armel armhf i386 
kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc]
graphicsmagick: graphicsmagick
libgraphics-magick-perl
libgraphicsmagick++3
libgraphicsmagick1-dev
libgraphicsmagick3
haskell-hsmagick: libghc-hsmagick-dev [amd64 armel armhf i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc s390x sparc]
imagemagick: libmagickcore-dev
inkscape: inkscape
libmng: libmng-dev
libmng1
photoprint: photoprint
rawstudio: rawstudio
scribus: scribus
ufraw: gimp-ufraw
   ufraw
   ufraw-batch
xastir: xastir [amd64 armel armhf i386 mips mipsel powerpc s390x sparc]
xsane: xsane

# Broken Build-Depends:
cegui-mk2: liblcms1-dev
crystalspace: liblcms-dev
dcraw: liblcms1-dev
devil: liblcms1-dev
entangle: liblcms1-dev
exactimage: liblcms1-dev
f-spot: liblcms1-dev
geeqie: liblcms1-dev
ghostscript: liblcms1-dev
gimp: liblcms1-dev (>= 1.16) |liblcms-dev
gimp-plugin-registry: liblcms1-dev
graphicsmagick: liblcms1-dev
inkscape: liblcms1-dev
libmng: liblcms1-dev
netsurf: liblcms1-dev
photoprint: liblcms1-dev
rawstudio: liblcms1-dev
scribus: liblcms1-dev (>= 1.13)
ufraw: liblcms-dev
xsane: liblcms1-dev


-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



signature.asc
Description: PGP signature

Bug#711332: now able to remove

[Neil Williams]

reassign 711332 ftp.debian.org
retitle 711332 RM: w3c-dtd-xhtml -- RoQA; superseded by w3c-sgml-lib
severity 711332 normal
thanks

It is now time to remove w3c-dtd-xhtml as outlined in the original bug.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



signature.asc
Description: PGP signature

Processed: now able to remove

[Debian Bug Tracking System]

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

> reassign 711332 ftp.debian.org
Bug #711332 [w3c-dtd-xhtml] remove w3c-dtd-xhtml
Bug reassigned from package 'w3c-dtd-xhtml' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #711332 to the same values 
previously set
Ignoring request to alter fixed versions of bug #711332 to the same values 
previously set
> retitle 711332 RM: w3c-dtd-xhtml -- RoQA; superseded by w3c-sgml-lib
Bug #711332 [ftp.debian.org] remove w3c-dtd-xhtml
Changed Bug title to 'RM: w3c-dtd-xhtml -- RoQA; superseded by w3c-sgml-lib' 
from 'remove w3c-dtd-xhtml'
> severity 711332 normal
Bug #711332 [ftp.debian.org] RM: w3c-dtd-xhtml -- RoQA; superseded by 
w3c-sgml-lib
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
711332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711332
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#638760: Removal of grace, pygrace and expeyes

[Michael Gilbert]

On Sun, Mar 23, 2014 at 10:02 AM, Michael Banck wrote:
> Hi,
>
> This is my summary, see below for specific replies to specific points:
>
> 1. Grace is not unmaintained, it is maintained in Debian by Nicholas
> Breen.  It also is not abandoned upstream, its latest stable release
> being from late 2012.
>
> 2. As t1lib is superseded and unmaintained, it should be removed from
> Debian as a library package.
>
> 3. As grace is a useful application, it should remain in Debian.  To
> this end, with respect to point #2 above, it could start to use the
> internal copy of t1lib instead of the external package.
>
> 4. As soon as grace is switched to the internal copy, t1lib becomes a
> convenience library of grace, similar to thousands of other convenience
> libraries in Debian package.  In particular, security concerns should be
> less pronounced, as grace does not (TTBOMK) run as root, nor does it
> listen on the network.  Basically, the security concerns should be
> similar to any other piece of C/C++ code in any other graphical
> application.

Embedded libraries are almost always to be avoided due to numerous
reasons listed in the Debian security documentation.

You can make the change to internal t1lib, but you should expect an RC
bug and removal from testing after some time.

That may be a compromise solution.  You get to keep grace in unstable,
and advanced users that need it can figure out how to fetch it there,
and at the same time, the deprecated library is kept out of testing
and stable.

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: retitle 637488 to t1lib: history of security issues, unmaintained upstream, unsupportable

[Debian Bug Tracking System]

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

> retitle 637488 t1lib: history of security issues, unmaintained upstream, 
> unsupportable
Bug #637488 [t1lib] t1lib: many severe security issues, unmaintained upstream, 
unsupportable
Changed Bug title to 't1lib: history of security issues, unmaintained upstream, 
unsupportable' from 't1lib: many severe security issues, unmaintained upstream, 
unsupportable'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
637488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637488
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#638760: Removal of grace, pygrace and expeyes

[Georges Khaznadar]

Dear Evgeny,

I strongly back your point of view.

As Neil wants a quick solution, I shall develop alternative depedencies
for expeyes which currently relies on grace: it will offer the
possibility to choose qtiplot.

I agree with you, a user which learned to use Xmgrace will grind loads
of work happily.

Best regards,   Georges.

Evgeny Stambulchik a écrit :
> Hello,
> 
> I'm the [passive] upstream maintainer. Just to make things clear:
> 
> 1. grace is perfectly happy using its own copy of t1lib. So you can
> safely remove the t1lib debian package.
> 
> 2. Yes, perhaps only 0.34% of all users use it. But same can be said
> about 90% of the entire debian archive (for each package separately,
> of course).
> 
> 3. Yes, it is potentially buggy and insecure. But since in 99.9% you
> use it within the projects you work yourself on, nothing wrong can
> happen. In the worst case you loose some time. (And in my
> experience, grace crashes MUCH less frequently than some
> high-profile softwares which are really exposed to the Internet.)
> 
> 4. I have no time and intention right now to switch to freetype. For
> the scope it is currently used in grace, t1lib is adequate. When I
> come across a bug, I fix it - that's how the bundled t1lib copy got
> emerged in the first place.
> 
> Best,
> 
> Evgeny
> 
> On 23/03/14 12:01, Neil Williams wrote:
> >On Sun, 23 Mar 2014 11:01:39 +1100
> >Drew Parsons  wrote:
> >
> >>Grace is one of the most useful packages in the entire archive.
> >
> >... for 0.34% of users of the archive, maybe. To me, it is simply an RC
> >buggy package which has had no new development upstream since 2012 and
> >which depends on an obsolete, abandoned library. Unless it can be
> >ported, it will need to be removed alongside t1lib.
> >
> >Those who care about grace need to scratch their own itch and fix it.
> >
> >>I am not aware of anything other package that provides the same degree
> >>of functionality.
> >>
> >>Removing it is not a good idea.
> >
> >Removing it is necessary, as explained. t1lib has been superseded and
> >packages which used to use it need to migrate. The other packages have
> >already done so, those which fail to do so cannot be supported when the
> >underlying dependency has been abandoned.
> >
> >
> 
> 

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: Digital signature

Processed: retitle 566947 to emacs23-nox fails to install on loongson2f, tagging 566947

[Debian Bug Tracking System]

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

> retitle 566947 emacs23-nox fails to install on loongson2f
Bug #566947 [emacs23-nox] emacs23-nox fails to install
Changed Bug title to 'emacs23-nox fails to install on loongson2f' from 
'emacs23-nox fails to install'
> tags 566947 + help
Bug #566947 [emacs23-nox] emacs23-nox fails to install on loongson2f
Added tag(s) help.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
566947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566947
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: Bug#725531: aptdaemon: FTBFS: Tests failed

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +confirmed
Bug #725531 [src:aptdaemon] aptdaemon: FTBFS: Tests failed
Added tag(s) confirmed.

-- 
725531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725531
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#725531: aptdaemon: FTBFS: Tests failed

[Steve McIntyre]

Control: tag -1 +confirmed

On Sun, Oct 06, 2013 at 08:07:49PM +0200, David Suárez wrote:
>Source: aptdaemon
>Version: 1.1.1-1
>Severity: serious
>Tags: jessie sid
>User: debian...@lists.debian.org
>Usertags: qa-ftbfs-20131006 qa-ftbfs
>Justification: FTBFS on amd64
>
>Hi,
>
>During a rebuild of all packages in sid, your package failed to build on
>amd64.
>
>Relevant part (hopefully): 
>> ==
>> ERROR: test (tests.test_pep8.AptDaemonPep8TestCase)
>> Check if the source code matches the PEP8 style conventions.
>> --
>> Traceback (most recent call last):
>>   File "/«PKGBUILDDIR»/tests/test_pep8.py", line 35, in test
>> "aptdaemon", "tests"])
>>   File "/usr/lib/python3.3/subprocess.py", line 547, in check_call
>> raise CalledProcessError(retcode, cmd)
>> subprocess.CalledProcessError: Command '['pep8', '--statistics', 
>> '--show-source', '--show-pep8', '--exclude', 'pkenums.py', 'aptdaemon', 
>> 'tests']' returned non-zero exit status 1
>> 
>> ==
>> FAIL: test_install_file (tests.test_worker.WorkerTestCase)
>> Test the installation of a local package file.
>> --
>> Traceback (most recent call last):
>>   File "/«PKGBUILDDIR»/tests/test_worker.py", line 342, in test_install_file
>> trans.error.details)
>> nose.proxy.AssertionError: False is not true : Lintian check results for 
>> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:
>> 
>> 'False is not true : Lintian check results for 
>> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n' 
>> = self._formatMessage('False is not true : Lintian check results for 
>> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n',
>>  "%s is not true" % safe_repr(False))
>> >>  raise self.failureException('False is not true : Lintian check results 
>> >> for 
>> >> /«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n')
>> 
>> 
>> --
>> Ran 78 tests in 136.860s
>> 
>> FAILED (failures=1, errors=1, skipped=4)
>> make[1]: *** [test-python3.3] Error 1

Ping?

Over 5 months later with no response. I have just confirmed the
problem locally with a test build. Should we remove aptdaemon?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
We don't need no education.
We don't need no thought control.


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

Bug#739499: marked as done (missing license in debian/copyright)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 15:52:04 +
with message-id 
and subject line Bug#739499: fixed in x264 2:0.142.2389+git956c8d8-2
has caused the Debian Bug report #739499,
regarding missing license in debian/copyright
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.)


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

Package: x264
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

Dear Maintainer,

please add the missing license of
  x264-0.142.2389+git956c8d8/extras/cl*
to debian/copyright.

Thanks!
  Thorsten
--- End Message ---
--- Begin Message ---
Source: x264
Source-Version: 2:0.142.2389+git956c8d8-2

We believe that the bug you reported is fixed in the latest version of
x264, 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 739...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated x264 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: Sun, 23 Mar 2014 11:09:02 -0400
Source: x264
Binary: x264 libx264-142 libx264-dev
Architecture: source i386
Version: 2:0.142.2389+git956c8d8-2
Distribution: experimental
Urgency: low
Maintainer: Reinhard Tartler 
Changed-By: Reinhard Tartler 
Description: 
 libx264-142 - x264 video coding library
 libx264-dev - development files for libx264
 x264   - video encoder for the H.264/MPEG-4 AVC standard
Closes: 701628 739499
Changes: 
 x264 (2:0.142.2389+git956c8d8-2) experimental; urgency=low
 .
   [ William Grant ]
   * Add aarch64-pic.patch to enable -fPIC on arm64 to fix link failure.
 .
   [ Andrew Starr-Bochicchio ]
   * Compile using -fno-aggressive-loop-optimizations (LP: #1241772)
 .
   [ Dimitri John Ledkov ]
   * Update config.guess/sub, attempt building on pp64el
 .
   [ Reinhard Tartler ]
   * Document the license of extras/cl*.h (Closes: #739499)
   * Pickup the patches documented above from Ubuntu while retaining proper
 attribution.
 .
   [ Roland Stigge ]
   * Disable altivec on powerpcspe (Closes: #701628)
   * Add autopkgtest test case "encode_testimage"
Checksums-Sha1: 
 e9c4f1a6515c879247cff67651f2ec4cbdf3ecba 2204 x264_0.142.2389+git956c8d8-2.dsc
 d21dbc94a2952e658239d44acae0ac7fbbaced7e 20716 
x264_0.142.2389+git956c8d8-2.debian.tar.xz
 e8e92d9fb4e0217092777dc7e2276bda09920dcb 291774 
x264_0.142.2389+git956c8d8-2_i386.deb
 3dfa82c72cf3a59cf42213cc44010642593a0648 698170 
libx264-142_0.142.2389+git956c8d8-2_i386.deb
 ab6437c155988ceac9180789ffb08009cdedaa5d 429038 
libx264-dev_0.142.2389+git956c8d8-2_i386.deb
Checksums-Sha256: 
 efe6bf9e682026f2d2cbed84a49e7bb795836637b6c5944dbcdd3204f4d18432 2204 
x264_0.142.2389+git956c8d8-2.dsc
 7b32b99fafca6d55ea0bb0a2a4e338eb92123dbc126652ceccb18de87e75ce0f 20716 
x264_0.142.2389+git956c8d8-2.debian.tar.xz
 2806177370d88e9a4e62e0c6d68004d9b4303364d03aadf0325cff431e510930 291774 
x264_0.142.2389+git956c8d8-2_i386.deb
 91a3a7478832489c713fe8c20141f3cb510f1bb007241d6d03e18974dcd31266 698170 
libx264-142_0.142.2389+git956c8d8-2_i386.deb
 ea526721f19d720711a74178e1ff87560d2a36d85e02484f8d0394c929cbe347 429038 
libx264-dev_0.142.2389+git956c8d8-2_i386.deb
Files: 
 0a8f067ef3dc2b00ada49873a8b3fcd4 2204 libs optional 
x264_0.142.2389+git956c8d8-2.dsc
 a3b036de7001a783c673ff00a693b61d 20716 libs optional 
x264_0.142.2389+git956c8d8-2.debian.tar.xz
 f316edf035bd2975d34c70341b93fde6 291774 graphics optional 
x264_0.142.2389+git956c8d8-2_i386.deb
 761135e1181dc675d28c12a79e166cca 698170 libs optional 
libx264-142_0.142.2389+git956c8d8-2_i386.deb
 225f800df84235531471996e699daadc 429038 libdevel optional 
libx264-dev_0.142.2389+git956c8d8-2_i386.deb

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

iQGcBAEBCAAGBQJTLv4rAAoJEIuAbIZKeKRFctEL/0JKSyhMFU59Hyk8XV0jcb8u
i10C94zn+Whr0TjT8zScVQiBNQuLg1ptjSZJdzkTdY0NLKvInwZmlh7m2mLwnpEQ
tPfpZ8uHiZzW5fCX/F/5mY6YWUbyW4peW0VMSZdiHdsY3NmnB0Lf8AQ2UXcI0L7s
IwNiq47o9SvDbJoV5q/BogBnTGH7RBe4IHc9tquiiygss5VZFrGF3hJi2fTwDBpq
vPtCcvwyCtCUZMVw+FyriZo48N1/eJhv2O6+lEgejaOkvt55YywUIm/FoTcfgJ0A
5vd9MSyM6+BR95

Bug#741774: marked as done (quagga: FTBFS: vtysh.c:2240:22: error: 'Function' undeclared (first use in this function))

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 15:51:38 +
with message-id 
and subject line Bug#741774: fixed in quagga 0.99.22.4-4
has caused the Debian Bug report #741774,
regarding quagga: FTBFS: vtysh.c:2240:22: error: 'Function' undeclared (first 
use in this function)
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.)


-- 
741774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quagga
Version: 0.99.22.4-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140315 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

On new readline versions old-style function typedefs have been deprecated.

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I../lib 
> -I../lib  -D_FORTIFY_SOURCE=2 -fPIE -g -O2 -fPIE -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c vtysh.c
> vtysh.c: In function 'vtysh_readline_init':
> vtysh.c:2240:22: error: 'Function' undeclared (first use in this function)
>rl_bind_key ('?', (Function *) vtysh_rl_describe);
>   ^
> vtysh.c:2240:22: note: each undeclared identifier is reported only once for 
> each function it appears in
> vtysh.c:2240:32: error: expected expression before ')' token
>rl_bind_key ('?', (Function *) vtysh_rl_describe);
> ^
> vtysh.c:2242:39: error: 'CPPFunction' undeclared (first use in this function)
>rl_attempted_completion_function = (CPPFunction *)new_completion;
>^
> vtysh.c:2242:52: error: expected expression before ')' token
>rl_attempted_completion_function = (CPPFunction *)new_completion;
> ^
> make[4]: *** [vtysh.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/03/15/quagga_0.99.22.4-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: quagga
Source-Version: 0.99.22.4-4

We believe that the bug you reported is fixed in the latest version of
quagga, 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 741...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Hammers  (supplier of updated quagga 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: Sun, 23 Mar 2014 15:28:42 +0100
Source: quagga
Binary: quagga quagga-dbg quagga-doc
Architecture: source amd64 all
Version: 0.99.22.4-4
Distribution: unstable
Urgency: medium
Maintainer: Christian Hammers 
Changed-By: Christian Hammers 
Description: 
 quagga - BGP/OSPF/RIP routing daemon
 quagga-dbg - BGP/OSPF/RIP routing daemon (debug symbols)
 quagga-doc - documentation files for quagga
Closes: 741774
Changes: 
 quagga (0.99.22.4-4) unstable; urgency=medium
 .
   * Fix build failure with readline-6.3 (thanks to Matthias Klose).
 Closes: #741774
Checksums-Sha1: 
 aafb1843b6efc873877ebb24cc61efcd9ee4abb3 1448 quagga_0.99.22.4-4.dsc
 d87ea8885b737d98ccd23ede1df975079e60b11e 35272 quagga_0.99.22.4-4.debian.tar.xz
 00ccae1ce9a631dde0d9c4eb450d79c87ac5205b 1196552 quagga_0.99.22.4-4_amd64.deb
 162fedca71d1991a12e659f06765e37dc5a45269 1804054 
quagga-dbg_0.99.22.4-4_amd64.deb
 5fb8c4fa1d8d3bb956ae0bb039deba6147259556 656882 quagga-doc_0.99.22.4-4_all.deb
Checksums-Sha256: 
 f452887fc83436f9cf65f3985cb0a200580b04b8486c4063993f28c29684e6f0 1448 
quagga_0.99.22.4-4.dsc
 1537bf112cb7be120504c80c8b20170b512ba1cb193b0eb937f677345cabf302 35272 
quagga_0.99.22.4-4.debian.tar.xz
 47519390c35e7960587e8463f08084cd2dd5f1f927d728ec4e1338c54e210109 1196552 
quagga_0.99.22.4-4_amd64.deb
 9f56b37fa9dda42d3d6a83587ee6b05b7893

Processed: severity of 739139 is serious

[Debian Bug Tracking System]

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

> severity 739139 serious
Bug #739139 [src:python-fixtures] python-fixtures: FTBFS: python3.4: not found
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
739139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739139
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#737204: zeroc-ice: diff for NMU version 3.5.1-5.2

[Jonathan Wiltshire]

tags 737204 + patch
tags 737204 + pending
thanks

Dear maintainer,

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

Regards.

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

diff -Nru zeroc-ice-3.5.1/debian/changelog zeroc-ice-3.5.1/debian/changelog
--- zeroc-ice-3.5.1/debian/changelog	2014-02-26 08:54:45.0 +
+++ zeroc-ice-3.5.1/debian/changelog	2014-03-23 14:53:57.0 +
@@ -1,3 +1,10 @@
+zeroc-ice (3.5.1-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Conflict/Replace on libzeroc-ice3.3-java as well (Closes: #737204)
+
+ -- Jonathan Wiltshire   Sun, 23 Mar 2014 14:53:15 +
+
 zeroc-ice (3.5.1-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru zeroc-ice-3.5.1/debian/control zeroc-ice-3.5.1/debian/control
--- zeroc-ice-3.5.1/debian/control	2014-02-26 08:57:01.0 +
+++ zeroc-ice-3.5.1/debian/control	2014-03-23 14:53:07.0 +
@@ -608,8 +608,8 @@
 Section: java
 Depends: ${misc:Depends}, libdb5.3-java | libdb-java
 Recommends: ice35-translators, ice35-slice, ant
-Replaces: libzeroc-ice-java, libzeroc-ice3.4-java
-Conflicts: libzeroc-ice-java, libzeroc-ice3.4-java
+Replaces: libzeroc-ice-java, libzeroc-ice3.4-java, libzeroc-ice3.3-java
+Conflicts: libzeroc-ice-java, libzeroc-ice3.4-java, libzeroc-ice3.3-java
 Description: Ice for Java libraries
  Ice, the Internet Communications Engine, is a middleware for the
  practical programmer developed by ZeroC Inc. A high-performance


signature.asc
Description: Digital signature

Processed: zeroc-ice: diff for NMU version 3.5.1-5.2

[Debian Bug Tracking System]

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

> tags 737204 + patch
Bug #737204 [libzeroc-ice3.5-java] libzeroc-ice3.5-java: fails to upgrade from 
squeeze - trying to overwrite /usr/share/java/ant-ice.jar
Added tag(s) patch.
> tags 737204 + pending
Bug #737204 [libzeroc-ice3.5-java] libzeroc-ice3.5-java: fails to upgrade from 
squeeze - trying to overwrite /usr/share/java/ant-ice.jar
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
737204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737204
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#742418: marked as done (astyle FTBFS on s390x: use -fPIC instead of -fpic when building shared libraries)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 11:25:37 -0400
with message-id 

and subject line Fwd: astyle_2.03-1.2_i386.changes ACCEPTED into unstable
has caused the Debian Bug report #742418,
regarding astyle FTBFS on s390x: use -fPIC instead of -fpic when building 
shared libraries
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.)


-- 
742418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: astyle
Version: 2.03-1.1
Severity: serious

build log:

obj/astyle_main_sj.o: In function `Java_AStyleInterface_AStyleGetVersion':
/«PKGBUILDDIR»/build/gcc/../../src/astyle_main.cpp:3103:(.text+0x35c):
relocation truncated to fit: R_390_GOT12 against symbol `astyle::g_version'
defined in .data.rel.local section in obj/astyle_main_sj.o
obj/astyle_main_sj.o: In function `AStyleGetVersion':
/«PKGBUILDDIR»/build/gcc/../../src/astyle_main.cpp:3253:(.text+0x386):
relocation truncated to fit: R_390_GOT12 against symbol `astyle::g_version'
defined in .data.rel.local section in obj/astyle_main_sj.o
obj/astyle_main_sj.o: In function `ASStreamIterator':
/«PKGBUILDDIR»/build/gcc/../../src/astyle_main.cpp:95:(.text+0x2b9e):
relocation truncated to fit: R_390_GOT12 against symbol `vtable for
astyle::ASStreamIterator,
std::allocator > >' defined in
..data.rel.ro._ZTVN6astyle16ASStreamIteratorISt19basic_istringstreamIcSt11char_traitsIcESaIc[_ZTVN6astyle16ASStreamIteratorISt19basic_istringstreamIcSt11char_traitsIcESaIc]
section in obj/astyle_main_sj.o
obj/astyle_main_sj.o: In function
`astyle::ASStreamIterator, std::allocator > >::~ASStreamIterator()':
/«PKGBUILDDIR»/build/gcc/../../src/astyle_main.cpp:111:(.text._ZN6astyle16ASStreamIteratorISt19basic_istringstreamIcSt11char_traitsIcESaIcEEED2Ev[_ZN6astyle16ASStreamIteratorISt19basic_istringstreamIcSt11char_traitsIcESaIcEEED5Ev]+0x18):
additional relocation overflows omitted from the output
collect2: error: ld returned 1 exit status
make[2]: *** [libastylej.so] Error 1
make[2]: Leaving directory `/«PKGBUILDDIR»/build/gcc'
dh_auto_build: make -j1 -C build/gcc astyle shared java returned exit code 2




Fix:
build/gcc/Makefile sets
CFLAGSs   = -DASTYLE_LIB -fpic $(CFLAGSr)
CFLAGSsd  = -DASTYLE_LIB -fpic $(CFLAGSd)
CFLAGSa   = -DASTYLE_LIB $(CFLAGSr)
CFLAGSad  = -DASTYLE_LIB $(CFLAGSd)
CFLAGSsj  = -DASTYLE_JNI -fpic $(CFLAGSr) $(JAVAINCS)
CFLAGSsjd = -DASTYLE_JNI -fpic $(CFLAGSd) $(JAVAINCS)

which should be -fPIC to build safely on more architectures

I'll do another 0-delay NMU to fix this.



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

Kernel: Linux 3.11.0-18-generic (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
--- End Message ---
--- Begin Message ---
Version: 2.03-1.2

-- Forwarded message --
From: Debian FTP Masters 
Date: Sun, Mar 23, 2014 at 11:18 AM
Subject: astyle_2.03-1.2_i386.changes ACCEPTED into unstable
To: Margarita Manterola , Scott Howard 




Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 23 Mar 2014 10:58:45 -0400
Source: astyle
Binary: astyle libastyle0debian0 libastyle-dev libastylej-jni
Architecture: source i386
Version: 2.03-1.2
Distribution: unstable
Urgency: low
Maintainer: Margarita Manterola 
Changed-By: Scott Howard 
Description:
 astyle - Source code indenter for C++/C/Java/C# source code
 libastyle-dev - Library header files for C++/C/Java/C# source code indenter
 libastyle0debian0 - Shared library for C++/C/Java/C# source code indenter
 libastylej-jni - Java JNI library for C++/C/Java/C# source code indenter
Changes:
 astyle (2.03-1.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix FTBFS on s390x due to using -fpic instead of -fPIC
 - debian/patches/FTBFS_FPIC.patch
Checksums-Sha1:
 d00ff11f6d17e441fc58333e639bcee9e68e90cc 1401 astyle_2.03-1.2.dsc
 668f984e80ec3b5ac81d5eb65f721566cef43b5a 14416
astyle_2.03-1.2.debian.tar.xz
 ffed272019d53bad51f6cee69ff06e6278ffce6a 144788 astyle_2.03-1.2_i386.deb
 998ea2ea75b842cfe35dcbf5d2d60460546a73aa 80468
libastyle0debian0_2.03-1.2_i386.deb
 f85c02183a97928b7513a75f398f64635203e33a 13808
libastyle-dev_2.03-1.2_i386.deb
 600654fc2e6c0974429ef8b2180ba809866b723c 98210
libastylej-jni_2.03-1.2_i386.deb
Checksums-Sha256:
 ef4b4a0779de7c9071eceef464bcdc0db08eada97187d8a3889384e9d1c77ec9 1401
astyle_2.03-1.2.dsc
 8d143eadacbd4036960bb380564f

Bug#713074: marked as done (pygpgme: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 14:39:53 +
with message-id <20140323143953.ga14...@lupin.home.powdarrmonkey.net>
and subject line Re: Bug#713074: pygpgme: FTBFS: tests failed
has caused the Debian Bug report #713074,
regarding pygpgme: FTBFS: tests 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.)


-- 
713074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygpgme
Version: 0.2-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»'
> python2.7 setup.py build_ext -i
> running build_ext
> building 'gpgme._gpgme' extension
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c src/gpgme.c -o 
> build/temp.linux-x86_64-2.7/src/gpgme.o -D_FILE_OFFSET_BITS=64
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c 
> src/pygpgme-error.c -o build/temp.linux-x86_64-2.7/src/pygpgme-error.o 
> -D_FILE_OFFSET_BITS=64
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c 
> src/pygpgme-data.c -o build/temp.linux-x86_64-2.7/src/pygpgme-data.o 
> -D_FILE_OFFSET_BITS=64
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c 
> src/pygpgme-context.c -o build/temp.linux-x86_64-2.7/src/pygpgme-context.o 
> -D_FILE_OFFSET_BITS=64
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c src/pygpgme-key.c 
> -o build/temp.linux-x86_64-2.7/src/pygpgme-key.o -D_FILE_OFFSET_BITS=64
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c 
> src/pygpgme-signature.c -o 
> build/temp.linux-x86_64-2.7/src/pygpgme-signature.o -D_FILE_OFFSET_BITS=64
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c 
> src/pygpgme-import.c -o build/temp.linux-x86_64-2.7/src/pygpgme-import.o 
> -D_FILE_OFFSET_BITS=64
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c 
> src/pygpgme-keyiter.c -o build/temp.linux-x86_64-2.7/src/pygpgme-keyiter.o 
> -D_FILE_OFFSET_BITS=64
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c 
> src/pygpgme-constants.c -o 
> build/temp.linux-x86_64-2.7/src/pygpgme-constants.o -D_FILE_OFFSET_BITS=64
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c 
> src/pygpgme-genkey.c -o build/temp.linux-x86_64-2.7/src/pygpgme-genkey.o 
> -D_FILE_OFFSET_BITS=64
> x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
> -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> build/temp.linux-x86_64-2.7/src/gpgme.o 
> build/temp.linux-x86_64-2.7/src/pygpgme-error.o 
> build/temp.linux-x86_64-2.7/src/pygpgme-data.o 
> build/temp.linux-x86_64-2.7/src/pygpgme-context.o 
> build/temp.linux-x86_64-2.7/src/pygpgme-key.o 
> build/temp.linux-x86_64-2.7/src/pygpgme-signature.o 
> build/temp.linux-x86_64-2.7/src/pygpgme-import.o 
> build/temp.linux-x86_64-2.7/src/pygpgme-keyiter.o 
> build/temp.linux-x86_64-2.7/src/pygpgme-constants.o 
> build/temp.linux-x86_64-2.7/src/pygpgme-genkey.o -lgpgme -o 
> /«PKGBUILDDIR»/gpgme/_gpgme.so
> GPG_AGENT_INFO= python2.7 test_all.py -v
> test_armor (gpgme.tests.test_context.ContextTestCase) ... ok
> test_constructor (gpgme.tests.test_context.ContextTestCase) ... ok
> test_include_certs (gpgme.tests.test_context.ContextTestCase) ... ok
> test_keylist_mode (gpgme.tests.test_context.ContextTestCase) ... ok
> test_passphrase_cb (gpgme.tests.test_context.ContextTestCase) ... ok
> test_progress_cb (gpgme.tests.test_context.ContextTestCase) ... ok
> test_protocol (gpgme.tests.test_context.ContextTestCase) ..

Processed: missing licence for a few files in debian/copyright, problems in stable

[Debian Bug Tracking System]

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

> notfound 740602 1.9.0-beta6.9+dfsg1-2.1
Bug #740602 [doomsday] missing license in debian/copyright
Ignoring request to alter found versions of bug #740602 to the same values 
previously set
> found 740602 1.10.4-1
Bug #740602 [doomsday] missing license in debian/copyright
Marked as found in versions doomsday/1.10.4-1.
> notfound 739616 1.2.99.1-1.1
Bug #739616 {Done: Tino Mettler } [syncevolution] missing 
license in debian/copyright
Ignoring request to alter found versions of bug #739616 to the same values 
previously set
> notfound 739499 2:0.123.2189+git35cf912-1
Bug #739499 [x264] missing license in debian/copyright
Ignoring request to alter found versions of bug #739499 to the same values 
previously set
> found 739499 2:0.142.2389+git956c8d8-1
Bug #739499 [x264] missing license in debian/copyright
Marked as found in versions x264/2:0.142.2389+git956c8d8-1.
> found 738967 0.48-2
Bug #738967 [libical] missing license in debian/copyright
There is no source info for the package 'libical' at version '0.48-2' with 
architecture ''
Unable to make a source version for version '0.48-2'
Marked as found in versions 0.48-2.
> tags 738967 + wheezy-ignore
Bug #738967 [libical] missing license in debian/copyright
Added tag(s) wheezy-ignore.
> notfound 738836 1:5.1.20080914-1.3
Bug #738836 {Done: Paul Hardy } [unifont] missing 
license in debian/copyright
Ignoring request to alter found versions of bug #738836 to the same values 
previously set
> #Thorsten, (no big deal but) if you had provided this in the first place...
> #maintaining RC bugs in stable would be a bit easier :)
> #thanks - 20 more these to go...
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
738836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738836
738967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738967
739499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739499
739616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739616
740602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740602
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: NMU for astyle FTBFS on s390x

[Debian Bug Tracking System]

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

> tags 742418 patch pending
Bug #742418 [astyle] astyle FTBFS on s390x: use -fPIC instead of -fpic when 
building shared libraries
Added tag(s) pending and patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
742418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742418
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#742418: NMU for astyle FTBFS on s390x

[Scott Howard]

tags 742418 patch pending
thanks

Hello all,

See NMU at:
http://anonscm.debian.org/gitweb/?p=collab-maint/astyle.git;a=commitdiff;h=40043eca6053949a6bfbfb98eb5fecb18988edef

has been uploaded to DELAYED/0.

Let me know if you need anything else.
~Scott

Bug#735921: issue is not fixed

[Steve McIntyre]

On Thu, Feb 27, 2014 at 11:40:58AM +0100, Matthias Klose wrote:
>issue is not fixed, see
>https://buildd.debian.org/status/fetch.php?pkg=radare2&arch=s390x&ver=0.9.6-3&stamp=1390938839

Here's a simple debdiff for a real fix. Uploaded to DELAYED/5 just now.

Add #define _GNU_SOURCE as shown in the strcasestr man page:

diff -Nru radare2-0.9.6/debian/changelog radare2-0.9.6/debian/changelog
--- radare2-0.9.6/debian/changelog  2014-01-28 18:29:35.0 +
+++ radare2-0.9.6/debian/changelog  2014-03-23 14:46:29.0 +
@@ -1,3 +1,10 @@
+radare2 (0.9.6-3.1) unstable; urgency=medium
+
+  * debian/patches/12_fix_strcasestr_declaration: Add #define _GNU_SOURCE
+as well, to get the definition of strcasestr (closes: #735921).
+
+ -- Steve McIntyre <93...@debian.org>  Sun, 23 Mar 2014 14:38:44 +
+
 radare2 (0.9.6-3) unstable; urgency=medium
 
   * debian/patches/12_fix_strcasestr_declaration: Fixed a missing include,
diff -Nru radare2-0.9.6/debian/patches/12_fix_strcasestr_declaration.patch 
radare2-0.9.6/debian/patches/12_fix_strcasestr_declaration.patch
--- radare2-0.9.6/debian/patches/12_fix_strcasestr_declaration.patch
2014-01-28 18:27:01.0 +
+++ radare2-0.9.6/debian/patches/12_fix_strcasestr_declaration.patch
2014-03-23 14:47:54.0 +
@@ -1,14 +1,18 @@
 Description: Fix an implicit declaration of strcasestr.
  Matthias Klose found a function not defined in the build logs.  It's due
  to a missing include.  I checked upstream and it's has already been fixed.
+ Updated by Steve McIntyre <93...@debian.org>
 Author: David Martínez Moreno 
 Bug-Debian: http://bugs.debian.org/735921
 Forwarded: not-needed
-Last-Update: 2014-01-28
+Last-Update: 2014-03-23
 
 --- radare2-0.9.6.orig/libr/util/str.c
 +++ radare2-0.9.6/libr/util/str.c
-@@ -3,6 +3,7 @@
+@@ -1,8 +1,10 @@
+ /* radare - LGPL - Copyright 2007-2013 - pancake */
+
++#define _GNU_SOURCE
  #include "r_types.h"
  #include "r_util.h"
  #include 


-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back


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

Bug#738434: marked as done (ruby-capybara: FTBFS: ERROR: Test "ruby1.9.1" failed)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 11:56:52 -0300
with message-id <20140323145652.ga30...@debian.org>
and subject line Re: Bug#738434: ruby-capybara: FTBFS: ERROR: Test "ruby1.9.1" 
failed
has caused the Debian Bug report #738434,
regarding ruby-capybara: FTBFS: ERROR: Test "ruby1.9.1" 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.)


-- 
738434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-capybara
Version: 2.1.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140208 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>   1) Capybara::Session DSL #select should return value of the first option
>  Failure/Error: @session.visit('/form')
>  NoMethodError:
>undefined method `mappings' for Tilt:Module
>  # ./lib/capybara/spec/test_app.rb:126:in `block in '
>  # ./lib/capybara/rack_test/browser.rb:59:in `process'
>  # ./lib/capybara/rack_test/browser.rb:35:in 
> `process_and_follow_redirects'
>  # ./lib/capybara/rack_test/browser.rb:21:in `visit'
>  # ./lib/capybara/rack_test/driver.rb:42:in `visit'
>  # ./lib/capybara/session.rb:193:in `visit'
>  # ./lib/capybara/dsl.rb:51:in `block (2 levels) in '
>  # ./lib/capybara/spec/session/select_spec.rb:3:in `block (2 levels) in 
> '
> 
>   2) Capybara::Session DSL #select should return value of the selected option
>  Failure/Error: @session.visit('/form')
>  NoMethodError:
>undefined method `mappings' for Tilt:Module
>  # ./lib/capybara/spec/test_app.rb:126:in `block in '
>  # ./lib/capybara/rack_test/browser.rb:59:in `process'
>  # ./lib/capybara/rack_test/browser.rb:35:in 
> `process_and_follow_redirects'
>  # ./lib/capybara/rack_test/browser.rb:21:in `visit'
>  # ./lib/capybara/rack_test/driver.rb:42:in `visit'
>  # ./lib/capybara/session.rb:193:in `visit'
>  # ./lib/capybara/dsl.rb:51:in `block (2 levels) in '
>  # ./lib/capybara/spec/session/select_spec.rb:3:in `block (2 levels) in 
> '
> 
>   3) Capybara::Session DSL #select should allow selecting options where there 
> are inexact matches
>  Failure/Error: @session.visit('/form')
>  NoMethodError:
>undefined method `mappings' for Tilt:Module
>  # ./lib/capybara/spec/test_app.rb:126:in `block in '
>  # ./lib/capybara/rack_test/browser.rb:59:in `process'
>  # ./lib/capybara/rack_test/browser.rb:35:in 
> `process_and_follow_redirects'
>  # ./lib/capybara/rack_test/browser.rb:21:in `visit'
>  # ./lib/capybara/rack_test/driver.rb:42:in `visit'
>  # ./lib/capybara/session.rb:193:in `visit'
>  # ./lib/capybara/dsl.rb:51:in `block (2 levels) in '
>  # ./lib/capybara/spec/session/select_spec.rb:3:in `block (2 levels) in 
> '
> 
>   4) Capybara::Session DSL #select should allow selecting options where they 
> are the only inexact match
>  Failure/Error: @session.visit('/form')
>  NoMethodError:
>undefined method `mappings' for Tilt:Module
>  # ./lib/capybara/spec/test_app.rb:126:in `block in '
>  # ./lib/capybara/rack_test/browser.rb:59:in `process'
>  # ./lib/capybara/rack_test/browser.rb:35:in 
> `process_and_follow_redirects'
>  # ./lib/capybara/rack_test/browser.rb:21:in `visit'
>  # ./lib/capybara/rack_test/driver.rb:42:in `visit'
>  # ./lib/capybara/session.rb:193:in `visit'
>  # ./lib/capybara/dsl.rb:51:in `block (2 levels) in '
>  # ./lib/capybara/spec/session/select_spec.rb:3:in `block (2 levels) in 
> '
> 
>   5) Capybara::Session DSL #select should not allow selecting options where 
> they are the only inexact match if `Capybara.exact_options = true`
>  Failure/Error: @session.visit('/form')
>  NoMethodError:
>undefined method `mappings' for Tilt:Module
>  # ./lib/capybara/spec/test_app.rb:126:in `block in '
>  # ./lib/capybara/rack_test/browser.rb:59:in `process'
>  # ./lib/capybara/rack_test/browser.rb:35:in 
> `process_and_follow_redirects'
>  # ./lib/capybara/rack_test/browser.rb:21:in `visit'
>  # ./lib/capybara/rack_test/driver.rb:42:in `visit'
>  # ./lib/capybara/session.rb:193:in `visit'
>  # ./lib/capybara/dsl.rb:51:in `block (2 levels) in '
>  # ./lib/capybara/spec/session/select_spec.rb:3:in `block (2 levels) in 
> '
> 
>   6) Capybara::Session DSL #select should not allow selecting an option if 
> the match is ambiguous
>  

Processed: jessie

[Debian Bug Tracking System]

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

> tags 741000 + sid jessie
Bug #741000 [libical-parser-html-perl] Syntax errors with perl 5.18
Bug #741010 [libical-parser-html-perl] libical-parser-html-perl: missing parens 
around qw()
Added tag(s) sid and jessie.
Added tag(s) sid and jessie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
741000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741000
741010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741010
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#742418: astyle FTBFS on s390x: use -fPIC instead of -fpic when building shared libraries

[Scott Howard]

Package: astyle
Version: 2.03-1.1
Severity: serious

build log:

obj/astyle_main_sj.o: In function `Java_AStyleInterface_AStyleGetVersion':
/«PKGBUILDDIR»/build/gcc/../../src/astyle_main.cpp:3103:(.text+0x35c):
relocation truncated to fit: R_390_GOT12 against symbol `astyle::g_version'
defined in .data.rel.local section in obj/astyle_main_sj.o
obj/astyle_main_sj.o: In function `AStyleGetVersion':
/«PKGBUILDDIR»/build/gcc/../../src/astyle_main.cpp:3253:(.text+0x386):
relocation truncated to fit: R_390_GOT12 against symbol `astyle::g_version'
defined in .data.rel.local section in obj/astyle_main_sj.o
obj/astyle_main_sj.o: In function `ASStreamIterator':
/«PKGBUILDDIR»/build/gcc/../../src/astyle_main.cpp:95:(.text+0x2b9e):
relocation truncated to fit: R_390_GOT12 against symbol `vtable for
astyle::ASStreamIterator,
std::allocator > >' defined in
..data.rel.ro._ZTVN6astyle16ASStreamIteratorISt19basic_istringstreamIcSt11char_traitsIcESaIc[_ZTVN6astyle16ASStreamIteratorISt19basic_istringstreamIcSt11char_traitsIcESaIc]
section in obj/astyle_main_sj.o
obj/astyle_main_sj.o: In function
`astyle::ASStreamIterator, std::allocator > >::~ASStreamIterator()':
/«PKGBUILDDIR»/build/gcc/../../src/astyle_main.cpp:111:(.text._ZN6astyle16ASStreamIteratorISt19basic_istringstreamIcSt11char_traitsIcESaIcEEED2Ev[_ZN6astyle16ASStreamIteratorISt19basic_istringstreamIcSt11char_traitsIcESaIcEEED5Ev]+0x18):
additional relocation overflows omitted from the output
collect2: error: ld returned 1 exit status
make[2]: *** [libastylej.so] Error 1
make[2]: Leaving directory `/«PKGBUILDDIR»/build/gcc'
dh_auto_build: make -j1 -C build/gcc astyle shared java returned exit code 2




Fix:
build/gcc/Makefile sets
CFLAGSs   = -DASTYLE_LIB -fpic $(CFLAGSr)
CFLAGSsd  = -DASTYLE_LIB -fpic $(CFLAGSd)
CFLAGSa   = -DASTYLE_LIB $(CFLAGSr)
CFLAGSad  = -DASTYLE_LIB $(CFLAGSd)
CFLAGSsj  = -DASTYLE_JNI -fpic $(CFLAGSr) $(JAVAINCS)
CFLAGSsjd = -DASTYLE_JNI -fpic $(CFLAGSd) $(JAVAINCS)

which should be -fPIC to build safely on more architectures

I'll do another 0-delay NMU to fix this.



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

Kernel: Linux 3.11.0-18-generic (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


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

Bug#741826: needs python-all python3-all in build-deps

[Neil Williams]

This comes down to the fact that python-versions -s tells you what is
supported, not necessarily what is installed. To ensure that the
versions you want are actually installed in the build chroot, you must
build-depend on the -all versions of the python interpreter packages:

Maintainer: Stephen M. Webb 
Build-Depends: asciidoc,
   debhelper (>= 9),
   dh-autoreconf,
   pkg-config,
   python-all,
   python3-all,
   xmlto
Standards-Version: 3.9.5

With this fixed, the package builds cleanly in a pbuilder chroot and
should therefore be fine on the buildds as well.

Please ensure all uploads are tested in a pbuilder or similar clean
chroot.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



signature.asc
Description: PGP signature

Bug#638760: Removal of grace, pygrace and expeyes

[Michael Banck]

Hi,

This is my summary, see below for specific replies to specific points:

1. Grace is not unmaintained, it is maintained in Debian by Nicholas
Breen.  It also is not abandoned upstream, its latest stable release
being from late 2012.

2. As t1lib is superseded and unmaintained, it should be removed from
Debian as a library package.

3. As grace is a useful application, it should remain in Debian.  To
this end, with respect to point #2 above, it could start to use the
internal copy of t1lib instead of the external package.

4. As soon as grace is switched to the internal copy, t1lib becomes a
convenience library of grace, similar to thousands of other convenience
libraries in Debian package.  In particular, security concerns should be
less pronounced, as grace does not (TTBOMK) run as root, nor does it
listen on the network.  Basically, the security concerns should be
similar to any other piece of C/C++ code in any other graphical
application.

5. Nobody gets to tell the grace maintainer at which level the grace
package should be maintained, but everybody is welcome to file bugs and
patches for specific issues.

On Sun, Mar 23, 2014 at 01:17:55PM +, Neil Williams wrote:
> On Sun, 23 Mar 2014 13:08:14 +0100
> Michael Banck  wrote:
> > On Sun, Mar 23, 2014 at 10:03:53AM +, Neil Williams wrote:
> > > On Sat, 22 Mar 2014 20:38:49 -0700
> > > Nicholas Breen  wrote:
> > > > On Sat, Mar 22, 2014 at 04:10:39PM +, Neil Williams wrote:
> > > > > I'm seeking the removal of pygrace and expeyes so that grace
> > > > > can be removed. CC'ing the relevant maintainers (and filing
> > > > > important bugs for each package). I expect the removal to start
> > > > > in two weeks unless I hear back about a viable solution.
> > > > 
> > > > If just getting standalone t1lib out of the archive is the goal, I
> > > > don't mind incorporating all of the existing t1lib patches into
> > > > the embedded copy. 
> > > 
> > > No. How does that solve the problem of t1lib being abandoned
> > > upstream and already superseded by freetype?
> > 
> > Why is it a problem in the first place? Software is being rewritten
> > and superseded constantly, this doesn't mean other software using
> > those old libraries are immediately to be sent to the bin.
> 
> It's not immediate. t1lib has had no upstream changes in Debian since
> 2008!
> 
> grace itself has not had upstream changes introduced into Debian since
> the same time.

For some values of 2008 being 2012:

|grace (1:5.1.23-1) unstable; urgency=low
|
|  * New upstream release.  (Closes: #689532)
|
| -- Nicholas Breen   Wed, 31 Oct 2012 17:09:21 -0700
 
> Abandoned software doesn't need to bit rot forever in Debian. If there
> is reason to keep it, there is reason for someone to maintain it.
> Whilst it remains orphaned, it will be considered unmaintained,
> abandoned and suitable for removal.
  
Which package are you talking about here? Grace is maintained by
Nicholas Breen, according to the PTS.

> > I think this is the grace's maintainer's call.  But then maybe I am
> > missing part of the conversatio and your motivation to have grace
> > removed.
>  
> Personally, I don't think it is good to have an embedded copy of a
> removed package inside a package which remains in the archive. What
> would be needed is an assurance from the grace maintainer and those who
> are keen to retain grace in Debian, that the internal t1lib code would
> be maintained inside grace to a better standard than it has so far been
> maintained outside grace.

Again, that is not your call to make, but the maintainer's.  He is
apparently willing to maintain the grace package, with or without an
internal copy of t1lib.

> That may be simpler to do if the grace maintainer & interested parties
> adopt t1lib (upstream and in Debian). At that point, the problem with
> t1lib become manageable again. That would close #637488 and #638760 at
> the same time.

If they want to do this, fine, but it is certainly not necessary for
them.  As t1lib is superseded, I think it makes more sense to keep its
code around just for grace inside the grace source package.  This will
also discourage other developers from using the t1lib library in their
projects.
 
> > > > As grace is almost exclusively used to plot
> > > > locally-supplied numeric data, and is not in any way practical to
> > > > use in a network setting, it has minimal security risk vs. some
> > > > other former users of t1lib like php5.
> > > 
> > > The security issues were only one part of this - t1lib has been
> > > abandoned and superseded. It is unsupportable, as are packages which
> > > rely on it.
> > 
> > It is being supported by grace upstream as part of the embedded
> > library, as written elsewhere on this thread.
> > 
> > For some values of supported, but I don't see the point in removing
> > grace completely.  If you want to get rid of the the t1lib package -
> > fine, but I think using the embedded copy is an acceptable solution
> > for grace.
> 
> T

Processed: notfound 738408 in 1.3.2-1

[Debian Bug Tracking System]

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

> notfound 738408 1.3.2-1
Bug #738408 {Done: Jonathan Wiltshire } [src:blockdiag] 
blockdiag: FTBFS: Tests failed
No longer marked as found in versions blockdiag/1.3.2-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
738408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738408
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#738989: marked as done (postfix: looking for plugins in '/usr/lib/sasl2', failed to open directory, error: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 15:02:18 +0100
with message-id <20140323140218.gj17...@betterave.cristau.org>
and subject line Re: Bug#738989: postfix: looking for plugins in 
'/usr/lib/sasl2', failed to open directory, error: No such file or directory
has caused the Debian Bug report #738989,
regarding postfix: looking for plugins in '/usr/lib/sasl2', failed to open 
directory, error: No such file or directory
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.)


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

Dear Maintainer,

after last update, /var/log/auth.log shows more lines like 

Feb 14 17:06:20 hpdv5 postfix/smtp[23848]: looking for plugins in
'/usr/lib/sasl2', failed to open directory, error: No such file or
directory

and if I search that pid into /var/log/mail.log I find 

Feb 14 17:06:26 hpdv5 postfix/smtp[23848]: 32986B8012:
to=, relay=127.0.0.1[127.0.0.1]:10024,
delay=4.2, delays=0.04/1.3/0.01/2.9, d sn=2.0.0, status=sent (250 2.0.0
from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 6B23BB8102)

The messages are sent regularly into the user (me) spool.

I found an old report (#426338) for the same error so I have looked inside
/usr/lib/sasl2

/etc <-su> # ls -la /var/spool/postfix/usr/lib/sasl2/
totale 0
drwxr-xr-x 2 root root  1 set 14  2008 ./
drwxr-xr-x 4 root root 16 feb  8  2009 ../

It is empty but I don't see permission problem.

Thanks.


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

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

Versions of packages postfix depends on:
ii  adduser3.113+nmu3
ii  cpio   2.11+dfsg-1
ii  debconf [debconf-2.0]  1.5.52
ii  dpkg   1.17.6
ii  libc6  2.17-97
ii  libdb5.3   5.3.28-3
ii  libsasl2-2 2.1.26.dfsg1-8
ii  libsqlite3-0   3.8.3.1-1
ii  libssl1.0.01.0.1f-1
ii  lsb-base   4.1+Debian12
ii  netbase5.2
ii  ssl-cert   1.0.33

Versions of packages postfix recommends:
ii  python  2.7.5-5

Versions of packages postfix suggests:
pn  dovecot-common
ii  heirloom-mailx [mail-reader]  12.5-2
ii  libsasl2-modules  2.1.26.dfsg1-8
ii  mutt [mail-reader]1.5.21-6.4
pn  postfix-cdb   
pn  postfix-doc   
pn  postfix-ldap  
pn  postfix-mysql 
pn  postfix-pcre  
pn  postfix-pgsql 
ii  procmail  3.22-21
ii  resolvconf1.74
pn  sasl2-bin 
pn  ufw   

-- debconf information:
  postfix/tlsmgr_upgrade_warning:
* postfix/main_mailer_type: No configuration
  postfix/protocols: all
  postfix/chattr: false
  postfix/relay_restrictions_warning:
  postfix/mailbox_limit: 0
  postfix/not_configured:
  postfix/retry_upgrade_warning:
* postfix/mailname: hpdv5.stecalle.uff
  postfix/kernel_version_warning:
  postfix/sqlite_warning:
  postfix/root_address:
  postfix/destinations: hpdv5.stecalle.uff, localhost.stecalle.uff, localhost
  postfix/recipient_delim: +
  postfix/mydomain_warning:
  postfix/bad_recipient_delimiter:
  postfix/rfc1035_violation: false
  postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
  postfix/relayhost: smtp.stecalle.uff
  postfix/procmail: true
--- End Message ---
--- Begin Message ---
On Sun, Mar 23, 2014 at 12:15:57 +0100, Stefano Callegari wrote:

> You are right, the log doesn't show these line anymore, so I think it has
> been fixed.
> 
Thanks.  Closing this bug.

Cheers,
Julien


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

Bug#742409: libsereal-encoder-perl: FTBFS on some architectures

[gregor herrmann]

Package: libsereal-encoder-perl
Version: 2.06-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

libsereal-encoder-perl 2.06-1 fail to build on some architectures:

https://buildd.debian.org/status/logs.php?pkg=libsereal-encoder-perl&ver=2.06-1


Cheers,
gregor


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJrBAEBCgBVBQJTLuYmThSAAB0AKGlzc3Vlci1mcHJAZ3BnLmNvbW9kby5w
cml2LmF0RDFFMTMxNkU5M0E3NjBBODEwNEQ4NUZBQkIzQTY4MDE4NjQ5QUEwNgAK
CRC7OmgBhkmqBlXaEACRIahymy8Lq4jj41XbU1KO/SJi1DdSL1gZnrGpuIou8/MT
HCUTMnIx8lgbm+67eUAauJ7gKPX2IUvrRhKfIvyCny8v1zIQxdGexygyU45fMw77
YMtSud/WfhZTb/xt7Ui3Pk4oa77OXpvhwisz8RbhcknXYxIad4nOD+8YEtnpTA6X
BEVn7lwo+ZKz8WsqcroTL7OgOCetkOMzBwSpOIBalc9WsYGDf9Sf1CEDKxye0//W
0Lkm4kuh/vJQ6bnukldShnJO4EaiqyEO5qSws9/rJXHeuY8Xa79l2+k2/fQXUSyZ
pKUgSVuq2pfYAGlXCa1W0Sa4yMMDx/3IOKuTQifXIzEeTXSiQ/uqmKn7ArZgZ0jc
69RfV1rVlW65xiil5r16pbd0Q+0/WCt72RL6kL7jEqshGFEFJysss2rkT/zkyt0U
Sbxzosc4hRlQw7R2ANRDgJXJGR1Mu1Cysmbry2rABwjtfnPnZZOp50qvE7AGV4Jx
b8YEneJFQ1HEmFBkWvrXyV67Izw8dwbd3NgEm6X6gO+9nkVZAWBIH/X7K7emrk2p
MVI+3BpTs1cJTaMziT5UvY72txx5uvx8BcpV0syrB2UzOY0nZI9CEX5bV6V3C83t
riFpJ9twocc8xROsENdPdGV2B49JFzc7beFTFQAKatz6DH/tVBeVSrIha7oONQ==
=aVjj
-END PGP SIGNATURE-


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

Bug#738408: marked as done (blockdiag: FTBFS: Tests failed)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 13:27:15 +
with message-id <20140323132715.ga8...@lupin.home.powdarrmonkey.net>
and subject line Re: Bug#738408: blockdiag: FTBFS: Tests failed
has caused the Debian Bug report #738408,
regarding blockdiag: FTBFS: Tests 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.)


-- 
738408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blockdiag
Version: 1.3.2-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140208 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> set -e; \
>   PYTHONPATH=/«PKGBUILDDIR»/src nosetests -d 
> ...E.E
> ==
> ERROR: test_separate_option_pdf 
> (blockdiag.tests.test_boot_params.TestBootParams)
> --
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/src/blockdiag/tests/test_boot_params.py", line 58, in 
> test_separate_option_pdf
> self.parser.parse(['-Tpdf', '--separate', 'input.diag'])
>   File "/«PKGBUILDDIR»/src/blockdiag/utils/bootstrap.py", line 95, in parse
> self.validate()
>   File "/«PKGBUILDDIR»/src/blockdiag/utils/bootstrap.py", line 151, in 
> validate
> raise RuntimeError(msg)
> RuntimeError: unknown format: PDF
> 
> ==
> ERROR: test_type_option_pdf (blockdiag.tests.test_boot_params.TestBootParams)
> --
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/src/blockdiag/tests/test_boot_params.py", line 43, in 
> test_type_option_pdf
> options = self.parser.parse(['-Tpdf', 'input.diag'])
>   File "/«PKGBUILDDIR»/src/blockdiag/utils/bootstrap.py", line 95, in parse
> self.validate()
>   File "/«PKGBUILDDIR»/src/blockdiag/utils/bootstrap.py", line 151, in 
> validate
> raise RuntimeError(msg)
> RuntimeError: unknown format: PDF
> 
> --
> Ran 330 tests in 6.872s
> 
> FAILED (errors=2)
> make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/02/08/blockdiag_1.3.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Control: notfound -1 1.3.2-1

On Sat, Feb 15, 2014 at 07:50:24PM +0900, Hideki Yamane wrote:
>  I've tested it with cowbuilder/pbuilder on amd64(sid) and kfreebsd-i386(sid)
>  but cannot reproduce it (no failure with test), so tags as unreproducible.

I also cannot reproduce it in a an up-to-date sid chroot, so as this was
probably a transient problem I'm closing the bug.


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



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

Processed: jessie

[Debian Bug Tracking System]

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

> tags 740985 + sid jessie
Bug #740985 {Done: } [libdispatch] FTBFS on 
amd64 mips mipsel: checking for KQUEUE... configure: error: Package 
requirements (libkqueue) were not met
Added tag(s) sid and jessie.
> tags 740620 + sid jessie
Bug #740620 [src:scalapack] scalapack: should not silently change the library 
SONAME when MPI implementation changes
Added tag(s) sid and jessie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
740620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740620
740985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740985
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#717131: update

[Neil Williams]

I have emailed Benoit privately and an MIA check shows that he has not
responded to the first MIA ping in February 2014. He has also made no
uploads to any packages in two years. So in order to fix the
outstanding bugs and because I am using minidlna currently, I decided
to test out the idea of a hijack on the basis of a non-responsive
maintainer and an active upstream.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



signature.asc
Description: PGP signature

Bug#740199: marked as done ([regression] tar mess up \ and \\ files)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 14:18:15 +0100
with message-id <532edf17.40...@thykier.net>
and subject line Re: [regression] tar mess up \ and \\ files
has caused the Debian Bug report #740199,
regarding [regression] tar mess up \ and \\ files
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.)


-- 
740199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tar
Version: 1.27.1-1
Severity: serious

Serious because it is a regression and it break at least lintian...

strange name is a tar regression:

bastien@bastien-debian:/tmp/testcase$ ls
'\   \  \\
bastien@bastien-debian:/tmp/testcase$ tar -cf test.tar * 
bastien@bastien-debian:/tmp/testcase$ tar -tf test.tar
'\\ 
\\
\\
bastien@bastien-debian:/tmp/testcase$ mkdir extract
bastien@bastien-debian:/tmp/testcase$ cd extract/
bastien@bastien-debian:/tmp/testcase/extract$ tar -xf ../test.tar 
bastien@bastien-debian:/tmp/testcase/extract$ ls
'\   \
bastien@bastien-debian:/tmp/testcase/extract$ tar --version
tar (GNU tar) 1.27.1
Copyright © 2013 Free Software Foundation, Inc.
Licence GPLv3+ : GNU GPL version 3 ou ultérieure 

Ceci est un logiciel libre : vous êtes libre de le modifier et de le 
redistribuer.
Il est fourni SANS GARANTIE, dans la mesure de ce que permet la loi.

Écrit par John Gilmore et Jay Fenlason.
--- End Message ---
--- Begin Message ---
Source: tar
Source-Version: 1.27.1-1
Control: found -1 1.27-1
Control: notfound -1 1.27.1-1


Hi,

The bug was forwarded to [1].  The issue seems to have been caused by
tar not "unquoting" files passed via -T in 1.27 and that was fixed
1.27.1.  As dpkg-deb creates the data.tar with -T, this seems like a
reasonable explanation for the change in behaviour that the Lintian
maintainers saw between 1.27 and 1.27.1.  The current behaviour should
be the same as << 1.27, if I understood upstream correctly.

Thus, I am marking this bug as found in 1.27-1 and closing it now as
fixed in 1.27.1-1.

~Niels

[1] http://lists.gnu.org/archive/html/bug-tar/2014-03/msg1.html--- End Message ---

Bug#738395: marked as done (python-repoze.who: FTBFS: cp: not writing through dangling symlink [...]/jquery.js)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 13:18:26 +
with message-id 
and subject line Bug#738395: fixed in python-repoze.who 1.0.18-3
has caused the Debian Bug report #738395,
regarding python-repoze.who: FTBFS: cp: not writing through dangling symlink 
[...]/jquery.js
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.)


-- 
738395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-repoze.who
Version: 1.0.18-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140208 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»/docs'
> mkdir -p .build/html .build/doctrees
> sphinx-build -b html -d .build/doctrees   . .build/html
> Running Sphinx v1.2.1
> running test
> running egg_info
> writing requirements to repoze.who.egg-info/requires.txt
> writing repoze.who.egg-info/PKG-INFO
> writing namespace_packages to repoze.who.egg-info/namespace_packages.txt
> writing top-level names to repoze.who.egg-info/top_level.txt
> writing dependency_links to repoze.who.egg-info/dependency_links.txt
> writing entry points to repoze.who.egg-info/entry_points.txt
> reading manifest file 'repoze.who.egg-info/SOURCES.txt'
> writing manifest file 'repoze.who.egg-info/SOURCES.txt'
> running build_ext
> .
> --
> Ran 213 tests in 0.062s
> 
> OK
> loading pickled environment... done
> building [html]: targets for 0 source files that are out of date
> updating environment: 0 added, 0 changed, 0 removed
> looking for now-outdated files... none found
> no targets are out of date.
> 
> Build finished. The HTML pages are in .build/html.
> make[1]: Leaving directory `/«PKGBUILDDIR»/docs'
> dh_link /usr/share/javascript/jquery/jquery.js \
>   /usr/share/doc/python-repoze.who/html/_static/jquery.js
> Adding cdbs dependencies to debian/python-repoze.who.substvars
> dh_installdirs -ppython-repoze.who 
> cd . && \
>   python setup.py install \
>   --root="/«PKGBUILDDIR»/debian/python-repoze.who/" \
>   --install-purelib=/usr/lib/python2.7/site-packages/ \
>   --prefix=/usr --no-compile -O0 
> --single-version-externally-managed 
> running install
> running build
> running build_py
> running egg_info
> writing requirements to repoze.who.egg-info/requires.txt
> writing repoze.who.egg-info/PKG-INFO
> writing namespace_packages to repoze.who.egg-info/namespace_packages.txt
> writing top-level names to repoze.who.egg-info/top_level.txt
> writing dependency_links to repoze.who.egg-info/dependency_links.txt
> writing entry points to repoze.who.egg-info/entry_points.txt
> reading manifest file 'repoze.who.egg-info/SOURCES.txt'
> writing manifest file 'repoze.who.egg-info/SOURCES.txt'
> running install_lib
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/__init__.py
>  (namespace package)
> copying repoze/who/interfaces.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/__init__.py
>  (namespace package)
> copying repoze/who/middleware.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> copying repoze/who/config.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> copying repoze/who/classifiers.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> copying repoze/who/restrict.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> copying repoze/who/utils.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/plugins/__init__.py
>  (namespace package)
> copying repoze/who/plugins/sql.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/plugins
> copying repoze/who/plugins/auth_tkt.py -> 
> /«PKGBUILDDIR»/debian/

Bug#638760: Removal of grace, pygrace and expeyes

[Neil Williams]

On Sun, 23 Mar 2014 13:08:14 +0100
Michael Banck  wrote:

> On Sun, Mar 23, 2014 at 10:03:53AM +, Neil Williams wrote:
> > On Sat, 22 Mar 2014 20:38:49 -0700
> > Nicholas Breen  wrote:
> > 
> > > On Sat, Mar 22, 2014 at 04:10:39PM +, Neil Williams wrote:
> > > > I'm seeking the removal of pygrace and expeyes so that grace
> > > > can be removed. CC'ing the relevant maintainers (and filing
> > > > important bugs for each package). I expect the removal to start
> > > > in two weeks unless I hear back about a viable solution.
> > > 
> > > If just getting standalone t1lib out of the archive is the goal, I
> > > don't mind incorporating all of the existing t1lib patches into
> > > the embedded copy. 
> > 
> > No. How does that solve the problem of t1lib being abandoned
> > upstream and already superseded by freetype?
> 
> Why is it a problem in the first place? Software is being rewritten
> and superseded constantly, this doesn't mean other software using
> those old libraries are immediately to be sent to the bin.

It's not immediate. t1lib has had no upstream changes in Debian since
2008!

grace itself has not had upstream changes introduced into Debian since
the same time.

Abandoned software doesn't need to bit rot forever in Debian. If there
is reason to keep it, there is reason for someone to maintain it.
Whilst it remains orphaned, it will be considered unmaintained,
abandoned and suitable for removal.
 
> I think this is the grace's maintainer's call.  But then maybe I am
> missing part of the conversatio and your motivation to have grace
> removed.
 
Personally, I don't think it is good to have an embedded copy of a
removed package inside a package which remains in the archive. What
would be needed is an assurance from the grace maintainer and those who
are keen to retain grace in Debian, that the internal t1lib code would
be maintained inside grace to a better standard than it has so far been
maintained outside grace.

That may be simpler to do if the grace maintainer & interested parties
adopt t1lib (upstream and in Debian). At that point, the problem with
t1lib become manageable again. That would close #637488 and #638760 at
the same time.

> > > As grace is almost exclusively used to plot
> > > locally-supplied numeric data, and is not in any way practical to
> > > use in a network setting, it has minimal security risk vs. some
> > > other former users of t1lib like php5.
> > 
> > The security issues were only one part of this - t1lib has been
> > abandoned and superseded. It is unsupportable, as are packages which
> > rely on it.
> 
> It is being supported by grace upstream as part of the embedded
> library, as written elsewhere on this thread.
> 
> For some values of supported, but I don't see the point in removing
> grace completely.  If you want to get rid of the the t1lib package -
> fine, but I think using the embedded copy is an acceptable solution
> for grace.

This would need to be declared clearly in the grace package
description and maintained as part of grace. It's not the ideal
solution.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



signature.asc
Description: PGP signature

Bug#741749: marked as done (ruby-literati: FTBFS: ERROR: Test "ruby1.9.1" failed: NoMethodError: undefined method `any_instance' for Literati::MarkdownRenderer:Class)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 13:04:07 +
with message-id 
and subject line Bug#741749: fixed in ruby-literati 0.0.4~git.20130318.3b3ea30-2
has caused the Debian Bug report #741749,
regarding ruby-literati: FTBFS: ERROR: Test "ruby1.9.1" failed: NoMethodError: 
undefined method `any_instance' for Literati::MarkdownRenderer:Class
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.)


-- 
741749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-literati
Version: 0.0.4~git.20130318.3b3ea30-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140315 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> NoMethodError: undefined method `any_instance' for 
> Literati::MarkdownRenderer:Class
> /«PKGBUILDDIR»/test/test_literati.rb:77:in `block (2 levels) in 
> '
> 
> 9 tests, 9 assertions, 0 failures, 2 errors, 0 skips
> rake aborted!
> Command failed with status (2): [ruby -I"lib:lib:test" 
> -I"/usr/lib/ruby/vendor_ruby" 
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/**/test_*.rb" ]
> 
> Tasks: TOP => default => test
> (See full trace by running task with --trace)
> ERROR: Test "ruby1.9.1" failed: 

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/03/15/ruby-literati_0.0.4~git.20130318.3b3ea30-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-literati
Source-Version: 0.0.4~git.20130318.3b3ea30-2

We believe that the bug you reported is fixed in the latest version of
ruby-literati, 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 741...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-literati 
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: Sun, 23 Mar 2014 13:39:36 +0100
Source: ruby-literati
Binary: ruby-literati ruby-literati-doc
Architecture: source all
Version: 0.0.4~git.20130318.3b3ea30-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description: 
 ruby-literati - render literate Haskell with Ruby
 ruby-literati-doc - render literate Haskell with Ruby (documentation)
Closes: 741749
Changes: 
 ruby-literati (0.0.4~git.20130318.3b3ea30-2) unstable; urgency=medium
 .
   * Team upload.
   * Add 0002_require_mocha_setup.patch to require mocha/setup instead of mocha
 in tests, as it is the way to ensure that mocha is correctly initialized
 with recent versions of ruby-mocha.
 Fix FTBFS with Mocha 1.0 (Closes: #741749)
   * Add version requirement for ruby-mocha.
   * Bump Standards-Version to 3.9.5 (no changes needed).
Checksums-Sha1: 
 33114c8ce67125ffdb9933612b092b50f6a74188 2269 
ruby-literati_0.0.4~git.20130318.3b3ea30-2.dsc
 682a986ed9362b9b29cc4176017b69e5cfd631f5 3364 
ruby-literati_0.0.4~git.20130318.3b3ea30-2.debian.tar.xz
 b2272edf8252063bfb1332e0528472ede86d2a82 5638 
ruby-literati_0.0.4~git.20130318.3b3ea30-2_all.deb
 4bd20ea11e570b30cb4bb301b604e1f69f96d3d7 30234 
ruby-literati-doc_0.0.4~git.20130318.3b3ea30-2_all.deb
Checksums-Sha256: 
 dcd58ba9e5f3b1361f33edd32d94f86cb8815224fb91db065a9dda8849752488 2269 
ruby-literati_0.0.4~git.20130318.3b3ea30-2.dsc
 e53a5be758349c5ff7c0debd22a10f77aa13f8c3e651035fb94afbc2f4b9efd8 3364 
ruby-literati_0.0.4~git.20130318.3b3ea30-2.debian.tar.xz
 dcedaf945bbc427642680f7767bfbb667e5faa845772ea155cf405f7f629961c 5638 
ruby-literati_0.0.4~git.20130318.3b3ea30-2_all.deb
 dd8f0962c07f8e64e63875c035de06c76a7046c3a9bdf3395f6c281ca523ca4b 30234 
ruby-literati-doc_0.0.4~git.20130318.3b3ea30-2_all.deb
Files: 
 d6a09f

Processed: adjust versions for 740730

[Debian Bug Tracking System]

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

> # remove fixed version as wel, as the issue is not related to any version of
> # fcitx-mozc
> notfixed 740730 1.13.1651.102-2
Bug #740730 {Done: Jens John } [fcitx-mozc] fcitx-mozc: input 
method doesn't load with GTK2 frontend
No longer marked as fixed in versions 1.13.1651.102-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
740730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740730
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#738775: insserv: Insserv 1.16 tries to connect to systemd even though system is running on sysv-init

[Jan Binder]

Am Dienstag, 18. Februar 2014, 00:20:40 schrieb Petter Reinholdtsen:
> [Jan Binder]
> 
> > Ok, here comes the make-testsuite output.
> > If debsums can be trusted, none of my initscripts were modified from
> > the packaged versions.
> 
> Thank you.  Still not able to reproduce it with my locally built
> insserv.  No idea why.  Will keep trying a bit more, but welcome
> ideas. :)

Yesterday I managed to get rid of the install-blocking behaviour by forcedly 
purging and reinstalling the  rpcbind package. I'm not sure why this resolves 
the problem with rpcbind being marked as missing in several runlevels.

Bug #741705 on the other hand is on a different system with systemd as pid1 
and when I tried the above method, systemd got itself stuck in a dependency 
loop and I could not even shut down the system any more.


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

Bug#742406: uhd: FTBFS on kfreebsd and powerpc

[Ivo De Decker]

package: uhd
version: 3.7.0-1
severity: serious

Hi,

It seems uhd 3.7.0-1 FTBFS on kfreebsd and powerpc, but built successfully in
the past.

Cheers,

Ivo


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

Bug#717131: Possible hijack

[Neil Williams]

The new upstream release builds cleanly and includes the majority of
changes currently provided as patches in Debian as well as other
updates.

I've prepared a local build of 1.1.2 which only needs patches to the
minidlna.conf file for better clarity of the comments and I propose to
take the manpages from upstream (minidlna.conf.5 needs a trivial patch
for what-is support).

The possible changelog at this stage would look like:

Source: minidlna
Version: 1.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Neil Williams 
Date: Sun, 23 Mar 2014 11:53:42 +
Closes: 697613 711234 717131 724207 732087
Changes: 
 minidlna (1.1.2-1) unstable; urgency=medium
 .
   * Hijack to move to new upstream release
   * Move to upstream 1.1.2 which is no longer prone
 to CVE-2013-2745 CVE-2013-2738 and CVE-2013-2739,
 builds cleanly and has migrated to libavformat54
 and libavutil52. (Closes: #717131) (Closes: #711234)
 (Closes: #724207) (Closes: #732087)
   * Add logrotate config - thanks to Guilhem Bonnefille.
 (Closes: #697613)

I need to do more testing of the built package and allow time for
Benoit to respond to this and my earlier email about minidlna. I do not
propose to retain the existing git packaging - I'll decide where to put
the new packaging at a later date.

If others are interested in testing minidlna, I can make my changes
available.

Note that the binary has changed from /usr/bin/minidlna
to /usr/sbin/minidlnad - I'll add a NEWS item about this if the hijack
is to proceed and allow minidlna into Jessie.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



signature.asc
Description: PGP signature

Processed: adjust versions for 740730

[Debian Bug Tracking System]

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

> # found and fixed version cannot be the same
> notfound 740730 1.13.1651.102-2
Bug #740730 {Done: Jens John } [fcitx-mozc] fcitx-mozc: input 
method doesn't load with GTK2 frontend
No longer marked as found in versions mozc/1.13.1651.102-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
740730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740730
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#742405: zookeeper: ftbfs on kfreebsd

[Ivo De Decker]

package: zookeeper
version: 3.4.5+dfsg-1
severity: serious

Hi,

It seems zookeeper 3.4.5+dfsg-2 FTBFS on kfreebsd-*:
https://buildd.debian.org/status/package.php?p=zookeeper

I tried rebuilding version 3.4.5+dfsg-1, which built successfully before, but
that now fails the same way as well.

Cheers,

Ivo


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

Processed: python-fixtures: diff for NMU version 0.3.14-1.1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #739139 [src:python-fixtures] python-fixtures: FTBFS: python3.4: not found
Severity set to 'normal' from 'serious'
> tag -1 patch pending
Bug #739139 [src:python-fixtures] python-fixtures: FTBFS: python3.4: not found
Added tag(s) pending and patch.

-- 
739139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739139
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#739139: python-fixtures: diff for NMU version 0.3.14-1.1

[Jonathan Wiltshire]

Control: severity -1 normal
Control: tag -1 patch pending

Dear maintainer,

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

It also properly enables the tests for all versions of python, and does
not ignore the result (it was failing unnoticed before now).

Regards.

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

diff -Nru python-fixtures-0.3.14/debian/changelog python-fixtures-0.3.14/debian/changelog
--- python-fixtures-0.3.14/debian/changelog	2013-09-07 03:57:14.0 +0100
+++ python-fixtures-0.3.14/debian/changelog	2014-03-23 11:37:00.0 +
@@ -1,3 +1,13 @@
+python-fixtures (0.3.14-1.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Depend on python-all and python3-all so that all supported
+versions are available (Closes: #739139, #735577)
+  * Properly enable tests for all supported versions, and stop
+ignoring the results
+
+ -- Jonathan Wiltshire   Sun, 23 Mar 2014 11:21:14 +
+
 python-fixtures (0.3.14-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru python-fixtures-0.3.14/debian/control python-fixtures-0.3.14/debian/control
--- python-fixtures-0.3.14/debian/control	2013-09-07 03:57:14.0 +0100
+++ python-fixtures-0.3.14/debian/control	2014-03-23 11:17:00.0 +
@@ -4,9 +4,9 @@
 Maintainer: Robert Collins 
 Uploaders: Thomas Goirand 
 Build-Depends: debhelper (>= 9),
-   python (>= 2.6.6-3~),
+   python-all (>= 2.6.6-3~),
python-setuptools,
-   python3,
+   python3-all,
python3-setuptools
 Build-Depends-Indep: python-docutils,
  python-nose,
diff -Nru python-fixtures-0.3.14/debian/rules python-fixtures-0.3.14/debian/rules
--- python-fixtures-0.3.14/debian/rules	2013-09-07 03:57:14.0 +0100
+++ python-fixtures-0.3.14/debian/rules	2014-03-23 11:19:12.0 +
@@ -22,5 +22,7 @@
 
 ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS)))
 override_dh_auto_test:
-	nosetests || true
+	set -e && for pyvers in $(PYTHONS) $(PYTHON3S); do \
+		PYTHON=python$$pyvers make check; \
+	done
 endif


signature.asc
Description: Digital signature

Bug#638760: Removal of grace, pygrace and expeyes

[Michael Banck]

On Sun, Mar 23, 2014 at 10:03:53AM +, Neil Williams wrote:
> On Sat, 22 Mar 2014 20:38:49 -0700
> Nicholas Breen  wrote:
> 
> > On Sat, Mar 22, 2014 at 04:10:39PM +, Neil Williams wrote:
> > > I'm seeking the removal of pygrace and expeyes so that grace can be
> > > removed. CC'ing the relevant maintainers (and filing important bugs
> > > for each package). I expect the removal to start in two weeks
> > > unless I hear back about a viable solution.
> > 
> > If just getting standalone t1lib out of the archive is the goal, I
> > don't mind incorporating all of the existing t1lib patches into the
> > embedded copy. 
> 
> No. How does that solve the problem of t1lib being abandoned upstream
> and already superseded by freetype?

Why is it a problem in the first place? Software is being rewritten and
superseded constantly, this doesn't mean other software using those old
libraries are immediately to be sent to the bin.

I think this is the grace's maintainer's call.  But then maybe I am
missing part of the conversatio and your motivation to have grace
removed.

> > As grace is almost exclusively used to plot
> > locally-supplied numeric data, and is not in any way practical to use
> > in a network setting, it has minimal security risk vs. some other
> > former users of t1lib like php5.
> 
> The security issues were only one part of this - t1lib has been
> abandoned and superseded. It is unsupportable, as are packages which
> rely on it.

It is being supported by grace upstream as part of the embedded library,
as written elsewhere on this thread.

For some values of supported, but I don't see the point in removing
grace completely.  If you want to get rid of the the t1lib package -
fine, but I think using the embedded copy is an acceptable solution for
grace.


Michael


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

Bug#738989: postfix: looking for plugins in '/usr/lib/sasl2', failed to open directory, error: No such file or directory

[Stefano Callegari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Il sab, mar 22, 2014 at 12:49:07 +0100, Julien Cristau scrisse:
> On Fri, Feb 14, 2014 at 17:29:35 +0100, Stefano wrote:
> 
> > Package: postfix
> > Version: 2.11.0-1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > after last update, /var/log/auth.log shows more lines like 
> > 
> > Feb 14 17:06:20 hpdv5 postfix/smtp[23848]: looking for plugins in
> > '/usr/lib/sasl2', failed to open directory, error: No such file or
> > directory
> > 
> I think this is a dupe of #739601, which was fixed in cyrus-sasl2
> 2.1.26.dfsg1-9
> 
> Your report said:
> > ii  libsasl2-2 2.1.26.dfsg1-8
> 
> Is this fixed with the newer libsasl2-2?

You are right, the log doesn't show these line anymore, so I think it has
been fixed.

> 
> Cheers,
> Julien

Thanks
- -- 
Stefano Callegari 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlMuwm0ACgkQHecMbhqYKHG/hwCffEV5ye9t43I+MtEimvQwCaRe
8CEAn2XkLIsQ7Ol9TqwGAzgHVfB4NKFb
=qThD
-END PGP SIGNATURE-


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

Bug#717131: watch file indicates wrong upstream version

[Neil Williams]

Just a note on investigations so far, the debian/watch file in 1.0.24
incorrectly points to 1.0.25 as the new upstream release but
sourceforge as 1.1.2.

https://launchpad.net/bugs/cve/CVE-2013-2745

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



signature.asc
Description: PGP signature

Bug#638760: Removal of grace, pygrace and expeyes

[Evgeny Stambulchik]

Hello,

I'm the [passive] upstream maintainer. Just to make things clear:

1. grace is perfectly happy using its own copy of t1lib. So you can 
safely remove the t1lib debian package.


2. Yes, perhaps only 0.34% of all users use it. But same can be said 
about 90% of the entire debian archive (for each package separately, of 
course).


3. Yes, it is potentially buggy and insecure. But since in 99.9% you use 
it within the projects you work yourself on, nothing wrong can happen. 
In the worst case you loose some time. (And in my experience, grace 
crashes MUCH less frequently than some high-profile softwares which are 
really exposed to the Internet.)


4. I have no time and intention right now to switch to freetype. For the 
scope it is currently used in grace, t1lib is adequate. When I come 
across a bug, I fix it - that's how the bundled t1lib copy got emerged 
in the first place.


Best,

Evgeny

On 23/03/14 12:01, Neil Williams wrote:

On Sun, 23 Mar 2014 11:01:39 +1100
Drew Parsons  wrote:


Grace is one of the most useful packages in the entire archive.


... for 0.34% of users of the archive, maybe. To me, it is simply an RC
buggy package which has had no new development upstream since 2012 and
which depends on an obsolete, abandoned library. Unless it can be
ported, it will need to be removed alongside t1lib.

Those who care about grace need to scratch their own itch and fix it.


I am not aware of anything other package that provides the same degree
of functionality.

Removing it is not a good idea.


Removing it is necessary, as explained. t1lib has been superseded and
packages which used to use it need to migrate. The other packages have
already done so, those which fail to do so cannot be supported when the
underlying dependency has been abandoned.





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

Bug#724469: FTBFS on all big-endian architectures

[Hiroyuki Yamamoto]

Lennart Sorensen wrote:
> On Sat, Mar 22, 2014 at 11:53:23AM +0100, intrigeri wrote:
>> intrigeri wrote (20 Jan 2014 17:58:03 GMT) :
>>>> https://rt.cpan.org/Ticket/Display.html?id=89552
>>> Sure. Debian porters, I'll let you subscribe to the RT ticket, and
>>> hopefully take care of this porting problem.
>>
>> I'd like to see this RC bug fixed eventually, and I still hope this
>> can be done without dropping support for too many architectures in
>> this package.
>>
>> AFAICT the latest patch proposed by upstream on February 9 [1] has
>> been tested on mips only. My understanding is that upstream has been
>> waiting for more test results since then. Can anyone please test this
>> on other big-endian architectures?
>>
>> It would good if we could at least fix this for the 32-bit ones.
>>
>> [1] 
>> https://rt.cpan.org/Ticket/Attachment/1324475/702426/0001-Fix-return-value-handling-on-big-endian-architecture.patch
> 
> Patch works for powerpc and someone else already reported it working
> for powerpcspe.
> 
> As expected it does NOT work on ppc64.  I am not currently awake enough
> to try and figure out why.
> 
> Since mips was already tested with the patch originally, that probably
> just leaves sparc and s390 to test (I can't tell if s390 tested it or not,
> only that s390x does not work yet due to being 64bit).


On ppc64, failing to build the source package patched was confirmed.

--

make[1]: Leaving directory `/«PKGBUILDDIR»'
   dh_auto_test -a
make[1]: Entering directory `/«PKGBUILDDIR»'
LD_LIBRARY_PATH=:build PERL_DL_NONLAZY=1 /usr/bin/perl 
"-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/00-basic-types.t  ok
t/arg-checks.t  ok

#   Failed test at t/arrays.t line 14.
#  got: '0'
# expected: '6'
t/arrays.t  
Failed 28/29 subtests 
t/boxed.t . ok
t/cairo-integration.t . ok

#   Failed test at t/callbacks.t line 14.
#  got: '-40706304'
# expected: '23'

#   Failed test at t/callbacks.t line 16.
#  got: '7395392'
# expected: '23'

#   Failed test at t/callbacks.t line 17.
#  got: '7395392'
# expected: '23'

#   Failed test at t/callbacks.t line 18.
#  got: '-33534596'
# expected: '46'

#   Failed test at t/callbacks.t line 22.
#  got: '7171660'
# expected: '23'

#   Failed test at t/callbacks.t line 26.
#  got: '-40706256'
# expected: '23'
# Looks like you failed 6 tests of 25.
t/callbacks.t . 
Dubious, test returned 6 (wstat 1536, 0x600)
Failed 6/25 subtests 
t/closures.t .. ok
t/constants.t . ok
t/enums.t . 
Failed 3/4 subtests 
t/hashes.t  ok
t/interface-implementation.t .. ok
t/objects.t ... ok
t/structs.t ... ok
t/values.t  ok
t/vfunc-chaining.t  ok
t/vfunc-ref-counting.t  ok
Failed 3/16 test programs. 7/299 subtests failed.

Test Summary Report
---
t/arrays.t  (Wstat: 9 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero wait status: 9
  Parse errors: Bad plan.  You planned 29 tests but ran 2.
t/callbacks.t   (Wstat: 1536 Tests: 25 Failed: 6)
  Failed tests:  3, 6, 9, 14, 19, 25
  Non-zero exit status: 6
t/enums.t   (Wstat: 11 Tests: 1 Failed: 0)
  Non-zero wait status: 11
  Parse errors: Bad plan.  You planned 4 tests but ran 1.
Files=16, Tests=299, 835 wallclock secs ( 0.25 usr  0.09 sys + 74.57 cusr 19.01 
csys = 93.92 CPU)
Result: FAIL
make[1]: *** [test_dynamic] Error 255
make[1]: Leaving directory `/«PKGBUILDDIR»'
dh_auto_test: make -j1 test returned exit code 2
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Build finished at 20140323-1923

Finished


-- 
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA  91AC 3A10 59C6 5203 04DC


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

Bug#724469: FTBFS on all big-endian architectures

[intrigeri]

Hi,

Bastian Blank wrote (23 Mar 2014 10:04:34 GMT) :
> Care to share the results of your own findings?

Unfortunately, I don't have the skills needed to work on this problem
myself, so there is no such thing to share. The best I can do is to go
on forwarding patches and test results between upstream and
Debian porters.

Cheers,
-- 
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


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

Processed: tagging 726000

[Debian Bug Tracking System]

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

> # as per https://lists.debian.org/debian-release/2014/03/msg00409.html
> tags 726000 + squeeze-ignore wheezy-ignore
Bug #726000 {Done: Simon McVittie } [dbus] dbus: 
debian/copyright does not mention the copyright holders
Added tag(s) squeeze-ignore and wheezy-ignore.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
726000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726000
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#724469: FTBFS on all big-endian architectures

[Bastian Blank]

On Sun, Mar 23, 2014 at 10:33:32AM +0100, intrigeri wrote:
> Any s390x porter planning to work on this? (And if so, ETA?)

Care to share the results of your own findings?  You know where the
problem is located and you obviously know zelenka.d.o.

Bastian

-- 
Power is danger.
-- The Centurion, "Balance of Terror", stardate 1709.2


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

Bug#638760: Removal of grace, pygrace and expeyes

[Neil Williams]

On Sat, 22 Mar 2014 20:38:49 -0700
Nicholas Breen  wrote:

> On Sat, Mar 22, 2014 at 04:10:39PM +, Neil Williams wrote:
> > I'm seeking the removal of pygrace and expeyes so that grace can be
> > removed. CC'ing the relevant maintainers (and filing important bugs
> > for each package). I expect the removal to start in two weeks
> > unless I hear back about a viable solution.
> 
> If just getting standalone t1lib out of the archive is the goal, I
> don't mind incorporating all of the existing t1lib patches into the
> embedded copy. 

No. How does that solve the problem of t1lib being abandoned upstream
and already superseded by freetype?

> As grace is almost exclusively used to plot
> locally-supplied numeric data, and is not in any way practical to use
> in a network setting, it has minimal security risk vs. some other
> former users of t1lib like php5.

The security issues were only one part of this - t1lib has been
abandoned and superseded. It is unsupportable, as are packages which
rely on it.
 
> If getting t1lib in all its forms out of the archive is the goal,
> then yes, grace would have to be removed.  Rewriting it is not
> practical and there doesn't seem to be anyone with the time + desire
> + skillset to adopt t1lib. However, there's also no real replacement
> for grace itself available.

OK, so that is confirmation that grace will have to be removed once
t1lib itself is removed and that reverse dependencies of grace like
expeyes need to migrate away from grace.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



signature.asc
Description: PGP signature

Bug#638760: Removal of grace, pygrace and expeyes

[Neil Williams]

On Sun, 23 Mar 2014 11:01:39 +1100
Drew Parsons  wrote:

> Grace is one of the most useful packages in the entire archive.  

... for 0.34% of users of the archive, maybe. To me, it is simply an RC
buggy package which has had no new development upstream since 2012 and
which depends on an obsolete, abandoned library. Unless it can be
ported, it will need to be removed alongside t1lib.

Those who care about grace need to scratch their own itch and fix it.

> I am not aware of anything other package that provides the same degree
> of functionality.
> 
> Removing it is not a good idea.

Removing it is necessary, as explained. t1lib has been superseded and
packages which used to use it need to migrate. The other packages have
already done so, those which fail to do so cannot be supported when the
underlying dependency has been abandoned.


-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



signature.asc
Description: PGP signature

Bug#724469: FTBFS on all big-endian architectures

[intrigeri]

Hi,

Lennart Sorensen wrote (22 Mar 2014 12:31:00 GMT) :
> Patch works for powerpc and someone else already reported it working
> for powerpcspe.

Adam Conrad wrote (22 Mar 2014 16:20:23 GMT) :
> Works fine for me on powerpc,

Thanks a lot for testing!

I've uploaded libglib-object-introspection-perl 0.020-2 with this
patch applied. This should at least fix the problem for 32-bit
big-endian architectures.

Any s390x porter planning to work on this? (And if so, ETA?)

I'd rather not drop s390x from the list of architectures this package
is built for, but this RC bug has now been around for 6 months, and at
some point I'll want to get rid of it.

Cheers,
-- 
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


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

Bug#738961: marked as done (synaptic: Application is closing at the moment that any key is pressed)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 10:14:08 +0100
with message-id <20140323091408.GK5794@bod>
and subject line Re: Bug#738961: synaptic: Application is closing at the moment 
that any key is pressed
has caused the Debian Bug report #738961,
regarding synaptic: Application is closing at the moment that any key is pressed
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.)


-- 
738961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synaptic
Version: 0.75.13
Severity: grave
Tags: d-i
Justification: causes non-serious data loss

Dear Maintainer,

   * What led up to the situation?
I always develop in Debian, so I got a New PC, then I installed the latest
version and when I use the synaptec for install some packages, I realized that
every time pressed I key it was automatically closing the app.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I Open the application, Accept the  Quick Introduction dialog, I put the cursor
in the Quick filter and write the app name. At the first key that I press it
get close. I tried several different keys(a, b, z, t..). However if I select
the package with the mouse it install normally.


   * What was the outcome of this action?

Application is close

   * What outcome did you expect instead?

A list filter by the written name

cordialement,



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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme  0.12-1
ii  libapt-inst1.5  0.9.7.9+deb7u1
ii  libapt-pkg4.12  0.9.7.9+deb7u1
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-38+deb7u1
ii  libcairo2   1.12.2-3
ii  libept1.4.121.0.9
ii  libfontconfig1  2.9.0-7.1
ii  libfreetype62.4.9-1.1
ii  libgcc1 1:4.7.2-5
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.33.12+really2.32.4-5
ii  libgtk2.0-0 2.24.10-2
ii  libpango1.0-0   1.30.0-1
ii  libstdc++6  4.7.2-5
ii  libvte9 1:0.28.2-5
ii  libx11-62:1.5.0-1+deb7u1
ii  libxapian22 1.2.12-2
ii  zlib1g  1:1.2.7.dfsg-13

Versions of packages synaptic recommends:
ii  gksu 2.0.2-6
ii  libgtk2-perl 2:1.244-1
ii  policykit-1  0.105-3
ii  rarian-compat0.8.1-5
ii  software-properties-gtk  0.82.7.1debian1

Versions of packages synaptic suggests:
ii  apt-xapian-index  0.45
pn  deborphan 
pn  dwww  
ii  menu  2.1.46

-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Feb 25, 2014 at 03:58:53PM +0100, Shopline wrote:
> Dear Vogt,
Hi Shopline,
 
> I run the debugging command and now is perfectly working! I couldn't make
> it crash. I'm so sorry, how ever is working fine. Also I have make a lot of
> updates, upgrades, so I'm not sure what happened. Let me know If can do
> something else for you!

Its good that its fixed now, I will close the bugreport now, please
contact me again if the error happens again.

Cheers,
 Michael
 
> best regards
> 
> 
> On 20 February 2014 08:16, Michael Vogt  wrote:
> 
> > On Fri, Feb 14, 2014 at 10:51:58AM +0100, AndresBurbano wrote:
> > > Package: synaptic
> > > Version: 0.75.13
> > > Severity: grave
> > > Tags: d-i
> > > Justification: causes non-serious data loss
> >
> > Thanks for your bugreport.
> >
> > > Dear Maintainer,
> > >
> > >* What led up to the situation?
> > > I always develop in Debian, so I got a New PC, then I installed the
> > latest
> > > version and when I use the synaptec for install some packages, I
> > realized that
> > > every time pressed I key it was automatically closing the app.
> > >* What exactly did you do (or not do) that was effective (or
> > >  ineffective)?
> > > I Open the application, Accept the  Quick Introduction dialog, I put the
> > cursor
> > > in the Quick filter and write the app name. At the first key that I
> > press it
> > > get close. I tried several different keys(a, b, z, t..). However if I
> > select
> > > the package with the mouse it install normally.
> > [..]
> >
> > Would it be possible to get a gdb backtrace of the situation? For this
> > you will need to open a terminal windows (like gnome-terminal) and
> > run:
> > $ sudo gdb synaptic
> > [ent

Bug#742392: hurd: Hang during apt-get upgrade from last image release

[Petter Reinholdtsen]

I forgot to mention that I am using Wheezy on the host, so the
virt-manager/kvm/qemu versions are from Wheezy.

-- 
Happy hacking
Petter Reinholdtsen


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

Bug#742392: hurd: Hang during apt-get upgrade from last image release

[Petter Reinholdtsen]

Package: hurd
Version: 1:0.5.git20140320-1
Severity: grave

I am unable to upgrade my virtual test hurd machine because it hang
completely during apt-get upgrade.  I have to "cut the power" on the
machine and reboot it to try to get going.  After the boot, the machine
hang again during boot.  As the file system is messed up, I run fsck
outside the virtual machine like this to fix it:

  kpartx -sa debian-hurd-20140211.img
  fsck -f -y /dev/mapper/loop0p1
  kpartx -d debian-hurd-20140211.img

To reproduce this, I start by downloading the
debian-hurd-20130504.img.tar.gz file, unpack the image and boot it using
virt-manager.  In the booted image, I run 'dhclient /dev/eth0' to get a
IP address, 'apt-get update' to fetch the package lists, install
etckeeper to track changes in /etc, edit /etc/apt/sources.list to drop
the CD source, and next try 'apt-get upgrade'.  After a while the
upgrade hang and the machine uses lots of CPU.

To try to figure out exactly what went wrong, I tried instead of
'apt-get upgrade' to use apt-get --download-only upgrade' and then used
dpkg -i on individual debs to see if I could find the trigger.
Upgrading the hurd package caused the hang after the unpack message is
printed.  Run these commands on a fresh image to reproduce it:

  dhclient /dev/eth0
  apt-get update
  apt-get install -y etckeeper
  vi /etc/apt/get/sources.list
  dpkg -i /var/cache/apt/packages/hurd_*.deb

As far as I know, etckeeper is not vital to reproduce it, but mentioning
it here in the hope that you consider installing it by default. :)

I'm setting severity to grave, as this make the package useless and can
cause data loss when I have to power off the machine and leave the file
system in an inconsistent state.

-- 
Happy hacking
Petter Reinholdtsen


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

Bug#638760: Removal of grace, pygrace and expeyes

[Sylvestre Ledru]

On 23/03/2014 01:50, Drew Parsons wrote:
> On Sat, 2014-03-22 at 20:07 -0400, Michael Gilbert wrote:
>> On Sat, Mar 22, 2014 at 8:01 PM, Drew Parsons wrote:
>>> Grace is one of the most useful packages in the entire archive.
>>>
>>> I am not aware of anything other package that provides the same degree
>>> of functionality.
>>>
>>> Removing it is not a good idea.
>> That can be fixed by anyone willing to spend the time to update it to
>> use freetype.
>>
>> Removing the package will likely provide an incentive for someone
>> sufficiently skilled and interested to do that, and it will eventually
>> be back.
>
> At the core of it, lib/canvas/t1fonts.c would need to be replaced, and
> Canvas in include/grace/canvasP.h and various client code points would
> need to be updated to match.
>
> Sounds like a worthy candidate for the Google Summer of Code.  
>
Too late for the GSoC (deadline for students was last Friday) and I
don't think we would have
accepted this as a project.

Sylvestre


-- 
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:

> severity 742359 grave
Bug #742359 [vtk] vtk: tcl libraries underlinked
Severity set to 'grave' from 'important'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
742359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742359
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#741800: marked as done (ruby-i18n: FTBFS: ERROR: Test "ruby1.9.1" failed: NoMethodError: undefined method `expects' for I18n:Module)

[Debian Bug Tracking System]

Your message dated Sun, 23 Mar 2014 07:04:27 +
with message-id 
and subject line Bug#741800: fixed in ruby-i18n 0.6.9-2
has caused the Debian Bug report #741800,
regarding ruby-i18n: FTBFS: ERROR: Test "ruby1.9.1" failed:   NoMethodError: 
undefined method `expects' for I18n:Module
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.)


-- 
741800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-i18n
Version: 0.6.9-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140315 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>   NoMethodError: undefined method `expects' for I18n:Module
> /«PKGBUILDDIR»/test/i18n_test.rb:146:in `block in '
> ===
> .
> 
> Finished in 2.034810413 seconds.
> 
> 1084 tests, 1524 assertions, 0 failures, 23 errors, 0 pendings, 0 omissions, 
> 0 notifications
> 97.8782% passed
> 
> 532.73 tests/s, 748.96 assertions/s
> ERROR: Test "ruby1.9.1" failed: 

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/03/15/ruby-i18n_0.6.9-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-i18n
Source-Version: 0.6.9-2

We believe that the bug you reported is fixed in the latest version of
ruby-i18n, 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 741...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Genannt  (supplier of updated ruby-i18n 
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: Thu, 20 Mar 2014 21:15:50 +0100
Source: ruby-i18n
Binary: ruby-i18n
Architecture: source all
Version: 0.6.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Jonas Genannt 
Description: 
 ruby-i18n  - I18n and localization solution for Ruby
Closes: 741800
Changes: 
 ruby-i18n (0.6.9-2) unstable; urgency=medium
 .
   * Team upload.
   * added patch fix_mocha, to support new moch versions (Closes: #741800)
Checksums-Sha1: 
 3ec47aae4d8b7baeb51492c2cd0890300bf9491b 2093 ruby-i18n_0.6.9-2.dsc
 bd83cae2a6f0386c78ef58d966d08154dcab3b79 3804 ruby-i18n_0.6.9-2.debian.tar.xz
 d1544c94698275035c52ece81fa7e375f5a30686 36204 ruby-i18n_0.6.9-2_all.deb
Checksums-Sha256: 
 3f4a4fd3ba50b23ceeb0d0d2a594504889dfbf93d4f82a51923f58309e224c16 2093 
ruby-i18n_0.6.9-2.dsc
 8dfbe16c90f0739601cc7757efe1e87ce50f0a05a60178b414f7016cdd5960e6 3804 
ruby-i18n_0.6.9-2.debian.tar.xz
 21985d18603c8c875d7e06292f59eab3d0707a0b289e955f29291a5d2dd09c2f 36204 
ruby-i18n_0.6.9-2_all.deb
Files: 
 4be1835de57be7b5cb438fe8f375a06c 2093 ruby optional ruby-i18n_0.6.9-2.dsc
 52ac45c91f85b72801c66b62e8a73eea 3804 ruby optional 
ruby-i18n_0.6.9-2.debian.tar.xz
 98432e571fbe359f645f8963ef5eb039 36204 ruby optional ruby-i18n_0.6.9-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJTLoM8AAoJEKkHZFuPn48JhZgQAJIk7Y0UGLvdeapYZ5psjpty
JYl44mDvB9RcMszPts2fNmJcrLAYf73aIMGmxiV/ReRuv0fFrGvuhBebGBIlfTi6
jO4ZR8ndFJXfkJxZx8KJqBGOMJPtAnp8sQnDfkPGhNoP1PCEYEaWc4XK59NZRNPw
iQsI/rjbLG5smjmZ9oRg3RLjXaBNqu7G8aobC4qO32QQMbCmKF69jbM41k+b8um5
gJGol4N1AF1G55S+xul9UsKafKb3PiTxlbvdUPNPr9oOOtS/Xiy+b1t9qgDcqd1M
s7q5cJkgVAqDcGHZGNPb/nW2G7zrYnmseEfRrCQsLUbVJfxOlpaWabZ73awc6s7z
dsVK+MQx9NZrtODdyYJ09Ao7K5JGwg4BLPgKyf4fSCyUu4cAj1jJm5aDZ2G92YNl
SGI9pOd5FwigHl3s7e79ZML+RSz6MVQ5Us9r2cbXc3tRN/QMER62daE8mbC8Blf0
pQ+WvP5JuILi/bS6jktJTv02+Pjc2pE3hGvdggGizDTGBwjSI4fNXl/+UYOGrpGK
585hnr7FSD8/sUnWFYfAWD8yGOA7WBtPg8t0pOYA9weYZBesriygsxX1U99T8ngm
DfIprFvANwnj3xwC+CxLmWpXA5kB+LcjBmhwpqSRYZ43tIoO7ibNcg+g8BRMW1Yn
8H7Y