Bug#752042: libghc-xmonad-dev: Package not installable - Dependencies not met
Control: reassign -1 libghc-xmonad-dev 0.11-7+b1 On Mi, 18 iun 14, 21:28:10, Philippe Grégoire wrote: Subject: libghc-xmonad-dev: Package not installable - Dependencies not met Source: libghc-xmonad-dev Version: 0.11-7+b1 Justification: renders package unusable Severity: grave Tags: d-i Dear Maintainer, * What led up to the situation? Trying to install the package to configure xmonad. * What exactly did you do (or not do) that was effective (or ineffective)? $ /bin/cat /etc/apt/sources.list deb http://http.debian.net/debian sid main contrib $ sudo apt-get update $ LANG=C.UTF-8 sudo apt-get install libghc-xmonad-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libghc-xmonad-dev : Depends: libghc-x11-dev-1.6.1.1-e59cf but it is not installable Recommends: libghc-xmonad-contrib-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. * What was the outcome of this action? xmonad is not configurable. * What outcome did you expect instead? Being able to configure xmonad. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Although I report the issue for xmonad-dev, I am well aware that the root cause is x11-dev. Thank you, P.G. -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Processed: Re: Bug#752042: libghc-xmonad-dev: Package not installable - Dependencies not met
Processing control commands: reassign -1 libghc-xmonad-dev 0.11-7+b1 Bug #752042 [src:libghc-xmonad-dev] libghc-xmonad-dev: Package not installable - Dependencies not met Warning: Unknown package 'src:libghc-xmonad-dev' Bug reassigned from package 'src:libghc-xmonad-dev' to 'libghc-xmonad-dev'. No longer marked as found in versions libghc-xmonad-dev/0.11-7+b1. Ignoring request to alter fixed versions of bug #752042 to the same values previously set Bug #752042 [libghc-xmonad-dev] libghc-xmonad-dev: Package not installable - Dependencies not met Marked as found in versions xmonad/0.11-7. -- 752042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752042 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 (with 1 errors): merging 752142 750899
Processing commands for cont...@bugs.debian.org:
merge 752142 750899
Bug #752142 [libnfs4] libnfs4 should conflict libnfs1
Unable to merge bugs because:
severity of #750899 is 'grave' not 'normal'
Failed to merge 752142: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x1ed6d40)',
'requester', 'Ritesh Raj Sarraf r...@debian.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'1403246615-1157-bts-...@debian.org', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', undef, 'clonebugs',
'HASH(0x1e020b8)', 'limit', 'HASH(0x1e01aa0)', 'common_control_options',
'ARRAY(0x1e01ae8)', 'errors', ...) called at /usr/lib/debbugs/service line 474
thanks
Stopping processing here.
Please contact me if you need assistance.
--
750899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750899
752142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752142
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#752047: latter half of Chinese lines now injured suddenly
Kool! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584162: ssmtp: Partial loss of message body, sending message to wrong recipicients
On Thu, 2014-06-19 14:44:30 -0400, Daniel Richard G. wrote:
Well, sSMTP is my dumb forwarder of choice, and as the original
reporter appears to have moved on, and sSMTP has been dropped from
testing due to this bug, and no one else seems to care, it looks like
I'll have to step in.
Attached is a patch against the original 2.64 source that should address
this bug, and hopefully not break anything. An overview of my changes:
* Added code to standarise() to drop the trailing 'r' if the line
originally ended with rn.
* Added a check to header_parse() that effectively converts an rn in
the input into 'n'.
* Added a conditional so that header_parse() doesn't pass the empty
string to header_save()---a behavior I observed in testing, at the end
of a header block with rn line endings.
* Simplified the last if(in_header) conditional in header_parse(),
because it erroneously assumes that if in_header == True, then c could
have some value other than EOF. (See the condition on the previous
while loop, and the lack of any other way to exit said loop.)
header_parse() will now properly grab a header if fed a message
without a body (i.e. no nn ending the header block), although this
code will still drop a header if there is no newline at the end.
Christoph, thank you for your excellent analysis, and the test cases. I
made use of them, and with my changes sSMTP appears to do the right
thing. I hope we can still count you as a Debian user, four years on!
Aníbal, please test this patch and let me know if there are any issues.
If everything looks good, I have two requests:
1. Convert all instances of (char)NULL in the source to '0'. The former
is silly, and if you add -Wall -Wextra to CFLAGS, GCC complains about
it voluminously. (I followed that convention in my patch, but only so
that this change could be applied across the board.)
2. Integrate all/most of debian/patches/* into the original upstream
source, and bump the version to = 2.65. It's about time.
Thank you!
I'll review/test/merge your patch this weekend. Hopefully, there will be
a 2.65 release in the next fwew days. :-)
--- ssmtp-2.64/ssmtp.c.orig 2009-11-23 04:55:11.0 -0500
+++ ssmtp-2.64/ssmtp.c2014-06-19 01:21:01.907825184 -0400
@@ -365,6 +365,12 @@
if((p = strchr(str, '\n'))) {
*p = (char)NULL;
*linestart = True;
+
+ /* If the line ended in \r\n, then drop the '\r' too */
+ sl = strlen(str);
+ if(sl = 1 str[sl - 1] == '\r') {
+ str[sl - 1] = (char)NULL;
+ }
}
return(leadingdot);
}
@@ -758,6 +764,14 @@
}
len++;
+ if(l == '\r' c == '\n') {
+ /* Properly handle input that already has \r\n
+line endings; see https://bugs.debian.org/584162 */
+ l = (len = 2 ? *(q - 2) : '\n');
+ q--;
+ len--;
+ }
+
if(l == '\n') {
switch(c) {
case ' ':
@@ -780,7 +794,9 @@
if((q = strrchr(p, '\n'))) {
*q = (char)NULL;
}
- header_save(p);
+ if(len 0) {
+ header_save(p);
+ }
q = p;
len = 0;
@@ -790,35 +806,12 @@
l = c;
}
- if(in_header) {
- if(l == '\n') {
- switch(c) {
- case ' ':
- case '\t':
- /* Must insert '\r' before
'\n's embedded in header
-fields otherwise qmail won't
accept our mail
-because a bare '\n' violates
some RFC */
-
- *(q - 1) = '\r';/*
Replace previous \n with \r */
- *q++ = '\n';/*
Insert \n */
- len++;
-
- break;
-
- case '\n':
- in_header = False;
-
- default:
- *q = (char)NULL;
- if((q = strrchr(p, '\n'))) {
-
Bug#752151: FTBFS: pdfetex error about missing cm-super
Package: src:flex Version: 2.5.39-7 Severity: serious Justification: FTBFS Dear Maintainer, flex fails to build from source. Relevant excerpt from the build log: | !pdfTeX error: pdfetex (file cm-super-t1.enc): cannot open encoding file for re | ading | == Fatal error occurred, no output PDF file produced! | /usr/bin/texi2dvi: pdfetex exited with bad status, quitting. | Makefile:434: recipe for target 'flex.pdf' failed | make[4]: *** [flex.pdf] Error 1 Full log attached. Likely this issue is fixed by adding cm-super as a B-D. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752047: latter half of Chinese lines now injured suddenly
- Original Message - | From: 積丹尼 Dan Jacobson jida...@jidanni.org | To: Thomas Dickey dic...@his.com | Cc: 752...@bugs.debian.org | Sent: Friday, June 20, 2014 2:35:24 AM | Subject: Re: Bug#752047: latter half of Chinese lines now injured suddenly | | Kool! no problem (I'd like to get the italics change stable while I work on mawk and vile, so regressions get my attention) -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752047: latter half of Chinese lines now injured suddenly
Do add all those missing chars I mentioned in another bug one day too... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728319: gworkspace.app: Preview.app fails with an error
tags 728319 + pending thanks Hi Yavor, thanks for the patch. I'll get down to work with the update. Cheers, 2014-06-19 10:52 GMT+02:00 Yavor Doganov ya...@gnu.org: tags 728319 + patch thanks Yavor Doganov wrote: It seems like Preview is not capable of opening images. Attached is a trivial patch that fixes this. These methods were removed in 2005 (it's even in the upstream ChangeLog), but apparently he forgot to remove the code that registers the notification observers. Somehow we got away with it, but not with -base 1.22 or newer. The bad news is that stable is affected so an update has to be prepared. -- Federico Giménez Nieto fgime...@coit.es
Bug#751343: python-tornado: FTBFS on mips due to test failure
Hello Scott, It seams that this failure is related to board performance, since this test failed three times but always on corelli (Cavium). I was not able to reproduce this test failure on my local boards, aside from decreasing time limit below 1.0. To resolve this issue we could increase time limit to 2.0 or 1.6, since time of test_multi_performance execution on corelli is between 1.4046919345855713 and 1.5510458946228027, at least according to existing build logs. The other solution could be to blacklist python-tornado on corelli. Best Regards, Dejan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752168: x264: FTBFS on arm*
Source: x264 Version: 2:0.142.2412+gitd7e6896-1 Severity: serious Justification: fails to build from source (but built successfully in the past) x264 failed to build on armel and armhf: | gcc -Wshadow -O3 -fno-fast-math -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -I. -I. -fno-aggressive-loop-optimizations -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -fPIC -fomit-frame-pointer -fno-tree-vectorize -D_FORTIFY_SOURCE=2 -c -o common/arm/predict-c.o common/arm/predict-c.c | common/arm/predict-c.c:36:6: error: conflicting types for 'x264_predict_8x8c_dc_neon' | void x264_predict_8x8c_dc_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:32:6: note: previous declaration of 'x264_predict_8x8c_dc_neon' was here | void x264_predict_8x8c_dc_neon( pixel *src ); | ^ | common/arm/predict-c.c:39:6: error: conflicting types for 'x264_predict_8x8c_h_neon' | void x264_predict_8x8c_h_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:33:6: note: previous declaration of 'x264_predict_8x8c_h_neon' was here | void x264_predict_8x8c_h_neon( pixel *src ); | ^ | common/arm/predict-c.c:40:6: error: conflicting types for 'x264_predict_8x8c_v_neon' | void x264_predict_8x8c_v_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:34:6: note: previous declaration of 'x264_predict_8x8c_v_neon' was here | void x264_predict_8x8c_v_neon( pixel *src ); | ^ | common/arm/predict-c.c:43:6: error: conflicting types for 'x264_predict_8x8_dc_neon' | void x264_predict_8x8_dc_neon( uint8_t *src, uint8_t edge[36] ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:31:6: note: previous declaration of 'x264_predict_8x8_dc_neon' was here | void x264_predict_8x8_dc_neon( pixel *src, pixel edge[36] ); | ^ | common/arm/predict-c.c:48:6: error: conflicting types for 'x264_predict_8x8_v_neon' | void x264_predict_8x8_v_neon( uint8_t *src, uint8_t edge[36] ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:29:6: note: previous declaration of 'x264_predict_8x8_v_neon' was here | void x264_predict_8x8_v_neon( pixel *src, pixel edge[36] ); | ^ | common/arm/predict-c.c:49:6: error: conflicting types for 'x264_predict_8x8_h_neon' | void x264_predict_8x8_h_neon( uint8_t *src, uint8_t edge[36] ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:30:6: note: previous declaration of 'x264_predict_8x8_h_neon' was here | void x264_predict_8x8_h_neon( pixel *src, pixel edge[36] ); | ^ | common/arm/predict-c.c:53:6: error: conflicting types for 'x264_predict_16x16_dc_neon' | void x264_predict_16x16_dc_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:37:6: note: previous declaration of 'x264_predict_16x16_dc_neon' was here | void x264_predict_16x16_dc_neon( pixel *src ); | ^ | common/arm/predict-c.c:56:6: error: conflicting types for 'x264_predict_16x16_h_neon' | void x264_predict_16x16_h_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:36:6: note: previous declaration of 'x264_predict_16x16_h_neon' was here | void x264_predict_16x16_h_neon( pixel *src ); | ^ | common/arm/predict-c.c:57:6: error: conflicting types for 'x264_predict_16x16_v_neon' | void x264_predict_16x16_v_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:35:6: note: previous declaration of 'x264_predict_16x16_v_neon' was here | void x264_predict_16x16_v_neon( pixel *src ); | ^ | make[2]: *** [common/arm/predict-c.o] Error 1 For the full log see https://buildd.debian.org/status/fetch.php?pkg=x264arch=armelver=2:0.142.2412+gitd7e6896-1stamp=1402770990 Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#702935: 'mount -f' does not update /run/mount/utab -- fixed-upstream
Control: tags -1 + fixed-upstream Hello! I made some tests with an updated util-linux. I didn't do exactly as described in the bug (I have no iscsi to test with) but hopefully my tests should be enough to conclude that this problem has been fixed upstream in = 2.24.2. Regards, Andreas Henriksson root@debianvm:~# cat /run//mount/utab SRC=/dev/sr0 TARGET=/media/cdrom0 ROOT=/ OPTS=user root@debianvm:~# mount -f -o user /dev/sda1 /mnt root@debianvm:~# cat /run//mount/utab SRC=/dev/sr0 TARGET=/media/cdrom0 ROOT=/ OPTS=user root@debianvm:~# umount --fake /dev/sda1 root@debianvm:~# cat /run//mount/utab SRC=/dev/sr0 TARGET=/media/cdrom0 ROOT=/ OPTS=user root@debianvm:~# root@debianvm:~# root@debianvm:~# root@debianvm:~# root@debianvm:~# dpkg -i /tmp/libmount1_2.24.2-0.1_amd64.deb /tmp/libblkid1_2.24.2-0.1_amd64.deb /tmp/util-linux_2.24.2-0.1_amd64.deb /tmp/util-linux-locales_2.24.2-0.1_all.deb /tmp/mount_2.24.2-0.1_amd64.deb /tmp/bsdutils_2.24.2-0.1_amd64.deb [] root@debianvm:~# cat /run//mount/utab SRC=/dev/sr0 TARGET=/media/cdrom0 ROOT=/ OPTS=user root@debianvm:~# mount -f -o user /dev/sda1 /mnt root@debianvm:~# cat /run//mount/utab SRC=/dev/sr0 TARGET=/media/cdrom0 ROOT=/ OPTS=user SRC=/dev/sda1 TARGET=/mnt ROOT=/ OPTS=user root@debianvm:~# umount --fake /dev/sda1root@debianvm:~# cat /run/mount/utab SRC=/dev/sr0 TARGET=/media/cdrom0 ROOT=/ OPTS=user SRC=/dev/sda1 TARGET=/mnt ROOT=/ OPTS=user root@debianvm:~# umount --fake /mnt root@debianvm:~# cat /run/mount/utab SRC=/dev/sr0 TARGET=/media/cdrom0 ROOT=/ OPTS=user root@debianvm:~#
Processed: 'mount -f' does not update /run/mount/utab -- fixed-upstream
Processing control commands: tags -1 + fixed-upstream Bug #702935 [mount] 'mount -f' does not update /run/mount/utab Added tag(s) fixed-upstream. -- 702935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702935 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#751888: [Gluster-devel] Fwd: Fwd: Bug#751888: glusterfs-server: creating symlinks generates errors
Control: forwarded -1 https://bugzilla.redhat.com/show_bug.cgi?id=454 On 06/20/2014 07:44 AM, Ravishankar N wrote: Hi Matteo, Thanks for the reproducer. I've filed a bug report here: https://bugzilla.redhat.com/show_bug.cgi?id=454 Feel free to add yourself to the CC List to get notified of the fix. Thanks a lot, Have you already reproduced the bug? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Gluster-devel] Fwd: Fwd: Bug#751888: glusterfs-server: creating symlinks generates errors
Processing control commands: forwarded -1 https://bugzilla.redhat.com/show_bug.cgi?id=454 Bug #751888 [glusterfs-server] glusterfs-server: creating symlinks generates errors Set Bug forwarded-to-address to 'https://bugzilla.redhat.com/show_bug.cgi?id=454'. -- 751888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751888 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#751888: [Gluster-devel] Fwd: Fwd: Bug#751888: glusterfs-server: creating symlinks generates errors
On 06/20/2014 06:26 PM, Matteo Checcucci wrote: Control: forwarded -1 https://bugzilla.redhat.com/show_bug.cgi?id=454 On 06/20/2014 07:44 AM, Ravishankar N wrote: Hi Matteo, Thanks for the reproducer. I've filed a bug report here: https://bugzilla.redhat.com/show_bug.cgi?id=454 Feel free to add yourself to the CC List to get notified of the fix. Thanks a lot, Have you already reproduced the bug? Yes, just sent a patch for review on master :http://review.gluster.org/#/c/8135/ Once it gets accepted, will back-port it to the 3.5 branch -Ravi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751888: [Gluster-devel] Fwd: Fwd: Bug#751888: glusterfs-server: creating symlinks generates errors
On 06/20/2014 03:05 PM, Ravishankar N wrote: On 06/20/2014 06:26 PM, Matteo Checcucci wrote: Control: forwarded -1 https://bugzilla.redhat.com/show_bug.cgi?id=454 On 06/20/2014 07:44 AM, Ravishankar N wrote: [...] Yes, just sent a patch for review on master :http://review.gluster.org/#/c/8135/ Once it gets accepted, will back-port it to the 3.5 branch -Ravi Hi Ravishankar, thanks again. I am looking forward to seeing it back-ported and integrated in the debian package. Bye Matteo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 740285
Processing commands for cont...@bugs.debian.org: tags 740285 + pending Bug #740285 [src:dune-pdelab] src:dune-pdelab: FTBFS against libsuperlu-dev = 4.3 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 740285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740285 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#751343: python-tornado: FTBFS on mips due to test failure
On 20/06/14 12:37, Dejan Latinovic wrote: Hello Scott, It seams that this failure is related to board performance, since this test failed three times but always on corelli (Cavium). I was not able to reproduce this test failure on my local boards, aside from decreasing time limit below 1.0. To resolve this issue we could increase time limit to 2.0 or 1.6, since time of test_multi_performance execution on corelli is between 1.4046919345855713 and 1.5510458946228027, at least according to existing build logs. The other solution could be to blacklist python-tornado on corelli. I've given it back and it has failed on lucatelli. Having a 1s timeout may make sense on some architectures, but not all, particularly when the buildd is building other packages in parallel. So I'd say increasing the timeout to at least 2s (or more) would be the preferred approach. Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751343: [Python-modules-team] Bug#751343: python-tornado: FTBFS on mips due to test failure
in svn I have disabled all performance relevant tests which includes this one. Upstream has a convinient switch for that for the CI. its currently waiting for sponsoring. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745015: marked as done (src:u1db: please update build-depends from libjson0-dev to libjson-c-dev)
Your message dated Fri, 20 Jun 2014 15:51:14 + with message-id e1wy15u-00043o...@franck.debian.org and subject line Bug#745015: fixed in u1db 13.10-1 has caused the Debian Bug report #745015, regarding src:u1db: please update build-depends from libjson0-dev to libjson-c-dev 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.) -- 745015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:u1db Version: 0.1.4-2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, the json-c upstream has dropped an compatibility layer from libjson0(-dev) to libjson-c2(-dev) in current upstream release. Please update your build-depends from libjson0-dev to libjson-c-dev. This bug severity will be bumped to serious when 0.12 is uploaded to unstable. Thank you, Ondrej - -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (900, 'stable'), (800, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJTT6L3AAoJEAyZtw70/LsHI6YP/Ax08FhcPnqb8i5ugEX/ebK3 KOMT74xi/TMzU9IJ1qsr1Cek6OF/69xSJAdtl+qItFjZcsiSrAOp/nucNryT3NaB mmBbnGyCZ8HCcvRSp8OWlW5xAVhraWN8s2lR5glLbPGklc0Ba5TaQkeZPFwew+3U fTk9Csdw+Q6uVIQ/KPlrsczxyb0bWwomXRy6X+9n4jvve9qTLfqs7rpl3qzUZ31a PlhHhBmQd6aoeSG3ICcyF5lSJZpRIhzYXGgk6tAFbcSzVKvoMR9fQeXvJ716TwEf CGfOkA1m7eWRF9M+/Sw3v+92zHTBOJW3AkWOf/1Mf2AuGtZEE7FdFW/KVlcUbnIQ +w4gIY7/B6sFjZdAawGMMW0TTV0fNBmi7Eqcbsnh9j7nMNt9DHCp1x3wVjAVhAC9 5sZpj5VPVMl1aA8w9QhgxW8XfS48Zc6LslqtJGRsw4LGrhRdPEkQaVPJdO+267pq bVMSZJXMkyxk4OPMkxPFii6OluM06uKz3hK1s355wnGl2aWBs+UKuhMTPGI7uNLN 7sjh4RnOwttVVAENliEzerBSe20rj8OKpdgskKH5TV8xx7ul0pZTKZZ7s14gxqX2 sJaQNj7hAYE2jWp+3XgBBqxFvG1Xa32rWQ8YCG3lcWfFNVHnWv9Pngfg773A+O9c OP7eCvYcDtase3rl7AIu =v59o -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: u1db Source-Version: 13.10-1 We believe that the bug you reported is fixed in the latest version of u1db, 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 745...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Micah Anderson mi...@debian.org (supplier of updated u1db 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: Fri, 20 Jun 2014 09:48:57 -0400 Source: u1db Binary: python-u1db libu1db1 libu1db-dev u1db-tools Architecture: source all amd64 Version: 13.10-1 Distribution: unstable Urgency: medium Maintainer: Micah Anderson mi...@debian.org Changed-By: Micah Anderson mi...@debian.org Description: libu1db-dev - Ubuntu One structured data storage - C API development files libu1db1 - Ubuntu One structured data storage - C API python-u1db - Ubuntu One structured data storage - Python API u1db-tools - ubuntu One structured data storage - Developer Tools Closes: 709486 745015 Changes: u1db (13.10-1) unstable; urgency=medium . * Update standards version (no changes) * Replace libjson0-dev with libjson-c-dev (Closes: #745015) * Update to new upstream version 13.10 - Remove upstreamed patches * debian/libu1db1.symbosl: - Update for new symbol addition from 13.05 build. * debian/control, debian/tests: - Add autopkgtest config. * debian/rules: - Do not need to set LD_LIBRARY_PATH when rpath is used. * Update debian/watch file for new series * Add debian/patches/json_object_object_get to fix deprecation * Add debian/patches/CVE-2013-2099 (Closes: #709486) Checksums-Sha1: 5e40c0a2c8bb7756a248a1cb68a73119125bcb75 2285 u1db_13.10-1.dsc 145be4d8275d23d025ff31a9071af061c81e4810 196777 u1db_13.10.orig.tar.bz2 fd33d393b6eb006d14c93cfac5f4310ca4c62628 5020 u1db_13.10-1.debian.tar.xz d67627c29aa2dc18428f597708df11c69ecfedcd 41486 python-u1db_13.10-1_all.deb d5642e5a90b051a798c4a9725b239ed1e1031bbf 32894 libu1db1_13.10-1_amd64.deb 6d30baac363277e36fe0aaf1a1a2630383b75650 7224 libu1db-dev_13.10-1_amd64.deb ce21664bba88bb11260b333ce3a38fc62c3a2b42 3726 u1db-tools_13.10-1_amd64.deb
Bug#751343: marked as done (python-tornado: FTBFS on mips due to test failure)
Your message dated Fri, 20 Jun 2014 15:50:18 + with message-id e1wy150-0003lk...@franck.debian.org and subject line Bug#751343: fixed in python-tornado 3.2.2-1 has caused the Debian Bug report #751343, regarding python-tornado: FTBFS on mips due to test failure 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.) -- 751343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-tornado Version: 3.2.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) While rebuilding your package on mips as part of the python3.3 removal transition, the following test failure (and FTBFS) ocurred: # python3 tests only in autopkgtest because I'm lazy set -e for pyvers in 2.7; do \ PYTHONPATH=/«PKGBUILDDIR» python$pyvers ./tornado/test/runtests.py; \ done ...sss..s.Fsss...sssss...s.s...ssss...s.s... == FAIL: test_multi_performance (tornado.test.gen_test.GenEngineTest) -- Traceback (most recent call last): File /«PKGBUILDDIR»/tornado/testing.py, line 427, in wrapper functools.partial(f, self), timeout=timeout) File /«PKGBUILDDIR»/tornado/ioloop.py, line 389, in run_sync return future_cell[0].result() File /«PKGBUILDDIR»/tornado/concurrent.py, line 129, in result raise_exc_info(self.__exc_info) File /«PKGBUILDDIR»/tornado/stack_context.py, line 302, in wrapped ret = fn(*args, **kwargs) File /«PKGBUILDDIR»/tornado/gen.py, line 574, in inner self.set_result(key, result) File /«PKGBUILDDIR»/tornado/gen.py, line 500, in set_result self.run() File /«PKGBUILDDIR»/tornado/gen.py, line 531, in run yielded = self.gen.send(next) File /«PKGBUILDDIR»/tornado/test/gen_test.py, line 327, in test_multi_performance self.assertLess(end - start, 1.0) AssertionError: 1.4046919345855713 not less than 1.0 -- Ran 739 tests in 42.257s FAILED (failures=1, skipped=76) Some tests were skipped because: PEP 380 not available, futures module not present, mock package not present, needs fix, pycares module not present, pycurl module not present, ssl.SSLContext not present, tornado.speedups module not present, twisted module not present [E 140611 20:26:50 testing:611] FAIL make[1]: *** [override_dh_auto_test] Error 1 debian/rules:31: recipe for target 'override_dh_auto_test' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-arch] Error 2 debian/rules:9: recipe for target 'build-arch' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: python-tornado Source-Version: 3.2.2-1 We believe that the bug you reported is fixed in the latest version of python-tornado, 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 751...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Taylor jtaylor.deb...@googlemail.com (supplier of updated python-tornado package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 19 May 2014 21:42:13 +0200 Source: python-tornado Binary: python-tornado python3-tornado Architecture: source i386 Version: 3.2.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team
Bug#752178: [unetbootin] The resulting usb pendrive looping with menu32.c32 error
Package: unetbootin Version: 603-1 Severity: serious --- Please enter the report below this line. --- --- System information. --- Architecture: amd64 Kernel: Linux 3.14-1-amd64 Debian Release: jessie/sid 500 unstable ftp.bme.hu 500 testing-updates ftp.bme.hu 500 testing security.debian.org 500 testing ftp.bme.hu 500 stable-updates ftp.bme.hu 500 stable security.debian.org 500 stable ftp.bme.hu 500 stable dl.google.com 1 experimental ftp.bme.hu --- Package information. --- Depends (Version) | Installed ==-+-=== libc6 (= 2.14) | libgcc1 (= 1:4.1.1) | libqt4-network (= 4:4.5.3) | libqtcore4 (= 4:4.7.0~beta1) | libqtgui4 (= 4:4.5.3) | libstdc++6 (= 4.1.1) | mtools | p7zip-full | syslinux | syslinux-common | udev | gksu | OR kdesudo | Recommends (Version) | Installed ==-+-=== extlinux | 3:6.03~pre17+dfsg-1 unetbootin-translations | 603-1 Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752151: FTBFS: pdfetex error about missing cm-super
Control: tag -1 patch Helmut Grohne hel...@subdivi.de (2014-06-20): | !pdfTeX error: pdfetex (file cm-super-t1.enc): cannot open encoding file for re | ading | == Fatal error occurred, no output PDF file produced! | /usr/bin/texi2dvi: pdfetex exited with bad status, quitting. | Makefile:434: recipe for target 'flex.pdf' failed | make[4]: *** [flex.pdf] Error 1 Full log attached. Likely this issue is fixed by adding cm-super as a B-D. The following patch seems to be sufficient. Mraw, KiBi. diff -Nru flex-2.5.39/debian/changelog flex-2.5.39/debian/changelog --- flex-2.5.39/debian/changelog 2014-05-27 03:13:23.0 +0200 +++ flex-2.5.39/debian/changelog 2014-06-20 17:54:54.0 +0200 @@ -1,3 +1,10 @@ +flex (2.5.39-7.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix missing cm-super-minimal build-dep (Closes: #752151). + + -- Cyril Brulebois k...@debian.org Fri, 20 Jun 2014 17:54:02 +0200 + flex (2.5.39-7) unstable; urgency=low * dh-autoreconf already depends on all the autotools that it will diff -Nru flex-2.5.39/debian/control flex-2.5.39/debian/control --- flex-2.5.39/debian/control 2014-05-27 03:13:23.0 +0200 +++ flex-2.5.39/debian/control 2014-06-20 17:55:17.0 +0200 @@ -6,7 +6,7 @@ Priority: optional Build-Depends: bison, gettext, texinfo, help2man, file, po-debconf, debhelper (= 9.0.0), dh-autoreconf, texlive-latex-base, - texlive-fonts-recommended, dpkg-dev (= 1.16.0) + texlive-fonts-recommended, dpkg-dev (= 1.16.0), cm-super-minimal Maintainer: Manoj Srivastava sriva...@debian.org Standards-Version: 3.9.5 signature.asc Description: Digital signature
Processed: Re: Bug#752151: FTBFS: pdfetex error about missing cm-super
Processing control commands: tag -1 patch Bug #752151 [src:flex] FTBFS: pdfetex error about missing cm-super Added tag(s) patch. -- 752151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752151 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#718272: [Pkg-bitcoin-devel] Bug#718272: Bug#718272: Bug#718272: Bitcoin still not ready for stable release in Debian
On Tue, Dec 17, 2013 at 6:16 PM, Dmitry Smirnov only...@debian.org wrote: Hi Scott, For your information I have a case that you might find interesting: Zabbix did not meet release criteria and was removed from testing just before release of Wheezy. Ever since yours truly was maintaining it in wheezy-backports. Why wouldn't we seek backports manager(s)' permission to provide bitcoin in wheezy-backports? Sorry for long delay, just saw this. This sounds good., it will give us the control to prevent stable release with the flexibility of constant updates. Users will have to enable backports, and thus know and be willing to keep the package up to date. I think it's crucial that we have several people working to keep the package up to date in backports, since it will not be automatic. There is more work, but I think this fits all the requirements upstream wants (flexibility of updating) with the way things work in Debian. We'd keep this bug open to prevent transition to stable, but maintain the package in unstable and backports directly. If someone wants to work and backport and maintain bticoin in backports, long-term, I think that's a good idea. It might be more responsibility than I can take on at the moment, however. ~Scott -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: This seems to be mke2fs' fault
Processing control commands: retitle -1 mke2fs apparently lacks large file support Bug #752107 [src:libguestfs] libguestfs: FTBFS on mips Changed Bug title to 'mke2fs apparently lacks large file support' from 'libguestfs: FTBFS on mips' reassign -1 e2fsprogs 1.42.10-1 Bug #752107 [src:libguestfs] mke2fs apparently lacks large file support Bug reassigned from package 'src:libguestfs' to 'e2fsprogs'. No longer marked as found in versions libguestfs/1:1.26.3. Ignoring request to alter fixed versions of bug #752107 to the same values previously set Bug #752107 [e2fsprogs] mke2fs apparently lacks large file support Marked as found in versions e2fsprogs/1.42.10-1. -- 752107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752107 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#752107: This seems to be mke2fs' fault
control: retitle -1 mke2fs apparently lacks large file support control: reassign -1 e2fsprogs 1.42.10-1 Here's what went wrong with the latest rebuild attempts for libguestfs on armhf, mips, mipsel: 1. supermin creates a 4G sparse file 2. supermin tries to create an ext2 filesystem in that file using mke2fs -t ext2 -Fq ... 3. Inside mkfs.ext2, opening that file fails with EOVERFLOW (Value too large for defined data type) I have been able to verify this in a fresh armhf chroot on harris.debian.org: $ /sbin/mke2fs -V mke2fs 1.42.10 (18-May-2014) Using EXT2FS Library version 1.42.10 $ truncate -s $((4 * 1024 * 1024 * 1024)) root $ /sbin/mke2fs -F root mke2fs 1.42.10 (18-May-2014) Could not open root: Value too large for defined data type 2^31-1 bytes is the largest file that mke2fs can open. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 751589
Processing commands for cont...@bugs.debian.org: tags 751589 + confirmed Bug #751589 [sysvinit-core,systemd-sysv] sysvinit-core: /sbin/init missing after switching from systemd to sysvinit Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 751589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751589 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#752195: apcupsd is not started via script
Package: apcupsd
Version: 3.14.10-2+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
when trying to start apcupsd through
service apcupsd start
nothing happens.
/var/log/syslog only shows:
systemd[1]: Starting LSB: Starts apcupsd daemon...
When starting /sbin/apcd manually, things work fine.
apctest also works.
I've also noticed (probably not related to apcupsd) that the UPS (Eaton 3s) is
not recognized during boot. Only un- and replugging the USB cable makes it show
up in lsusb. Is this caused by the switch to systemd?
NB: I had done so before trying to start apcupsd.
Thanks for looking into this.
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apcupsd depends on:
ii libc6 2.19-1
ii libgcc1 1:4.9.0-6
ii libwrap0 7.6.q-25
Versions of packages apcupsd recommends:
ii apcupsd-doc 3.14.10-2
Versions of packages apcupsd suggests:
pn apcupsd-cgi none
ii udev 204-8
-- Configuration Files:
/etc/apcupsd/apcupsd.conf changed:
UPSNAME EATON3S
UPSCABLE usb
UPSTYPE usb
DEVICE
POLLTIME 30
LOCKFILE /var/lock
SCRIPTDIR /etc/apcupsd
PWRFAILDIR /etc/apcupsd
NOLOGINDIR /etc
ONBATTERYDELAY 10
BATTERYLEVEL 10
MINUTES 6
TIMEOUT 0
ANNOY 300
ANNOYDELAY 30
NOLOGON disable
KILLDELAY 0
NETSERVER on
NISIP 192.168.1.1
NISPORT 3551
EVENTSFILE /var/log/apcupsd.events
EVENTSFILEMAX 10
UPSCLASS standalone
UPSMODE disable
STATTIME 0
STATFILE /var/log/apcupsd.status
LOGSTATS off
DATATIME 0
/etc/default/apcupsd changed:
APCACCESS=/sbin/apcaccess
ISCONFIGURED=yes
/etc/init.d/apcupsd changed:
True, I did remove the --quiet option.
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/sbin/apcupsd
CONFIG=/etc/default/apcupsd
NAME=apcupsd
DESC=UPS power management
test -x $DAEMON || exit 0
test -e $CONFIG || exit 0
set -e
.. $CONFIG
if [ x$ISCONFIGURED != xyes ] ;
then
echo Please check your configuration ISCONFIGURED in
/etc/default/apcupsd
exit 0
fi
case $1 in
start)
echo -n Starting $DESC:
rm -f /etc/apcupsd/powerfail
if [ `pidof apcupsd` = ]
then
start-stop-daemon --start --exec $DAEMON
echo $NAME.
else
echo
echo A copy of the daemon is still running. If you
just stopped it,
echo please wait about 5 seconds for it to shut down.
exit 0
fi
;;
stop)
echo -n Stopping $DESC:
start-stop-daemon --stop --oknodo --pidfile
/var/run/apcupsd.pid || echo Not Running.
rm -f /var/run/apcupsd.pid
echo $NAME.
;;
restart|force-reload)
$0 stop
sleep 10
$0 start
;;
status)
#/sbin/apcaccess status
$APCACCESS status
;;
*)
N=/etc/init.d/$NAME
echo Usage: $N {start|stop|restart|force-reload} 2
exit 1
;;
esac
exit 0
-- 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#746901: marked as done (qtsensors-opensource-src: ftbfs with GCC-4.9)
Your message dated Fri, 20 Jun 2014 23:33:37 + with message-id e1wy8jn-00050w...@franck.debian.org and subject line Bug#746901: fixed in qtsensors-opensource-src 5.3.0+dfsg-3 has caused the Debian Bug report #746901, regarding qtsensors-opensource-src: ftbfs with GCC-4.9 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.) -- 746901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:qtsensors-opensource-src Version: 5.2.1+dfsg-4 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.9 The package fails to build in a test rebuild on at least amd64 with gcc-4.9/g++-4.9, but succeeds to build with gcc-4.8/g++-4.8. The severity of this report may be raised before the jessie release. The full build log can be found at: http://people.debian.org/~doko/logs/failed-gcc49/qtsensors-opensource-src_5.2.1+dfsg-4_unstable_gcc49.log The last lines of the build log are at the end of this report. To build with GCC 4.9, either set CC=gcc-4.9 CXX=g++-4.9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-4.9/porting_to.html [...] - _ZN19QAmbientLightFilterD1Ev@Base 5.1.1 - _ZN19QAmbientLightFilterD2Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN19QAmbientLightFilterD0Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN19QAmbientLightFilterD1Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN19QAmbientLightFilterD2Ev@Base 5.1.1 _ZN19QAmbientLightSensor11qt_metacallEN11QMetaObject4CallEiPPv@Base 5.1.1 _ZN19QAmbientLightSensor11qt_metacastEPKc@Base 5.1.1 _ZN19QAmbientLightSensor16staticMetaObjectE@Base 5.1.1 @@ -352,9 +352,9 @@ _ZN19QIRProximityReadingD1Ev@Base 5.1.1 _ZN19QIRProximityReadingD2Ev@Base 5.1.1 _ZN19QMagnetometerFilter6filterEP14QSensorReading@Base 5.1.1 - _ZN19QMagnetometerFilterD0Ev@Base 5.1.1 - _ZN19QMagnetometerFilterD1Ev@Base 5.1.1 - _ZN19QMagnetometerFilterD2Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN19QMagnetometerFilterD0Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN19QMagnetometerFilterD1Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN19QMagnetometerFilterD2Ev@Base 5.1.1 _ZN19QOrientationReading11qt_metacallEN11QMetaObject4CallEiPPv@Base 5.1.1 _ZN19QOrientationReading11qt_metacastEPKc@Base 5.1.1 _ZN19QOrientationReading14copyValuesFromEP14QSensorReading@Base 5.1.1 @@ -366,9 +366,9 @@ _ZN19QOrientationReadingD1Ev@Base 5.1.1 _ZN19QOrientationReadingD2Ev@Base 5.1.1 _ZN20QAccelerometerFilter6filterEP14QSensorReading@Base 5.1.1 - _ZN20QAccelerometerFilterD0Ev@Base 5.1.1 - _ZN20QAccelerometerFilterD1Ev@Base 5.1.1 - _ZN20QAccelerometerFilterD2Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN20QAccelerometerFilterD0Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN20QAccelerometerFilterD1Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN20QAccelerometerFilterD2Ev@Base 5.1.1 _ZN20QAmbientLightReading11qt_metacallEN11QMetaObject4CallEiPPv@Base 5.1.1 _ZN20QAmbientLightReading11qt_metacastEPKc@Base 5.1.1 _ZN20QAmbientLightReading13setLightLevelENS_10LightLevelE@Base 5.1.1 @@ -437,9 +437,9 @@ _ZN24QSensorGestureRecognizerD1Ev@Base 5.1.1 _ZN24QSensorGestureRecognizerD2Ev@Base 5.1.1 _ZN25QAmbientTemperatureFilter6filterEP14QSensorReading@Base 5.1.1 - _ZN25QAmbientTemperatureFilterD0Ev@Base 5.1.1 - _ZN25QAmbientTemperatureFilterD1Ev@Base 5.1.1 - _ZN25QAmbientTemperatureFilterD2Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN25QAmbientTemperatureFilterD0Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN25QAmbientTemperatureFilterD1Ev@Base 5.1.1 +#MISSING: 5.2.1+dfsg-4# _ZN25QAmbientTemperatureFilterD2Ev@Base 5.1.1 _ZN25QAmbientTemperatureSensor11qt_metacallEN11QMetaObject4CallEiPPv@Base 5.1.1 _ZN25QAmbientTemperatureSensor11qt_metacastEPKc@Base 5.1.1 _ZN25QAmbientTemperatureSensor16staticMetaObjectE@Base 5.1.1 dh_makeshlibs: failing due to earlier errors make: *** [binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: qtsensors-opensource-src Source-Version: 5.3.0+dfsg-3 We believe that the bug you reported is fixed in the latest version of qtsensors-opensource-src, 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
Bug#746903: marked as done (qttools-opensource-src: ftbfs with GCC-4.9)
Your message dated Sat, 21 Jun 2014 01:04:43 +
with message-id e1wy9jx-0006u3...@franck.debian.org
and subject line Bug#746903: fixed in qttools-opensource-src 5.3.0-4
has caused the Debian Bug report #746903,
regarding qttools-opensource-src: ftbfs with GCC-4.9
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.)
--
746903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:qttools-opensource-src
Version: 5.2.1-8
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9
The package fails to build in a test rebuild on at least amd64 with
gcc-4.9/g++-4.9, but succeeds to build with gcc-4.8/g++-4.8. The
severity of this report may be raised before the jessie release.
The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/qttools-opensource-src_5.2.1-8_unstable_gcc49.log
The last lines of the build log are at the end of this report.
To build with GCC 4.9, either set CC=gcc-4.9 CXX=g++-4.9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++
Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols
files. For other C/C++ related build failures see the porting guide
at http://gcc.gnu.org/gcc-4.9/porting_to.html
[...]
- (subst)_ZSt16__introsort_loopIPi{ssize_t}EvT_S1_T0_@Base 5.2.0~alpha1
- (subst)_ZSt16__merge_adaptiveIPi{ssize_t}S0_EvT_S1_S1_T0_S2_T1_S2_@Base
5.2.0~alpha1
- (subst)_ZSt17__merge_sort_loopIPiS0_{ssize_t}EvT_S1_T0_T1_@Base 5.2.0~alpha1
+#MISSING: 5.2.1-8# (subst)_ZSt16__introsort_loopIPi{ssize_t}EvT_S1_T0_@Base
5.2.0~alpha1
+#MISSING: 5.2.1-8#
(subst)_ZSt16__merge_adaptiveIPi{ssize_t}S0_EvT_S1_S1_T0_S2_T1_S2_@Base
5.2.0~alpha1
+#MISSING: 5.2.1-8#
(subst)_ZSt17__merge_sort_loopIPiS0_{ssize_t}EvT_S1_T0_T1_@Base 5.2.0~alpha1
(optional=templinst|arch=ia64 s390
sparc|subst)_ZSt17__rotate_adaptiveIN5QListIP7QWidgetE8iteratorEPS2_{qptrdiff}ET_S6_S6_S6_T1_S7_T0_S7_@Base
5.2.0~beta1
- (optional=templinst|arch=ia64 s390
sparc|subst)_ZSt17__rotate_adaptiveIPiS0_{ssize_t}ET_S1_S1_S1_T1_S2_T0_S2_@Base
5.2.0~beta1
+
(optional=templinst|subst)_ZSt17__rotate_adaptiveIPiS0_{ssize_t}ET_S1_S1_S1_T1_S2_T0_S2_@Base
5.2.0~beta1
(optional=templinst|arch=ia64 s390
sparc)_ZSt19__move_median_firstIN5QListI11QModelIndexE8iteratorEPFbRKS1_S5_EEvT_S8_S8_T0_@Base
5.2.0~beta1
(optional=templinst|arch=ia64 s390
sparc)_ZSt19__move_median_firstIN5QListIP11RCCFileInfoE8iteratorEPFbPKS1_S6_EEvT_S9_S9_T0_@Base
5.2.0~beta1
(optional=templinst|arch=!ia64 !s390
!sparc|subst)_ZSt20get_temporary_bufferIP7QWidgetESt4pairIPT_{ssize_t}E{ssize_t}@Base
5.2.0~alpha1
- _ZSt21__inplace_stable_sortIPiEvT_S1_@Base 5.2.0~alpha1
+#MISSING: 5.2.1-8# _ZSt21__inplace_stable_sortIPiEvT_S1_@Base 5.2.0~alpha1
(optional=templinst|arch=ia64 s390
sparc)_ZSt21__unguarded_partitionIN5QListI11QModelIndexE8iteratorES1_PFbRKS1_S5_EET_S8_S8_RKT0_T1_@Base
5.2.0~beta1
(optional=templinst|arch=ia64 s390
sparc)_ZSt21__unguarded_partitionIN5QListIP11RCCFileInfoE8iteratorES2_PFbPKS1_S6_EET_S9_S9_RKT0_T1_@Base
5.2.0~beta1
(optional=templinst|arch=ia64 s390
sparc)_ZSt22__final_insertion_sortIN5QListIP11RCCFileInfoE8iteratorEPFbPKS1_S6_EEvT_S9_T0_@Base
5.2.0~beta1
- (subst)_ZSt22__merge_without_bufferIPi{ssize_t}EvT_S1_S1_T0_S2_@Base
5.2.0~alpha1
- (subst)_ZSt22__stable_sort_adaptiveIPiS0_{ssize_t}EvT_S1_T0_T1_@Base
5.2.0~alpha1
- _ZSt24__merge_sort_with_bufferIPiS0_EvT_S1_T0_@Base 5.2.0~alpha1
+#MISSING: 5.2.1-8#
(subst)_ZSt22__merge_without_bufferIPi{ssize_t}EvT_S1_S1_T0_S2_@Base
5.2.0~alpha1
+#MISSING: 5.2.1-8#
(subst)_ZSt22__stable_sort_adaptiveIPiS0_{ssize_t}EvT_S1_T0_T1_@Base
5.2.0~alpha1
+#MISSING: 5.2.1-8# _ZSt24__merge_sort_with_bufferIPiS0_EvT_S1_T0_@Base
5.2.0~alpha1
(optional=templinst|arch=ia64 s390
sparc)_ZSt25__unguarded_linear_insertIN5QListI11QModelIndexE8iteratorEPFbRKS1_S5_EEvT_T0_@Base
5.2.0~beta1
(optional=templinst|arch=!alpha !amd64 !arm64 !hppa !ia64 !kfreebsd-amd64
!ppc64 !ppc64el !s390 !s390x !sparc)_ZSt4swapIN8QVariant7PrivateEEvRT_S3_@Base
5.0.2
(optional=templinst|arch=ia64 s390
sparc)_ZSt6__findIPP7QWidgetS1_ET_S3_S3_RKT0_St26random_access_iterator_tag@Base
5.2.0~beta1
(optional=templinst|arch=ia64 s390
sparc)_ZSt8__rotateIN5QListIP7QWidgetE8iteratorEEvT_S5_S5_St26random_access_iterator_tag@Base
5.2.0~beta1
- _ZSt8__rotateIPiEvT_S1_S1_St26random_access_iterator_tag@Base 5.2.0~alpha1
+#MISSING:
Bug#752199: Useless in Jessie
Package: php-sabre-event php-sabre-http Severity: serious [Filled as an RC-bug by the maintainer to exclude packages from testing] php-sabre-event and php-sabre-http are mostly useful as php-sabre-dav 2 dependencies, but php-sabre-dav 1.8 is targeted for Jessie, so there is little point in releasing Jessie with those two packages. #749641 contains a few pointers for the rationale of php-sabre-dav 1.8 for Jessie. Regards David signature.asc Description: Digital signature
Bug#749487: Help (Was: Bug#749487: ginkgocadx: Please update to use wxwidgets3.0)
On Tue, Jun 17, 2014 at 10:11:05AM +0200, Andreas Tille wrote: Any help is really appreciated. Feel free to do a team upload if you manage a successful build. I can take a look if you send me a link to get your WIP source tree from. debian/rules get-orig-source That just seems to give me the orig source for the current version, but I've managed to hack my way around that. And then fix-wx.patch doesn't apply cleanly, so I guessed how to fix that. That done, it seems just removing the problematic header include is enough. But at the end of the buold, I get (unrelated) linking errors due to the wx propgrid library being needed, and fixing that, the rather odd: ../cadxcore/libCADxCore.a(selectimagesimportation.cpp.o): In function `wxEvtHandler::AddPendingEvent(wxEvent const)': /usr/include/wx-3.0/wx/event.h:3395: undefined reference to `wxCommandEvent::Clone() const' collect2: error: ld returned 1 exit status I need to stop for now, but that's progress so far. Will try to resolve the above later and send a patch either way. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752151: [d7b859a] Fix for Bug#752151 committed to git
tags 752151 +pending thanks Hi, The following change has been committed for this bug by Manoj Srivastava sriva...@golden-gryphon.com on Fri, 20 Jun 2014 21:01:27 -0700. The fix will be in the next upload. = [master]: Build dependency fixes, no code change Added a missing build depends on vm-super-minimal, reuired fro building the pdf documentation, (Closes: #752151). Move flex.pdf to the flex-doc package. This makes it possible for the flex package's contents to not change if texinfo is not installed, e.g. in the stage1 build profile. Thanks to Peter Pentchev r...@ringlet.net Move the flex-doc build dependencies to B-D-I. Move the TeX Live dependencies to Build-Depends-Indep and only build the HTML and PDF documentation if actually requested. This breaks a circular build dependency by not requiring texlive for the build of the arch-dependent flex binary packages. (Closes: #749344). Signed-off-by: Manoj Srivastava sriva...@golden-gryphon.com = -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [d7b859a] Fix for Bug#752151 committed to git
Processing commands for cont...@bugs.debian.org: tags 752151 +pending Bug #752151 [src:flex] FTBFS: pdfetex error about missing cm-super Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 752151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 751853, severity of 751853 is normal
Processing commands for cont...@bugs.debian.org: tags 751853 + unreproducible Bug #751853 [polkit-kde-1] polkit-kde-1: polkit-kde broken: bad exec path Added tag(s) unreproducible. severity 751853 normal Bug #751853 [polkit-kde-1] polkit-kde-1: polkit-kde broken: bad exec path Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 751853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751853 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#752151: marked as done (FTBFS: pdfetex error about missing cm-super)
Your message dated Sat, 21 Jun 2014 05:03:29 + with message-id e1wydsb-t3...@franck.debian.org and subject line Bug#752151: fixed in flex 2.5.39-8 has caused the Debian Bug report #752151, regarding FTBFS: pdfetex error about missing cm-super 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.) -- 752151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:flex Version: 2.5.39-7 Severity: serious Justification: FTBFS Dear Maintainer, flex fails to build from source. Relevant excerpt from the build log: | !pdfTeX error: pdfetex (file cm-super-t1.enc): cannot open encoding file for re | ading | == Fatal error occurred, no output PDF file produced! | /usr/bin/texi2dvi: pdfetex exited with bad status, quitting. | Makefile:434: recipe for target 'flex.pdf' failed | make[4]: *** [flex.pdf] Error 1 Full log attached. Likely this issue is fixed by adding cm-super as a B-D. Helmut ---End Message--- ---BeginMessage--- Source: flex Source-Version: 2.5.39-8 We believe that the bug you reported is fixed in the latest version of flex, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Manoj Srivastava sriva...@debian.org (supplier of updated flex 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: Fri, 20 Jun 2014 20:58:31 -0700 Source: flex Binary: flex flex-doc libfl-dev Architecture: source amd64 all Version: 2.5.39-8 Distribution: unstable Urgency: low Maintainer: Manoj Srivastava sriva...@debian.org Changed-By: Manoj Srivastava sriva...@debian.org Description: flex - fast lexical analyzer generator flex-doc - Documentation for flex (a fast lexical analyzer generator) libfl-dev - static library for flex (a fast lexical analyzer generator) Closes: 749344 752151 Changes: flex (2.5.39-8) unstable; urgency=low . * Added a missing build depends on vm-super-minimal, reuired fro building the pdf documentation, (Closes: #752151). * Move flex.pdf to the flex-doc package. This makes it possible for the flex package's contents to not change if texinfo is not installed, e.g. in the stage1 build profile. Thanks to Peter Pentchev r...@ringlet.net * Move the flex-doc build dependencies to B-D-I. Move the TeX Live dependencies to Build-Depends-Indep and only build the HTML and PDF documentation if actually requested. This breaks a circular build dependency by not requiring texlive for the build of the arch-dependent flex binary packages. (Closes: #749344). * Bug fix #752151: pdfetex error about missing cm-super, thanks to Helmut Grohne and Cyril Brulebois * Bug fix: #749344 Allow bootstrapping without texlive and dh-autoreconf, thanks to Peter Pentchev Checksums-Sha1: c1f89835894c8a47a5582686e7e81f4655c615d0 1851 flex_2.5.39-8.dsc c61df31ab947e5446484b60041609d37813b7723 26568 flex_2.5.39-8.debian.tar.xz a743c2f8eab6f2b6692e837b44832ab61a588fee 422010 flex_2.5.39-8_amd64.deb bec297a7bfaa7fe70ab9b850b97929ea2d0878e6 738372 flex-doc_2.5.39-8_all.deb 2369757445141007f4ae535587d962325911bd0e 75046 libfl-dev_2.5.39-8_amd64.deb Checksums-Sha256: d5757dbd95814ff6724e13e4fbe19a9fe5b4d1992d86b9c3bd5c765c1cd9b28e 1851 flex_2.5.39-8.dsc b6fa59036a24bc0c4ad4ccb7fb15ae7faf22269139ea050e98eec9026644b5fc 26568 flex_2.5.39-8.debian.tar.xz 724b653c6ad43e625d090ba16e56da8977cc22e3e3eb575e48558e23aaf1bd01 422010 flex_2.5.39-8_amd64.deb 4c879658048c14d5225c090d7ca6ed2b17d39e29a15c1bff5878cd1fa4a5131d 738372 flex-doc_2.5.39-8_all.deb 0e5cdbe3697ad38966062a65d099e2d9790ca6670f008ed0dbf0083b3f32d1d7 75046 libfl-dev_2.5.39-8_amd64.deb Files: 42ebd5f9c098ad2ca6d60e5c82ad8791 422010 devel optional flex_2.5.39-8_amd64.deb 627ddc1fff823aef64f594e32845b91e 738372 doc optional flex-doc_2.5.39-8_all.deb 9125630a5331d8cdcb6588c6ee59c8ac 75046 libdevel optional libfl-dev_2.5.39-8_amd64.deb b9f73414aaa320ed2e3a6c8fdde8a1a5 1851 devel optional flex_2.5.39-8.dsc e6f9825e6447f62bda43a94aa13d4df6 26568 devel optional
Bug#749487: Help (Was: Bug#749487: ginkgocadx: Please update to use wxwidgets3.0)
On Sat, Jun 21, 2014 at 03:00:11AM +0100, Olly Betts wrote: debian/rules get-orig-source That just seems to give me the orig source for the current version, but I've managed to hack my way around that. Sorry for not beeing precidse - I was talking about the packaging in svn://anonscm.debian.org/debian-med/trunk/packages/ginkgocadx/trunk/ which should give you the latest version. And then fix-wx.patch doesn't apply cleanly, so I guessed how to fix that. That done, it seems just removing the problematic header include is enough. But at the end of the buold, I get (unrelated) linking errors due to the wx propgrid library being needed, and fixing that, the rather odd: ../cadxcore/libCADxCore.a(selectimagesimportation.cpp.o): In function `wxEvtHandler::AddPendingEvent(wxEvent const)': /usr/include/wx-3.0/wx/event.h:3395: undefined reference to `wxCommandEvent::Clone() const' collect2: error: ld returned 1 exit status I need to stop for now, but that's progress so far. Will try to resolve the above later and send a patch either way. Great. This help is very welcome. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746871: marked as done (libgtextutils: ftbfs with GCC-4.9)
Your message dated Sat, 21 Jun 2014 05:48:37 + with message-id e1wyeah-0005ns...@franck.debian.org and subject line Bug#746871: fixed in libgtextutils 0.7-2 has caused the Debian Bug report #746871, regarding libgtextutils: ftbfs with GCC-4.9 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.) -- 746871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746871 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libgtextutils Version: 0.7-1 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.9 The package fails to build in a test rebuild on at least amd64 with gcc-4.9/g++-4.9, but succeeds to build with gcc-4.8/g++-4.8. The severity of this report may be raised before the jessie release. The full build log can be found at: http://people.debian.org/~doko/logs/failed-gcc49/libgtextutils_0.7-1_unstable_gcc49.log The last lines of the build log are at the end of this report. To build with GCC 4.9, either set CC=gcc-4.9 CXX=g++-4.9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-4.9/porting_to.html [...] find debian/libgtextutils0 -print0 2/dev/null | xargs -0r chown --no-dereference 0:0 find debian/libgtextutils0 ! -type l -print0 2/dev/null | xargs -0r chmod go=rX,u+rw,a-s find debian/libgtextutils0/usr/share/doc -type f ! -regex 'debian/libgtextutils0/usr/share/doc/[^/]*/examples/.*' -print0 2/dev/null | xargs -0r chmod 644 find debian/libgtextutils0/usr/share/doc -type d -print0 2/dev/null | xargs -0r chmod 755 find debian/libgtextutils0/usr/share/man debian/libgtextutils0/usr/man/ debian/libgtextutils0/usr/X11*/man/ -type f -print0 2/dev/null | xargs -0r chmod 644 find debian/libgtextutils0 -perm -5 -type f \( -name '*.so.*' -or -name '*.so' -or -name '*.la' -or -name '*.a' \) -print0 2/dev/null | xargs -0r chmod 644 find debian/libgtextutils0/usr/include -type f -print0 2/dev/null | xargs -0r chmod 644 find debian/libgtextutils0/usr/share/applications -type f -print0 2/dev/null | xargs -0r chmod 644 find debian/libgtextutils0 -perm -5 -type f \( -name '*.cmxs' \) -print0 2/dev/null | xargs -0r chmod 644 find debian/libgtextutils0/usr/lib/perl5 debian/libgtextutils0/usr/share/perl5 -type f -perm -5 -name '*.pm' -print0 2/dev/null | xargs -0r chmod a-X find debian/libgtextutils0/usr/lib -type f -name '*.ali' -print0 2/dev/null | xargs -0r chmod uga-w dh_strip -a strip --remove-section=.comment --remove-section=.note --strip-unneeded debian/libgtextutils0/usr/lib/x86_64-linux-gnu/libgtextutils-0.7.so.0.0.0 dh_makeshlibs -a rm -f debian/libgtextutils-dev/DEBIAN/shlibs rm -f debian/libgtextutils0/DEBIAN/shlibs install -d debian/libgtextutils0/DEBIAN echo 'libgtextutils-0.7 0 libgtextutils0' debian/libgtextutils0/DEBIAN/shlibs echo # Automatically added by dh_makeshlibs debian/libgtextutils0.postinst.debhelper sed /usr/share/debhelper/autoscripts/postinst-makeshlibs debian/libgtextutils0.postinst.debhelper echo '# End automatically added section' debian/libgtextutils0.postinst.debhelper echo # Automatically added by dh_makeshlibs debian/libgtextutils0.postrm.debhelper sed /usr/share/debhelper/autoscripts/postrm-makeshlibs debian/libgtextutils0.postrm.debhelper echo '# End automatically added section' debian/libgtextutils0.postrm.debhelper chmod 644 debian/libgtextutils0/DEBIAN/shlibs chown 0:0 debian/libgtextutils0/DEBIAN/shlibs dpkg-gensymbols -plibgtextutils0 -Idebian/libgtextutils0.symbols -Pdebian/libgtextutils0 -edebian/libgtextutils0/usr/lib/x86_64-linux-gnu/libgtextutils-0.7.so.0.0.0\ dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libgtextutils0/DEBIAN/symbols doesn't match completely debian/libgtextutils0.symbols --- debian/libgtextutils0.symbols (libgtextutils0_0.7-1_amd64) +++ dpkg-gensymbolsvBIjzH 2014-04-18 12:50:15.855354558 + @@ -6,9 +6,9 @@ _ZN18InputStreamWrapperC2ERKSs@Base 0.7 _ZN19OutputStreamWrapperC1ERKSsb@Base 0.7 _ZN19OutputStreamWrapperC2ERKSsb@Base 0.7 -
