Processed: severity of 809903 is normal
Processing commands for cont...@bugs.debian.org: > severity 809903 normal Bug #809903 [systemd] (no subject) Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 809903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#799837: marked as done (sddm becomes unusable after logout)
Your message dated Tue, 05 Jan 2016 07:04:21 +
with message-id
and subject line Bug#799837: fixed in sddm 0.13.0-1
has caused the Debian Bug report #799837,
regarding sddm becomes unusable after logout
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.)
--
799837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sddm
Version: 0.12.0-4
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
I normally use a laptop where I am the single user, so I only login once
in sddm, and I use "shutdown" when I (rarely) need to turn it off.
Today I needed to logout and login again. What happened was that:
1. KDE took several minutes to disappear
2. After it disappeared the screen went off! Backlight off and completely
dark.
With great difficulty I managed to reach a virtual terminal (the system was
very unresponsive) and noticed that there were no longer any processes from
my session running. sddm was running.
I attach some logs in hope that they can help.
I think it's a really terrible behaviour.
Best
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.1.6a (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages sddm depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.57
ii libc6 2.19-22
ii libgcc1 1:5.2.1-17
ii libpam0g1.1.8-3.1
ii libqt5core5a5.4.2+dfsg-9
ii libqt5dbus5 5.4.2+dfsg-9
ii libqt5gui5 5.4.2+dfsg-9
ii libqt5network5 5.4.2+dfsg-9
ii libqt5qml5 5.4.2-6
ii libqt5quick55.4.2-6
ii libstdc++6 5.2.1-17
ii libsystemd0 226-3
ii libxcb-xkb1 1.10-3+b1
ii libxcb1 1.10-3+b1
ii qml-module-qtquick2 5.4.2-6
ii sddm-theme-breeze [sddm-theme] 4:5.4.1-1
sddm recommends no packages.
Versions of packages sddm suggests:
pn libpam-kwallet5
-- debconf information:
* shared/default-x-display-manager: sddm
sddm/daemon_name: /usr/bin/sddm
Sep 23 08:28:01 localhost sddm-helper[5271]: [PAM] Ended.
Sep 23 08:28:02 localhost sddm[5213]: Auth: sddm-helper exited successfully
Sep 23 08:28:02 localhost sddm[5213]: Socket server stopping...
Sep 23 08:28:02 localhost sddm[5213]: Socket server stopped.
Sep 23 08:28:02 localhost sddm[5213]: Display server stopping...
Sep 23 08:28:07 localhost sddm[5213]: Removing display ":0" ...
Sep 23 08:28:24 localhost sddm[5213]: Adding new display on vt 7 ...
Sep 23 08:28:24 localhost sddm[5213]: Display server starting...
Sep 23 08:28:24 localhost sddm[5213]: Running: /usr/bin/X -nolisten tcp -auth
/var/run/sddm/{454d9a97-c40c-4a40-98a8-0df97885bc89} -background none -noreset
-displayfd 22 vt7
Sep 23 08:28:28 localhost sddm[5213]: Running display setup script
"/usr/share/sddm/scripts/Xsetup"
Sep 23 08:28:28 localhost sddm[5213]: Display server started.
Sep 23 08:28:28 localhost sddm[5213]: Socket server starting...
Sep 23 08:28:28 localhost sddm[5213]: Socket server started.
Sep 23 08:28:28 localhost sddm[5213]: Greeter starting...
Sep 23 08:28:28 localhost sddm[5213]: Adding cookie to
"/var/run/sddm/{454d9a97-c40c-4a40-98a8-0df97885bc89}"
Sep 23 08:28:28 localhost sddm[5213]: Display server stopping...
Sep 23 08:28:28 localhost sddm[5213]: Display server stopped.
Sep 23 08:28:28 localhost sddm[5213]: Running display stop script
"/usr/share/sddm/scripts/Xstop"
Sep 23 08:28:28 localhost sddm-helper[802]: [PAM] Starting...
Sep 23 08:28:28 localhost sddm-helper[802]: [PAM] Authenticating...
Sep 23 08:28:28 localhost sddm-helper[802]: [PAM] returning.
Sep 23 08:28:29 localhost systemd[1]: Started Session c1 of user sddm.
Sep 23 08:28:31 localhost kernel: [461586.521292] sddm-greeter[844]: segfault
at 18 ip 7f7aa72e26f8 sp 7ffd8ea10b20 error 4 in
libqxcb.so[7f7aa7298000+b6000]
Sep 23 08:28:31 localhost sddm[5213]: Greeter session started successfully
Sep 23 08:28:31 localhost sddm-helper[802]: [PAM] Ended.
Sep 23 08:28:31 localhost sddm[5213]: Auth: sddm-helper exited successfully
Sep 23 08:28:31 localhost sddm[5213]: Greeter stopped.
-
Bug#770591: Creepy: Flickr plugin not working
[Petter Reinholdtsen] > I had a closer look at the flickr failure, and the flickr plugin need > python-flickrapi version 2, while version 1.2 is in Debian at the > moment. I tested using version 2, and discovered that this in turn need the requests-toolbelt package. I've asked for its inclusion in WNPP request http://bugs.debian.org/809969 >. -- Happy hacking Petter Reinholdtsen
Bug#809984: Documentation can't be rebuilt within Debian
Package: sudo Version: 1.8.15-1 Severity: serious The source format for sudo documentation is mandoc (aka mdocml), which it is converted to regular man pages using the BSD mandoc program. That isn't packaged for Debian yet, so it's not possible to rebuild the generated documentation. groff is *not* a suitable substitute in this case. Ben. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sudo depends on: ii libaudit1 1:2.4.5-1 ii libc6 2.21-6 ii libpam-modules 1.1.8-3.1 ii libpam0g1.1.8-3.1 ii libselinux1 2.4-3 sudo recommends no packages. sudo suggests no packages. -- Configuration Files: /etc/sudoers [Errno 13] Permission denied: u'/etc/sudoers' /etc/sudoers.d/README [Errno 13] Permission denied: u'/etc/sudoers.d/README' -- no debconf information
Bug#800201: marked as done (pgpgpg: Please migrate a supported debhelper compat level)
Your message dated Tue, 05 Jan 2016 04:33:59 +
with message-id
and subject line Bug#800201: fixed in pgpgpg 0.13-9.1
has caused the Debian Bug report #800201,
regarding pgpgpg: Please migrate a supported debhelper compat level
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.)
--
800201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgpgpg
Severity: important
Usertags: deprecated-debhelper-compat-leq-3
Hi,
The package pgpgpg is using a debhelper compat level of 3 or less
according to lintian. These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).
* Please migrate the package to a supported debhelper compat level.
- Compat 9 is recommended
- Compat 5 is the bare minimum (compat 4 will be removed soon as
well)
* If your package uses any of the following tools, please remove them
from the rules files. Neither of them does anything except warn
about their deprecation.
- dh_desktop
- dh_scrollkeeper (deadline: January 1st 2016)
- dh_suidregister
- dh_undocumented
* Please note that your package might have been flagged for using
e.g. "DH_COMPAT=2 dh_foo ...".
- This will still cause issues when the compat level is removed.
* If the package has been relying on dh_install being lenient about
missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].
* Deadline:
- compat 1+2: November 1st 2015
- compat 3: January 1st 2016
If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.
Thanks,
~Niels
[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: pgpgpg
Source-Version: 0.13-9.1
We believe that the bug you reported is fixed in the latest version of
pgpgpg, 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 800...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho (supplier of updated pgpgpg
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: Sat, 26 Dec 2015 01:13:27 -0200
Source: pgpgpg
Binary: pgpgpg
Architecture: source
Version: 0.13-9.1
Distribution: unstable
Urgency: medium
Maintainer: Paweł Więcek
Changed-By: Joao Eriberto Mota Filho
Description:
pgpgpg - Wrapper for using GnuPG in programs designed for PGP
Closes: 800201
Changes:
pgpgpg (0.13-9.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Migrated DH level to 9 to avoid a FTBFS. Thanks to Logan Rosen
. (Closes: #800201)
* debian/compat: added.
* debian/control:
- Added the ${misc:Depends} variable to provide the right install
dependencies.
- Bumped Standards-Version to 3.9.6.
* debian/rules:
- Added the --no-ddebs option to dh_strip to avoid the dbgsym
creation. It would be a NEW binary (pgpgpg-dbgsym).
- Changed the binary-arch target to install files in right place.
Thanks to Logan Rosen . (Closes: #800201)
- Some actions to allow the package build twice:
~ Added a condition to execute '$(MAKE) distclean'.
~ Using dh_clean to clean the debian/ directory.
* debian/watch: added.
Checksums-Sha1:
fa94358db7ec6e97f5e277eb247f9366d5da3e9f 1600 pgpgpg_0.13-9.1.dsc
217b300d9a3283dc1b1e416823c7abb4f1548d03 4026 pgpgpg_0.13-9.1.diff.gz
Checksums-Sha256:
275b80caae34d82112a0cdb25d99dc1aa6e1da79d8a8e01d59105bcde1f5dd3d 1600
pgpgpg_0.13-9.1.dsc
927197ad4e0bf6f874c9f8929433d888472395d57d6e177d6cfa5fa8f3c0bab8 4026
pgpgpg_0.13-9.1.diff.gz
Files:
39cc0e4c4974ac9a6187243c25be61d5 1600 utils optional pgpgpg_0.13-9.1.dsc
521942e4e0f9ed0ce508d5b8d0bd24df 4026 utils optional pgpgpg_0.13-9.1.diff.gz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBAgAGBQJWfhE8AAoJEN5juccE6+nvSB8QAIwltW1UOlwjZ+spaRhx5mFp
zvqILYSoLGktAQCiY8FhK5rlXO4NA/kODJaI4F1O9HVTkeMI4TBCNMwpLJem+rZJ
raZJo+5kq7e9rvGgnGyIlLykT2I/c/KAITMaly+0hzn7OzqCV62pYIPxr61UI3CY
gak
Bug#809711: marked as done (dillo: FTBFS: /usr/bin/ld: bw.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC)
Your message dated Tue, 05 Jan 2016 04:19:03 +
with message-id
and subject line Bug#809711: fixed in fltk1.3 1.3.3-6
has caused the Debian Bug report #809711,
regarding dillo: FTBFS: /usr/bin/ld: bw.o: relocation R_X86_64_32 against
`.rodata.str1.1' can not be used when making a shared object; recompile with
-fPIC
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.)
--
809711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dillo
Version: 3.0.5-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
dillo fails to build from source in unstable/amd64:
[..]
g++ -DHAVE_CONFIG_H -I. -I.. -I.. -DDILLO_SYSCONF='"/etc/dillo/"'
-DDILLO_DOCDIR='"/usr/share/doc/dillo/"' -Wdate-time -D_FORTIFY_SOURCE=2
-I/usr/local/include -I/usr/include/libpng12 -I/usr/include/cairo
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12
-I/usr/include/freetype2 -I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/libpng12 -fPIE
-fstack-protector-strong -Wformat -Werror=format-security
-fvisibility-inlines-hidden -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_THREAD_SAFE -D_REENTRANT -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall -W -Wno-unused-parameter -fno-rtti
-fno-exceptions -c -o xembed.o xembed.cc
html.cc: In function 'const char* Html_get_attr2(DilloHtml*, const char*,
int, const char*, int)':
html.cc:4071:18: warning: assuming signed overflow does not occur when
assuming that (X + c) >= X is always true [-Wstrict-overflow]
for (i = 1; i < tagsize; ++i) {
^
g++ -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/freetype2
-I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/libpng12 -fPIE
-fstack-protector-strong -Wformat -Werror=format-security
-fvisibility-inlines-hidden -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_THREAD_SAFE -D_REENTRANT -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall -W -Wno-unused-parameter -fno-rtti
-fno-exceptions -Wl,-z,relro -L/usr/local/lib -o dillo dillo.o paths.o
tipwin.o ui.o uicmd.o bw.o cookies.o auth.o md5.o digest.o colors.o misc.o
history.o prefs.o prefsparser.o keys.o url.o bitvec.o klist.o chain.o utf8.o
timeout.o dialog.o web.o nav.o cache.o decode.o dicache.o capi.o domain.o css.o
cssparser.o styleengine.o plain.o html.o form.o table.o bookmark.o dns.o gif.o
jpeg.o png.o imgbuf.o image.o menu.o dpiapi.o findbar.o xembed.o
../dlib/libDlib.a ../dpip/libDpip.a IO/libDiof.a ../dw/libDw-widgets.a
../dw/libDw-fltk.a ../dw/libDw-core.a ../lout/liblout.a -ljpeg -lpng12 -fPIE
-pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -lfltk -lX11 -lz -lpthread -lX11
/usr/bin/ld: bw.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be
used when making a shared object; recompile with -fPIC
bw.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:589: recipe for target 'dillo' failed
make[4]: *** [dillo] Error 1
make[4]: Leaving directory
'/home/lamby/temp/cdt.20160103094342.oVDEJkW1ZH/dillo-3.0.5/src'
Makefile:703: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
'/home/lamby/temp/cdt.20160103094342.oVDEJkW1ZH/dillo-3.0.5/src'
Makefile:478: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
'/home/lamby/temp/cdt.20160103094342.oVDEJkW1ZH/dillo-3.0.5'
Makefile:363: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory
'/home/lamby/temp/cdt.20160103094342.oVDEJkW1ZH/dillo-3.0.5'
dh_auto_build: make -j8 returned exit code 2
debian/rules:11: recipe for target 'build' failed
make: *** [build] Error 2
[..]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
dillo.3.0.5-1.unstable.amd64.log.txt.gz
Descr
Processed: Re: twinkle: FTBFS: configure: error: Library requirements (libzrtpcpp >= 1.3.0) not met
Processing commands for cont...@bugs.debian.org:
> fixed 746054 1:1.9.0+dfsg-2
Bug #746054 {Done: Peter Colberg } [src:twinkle] twinkle:
FTBFS: configure: error: Library requirements (libzrtpcpp >= 1.3.0) not met
Marked as fixed in versions twinkle/1:1.9.0+dfsg-2.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
746054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#808205: libc6: Unrecognized relocation when compiling
You are right. I apologize, I so much did not expect testing packages on the system I am working on that I was in denial of libc6 not being the stable version! I don’t remember why I have sid/stretch packages (I really should not have). $ dpkg -l libc6:amd64 […] ii libc6:amd64 2.21-1 amd64 GNU C Library: Shared libraries $ md5sum /usr/lib/x86_64-linux-gnu/crti.o 4ca8dc3c02f848753e5a5317fe78fb14 /usr/lib/x86_64-linux-gnu/crti.o I have downgraded everything to stable and the issue has of course disappeared. Sorry for the noise and thanks for your help. > On Jan 5, 2016, at 1:39 AM, Aurelien Jarno wrote: > > On 2016-01-05 00:55, Mahesh Kronecker wrote: >> Dear all, >> I am on Debian/Jessie, not sid nor Stretch, but I can reproduce the hello.c >> bug as done by John Aston: >> >> $ gcc hello.c -o hello >> /usr/bin/ld: >> /usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/crti.o: >> réadressage inconnu (0x2a) dans la section « .init » >> /usr/bin/ld: édition de lien finale en échec: Mauvaise valeur >> collect2: error: ld returned 1 exit status >> >> Packages: >> -- >> sudo apt-cache show binutils >> Package: binutils >> Version: 2.25-5 >> >> Package: libc6-dev >> Source: glibc >> Version: 2.19-18+deb8u1 >> >> sudo apt-cache show libgcc1 >> Package: libgcc1 >> Source: gcc-4.9 (4.9.2-10) >> Version: 1:4.9.2-10 >> >> sudo apt-cache show libc6 >> Package: libc6 >> Status: install ok installed >> […] >> Source: glibc >> Version: 2.21-1 > > glibc version 2.21-1 has never been available in jessie... > >> […] >> - >> >> Is there something wrong in my settings or is this related to the bug you >> are describing in the testing versions of Debian? >> I do not know what to do to fix the issue on my system. > > It really looks like your system have a mix of jessie and stretch or > sid. Can you please try to run the following commands and send me the > output: > > dpkg -l libc6:amd64 > > md5sum /usr/lib/x86_64-linux-gnu/crti.o > > -- > Aurelien Jarno GPG: 4096R/1DDD8C9B > aurel...@aurel32.net http://www.aurel32.net
Bug#800135: [Debian-med-packaging] Bug#800135: python-mne: FTBFS: /usr/share/openmpi/help-mpi-errors.txt: No such file or directory
Version: 0.10.1+dfsg-1 Since that version built just fine for me in a clean environment and Gael's problem was probably different, I am closing this isssue PS updated package for 0.11 release and will try building it now ;) -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Processed: tagging 808898
Processing commands for cont...@bugs.debian.org:
> tags 808898 + pending
Bug #808898 [src:python-crontab] python-crontab: FTBFS: ImportError: Entry
point ('console_scripts', 'py.test-3.5') not found
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
808898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#809584: marked as done (lizardfs: FTBFS: Unknown CMake command "check_include_files".)
Your message dated Tue, 05 Jan 2016 12:34:39 +1100 with message-id <6058192.LaUjC1TacE@deblab> and subject line Done: lizardfs: FTBFS: Unknown CMake command "check_include_files". has caused the Debian Bug report #809584, regarding lizardfs: FTBFS: Unknown CMake command "check_include_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.) -- 809584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lizardfs Version: 2.6.0+dfsg-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.8") -- Found Zlib 1.2.8 -- Could NOT find Boost -- Thrift requires Boost headers -- Could NOT find Thrift (but it's not required) --If it's installed in a non-standard path, set THRIFT_ROOT variable --to point this path (cmake -DTHRIFT_ROOT=...) -- Could NOT find Polonaise v0.3.1 (but it's not required) --If it's installed in a non-standard path, set Polonaise_DIR variable --to point this path (cmake -DPolonaise_DIR=...) -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") -- Checking for module 'libcrcutil' -- Found libcrcutil, version 1.0 -- Found libcrcutil CMake Error at CheckIncludes.cmake:4 (check_include_files): Unknown CMake command "check_include_files". Call Stack (most recent call first): CMakeLists.txt:87 (check_includes) -- Configuring incomplete, errors occurred! See also "/lizardfs-2.6.0+dfsg/build/CMakeFiles/CMakeOutput.log". See also "/lizardfs-2.6.0+dfsg/build/CMakeFiles/CMakeError.log". "tail -v -n +0 CMakeCache.txt" Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/lizardfs.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) --- End Message --- --- Begin Message --- Source: lizardfs Version: 3.9.4+dfsg-2 Fixed in "unstable" by 3.9.4+dfsg-3. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. -- Regards, Dmitry Smirnov GPG key : 4096R/53968D1B signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: block 807539 with 809915
Processing commands for cont...@bugs.debian.org: > block 807539 with 809915 Bug #807539 [src:python-webm] python-webm: FTBFS: Exception: tostring() has been removed. Please call tobytes() instead. 807539 was not blocked by any bugs. 807539 was not blocking any bugs. Added blocking bug(s) of 807539: 809915 > thanks Stopping processing here. Please contact me if you need assistance. -- 807539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: sosreport: Please backport CVE-2015-7529 to the stable release
Processing commands for cont...@bugs.debian.org: > severity 809844 important Bug #809844 [sosreport] sosreport: Please backport CVE-2015-7529 to the stable release Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 809844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809844: sosreport: Please backport CVE-2015-7529 to the stable release
severity 809844 important thanks On Mon, Jan 04, 2016 at 05:28:27PM +0100, Louis Bouchard wrote: > Package: sosreport > Version: 3.2-2 > Severity: critical > Tags: security > Justification: root security hole Debian uses fs.protected_symlinks by default (and we also mandate it for custom-built kernels, see https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#security ) Feel free to fix this in a jessie point release, though. See here for details: https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#upload-stable Cheers, Moritz
Processed: Re: [Reproducible-builds] [multiple bugs] FTBFS: /usr/bin/ld: seaview.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
Processing control commands: > block -1 by 809825 Bug #809712 [src:p4vasp] p4vasp: FTBFS: src/cp4vasp_wrap.cpp:1239: undefined reference to `PyErr_SetString' 809712 was not blocked by any bugs. 809712 was not blocking any bugs. Added blocking bug(s) of 809712: 809825 -- 809712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809711: [Reproducible-builds] [multiple bugs] FTBFS: /usr/bin/ld: seaview.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
Control: block -1 by 809825 Hi Chris, Chris Lamb wrote: > g++ -o seaview -Wl,-z,relro -Wl,--as-needed seaview.o custom.o > use_mase_files.o regions.o load_seq.o align.o xfmatpt.o comlines.o resource.o > nexus.o viewasprots.o racnuc_fetch.o concatenate.o statistics.o trees.o > treedraw.o addbootstrap.o least_squares_brl.o pseudoterminal.o unrooted.o > pdf_or_ps.o svg.o threads.o Fl_Native_File_Chooser_FLTK.o raa_acnuc.o > parser.o md5.o zsockr.o misc_acnuc.o dnapars.o protpars.o seq.o phylip.o > lwl.o bionj.o phyml_util.o `fltk-config --use-images --ldflags` -ldl > -lpthread -lz > /usr/bin/ld: seaview.o: relocation R_X86_64_32 against `.rodata.str1.1' can > not be used when making a shared object; recompile with -fPIC Chris Lamb wrote: > g++ -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/freetype2 > -I/usr/include/cairo -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/freetype2 -I/usr/include/libpng12 -fPIE > -fstack-protector-strong -Wformat -Werror=format-security > -fvisibility-inlines-hidden -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -D_THREAD_SAFE -D_REENTRANT -g -O2 -fstack-protector-strong -Wformat > -Werror=format-security -Wall -W -Wno-unused-parameter -fno-rtti > -fno-exceptions -Wl,-z,relro -L/usr/local/lib -o dillo dillo.o paths.o > tipwin.o ui.o uicmd.o bw.o cookies.o auth.o md5.o digest.o colors.o misc.o > history.o prefs.o prefsparser.o keys.o url.o bitvec.o klist.o chain.o utf8.o > timeout.o dialog.o web.o nav.o cache.o decode.o dicache.o capi.o domain.o > css.o cssparser.o styleengine.o plain.o html.o form.o table.o bookmark.o > dns.o gif.o jpeg.o png.o imgbuf.o image.o menu.o dpiapi.o findbar.o xembed.o > ../dlib/libDlib.a ../dpip/libDpip.a IO/libDiof.a ../dw/libDw-widgets.a > ../dw/libDw-fltk.a ../dw/libDw-core.a ../lout/liblout.a -ljpeg -lpng12 -fPIE > -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -lfltk -lX11 -lz -lpthread -lX11 > /usr/bin/ld: bw.o: relocation R_X86_64_32 against `.rodata.str1.1' can not > be used when making a shared object; recompile with -fPIC These two issues are clearly related as they emitted the same error. p4vasp also FTBFS since the recent fltk1.3 upload (#809712), but with different linking issues. I concur with the p4vasp maintainer that these issues are likely all related to each other via #809825 (libfltk1.3-dev: fltk-config setting hardening flags). Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#809970: [linphone] fails to install
Package: linphone Version: 3.6.1-2.4 Severity: serious It seems with the recent rebuild for the libvpx transition, linphone-common somehow picked up a +b1 which is not in the versioned linphone-common depends of the other linphone packages. ..or something like that. Also picked up by piuparts: https://piuparts.debian.org/sid/source/l/linphone.html
Processed: Re: [Reproducible-builds] [multiple bugs] FTBFS: /usr/bin/ld: seaview.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
Processing control commands: > block -1 by 809825 Bug #809711 [src:dillo] dillo: FTBFS: /usr/bin/ld: bw.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC 809711 was not blocked by any bugs. 809711 was not blocking any bugs. Added blocking bug(s) of 809711: 809825 -- 809711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [Reproducible-builds] [multiple bugs] FTBFS: /usr/bin/ld: seaview.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
Processing control commands:
> block -1 by 809825
Bug #809713 {Done: Andreas Tille } [src:seaview] seaview:
FTBFS: /usr/bin/ld: seaview.o: relocation R_X86_64_32 against `.rodata.str1.1'
can not be used when making a shared object; recompile with -fPIC
809713 was not blocked by any bugs.
809713 was not blocking any bugs.
Added blocking bug(s) of 809713: 809825
--
809713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#808151: systemd: failed to start remount root and kernel file system
Am 05.01.2016 um 00:58 schrieb Michael Biebl: > Am 03.01.2016 um 16:21 schrieb Martin Pitt: >> https://github.com/systemd/systemd/commit/9d06297e26 >> >> Frank, Michael, if possible, it would be nice if you could confirm >> that this really fixes your case as well? > > I tried the patch, but I still get odd behaviour here. > > Systemd still tries to stop usr.mount during boot (full log attached). The behaviour did change a bit though. I don't see the > Dez 19 23:18:46 debian systemd[1]: usr.mount: Unit is bound to inactive unit > dev-sda5.device. Stopping, too. log message anymore. So something changed, but systemd still behaves incorrectly I think, as it tries to run umount on sda5. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#770591: Creepy: Flickr plugin not working
I had a closer look at the flickr failure, and the flickr plugin need python-flickrapi version 2, while version 1.2 is in Debian at the moment. This code in flickr.py fail: flickr = flickrapi.FlickrAPI(self.options_string['hidden_api_key'], self.options_string['hidden_api_secret'], cache=False, store_token=False) flickr.get_request_token(oauth_callback='oob') The get_request_token() method do not exist in version 1.2 -- Happy hacking Petter Reinholdtsen
Bug#804149: marked as done (CVE-2015-5602: Unauthorized privilege escalation in sudoedit)
Your message dated Mon, 04 Jan 2016 23:50:26 + with message-id and subject line Bug#804149: fixed in sudo 1.8.15-1.1 has caused the Debian Bug report #804149, regarding CVE-2015-5602: Unauthorized privilege escalation in sudoedit 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.) -- 804149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sudo Version: 1.7.4p4-2.squeeze.4 Severity: critical Tags: upstream security Justification: root security hole Hi, Apparently a security has been disclosed (CVE-2015-5602) allowing users to open files with sudoedit that is not supposed to using a symlinks, see: https://www.exploit-db.com/exploits/37710/ Upstream has released a new fixed version by no following the symlinks by default. But according to this comment[0], this is not fixing the issue completely. Cheers, Laurent Bigonville [0] https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1512781/comments/1 --- End Message --- --- Begin Message --- Source: sudo Source-Version: 1.8.15-1.1 We believe that the bug you reported is fixed in the latest version of sudo, 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 804...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated sudo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Jan 2016 23:36:50 + Source: sudo Binary: sudo sudo-ldap Architecture: source Version: 1.8.15-1.1 Distribution: unstable Urgency: medium Maintainer: Bdale Garbee Changed-By: Ben Hutchings Description: sudo - Provide limited super user privileges to specific users sudo-ldap - Provide limited super user privileges to specific users Closes: 804149 Changes: sudo (1.8.15-1.1) unstable; urgency=medium . * Non-maintainer upload * Disable editing of files via user-controllable symlinks (Closes: #804149) (CVE-2015-5602) - Fix directory writability checks for sudoedit - Enable sudoedit directory writability checks by default Checksums-Sha1: 28fda1fa7131168db879e78d264e84dd67cfb7dd 1962 sudo_1.8.15-1.1.dsc ab0150acf5e43f26a8f2f3979d2db16de1a917c5 24336 sudo_1.8.15-1.1.debian.tar.xz Checksums-Sha256: c94af51d8ac81c27f231fc2deef471bf671ee16a352834ea3a86e9c93e303670 1962 sudo_1.8.15-1.1.dsc b2543f8fd92e03d6f7e2ba6ba8875cf3987bf5cf285b25c31c8ec535b08cb10b 24336 sudo_1.8.15-1.1.debian.tar.xz Files: 455fe06f16b8843d25bfef9cfce9cd93 1962 admin optional sudo_1.8.15-1.1.dsc c633ae88cdc8ed3b5ba53e78a89feb39 24336 admin optional sudo_1.8.15-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVosCvOe/yOyVhhEJAQpiVg/9FrhB7qi/lk3u2q3RUKtXVtmvjbadQkw4 xMh22vV6MuFHxGqGi1bOf/DwhjSCmp0tKbof6hu6It8ttxBGug4vFfXiJzLM3pW1 UN1lQCTcAbOpYLw12/MB4q0X7m4v4bRQr+3bB7wNqyYRVnSrrs3ovweCVvGJStgf HvMNfXgt788r4hDTEyqzoJfNC+8piUQ7vWH8667T/fx+Zjn1op126CiT68l20hmM YSS32YYnQU1EDJ32gqLuoU3k0XGwQbKW96nVl5yhD2UcRXPZ9OtZcZABxKcGzLZG SgABpJFVj7xDY87spCtbGgH6tV/EibJ+CKF58e27SoO4aqZm5O56XZ6sJPtttSew Ru60nftGGy5513wyEUWa5zYZyJDXSeI/Ly/jIZPHa4OA2H6kdCQhiTKTTct4m6vV QOa9TxlKuPLUYTGiOlfga3v6mOpX1JUsHnKA02cr7UCuw+6VEbN0SJMl3mMT2LK+ IljSUhEsIPG9Od4uj1C2VCX4DVL7dpHjB+/jJKIPdPdpC/4irh1PxN7J3wQjDLua SB0bOLAVJLqNH1B1XrtleAZAXccv0+jCFWrBmvkgdMDa7PfxdQ5XjUs7thFuJWTZ mpw9Jrzhr57mnQks3y4f906BXtEtQfJtKbRqIs9NvNM4SjO9PCtnEMQq4oWPHZok 1FXIMrV3Yl8= =rFOg -END PGP SIGNATURE End Message ---
Bug#743155: marked as done (libcore-ocaml: Cannot be installed under Sid)
Your message dated Mon, 04 Jan 2016 23:49:16 + with message-id and subject line Bug#743155: fixed in janest-core 113.00.00-1 has caused the Debian Bug report #743155, regarding libcore-ocaml: Cannot be installed under Sid 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.) -- 743155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcore-ocaml Version: 107.01-5 Severity: normal The following packages have unmet dependencies: libcore-ocaml : Depends: ocaml-base-nox-3.12.1 which is a virtual package. Upon trying to install libcore-ocaml-dev I get these additional dependency issues: The following packages have unmet dependencies: libcore-ocaml-dev : Depends: libbin-prot-camlp4-dev-gt3f4 which is a virtual package. Depends: libcore-ocaml-y9832 which is a virtual package. Depends: libfields-camlp4-dev-kk6t0 which is a virtual package. Depends: libres-ocaml-dev-08mm3 which is a virtual package. Depends: libsexplib-camlp4-dev-nwls8 which is a virtual package. Depends: ocaml-nox-3.12.1 which is a virtual package. I think the package should be brought up to date from upstream and with the dependencies resolved. --- End Message --- --- Begin Message --- Source: janest-core Source-Version: 113.00.00-1 We believe that the bug you reported is fixed in the latest version of janest-core, 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 743...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated janest-core 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, 04 Jan 2016 23:33:54 +0100 Source: janest-core Binary: libcore-ocaml-dev libcore-ocaml libcore-ocaml-doc Architecture: source Version: 113.00.00-1 Distribution: unstable Urgency: low Maintainer: Debian OCaml Maintainers Changed-By: Hilko Bengen Description: libcore-ocaml - Jane Street's standard library for OCaml (runtime) libcore-ocaml-dev - Jane Street's standard library for OCaml libcore-ocaml-doc - Jane Street's standard library for OCaml - documentation Closes: 731817 743155 754303 Changes: janest-core (113.00.00-1) unstable; urgency=low . [ Stéphane Glondu ] * Add bc to Build-Depends (thanks to Thorsten Glaser) . [ Hilko Bengen ] * New upstream version (Closes: #754303)... which builds with OCaml version 4 and greater (Closes: #731817), can be installed on unstable (Closes: #743155) * Update watch file (point to github), copyright, control (add myself to Uploaders, bump Standards-Version, update Homepage, build-dependencies, descriptions) * Generate API documentation using dh_ocamldoc(1) Checksums-Sha1: 655d6ed536bd4956b51f077022d46f8808f4fc37 2616 janest-core_113.00.00-1.dsc d217af3bd34efefda98a281ad86034c4ab343cfd 770356 janest-core_113.00.00.orig.tar.gz 7c4785038bda93161013840b549d34c0c5b7d2f9 5076 janest-core_113.00.00-1.debian.tar.xz Checksums-Sha256: 9f01befa817fca13744c347e7e0a565eab7be9d6de1695c715f5c5a3dcdd14b2 2616 janest-core_113.00.00-1.dsc 5d6f948237c7eef3b2bd36b7e51994f36a1b9bbc315bbd7d41d299ad8221b7f3 770356 janest-core_113.00.00.orig.tar.gz 9ce31c54403600dbe99888ba6d5f82efb263990192fd61a51519b70b3faca4d8 5076 janest-core_113.00.00-1.debian.tar.xz Files: 76c531f04d52bdec3c3ec507289ea9ba 2616 ocaml optional janest-core_113.00.00-1.dsc 9eca76d553f62f69f93cf9dcc70b0107 770356 ocaml optional janest-core_113.00.00.orig.tar.gz 22151bfefd0e0a3fe7e1bad7cf8a8b40 5076 ocaml optional janest-core_113.00.00-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWivPWAAoJEHW3EGNcITp+SvoQAJUKmiJifU8T6+G8wozepGEv 6JL62LLM+3DOIDJ2vtAqpNjh+BxGQokE1DyEXGK1Bjiwhf5C7DP9dlX0L05n+1rK jrvusazM3foUH8qrws3C7MwEVwBtMHfrJt/AkiwM517GfTBgDYYLB5lbgv1No5RP BV8SBMc9hdyi9bbmpIsYsiImhqeX7DPU6hxOEpB5JbGbcA5EiXX6Fcw2ohli0Fz5 /eE0Vsz9o2vnVLoBjNwEWFsjqj8AE+fDL++KiuzCLJlwk+HzA/qX1QkU7xYDxJg7 K0UZUvCbjfiMzpYHj5p1gEngUYA1nOi2rG3/Af/ygR2qRD5BB50osZ4mTk7tDfuw N85zcA5W0dd6sCnayVK4f
Bug#731817: marked as done (janest-core: FTBFS with ocaml 4.01.0)
Your message dated Mon, 04 Jan 2016 23:49:16 + with message-id and subject line Bug#731817: fixed in janest-core 113.00.00-1 has caused the Debian Bug report #731817, regarding janest-core: FTBFS with ocaml 4.01.0 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.) -- 731817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: janest-core Version: 107.01-5 Severity: serious Tags: jessie sid Control: block 718767 with -1 Hi, janest-core FTBFS when binNMUed against ocaml 4.01.0. From the amd64 build log: > ocamlfind ocamldep -package unix -package threads -package sexplib.syntax > -package sexplib -package res -package fieldslib.syntax -package fieldslib > -package bin_prot.syntax -package bin_prot -package bigarray -syntax camlp4o > -modules lib/interfaces.ml > lib/interfaces.ml.depends > ocamlfind ocamldep -package unix -package threads -package sexplib.syntax > -package sexplib -package res -package fieldslib.syntax -package fieldslib > -package bin_prot.syntax -package bin_prot -package bigarray -syntax camlp4o > -modules lib/binable.ml > lib/binable.ml.depends > ocamlfind ocamldep -package unix -package threads -package sexplib.syntax > -package sexplib -package res -package fieldslib.syntax -package fieldslib > -package bin_prot.syntax -package bin_prot -package bigarray -syntax camlp4o > -modules lib/comparable.ml > lib/comparable.ml.depends > ocamlfind ocamlc -c -g -annot -ccopt -D_LARGEFILE64_SOURCE -package unix > -package threads -package sexplib.syntax -package sexplib -package res > -package fieldslib.syntax -package fieldslib -package bin_prot.syntax > -package bin_prot -package bigarray -syntax camlp4o -thread -I lib -o > lib/binable.cmo lib/binable.ml > ocamlfind ocamldep -package unix -package threads -package sexplib.syntax > -package sexplib -package res -package fieldslib.syntax -package fieldslib > -package bin_prot.syntax -package bin_prot -package bigarray -syntax camlp4o > -modules lib/core_map.mli > lib/core_map.mli.depends > ocamlfind ocamldep -package unix -package threads -package sexplib.syntax > -package sexplib -package res -package fieldslib.syntax -package fieldslib > -package bin_prot.syntax -package bin_prot -package bigarray -syntax camlp4o > -modules lib/core_map_intf.ml > lib/core_map_intf.ml.depends > ocamlfind ocamlc -c -g -annot -ccopt -D_LARGEFILE64_SOURCE -package unix > -package threads -package sexplib.syntax -package sexplib -package res > -package fieldslib.syntax -package fieldslib -package bin_prot.syntax > -package bin_prot -package bigarray -syntax camlp4o -thread -I lib -o > lib/core_map_intf.cmo lib/core_map_intf.ml > + ocamlfind ocamlc -c -g -annot -ccopt -D_LARGEFILE64_SOURCE -package unix > -package threads -package sexplib.syntax -package sexplib -package res > -package fieldslib.syntax -package fieldslib -package bin_prot.syntax > -package bin_prot -package bigarray -syntax camlp4o -thread -I lib -o > lib/core_map_intf.cmo lib/core_map_intf.ml > File "lib/core_map_intf.ml", line 285, characters 10-61: > Error: The signature constrained by `with' has no component named binable > Command exited with code 2. > E: Command '/usr/bin/ocamlbuild lib/libcore.a lib/dllcore.so lib/core.cma > lib/core.cmxa lib/core.a lib_test/test_runner.byte -tag debug' terminated > with error code 10 > make[1]: *** [override_dh_auto_build] Error 1 > make[1]: Leaving directory `/«PKGBUILDDIR»' > make: *** [build-arch] Error 2 Full build logs available via: https://buildd.debian.org/status/package.php?p=janest-core&suite=sid Cheers, -- Stéphane --- End Message --- --- Begin Message --- Source: janest-core Source-Version: 113.00.00-1 We believe that the bug you reported is fixed in the latest version of janest-core, 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 731...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated janest-core 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, 04 Jan 2016 23:33:54 +0100 Source: janest-core Binary:
Processed: tagging 809711
Processing commands for cont...@bugs.debian.org: > tags 809711 + confirmed Bug #809711 [src:dillo] dillo: FTBFS: /usr/bin/ld: bw.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 809711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#804149: NMU diff for sudo 1.8.15-1.1
See attachment.
Ben.
--
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing anyway.
diff -Nru sudo-1.8.15/debian/changelog sudo-1.8.15/debian/changelog
--- sudo-1.8.15/debian/changelog 2015-12-23 18:58:20.0 +
+++ sudo-1.8.15/debian/changelog 2016-01-04 23:36:56.0 +
@@ -1,3 +1,13 @@
+sudo (1.8.15-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Disable editing of files via user-controllable symlinks
+(Closes: #804149) (CVE-2015-5602)
+- Fix directory writability checks for sudoedit
+- Enable sudoedit directory writability checks by default
+
+ -- Ben Hutchings Mon, 04 Jan 2016 23:36:50 +
+
sudo (1.8.15-1) unstable; urgency=low
* new upstream version, closes: #804149
diff -Nru sudo-1.8.15/debian/patches/CVE-2015-5602-6.patch sudo-1.8.15/debian/patches/CVE-2015-5602-6.patch
--- sudo-1.8.15/debian/patches/CVE-2015-5602-6.patch 1970-01-01 01:00:00.0 +0100
+++ sudo-1.8.15/debian/patches/CVE-2015-5602-6.patch 2016-01-04 23:38:45.0 +
@@ -0,0 +1,102 @@
+Description: CVE-2015-5602: Fix directory writability checks for sudoedit.
+Bug: https://bugzilla.sudo.ws/show_bug.cgi?id=707
+Bug-Debian: https://bugs.debian.org/804149
+Author: Ben Hutchings
+Forwarded: https://bugzilla.sudo.ws/show_bug.cgi?id=707#c11
+
+This prevents access to a file in a writable directory *or* accessed
+through a symlink in a writable directory.
+
+--- a/src/sudo_edit.c
b/src/sudo_edit.c
+@@ -248,46 +248,52 @@ dir_is_writable(struct stat *sb, uid_t u
+ static int
+ sudo_edit_open_nonwritable(char *path, int oflags, mode_t mode)
+ {
+-char *base, *dir;
++#ifndef O_NOFOLLOW
++error(1, "%s: Can't check writability without O_NOFOLLOW", __func__);
++#else
++char *sep;
+ struct stat sb;
+-int dfd, fd;
++int dfd, subdfd, fd;
++int is_writable;
+ debug_decl(sudo_edit_open_nonwritable, SUDO_DEBUG_EDIT)
+
+-base = strrchr(path, '/');
+-if (base != NULL) {
+- *base++ = '\0';
+- dir = path;
++if (path[0] == '/') {
++ dfd = open("/", O_RDONLY);
++ ++path;
+ } else {
+- base = path;
+- dir = ".";
+-}
+-#ifdef O_PATH
+-if ((dfd = open(dir, O_PATH)) != -1) {
+- /* Linux kernels < 3.6 can't do fstat on O_PATH fds. */
+- if (fstat(dfd, &sb) == -1) {
+- close(dfd);
+- dfd = open(dir, O_RDONLY);
+- if (fstat(dfd, &sb) == -1) {
+- close(dfd);
+- dfd = -1;
+- }
+- }
++ /* XXX It doesn't make any sense to allow editing relative paths */
++ dfd = open(".", O_RDONLY);
+ }
+-#else
+-if ((dfd = open(dir, O_RDONLY)) != -1) {
++if (dfd == -1)
++ debug_return_int(-1);
++
++for (;;) {
++ /*
++ * Look up one component at a time, avoiding symbolic links in
++ * writable directories
++ */
++
+ if (fstat(dfd, &sb) == -1) {
+ close(dfd);
+- dfd = -1;
++ debug_return_int(-1);
+ }
++ is_writable = dir_is_writable(&sb, user_details.uid, user_details.gid,
++ user_details.ngroups, user_details.groups);
++
++ sep = strchr(path, '/');
++ if (sep == NULL)
++ break;
++ *sep = '\0';
++ subdfd = openat(dfd, path, O_RDONLY | (is_writable ? O_NOFOLLOW : 0), 0);
++ *sep = '/'; /* restore path */
++ close(dfd);
++ if (subdfd == -1)
++ debug_return_int(-1);
++ path = sep + 1;
++ dfd = subdfd;
+ }
+-#endif
+-if (base != path)
+- base[-1] = '/'; /* restore path */
+-if (dfd == -1)
+- debug_return_int(-1);
+
+-if (dir_is_writable(&sb, user_details.uid, user_details.gid,
+- user_details.ngroups, user_details.groups)) {
++if (is_writable) {
+ close(dfd);
+ errno = EISDIR;
+ debug_return_int(-1);
+@@ -296,6 +302,7 @@ sudo_edit_open_nonwritable(char *path, i
+ fd = openat(dfd, path, oflags, mode);
+ close(dfd);
+ debug_return_int(fd);
++#endif
+ }
+
+ #ifdef O_NOFOLLOW
diff -Nru sudo-1.8.15/debian/patches/CVE-2015-5602-7.patch sudo-1.8.15/debian/patches/CVE-2015-5602-7.patch
--- sudo-1.8.15/debian/patches/CVE-2015-5602-7.patch 1970-01-01 01:00:00.0 +0100
+++ sudo-1.8.15/debian/patches/CVE-2015-5602-7.patch 2016-01-04 23:38:58.0 +
@@ -0,0 +1,49 @@
+Description: CVE-2015-5602: Enable sudoedit directory writability checks by default
+Bug: https://bugzilla.sudo.ws/show_bug.cgi?id=707
+Bug-Debian: https://bugs.debian.org/804149
+Author: Ben Hutchings
+Forwarded: not-needed
+
+--- a/plugins/sudoers/defaults.c
b/plugins/sudoers/defaults.c
+@@ -504,6 +504,7 @@ init_defaults(void)
+ goto oom;
+ def_set_utmp = true;
+ def_pam_setcred = true;
++def_sudoedit_checkdir = true;
+
+ /* Finally do the lists (currently just environment tables). */
+ if (!init_envtables())
+--- a/doc/sudoers.cat
b/doc/sudoers.cat
+@@ -1280,7 +1280,7 @@ SSUUDDOOEERRSS OOPPTTIIOONN
+it is run by root. On many systems, this option
+requires that the parent directory of the file to be
+edited be readable by
Processed: unblock 650601 with 809918 809927 809901 809924 809914 809916 809928 809922 809920 809915 809919 809932 809902 809917 809926 809923 809927 809931 809930 809929 809900 809925 809903
Processing commands for cont...@bugs.debian.org: > unblock 650601 with 809918 809927 809901 809924 809914 809916 809928 809922 > 809920 809915 809919 809932 809902 809917 809926 809923 809927 809931 809930 > 809929 809900 809925 809903 Bug #650601 [release.debian.org] transition: libpng 1.6 650601 was blocked by: 809860 742569 809883 809950 809894 809936 809898 809869 809859 809889 662522 662273 809913 809942 809890 809901 809945 809836 809905 809924 809885 662407 809949 809879 809952 809914 641892 650483 809921 809907 809940 809916 809937 662411 809928 809922 809867 809895 809933 636004 809892 649552 809944 809953 809871 809888 809861 809910 809868 809920 809939 809870 809946 809873 809884 809943 809915 809919 809932 809891 809954 809951 809902 809862 649546 809865 809917 809878 809912 662421 662381 809893 809938 809926 809886 662314 809947 635945 809899 636998 809833 809935 635946 809874 809864 809923 649798 809927 809909 635704 809918 809904 809880 662523 809941 648131 741901 809934 809866 809931 809948 809881 809872 809887 809930 809896 809929 809897 809900 809911 809835 809863 742559 641889 809925 809903 809908 809882 809906 650601 was blocking: 649556 649973 Removed blocking bug(s) of 650601: 809915, 809920, 809919, 809902, 809917, 809900, 809932, 809927, 809924, 809901, 809931, 809918, 809929, 809930, 809923, 809916, 809928, 809925, 809903, 809914, 809922, and 809926 Warning: Unknown package 'linux-image-4.3.0-1-m68k' > thanks Stopping processing here. Please contact me if you need assistance. -- 650601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#799340: marked as done (libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz)
Your message dated Mon, 04 Jan 2016 23:24:10 + with message-id and subject line Bug#799340: fixed in libgetdata 0.9.0-2.1 has caused the Debian Bug report #799340, regarding libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz 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.) -- 799340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgetdata-doc Version: 0.8.9-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libgetdata-doc. Preparing to unpack .../libgetdata-doc_0.8.9-2_all.deb ... Unpacking libgetdata-doc (0.8.9-2) ... dpkg: error processing archive /var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/gd_frameoffset.3.gz', which is also in package libgetdata-dev 0.7.3-6+b2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb and Selecting previously unselected package libgetdata-doc. Preparing to unpack .../libgetdata-doc_0.8.9-2_all.deb ... Unpacking libgetdata-doc (0.8.9-2) ... dpkg: error processing archive /var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb (--unpack): trying to overwrite '/usr/share/man/man5/dirfile.5.gz', which is also in package libgetdata-tools 0.7.3-6+b2 Errors were encountered while processing: /var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) cheers, Andreas libgetdata-dev=0.7.3-6+b2_libgetdata-doc=0.8.9-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: libgetdata Source-Version: 0.9.0-2.1 We believe that the bug you reported is fixed in the latest version of libgetdata, 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 799...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Wiltshire (supplier of updated libgetdata 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: Sat, 02 Jan 2016 22:23:48 + Source: libgetdata Binary: libgetdata-doc libgetdata-dev libgetdata5 libgetdata++3 libfgetdata2 libf95getdata2 libgetdata-tools python-pygetdata libgetdata-perl Architecture: source all amd64 Version: 0.9.0-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jonathan Wiltshire Description: libf95getdata2 - library to read/write dirfile data - Fortran 95 bindings libfgetdata2 - library to read/write dirfile data - Fortran 77 bindings libgetdata++3 - library to read/write dirfile data - C++ bindings libgetdata-dev - library to read/write dirfile data - devel files (C, C++, F77, F9 libgetdata-doc - library to read/write dirfile data - API and standards documents libgetdata-perl - library to read/write dirfile data - perl bindings libgetdata-tools - library to read/write dirfile data - extra tools libgetdata5 - library to read/write dirfile data python-pygetdata - library to read/write dirfile data - python bindings Closes: 799340 Changes: libgetdata (0.9.0-2.1) unstable; urgency=medium . * Non-maintainer upload. * Correct Breaks/Replaces on libgetdata-doc, remove those added in previous uploads (Closes: #799340) Checksums-Sha1: 4c6ee1c4ab05bcd3d255a36050edb72db07274be 2669 libgetdata_0.9.0-2.1.dsc 130e96f464138e38ea39bfeddfcf1a7050c4d50c 4520 libgetdata_0.9.0-2.1.debian.tar.xz 0a50482f8eccf3297e6bfd137cbd40899f39fa40 330328 libgetdata-doc_0.9.0-2.1_all.deb 88474dcdb9b59708a8c5c704acfbb44cce472fe9
Processed: block 650601 with 809878 809879 809880 809881 809882 809883 809884 809885 809886 809887 809888 809889 809890 809891 809892 809893 809894 809895 809896 809897 809898 809899 809900 809901 809
Processing commands for cont...@bugs.debian.org: > block 650601 with 809878 809879 809880 809881 809882 809883 809884 809885 > 809886 809887 809888 809889 809890 809891 809892 809893 809894 809895 809896 > 809897 809898 809899 809900 809901 809902 809903 809904 809905 809906 809907 > 809908 809909 809910 809911 809912 809913 809914 809915 809916 809917 809918 > 809919 809920 809921 809922 809923 809924 809925 809926 809927 809928 809929 > 809930 809931 809932 809933 809934 809935 809936 809937 809938 809939 809940 > 809941 809942 809943 809944 809945 809946 809947 809948 809949 809950 809951 > 809952 809953 809954 809955 809956 809957 809958 809959 809960 809961 809962 > 809963 809964 809965 809966 809967 809968 809969 809970 809971 809972 809973 > 809974 809975 809976 809977 809978 809979 809980 809981 809982 809983 809984 > 809985 809986 809987 809988 809989 809990 809991 809992 809993 809994 809995 > 809996 809997 809998 80 Bug #650601 [release.debian.org] transition: libpng 1.6 650601 was blocked by: 741901 742569 809864 809866 809910 809861 662314 809869 809836 635945 636998 742559 809863 649798 809860 662421 662407 809913 662411 648131 809874 809865 809870 662381 809906 662522 809835 809871 662523 635704 809905 650483 809909 636004 809859 809904 809872 809907 809833 809862 809868 809912 635946 662273 641892 641889 649552 809867 809908 649546 809873 809911 650601 was blocking: 649556 649973 Added blocking bug(s) of 650601: 809891, 809954, 809951, 809902, 809917, 809878, 809938, 809893, 809926, 809886, 809947, 809899, 809935, 809923, 809927, 809918, 809880, 809941, 809934, 809948, 809881, 809931, 809887, 809930, 809896, 809897, 809929, 809900, 809925, 809903, 809882, 809883, 809950, 809894, 809898, 809936, 809889, 809942, 809890, 809901, 809945, 809924, 809885, 809949, 809879, 809952, 809914, 809921, 809940, 809916, 809928, 809937, 809922, 809933, 809895, 809892, 809944, 809953, 809888, 809920, 809939, 809946, 809884, 809943, 809915, 809919, and 809932 Warning: Unknown package 'linux-image-4.3.0-1-m68k' > thanks Stopping processing here. Please contact me if you need assistance. -- 650601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809263: beignet: FTBFS: /usr/include/CL/cl_egl.h:31:21: fatal error: EGL/egl.h: No such file or directory
[ 31%] Building C object src/CMakeFiles/cl.dir/cl_khr_icd.c.o cd /home/lamby/temp/cdt.20151228220726.tJcO28ENAf/beignet-1.1.1/obj-x86_64-linux-gnu/src && /usr/bin/cc -DGEN7_SAMPLER_CLAMP_BORDER_WORKAROUND -DLLVM_36 -Dcl_EXPORTS -I/home/lamby/temp/cdt.20151228220726.tJcO28ENAf/beignet-1.1.1/obj-x86_64-linux-gnu -I/home/lamby/temp/cdt.20151228220726.tJcO28ENAf/beignet-1.1.1 -I/usr/include/libdrm -I/home/lamby/temp/cdt.20151228220726.tJcO28ENAf/beignet-1.1.1/src -I/usr/include/libdrm/.. -I/home/lamby/temp/cdt.20151228220726.tJcO28ENAf/beignet-1.1.1/src/../backend/src/backend -I/home/lamby/temp/cdt.20151228220726.tJcO28ENAf/beignet-1.1.1/src/../include -I/usr/lib/llvm-3.6/include -DHAS_SUBSLICE_TOTAL -DHAS_EU_TOTAL -DHAS_USERPTR -DHAS_OCLIcd -DHAS_X11 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DGBE_DEBUG=1 -funroll-loops -fstrict-aliasing -fPIC -Wall -Wcast-align -Wl,-E -fPIC -o CMakeFiles/cl.dir/cl_khr_icd.c.o -c /home/lamby/temp/cdt.20151228220726.tJcO28ENAf/beignet-1.1.1/src/cl_ k hr_icd.c In file included from /usr/include/ocl_icd.h:40:0, from /home/lamby/temp/cdt.20151228220726.tJcO28ENAf/beignet-1.1.1/src/cl_khr_icd.c:17: /usr/include/CL/cl_egl.h:31:21: fatal error: EGL/egl.h: No such file or directory This is probably due to ocl-icd 2.2.8 adding CL/cl_egl.h to the headers #included by ocl_icd.h (https://anonscm.debian.org/cgit/collab-maint/ocl-icd.git/commit/icd_generator.rb?id=9fdd8caf362d9b848f6a722e05e4f79768a82f72). The obvious (but untested) fix is to add a dependency on libegl1-mesa-dev, but does that belong in ocl-icd-dev or beignet? It is likely that pocl (the other user of ocl-icd-dev in main) is also affected, but I haven't tested this.
Bug#808843: marked as done (python-pyramid: FTBFS: ValueError: Invalid status code, integer required.)
Your message dated Mon, 04 Jan 2016 22:38:03 +
with message-id
and subject line Bug#808843: fixed in python-pyramid 1.6+dfsg-1
has caused the Debian Bug report #808843,
regarding python-pyramid: FTBFS: ValueError: Invalid status code, integer
required.
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.)
--
808843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyramid
Version: 1.5.7+dfsg-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
python-pyramid fails to build from source in unstable/amd64:
[..]
==
ERROR: test_ctor_with_app_iter_doesnt_set_default_app_iter
(pyramid.tests.test_httpexceptions.TestHTTPException)
--
Traceback (most recent call last):
File
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
line 140, in test_ctor_with_app_iter_doesnt_set_default_app_iter
exc = self._makeOne(app_iter=[b'123'])
File
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
line 78, in _makeOne
return cls(*arg, **kw)
File
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/httpexceptions.py",
line 209, in __init__
Response.__init__(self, status=status, **kw)
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 107, in
__init__
self.status = status
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 276, in
_status__set
raise ValueError('Invalid status code, integer required.')
ValueError: Invalid status code, integer required.
==
ERROR: test_ctor_with_body_doesnt_set_default_app_iter
(pyramid.tests.test_httpexceptions.TestHTTPException)
--
Traceback (most recent call last):
File
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
line 132, in test_ctor_with_body_doesnt_set_default_app_iter
exc = self._makeOne(body=b'123')
File
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
line 78, in _makeOne
return cls(*arg, **kw)
File
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/httpexceptions.py",
line 209, in __init__
Response.__init__(self, status=status, **kw)
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 107, in
__init__
self.status = status
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 276, in
_status__set
raise ValueError('Invalid status code, integer required.')
ValueError: Invalid status code, integer required.
==
ERROR: test_ctor_with_unicode_body_doesnt_set_default_app_iter
(pyramid.tests.test_httpexceptions.TestHTTPException)
--
Traceback (most recent call last):
File
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
line 136, in test_ctor_with_unicode_body_doesnt_set_default_app_iter
exc = self._makeOne(unicode_body=text_('123'))
File
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
line 78, in _makeOne
return cls(*arg, **kw)
File
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/httpexceptions.py",
line 209, in __init__
Response.__init__(self, status=status, **kw)
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 107, in
__init__
self.status = status
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 276, in
_status__set
raise ValueError('Invalid status code, integer required.')
ValueError: Invalid status code, integer required.
==
ERROR: test_exception (pyramid.tests.test_httpexceptions.TestHTTPException)
Bug#803291: marked as done (prepare for giflib5)
Your message dated Mon, 04 Jan 2016 22:38:17 + with message-id and subject line Bug#803291: fixed in swftools 0.9.2+git20130725-4 has caused the Debian Bug report #803291, regarding prepare for giflib5 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.) -- 803291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:swftools_ Version: 0.9.2+git20130725-2 Tags: sid stretch patch Blocks: 803158 User: gif...@packages.debian.org Usertags: giflib5 Planning an update of giflib to the current version 5.1.1. Giflib slightly changes it's API, requiring soureful changes. There are some options for getting giflib5.1 support: - Look for a newer upstream version, if upstream supports both giflib4 and giflib5.1. Upload the new package, and close the bug report. - Patch the code to both use the NEW API. This can be done using #if GIFLIB_MAJOR >= 5 #else #endif Please upload the package, and close the report. - Unconditionally patch the code, not supporting giflib4 anymore. Please upload a package to experimental once giflib5 hits experimental. For the latter two options, please see a patch at http://launchpadlibrarian.net/222931742/swftools_0.9.2%2Bgit20130725-2build2_0.9.2%2Bgit20130725-2ubuntu1.diff.gz To test your changes before giflib5 is found in experimental, please use deb https://people.debian.org/~doko/tmp/giflib5 ./ Thanks, Matthias --- End Message --- --- Begin Message --- Source: swftools Source-Version: 0.9.2+git20130725-4 We believe that the bug you reported is fixed in the latest version of swftools, 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 803...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Welzel (supplier of updated swftools 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: Tue, 15 Dec 2015 22:46:11 +0100 Source: swftools Binary: swftools swftools-dbg Architecture: source amd64 Version: 0.9.2+git20130725-4 Distribution: unstable Urgency: medium Maintainer: Christian Welzel Changed-By: Christian Welzel Description: swftools - Collection of utilities for SWF file manipulation/creation swftools-dbg - Collection of utilities for SWF file manipulation/creation (debug Closes: 803291 Changes: swftools (0.9.2+git20130725-4) unstable; urgency=medium . * Build using giflib5 (patch by Matthias Klose ) (Closes: #803291) * Bumped standards version. * Fixed ordering in copyright file. * Renamed config sections in gbp.conf Checksums-Sha1: 704c861f8798ec1340e6fbb661e8578c2c55480c 2094 swftools_0.9.2+git20130725-4.dsc 1c35b3776d63baf63471983c2f5fed4b563b1dba 34740 swftools_0.9.2+git20130725-4.debian.tar.xz c400774d39ec2229f128785df2b6a3de3ee30ffd 1790118 swftools-dbg_0.9.2+git20130725-4_amd64.deb 80e2b36721bbeccd9e68254b7cd46398f18e748e 841908 swftools_0.9.2+git20130725-4_amd64.deb Checksums-Sha256: 19b5bf96d0e8de3c3ac7aa7a7ec59e26fc60a03ad1e71cd6f8a630fd551274fe 2094 swftools_0.9.2+git20130725-4.dsc 57483c0daab9efefdb6196325a87d4124a798b1569a708bfea938aa90e85e669 34740 swftools_0.9.2+git20130725-4.debian.tar.xz 5b64aecd48140f029ba27d3ccd51cd22b475fc3684d1fa9bbe6630f9a5946060 1790118 swftools-dbg_0.9.2+git20130725-4_amd64.deb 737fb29aa568233f526042849bd7e448ed6cf3be23760141d57942d912255d3a 841908 swftools_0.9.2+git20130725-4_amd64.deb Files: e5d8e5dcafdfa0bba49673cee631904c 2094 utils extra swftools_0.9.2+git20130725-4.dsc 86037da050cbd2e5d7718f95751dd82d 34740 utils extra swftools_0.9.2+git20130725-4.debian.tar.xz 2c709fa9c86f71c826aad9d8e8588ab8 1790118 debug extra swftools-dbg_0.9.2+git20130725-4_amd64.deb 2e95282c120661d23a4f6828ff997c65 841908 utils extra swftools_0.9.2+git20130725-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWiu4hAAoJEL1+qmB3j6b17U4QAJpwFXTQzyPmiHMjHpT44p3l vLrVd6fo2hoobEnLLIzbNXv48uaKDBOB+moLGuoVz4S89IWjCDyP9LzbkkQCfa8z 87u70ZHNvVdeDCnC+1MwFPhxKyMEl51oUlUPazm51cB9gwjtgGtCCplus5JIg9qa ku8uzjCGQ5lyXRYE5qRUWCgWfn8LVYgS8+i5WcnzcJLVyu+7oTI1tQeuPSPRJEjf XnopPkr/INYneQm9FTNI+BS3ISXSkVQiPmGY42T5H6Uedwjawfa5NYcIyI+URA
Bug#809764: [Debian-ha-maintainers] Bug#809764: Bug#809764:
libqb6-dev and libqb-dev: error when trying to install together Message-Id: <20160104203941.ddf730e348cc1b28b57cf...@ig.com.br> In-Reply-To: <20160104184503.027eddc33a740ce2ec872...@ig.com.br> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > I received a quick response from the upstream. > > The lib will be libWebcamoid. I can change the > name with patches for this release. Will be > in NEW and the .symbols file will be tested > again in 'experimental'. But the bug can be > closed with a new Debian revison. https://github.com/hipersayanX/webcamoid/issues/35 -- Herbert Parentes Fortes Neto (hpfn)
Processed (with 1 error): unarchiving 766108, forcibly merging 766108 809682
Processing commands for cont...@bugs.debian.org:
> unarchive 766108
Bug #766108 {Done: Daniel Kahn Gillmor }
[pinentry-gtk2] pinentry-gtk2 prevents pasting from the clipboard
Unarchived Bug 766108
> forcemerge 766108 809682
Bug #766108 {Done: Daniel Kahn Gillmor }
[pinentry-gtk2] pinentry-gtk2 prevents pasting from the clipboard
Unable to merge bugs because:
package of #809682 is 'pinentry-qt4' not 'pinentry-gtk2'
Failed to forcibly merge 766108: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
766108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766108
809682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#809927: klibc: requires kernel features not in previous stable
Source: klibc Version: 2.0.4-5 Severity: serious Justification: makes upgrading to stretch with kernel from jessie impossible I just saw this: klibc (2.0.4-5) unstable; urgency=medium . * syscalls: Use direct socket syscalls on i386 (Closes: 809423). This requires Linux 4.3. You cannot do this, this breaks installing stretch with the kernel from jessie, which is normally a supported scenario. This is especially grave as this can affect shells (lksh and mksh-static, for example).
Bug#803291: prepare for giflib5
Am 02.01.2016 um 10:27 schrieb Matthias Klose: any update on this? Uploaded a new version to m.d.n but cannot upload to archive. See here for more information: http://mentors.debian.net/package/swftools -- MfG, Christian Welzel GPG-Key: pub 4096R/5117E119 2011-09-19 Fingerprint: 3688 337C 0D3E 3725 94EC E401 8D52 CDE9 5117 E119
Bug#808248: marked as done (SAGA 2.2.2 (source) contains non-free code)
Your message dated Mon, 04 Jan 2016 21:58:48 + with message-id and subject line Bug#808248: fixed in saga 2.2.3+dfsg-1 has caused the Debian Bug report #808248, regarding SAGA 2.2.2 (source) contains non-free code 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.) -- 808248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: saga Version: 2.2.2-1 Severity: serious While starting packaging SAGA 2.2.3 I noticed that the previous package somehow contains the files which should have been excluded as documented in the debian/copyright file. Note that this does not really affect the binary package as the code is not used in the build- the results should be identical. I'll proceed creating a package for SAGA 2.2.3, but I wanted to document this error in version 2.2.2-1 in Debian. --- End Message --- --- Begin Message --- Source: saga Source-Version: 2.2.3+dfsg-1 We believe that the bug you reported is fixed in the latest version of saga, 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 808...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johan Van de Wauw (supplier of updated saga package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 04 Jan 2016 20:58:20 +0100 Source: saga Binary: saga libsaga-dev libsaga python-saga Architecture: source amd64 Version: 2.2.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Johan Van de Wauw Description: libsaga- SAGA GIS shared libraries libsaga-dev - SAGA GIS development files python-saga - SAGA GIS Python bindings saga - System for Automated Geoscientific Analyses Closes: 808248 Changes: saga (2.2.3+dfsg-1) unstable; urgency=medium . * Fix files-excluded path * Imported Upstream version 2.2.3+dfsg (closes: #808248) * Refresh patches * No longer install menu file * Don't install projection definitions twice * Update saga-depends Checksums-Sha1: c2b178e68bc0d37ae10f2edd128e6191dd7e84fa 2397 saga_2.2.3+dfsg-1.dsc e515f01086df5a988e18d1dde77bceb151836788 3880983 saga_2.2.3+dfsg.orig.tar.gz 4728b245047469681fab9ed419ccbadcd42db08b 13940 saga_2.2.3+dfsg-1.debian.tar.xz ea8d785b45e7ac7a215e639fe9a538278f16183c 2347882 libsaga-dbgsym_2.2.3+dfsg-1_amd64.deb a9c79d0a891b207a73cafb54e673725b1f5840c0 66966 libsaga-dev_2.2.3+dfsg-1_amd64.deb dae4fea9e4a66bc165a205438f16ff5fcaffae86 552056 libsaga_2.2.3+dfsg-1_amd64.deb 1fc238d854c1850814b240bc8f2c27df232ac4cf 2213578 python-saga-dbgsym_2.2.3+dfsg-1_amd64.deb ca58ffcc544ef28fb993ea0fc40de541c1c5d323 517086 python-saga_2.2.3+dfsg-1_amd64.deb bb31b5cefc42a5a2b3af4477753793947d5a43a0 25518840 saga-dbgsym_2.2.3+dfsg-1_amd64.deb 2d997250488842596c1d80e1f7109ea37d4f79ed 4889092 saga_2.2.3+dfsg-1_amd64.deb Checksums-Sha256: 5ecf293cc7811027d7bf7b46c275b90b1ede56a048430ab5d8d423f7e6f87372 2397 saga_2.2.3+dfsg-1.dsc 9e131113f55db745b704c75a5a3fe49d375699771ba91d281b674d462c464350 3880983 saga_2.2.3+dfsg.orig.tar.gz 1b1cdb70aed4223b8e889e30697895b6ab1737832460f9e53e51d283012d5b8b 13940 saga_2.2.3+dfsg-1.debian.tar.xz b3fd9e8ba673bb9cebd203e0fb64ef097aab0583a6c2e3f9f13a2b4151cd3371 2347882 libsaga-dbgsym_2.2.3+dfsg-1_amd64.deb 28042205a29d590db11f2ffe4ac45e5856ce1d41269f34a74a618dd7fa34a125 66966 libsaga-dev_2.2.3+dfsg-1_amd64.deb 6e1799f7d174879f22a740fd9298e515bd205369404d4169d117d1c379bd765a 552056 libsaga_2.2.3+dfsg-1_amd64.deb a73533dfdbe24ff9a244c4723780b0922925b5b547b46a78a27870d4e6e944c2 2213578 python-saga-dbgsym_2.2.3+dfsg-1_amd64.deb ffbd26608560f3e969074e758615b494d896a83565e11b27d21c3c332691cf81 517086 python-saga_2.2.3+dfsg-1_amd64.deb 77b70a10b554f577a7f8510dc63a8afcfa1761894ee16af6b3199c22d38e9d37 25518840 saga-dbgsym_2.2.3+dfsg-1_amd64.deb 93292bd931b7915128ecac19d7e73fd482170f8048cb386a9863de8ca1ec83ad 4889092 saga_2.2.3+dfsg-1_amd64.deb Files: 5afd97e72331e17fa01e79342e18ce2e 2397 science optional saga_2.2.3+dfsg-1.dsc ed5d9d43b4694d6d3a489f6ad06ebf65 3880983 science optional saga_2.2.3+dfsg.orig.tar.gz c1f60c7b5523bda98a1f9afc0b2f9895 13
Bug#802950: norwegian: FTBFS when awk is mawk
]] Petter Reinholdtsen > [Robert Luberda] > > `--source' seems to be supported by GNU awk only. > > Tollef, what is your view here? Should the build be changed to > always use gawk, or rewritten to not use --source? Probably just use gawk. Seems like the easier option? -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
Bug#809423: marked as done (klibc: FTBFS on i386: Multiple definition of `socket')
Your message dated Mon, 04 Jan 2016 21:51:44 + with message-id and subject line Bug#809423: fixed in klibc 2.0.4-5 has caused the Debian Bug report #809423, regarding klibc: FTBFS on i386: Multiple definition of `socket' 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.) -- 809423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: klibc Version: 2.0.4-4 Severity: serious >From my pbuilder build log: ... ld -m elf_i386 -Ttext 0x06000200 -o usr/klibc/libc.so --start-group usr/klibc/arch/i386/crt0.o usr/klibc/__shared_init.o usr/klibc/vsnprintf.o usr/klibc/snprintf.o usr/klibc/vsprintf.o usr/klibc/sprintf.o usr/klibc/asprintf.o usr/klibc/vasprintf.o usr/klibc/vsscanf.o usr/klibc/sscanf.o usr/klibc/ctypes.o usr/klibc/strntoumax.o usr/klibc/strntoimax.o usr/klibc/atoi.o usr/klibc/atol.o usr/klibc/atoll.o usr/klibc/strtol.o usr/klibc/strtoll.o usr/klibc/strtoul.o usr/klibc/strtoull.o usr/klibc/strtoimax.o usr/klibc/strtoumax.o usr/klibc/globals.o usr/klibc/exit.o usr/klibc/atexit.o usr/klibc/onexit.o usr/klibc/execl.o usr/klibc/execle.o usr/klibc/execv.o usr/klibc/execvpe.o usr/klibc/execvp.o usr/klibc/execlp.o usr/klibc/execlpe.o usr/klibc/fork.o usr/klibc/vfork.o usr/klibc/wait.o usr/klibc/wait3.o usr/klibc/waitpid.o usr/klibc/system.o usr/klibc/setpgrp.o usr/klibc/getpgrp.o usr/klibc/daemon.o usr/klibc/printf.o usr/klibc/vprintf.o usr/klibc/fprintf.o usr/klibc/vfprintf.o usr/klibc/perror.o usr/klibc/statfs.o usr/klibc/fstatfs.o usr/klibc/umount.o usr/klibc/creat.o usr/klibc/open.o usr/klibc/openat.o usr/klibc/open_cloexec.o usr/klibc/fread2.o usr/klibc/fwrite2.o usr/klibc/fgets.o usr/klibc/fputc.o usr/klibc/fputs.o usr/klibc/puts.o usr/klibc/putchar.o usr/klibc/sleep.o usr/klibc/usleep.o usr/klibc/strtotimespec.o usr/klibc/strtotimeval.o usr/klibc/raise.o usr/klibc/abort.o usr/klibc/assert.o usr/klibc/alarm.o usr/klibc/pause.o usr/klibc/__signal.o usr/klibc/sysv_signal.o usr/klibc/bsd_signal.o usr/klibc/siglist.o usr/klibc/sigabbrev.o usr/klibc/siglongjmp.o usr/klibc/sigaction.o usr/klibc/sigpending.o usr/klibc/sigprocmask.o usr/klibc/sigsuspend.o usr/klibc/pselect.o usr/klibc/ppoll.o usr/klibc/pread.o usr/klibc/pwrite.o usr/klibc/brk.o usr/klibc/sbrk.o usr/klibc/malloc.o usr/klibc/realloc.o usr/klibc/zalloc.o usr/klibc/calloc.o usr/klibc/mmap.o usr/klibc/shm_open.o usr/klibc/shm_unlink.o usr/klibc/memcpy.o usr/klibc/memcmp.o usr/klibc/memset.o usr/klibc/memccpy.o usr/klibc/memmem.o usr/klibc/memswap.o usr/klibc/memmove.o usr/klibc/memchr.o usr/klibc/memrchr.o usr/klibc/bzero.o usr/klibc/strcasecmp.o usr/klibc/strncasecmp.o usr/klibc/strndup.o usr/klibc/strerror.o usr/klibc/strsignal.o usr/klibc/strcat.o usr/klibc/strchr.o usr/klibc/strcmp.o usr/klibc/strcpy.o usr/klibc/strdup.o usr/klibc/strlen.o usr/klibc/strnlen.o usr/klibc/strncat.o usr/klibc/strlcpy.o usr/klibc/strlcat.o usr/klibc/strstr.o usr/klibc/strncmp.o usr/klibc/strncpy.o usr/klibc/strrchr.o usr/klibc/strxspn.o usr/klibc/strspn.o usr/klibc/strcspn.o usr/klibc/strpbrk.o usr/klibc/strsep.o usr/klibc/strtok.o usr/klibc/strtok_r.o usr/klibc/fnmatch.o usr/klibc/gethostname.o usr/klibc/getdomainname.o usr/klibc/getcwd.o usr/klibc/seteuid.o usr/klibc/setegid.o usr/klibc/getenv.o usr/klibc/setenv.o usr/klibc/putenv.o usr/klibc/__put_env.o usr/klibc/unsetenv.o usr/klibc/clearenv.o usr/klibc/nullenv.o usr/klibc/getopt.o usr/klibc/getopt_long.o usr/klibc/readdir.o usr/klibc/scandir.o usr/klibc/alphasort.o usr/klibc/remove.o usr/klibc/syslog.o usr/klibc/closelog.o usr/klibc/pty.o usr/klibc/getpt.o usr/klibc/posix_openpt.o usr/klibc/isatty.o usr/klibc/reboot.o usr/klibc/time.o usr/klibc/utime.o usr/klibc/lseek.o usr/klibc/nice.o usr/klibc/getpriority.o usr/klibc/qsort.o usr/klibc/bsearch.o usr/klibc/lrand48.o usr/klibc/jrand48.o usr/klibc/mrand48.o usr/klibc/nrand48.o usr/klibc/srand48.o usr/klibc/seed48.o usr/klibc/inet/inet_ntoa.o usr/klibc/inet/inet_aton.o usr/klibc/inet/inet_addr.o usr/klibc/inet/inet_ntop.o usr/klibc/inet/inet_pton.o usr/klibc/inet/bindresvport.o usr/klibc/send.o usr/klibc/recv.o usr/klibc/access.o usr/klibc/chmod.o usr/klibc/chown.o usr/klibc/dup2.o usr/klibc/mknod.o usr/klibc/poll.o usr/klibc/rename.o usr/klibc/stat.o usr/klibc/lchown.o usr/klibc/link.o usr/klibc/rmdir.o usr/klibc/unlink.o usr/klibc/utimes.o usr/klibc/lstat.o usr/klibc/mkdir.o usr/klibc/readlink.o usr/klibc/realpath.o usr/klibc/select.o usr/klibc/symlink.o usr/klibc/pipe.o usr/klibc/ctype/isalnum.o usr/klibc/ctype/isalpha.o usr/kl
Bug#804888: Re: djview plugin unusable in debian testing...
On Tuesday, December 29, 2015 18:36:43 Leon Bottou wrote: > >>So maybe the best thing would be to file a bug against qt5, fix things > >>in this package by using qt4, and filing a wishlist bug against this > >>package to use qt5, with a "blocked by" referring to the qt5 bug > >>report above. That way when the qt5 issue is resolved the wishlist bug > >>will be unblocked and notifications will flow... Nevermind. After understanding sufficiently what is going on in the bowels of Qt, I implemented a workaround hack in a new release 4.10.5. This involves capturing the native xcb events and checking later whether Qt did the right thing. This is ugly, but waiting for these guys could take forever... I should do some real work now... - L.
Bug#802950: norwegian: FTBFS when awk is mawk
]] Petter Reinholdtsen > [Tollef Fog Heen] > > Probably just use gawk. Seems like the easier option? > > Yeah. Do you need a hand with the patch? Nah, should be trivial enough, going to make a sweep and upload soonish, I think. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
Bug#809920: Upstream version 1.1 fixes several security issues
Package: radicale Version: 1.0.1-2 Severity: critical Upstream of radicale has released a version 1.1 of radicale fixing several security issues. See http://radicale.org/news/ "Many improvements in this release are related to security, you should upgrade Radicale as soon as possible:" Improve the regex used for well-known URIs (by Unrud) Prevent regex injection in rights management (by Unrud) Prevent crafted HTTP request from calling arbitrary functions (by Unrud) Improve URI sanitation and conversion to filesystem path (by Unrud) Decouple the daemon from its parent environment (by Unrud)
Bug#802950: norwegian: FTBFS when awk is mawk
[Tollef Fog Heen] > Probably just use gawk. Seems like the easier option? Yeah. Do you need a hand with the patch? -- Vennlig hilsen Petter Reinholdtsen
Bug#804888: Fixed in usptream release 4.10.5
Upstream release 4.10.5 contains a workaround for this qt bug. - L.
Processed: tagging 799837
Processing commands for cont...@bugs.debian.org: > tags 799837 + pending Bug #799837 [sddm] sddm becomes unusable after logout Added tag(s) pending. > tags 806758 + pending Bug #806758 [sddm] sddm: On Login produces No Session for PID Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 799837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799837 806758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: xca: diff for NMU version 1.0.0-2.1
Processing control commands: > tags 809056 + patch Bug #809056 [src:xca] xca: FTBFS due to CPPFLAGS containing spaces Added tag(s) patch. > tags 809056 + pending Bug #809056 [src:xca] xca: FTBFS due to CPPFLAGS containing spaces Added tag(s) pending. -- 809056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809056: xca: diff for NMU version 1.0.0-2.1
Control: tags 809056 + patch Control: tags 809056 + pending Dear maintainer, Chris Knadle has prepared an NMU for xca (versioned as 1.0.0-2.1) and I've uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Cheers, gregor -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Pink Floyd: Mother diff -Nru xca-1.0.0/debian/changelog xca-1.0.0/debian/changelog --- xca-1.0.0/debian/changelog 2014-11-18 22:10:18.0 +0100 +++ xca-1.0.0/debian/changelog 2016-01-04 21:58:57.0 +0100 @@ -1,3 +1,11 @@ +xca (1.0.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: +- Quote CF variable contents to fix FTBFS bug (Closes: #809056) + + -- Christopher Knadle Mon, 04 Jan 2016 01:49:40 -0500 + xca (1.0.0-2) unstable; urgency=medium * RedHat Bug #1164340 - segfault when viewing a RHEL entitlement certificate diff -Nru xca-1.0.0/debian/rules xca-1.0.0/debian/rules --- xca-1.0.0/debian/rules 2014-11-18 22:10:18.0 +0100 +++ xca-1.0.0/debian/rules 2016-01-04 21:58:57.0 +0100 @@ -7,7 +7,7 @@ Local.mak: dh_testdir - CF=$(CPPFLAGS) docdir=/usr/share/doc/xca prefix=/usr ./configure + CF="$(CPPFLAGS)" docdir=/usr/share/doc/xca prefix=/usr ./configure build-arch: build signature.asc Description: Digital Signature
Processed: reassign 809764 to libqb6-dev
Processing commands for cont...@bugs.debian.org: > reassign 809764 libqb6-dev Bug #809764 [libqb-dev,libqb6-dev] libqb6-dev and libqb-dev: error when trying to install together Bug reassigned from package 'libqb-dev,libqb6-dev' to 'libqb6-dev'. Ignoring request to alter found versions of bug #809764 to the same values previously set Ignoring request to alter fixed versions of bug #809764 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 809764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809764: [Debian-ha-maintainers] Bug#809764: Bug#809764: libqb6-dev and libqb-dev: error when trying to install together
On Mon, 4 Jan 2016 16:12:19 -0200 Herbert Fortes (hpfn) wrote: > > > > "In case several development versions of a library exist, you may need > > > to use dpkg's Conflicts mechanism" > > > > I think the Policy means this between versions of the same library > > (eg. your libqb6-dev and a later libqb7-dev). > > > > But anyway, this is a more broader problem: there are now two libraries > > named libqb in Debian. Currently we provide libqb0 and libqb-dev > > packages, you provide libqb6 and libqb6-dev and we have a guarranteed > > file name conflict in the dev packages. It's already confusing, but > > there's no telling when the package names themselves will clash. The > > absolutely best solution would be persuading an upstream to change the > > library name. Webcamoid seems to be the newer project, therefore its Qb > > library might have seen less use, so I don't find it unreasonable to > > approach its maintainer with this problem. > > I was thinking about talk to the upstream. But it > will take more time to solve the situation. > > What about the bug ? > I received a quick response from the upstream. The lib will be libWebcamoid. I can change the name with patches for this release. Will be in NEW and the .symbols file will be tested again in 'experimental'. But the bug can be closed with a new Debian revison. I will do the upload untill tomorrow. regards, -- Herbert Parentes Fortes Neto (hpfn)
Processed: Re: Bug#809903: (no subject)
Processing control commands: > tags -1 + moreinfo Bug #809903 [systemd] (no subject) Added tag(s) moreinfo. -- 809903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809903: (no subject)
Control: tags -1 + moreinfo Hello Ian, your bug report doesn't contain anything. Can you please elaborate what your problem is. Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#809901: [xul-ext-pwdhash] package broken by iceveasel 43.0.2-1 (not compatible)
Package: xul-ext-pwdhash Version: 1.7-14 Severity: grave Package is said to be not compatible with newer iceweasel version Thanks
Processed: user lib...@packages.debian.org, usertagging 636998, usertagging 636998, usertagging 636998 ...
Processing commands for cont...@bugs.debian.org: > user lib...@packages.debian.org Setting user to lib...@packages.debian.org (was t...@debian.org). > usertags 636998 = Usertags were: by libpng15-transition 636998 block 650601 libpng16-transition. Usertags are now: . > usertags 636998 libpng15-transition There were no usertags set. Usertags are now: libpng15-transition. > usertags 636998 libpng16-transition Usertags were: libpng15-transition. Usertags are now: libpng16-transition libpng15-transition. > block 650601 with 636998 Bug #650601 [release.debian.org] transition: libpng 1.6 650601 was blocked by: 809835 809833 636004 809836 635704 641889 650601 was blocking: 649556 649973 Added blocking bug(s) of 650601: 636998 > thanks Stopping processing here. Please contact me if you need assistance. -- 636998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636998 650601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 809526 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=759892
Processing commands for cont...@bugs.debian.org: > forwarded 809526 https://bugzilla.gnome.org/show_bug.cgi?id=759892 Bug #809526 [network-manager] network-manager-openvpn: Fail to set IPv4 route Bug #809195 [network-manager] network-manager_1.0.10-1_amd64.deb does not update my I.P address correctly when I start my VPN Bug #809494 [network-manager] network-manager: NetworkManager 1.0.10-1 does not add default route for VPN Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=759892'. Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=759892'. Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=759892'. > thanks Stopping processing here. Please contact me if you need assistance. -- 809195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809195 809494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809494 809526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 809526 is serious
Processing commands for cont...@bugs.debian.org: > severity 809526 serious Bug #809526 [network-manager] network-manager-openvpn: Fail to set IPv4 route Bug #809195 [network-manager] network-manager_1.0.10-1_amd64.deb does not update my I.P address correctly when I start my VPN Bug #809494 [network-manager] network-manager: NetworkManager 1.0.10-1 does not add default route for VPN Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 809195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809195 809494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809494 809526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809877: xdg-utils: fix for #801048 breaks xdg-open if whitespaces in the filename on Debian/Cinnamon
Package: xdg-utils Version: 1.1.1-1 Severity: grave Justification: renders package unusable To reproduce, install Cinnamon on Debian 8.2, then pull 1.1.1-1 from Stretch. You should find that xdg-open will no longer correctly parse file paths with spaces in them. This is probably due to the fix for #801048 which dealt with some whitespace stuff, since whitespaces worked just fine in 1.1.0. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) xdg-utils depends on no packages. Versions of packages xdg-utils recommends: ii libfile-mimeinfo-perl 0.27-1 ii libnet-dbus-perl 1.1.0-3 ii libx11-protocol-perl 0.56-7 ii x11-utils 7.7+3 ii x11-xserver-utils 7.7+5 Versions of packages xdg-utils suggests: ii gvfs-bin 1.26.2-1 -- no debconf information
Processed: Bug#808843 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 808843 pending Bug #808843 [src:python-pyramid] python-pyramid: FTBFS: ValueError: Invalid status code, integer required. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 808843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809875: ruby-activerecord-session-store and ruby-activerecord-nulldb-adapter: error when trying to install together
Package: ruby-activerecord-nulldb-adapter,ruby-activerecord-session-store Version: ruby-activerecord-nulldb-adapter/0.3.1-1 Version: ruby-activerecord-session-store/0.1.1-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2016-01-04 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 49% Extracting templates from packages: 98% Extracting templates from packages: 100% Preconfiguring packages ... Selecting previously unselected package libyaml-0-2:amd64. (Reading database ... 10930 files and directories currently installed.) Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ... Unpacking libyaml-0-2:amd64 (0.1.6-3) ... Selecting previously unselected package gcc-5-base:amd64. Preparing to unpack .../gcc-5-base_5.3.1-5_amd64.deb ... Unpacking gcc-5-base:amd64 (5.3.1-5) ... Setting up gcc-5-base:amd64 (5.3.1-5) ... (Reading database ... 10944 files and directories currently installed.) Preparing to unpack .../libstdc++6_5.3.1-5_amd64.deb ... Unpacking libstdc++6:amd64 (5.3.1-5) over (4.8.2-19) ... Processing triggers for libc-bin (2.21-6) ... Setting up libstdc++6:amd64 (5.3.1-5) ... Processing triggers for libc-bin (2.21-6) ... Selecting previously unselected package libssl1.0.2:amd64. (Reading database ... 10958 files and directories currently installed.) Preparing to unpack .../libssl1.0.2_1.0.2e-1_amd64.deb ... Unpacking libssl1.0.2:amd64 (1.0.2e-1) ... Selecting previously unselected package libgcrypt20:amd64. Preparing to unpack .../libgcrypt20_1.6.4-4_amd64.deb ... Unpacking libgcrypt20:amd64 (1.6.4-4) ... Selecting previously unselected package libicu55:amd64. Preparing to unpack .../libicu55_55.1-7_amd64.deb ... Unpacking libicu55:amd64 (55.1-7) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.3+dfsg1-1_amd64.deb ... Unpacking libxml2:amd64 (2.9.3+dfsg1-1) ... Selecting previously unselected package openssl. Preparing to unpack .../openssl_1.0.2e-1_amd64.deb ... Unpacking openssl (1.0.2e-1) ... Selecting previously unselected package ca-certificates. Preparing to unpack .../ca-certificates_20151214_all.deb ... Unpacking ca-certificates (20151214) ... Selecting previously unselected package rubygems-integration. Preparing to unpack .../rubygems-integration_1.10_all.deb ... Unpacking rubygems-integration (1.10) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.1.0+dfsg-2_amd64.deb ... Unpacking libgmp10:amd64 (2:6.1.0+dfsg-2) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ... Unpacking libffi6:amd64 (3.2.1-4) ... Selecting previously unselected package ruby-power-assert. Preparing to unpack .../ruby-power-assert_0.2.6-1_all.deb ... Unpacking ruby-power-assert (0.2.6-1) ... Selecting previously unselected package ruby-test-unit. Preparing to unpack .../ruby-test-unit_3.1.5-1_all.deb ... Unpacking ruby-test-unit (3.1.5-1) ... Selecting previously unselected package ruby-minitest. Preparing to unpack .../ruby-minitest_5.8.3-1_all.deb ... Unpacking ruby-minitest (5.8.3-1) ... Selecting previously unselected package libruby2.2:amd64. Preparing to unpack .../libruby2.2_2.2.3-2_amd64.deb ... Unpacking libruby2.2:amd64 (2.2.3-2) ... Selecting previously unselected package ruby2.2. Preparing to unpack .../ruby2.2_2.2.3-2_amd64.deb ... Unpacking ruby2.2 (2.2.3-2) ... Selecting previously unselected package ruby. Preparing to unpack .../ruby_1%3a2.2.4_all.deb ... Unpacking ruby (1:2.2.4) ... Selecting previously unselected package ruby-molinillo. Preparing to unpack .../ruby-molinillo_0.2.3-1_all.deb ... Unpacking ruby-molinillo (0.2.3-1) ... Selecting previously unselected package ruby-net-http-persistent. Preparing to unpack .../ruby-net-http-persistent_2.9-3_all.deb ... Unpacking ruby-net-http-persistent (2.9-3) ... Selecting previously unselected package ruby-thor. Preparing to unpack .../ruby-thor_0.19.1-2_all.deb ... Unpacking ruby-thor (0.19.1-2) ... Selecting previously unselected package bundler. Preparing to unpack .../bundler_1.10.6-2_all.deb ... Unpacking bundler (1.10.6-2) ... Selecting previously unselected package libxslt1.1:amd64. Preparing to unpack .../libxslt1.1_1.1.28-2.1_amd64.deb ... Unpacking libxslt1.1:amd64 (1.1.28-2.1) ... Selecting previously unselected package rake. Preparing to unpack .../archives/rake_10.4.2-2_all.deb ... Unpacking rake (10.4.2-2) ... Selecting previously unselected package ruby-i18n. Preparing to unpack .../ruby-i18n_0.7.0-2_all.deb ... Unpacking ruby-i18n (0.7.0-2) ... Selecting previously unselected package ruby-json. Preparing to unpack .../ruby-json_1.8.3-1+b1_amd64.deb ... Unpacking ruby-json (1.8.3-1+b1) ... Selecting previously unselected package ruby-atomic. Preparing t
Bug#808843: marked as pending
tag 808843 pending thanks Hello, Bug #808843 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/python-pyramid.git;a=commitdiff;h=52a8f94 --- commit 52a8f944af07a44758c6f5b8f815856d77787b59 Author: Barry Warsaw Date: Mon Jan 4 13:42:53 2016 -0500 New upstream release. * Team upload. * New upstream release. (Closes: #808843) * d/watch: Adjust filenamemangle to account for seemingly recent uscan behavior change where it doesn't strip everything before the last slash. diff --git a/debian/changelog b/debian/changelog index 6c4088e..c57226b 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +python-pyramid (1.6+dfsg-1) UNRELEASED; urgency=medium + + * Team upload. + * New upstream release. (Closes: #808843) + * d/watch: Adjust filenamemangle to account for seemingly recent uscan +behavior change where it doesn't strip everything before the last slash. + + -- Barry Warsaw Mon, 04 Jan 2016 13:39:41 -0500 + python-pyramid (1.5.7+dfsg-1) unstable; urgency=medium * Team upload.
Processed: fixed 809584 in 3.9.4+dfsg-2
Processing commands for cont...@bugs.debian.org: > fixed 809584 3.9.4+dfsg-2 Bug #809584 [src:lizardfs] lizardfs: FTBFS: Unknown CMake command "check_include_files". Marked as fixed in versions lizardfs/3.9.4+dfsg-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 809584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809764: [Debian-ha-maintainers] Bug#809764: Bug#809764: libqb6-dev and libqb-dev: error when trying to install together
> > "In case several development versions of a library exist, you may need > > to use dpkg's Conflicts mechanism" > > I think the Policy means this between versions of the same library > (eg. your libqb6-dev and a later libqb7-dev). > > But anyway, this is a more broader problem: there are now two libraries > named libqb in Debian. Currently we provide libqb0 and libqb-dev > packages, you provide libqb6 and libqb6-dev and we have a guarranteed > file name conflict in the dev packages. It's already confusing, but > there's no telling when the package names themselves will clash. The > absolutely best solution would be persuading an upstream to change the > library name. Webcamoid seems to be the newer project, therefore its Qb > library might have seen less use, so I don't find it unreasonable to > approach its maintainer with this problem. I was thinking about talk to the upstream. But it will take more time to solve the situation. What about the bug ? regards, -- Herbert Parentes Fortes Neto (hpfn)
Bug#809764: [Debian-ha-maintainers] Bug#809764: Bug#809764: libqb6-dev and libqb-dev: error when trying to install together
Herbert Fortes (hpfn) writes: > "In case several development versions of a library exist, you may need > to use dpkg's Conflicts mechanism" I think the Policy means this between versions of the same library (eg. your libqb6-dev and a later libqb7-dev). But anyway, this is a more broader problem: there are now two libraries named libqb in Debian. Currently we provide libqb0 and libqb-dev packages, you provide libqb6 and libqb6-dev and we have a guarranteed file name conflict in the dev packages. It's already confusing, but there's no telling when the package names themselves will clash. The absolutely best solution would be persuading an upstream to change the library name. Webcamoid seems to be the newer project, therefore its Qb library might have seen less use, so I don't find it unreasonable to approach its maintainer with this problem. -- Regards, Feri.
Processed: Re: Bug#809570: roxterm: FTBFS: MaitchNotFoundError: Resource '[..]/debian/build/po/glade.pot'
Processing commands for cont...@bugs.debian.org: > block 809570 by 809846 Bug #809570 [src:roxterm] roxterm: FTBFS: MaitchNotFoundError: Resource '[..]/debian/build/po/glade.pot' 809570 was not blocked by any bugs. 809570 was not blocking any bugs. Added blocking bug(s) of 809570: 809846 > thanks Stopping processing here. Please contact me if you need assistance. -- 809570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#808205: libc6: Unrecognized relocation when compiling
On 2016-01-05 00:55, Mahesh Kronecker wrote: > Dear all, > I am on Debian/Jessie, not sid nor Stretch, but I can reproduce the hello.c > bug as done by John Aston: > > $ gcc hello.c -o hello > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/crti.o: > réadressage inconnu (0x2a) dans la section « .init » > /usr/bin/ld: édition de lien finale en échec: Mauvaise valeur > collect2: error: ld returned 1 exit status > > Packages: > -- > sudo apt-cache show binutils > Package: binutils > Version: 2.25-5 > > Package: libc6-dev > Source: glibc > Version: 2.19-18+deb8u1 > > sudo apt-cache show libgcc1 > Package: libgcc1 > Source: gcc-4.9 (4.9.2-10) > Version: 1:4.9.2-10 > > sudo apt-cache show libc6 > Package: libc6 > Status: install ok installed > […] > Source: glibc > Version: 2.21-1 glibc version 2.21-1 has never been available in jessie... > […] > - > > Is there something wrong in my settings or is this related to the bug you are > describing in the testing versions of Debian? > I do not know what to do to fix the issue on my system. It really looks like your system have a mix of jessie and stretch or sid. Can you please try to run the following commands and send me the output: dpkg -l libc6:amd64 md5sum /usr/lib/x86_64-linux-gnu/crti.o -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#809284: marked as done (ocserv: FTBFS: ocpasswd-args.h:1:1: error: unterminated comment)
Your message dated Mon, 04 Jan 2016 17:16:57 +
with message-id
<1451927817.1522412.482520458.67684...@webmail.messagingengine.com>
and subject line Re: Bug#809284: ocserv: FTBFS: ocpasswd-args.h:1:1: error:
unterminated comment
has caused the Debian Bug report #809284,
regarding ocserv: FTBFS: ocpasswd-args.h:1:1: error: unterminated comment
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.)
--
809284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocserv
Version: 0.10.10-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
ocserv fails to build from source in unstable/amd64:
[..]
gcc -DHAVE_CONFIG_H -I. -I.. -I./../gl/ -I./../gl/ -I./ -I./../ -I./../
-I/usr/include/p11-kit-1 -I/usr/include/libnl3 -Wdate-time
-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector-strong -Wformat
-Werror=format-security -Wall -c -o ctl.pb-c.o ctl.pb-c.c
In file included from ocpasswd.c:34:0:
./ocpasswd-args.h:1:1: error: unterminated comment
/* -*- buffer-read-only: t -*- vi: set ro:
^
ocpasswd.c: In function 'main':
ocpasswd.c:367:10: warning: implicit declaration of function 'optionProcess'
[-Wimplicit-function-declaration]
optct = optionProcess(&ocpasswdOptions, argc, argv);
^
ocpasswd.c:367:25: error: 'ocpasswdOptions' undeclared (first use in this
function)
optct = optionProcess(&ocpasswdOptions, argc, argv);
^
ocpasswd.c:367:25: note: each undeclared identifier is reported only once for
each function it appears in
ocpasswd.c:374:3: warning: implicit declaration of function 'optionUsage'
[-Wimplicit-function-declaration]
optionUsage(&ocpasswdOptions, 1);
^
ocpasswd.c:378:6: warning: implicit declaration of function 'HAVE_OPT'
[-Wimplicit-function-declaration]
if (HAVE_OPT(PASSWD)) {
^
ocpasswd.c:378:15: error: 'PASSWD' undeclared (first use in this function)
if (HAVE_OPT(PASSWD)) {
^
ocpasswd.c:379:13: warning: implicit declaration of function 'OPT_ARG'
[-Wimplicit-function-declaration]
fpasswd = OPT_ARG(PASSWD);
^
ocpasswd.c:384:15: error: 'GROUPNAME' undeclared (first use in this function)
if (HAVE_OPT(GROUPNAME))
^
ocpasswd.c:390:15: error: 'LOCK' undeclared (first use in this function)
if (HAVE_OPT(LOCK))
^
ocpasswd.c:392:20: error: 'UNLOCK' undeclared (first use in this function)
else if (HAVE_OPT(UNLOCK))
^
ocpasswd.c:394:20: error: 'DELETE' undeclared (first use in this function)
else if (HAVE_OPT(DELETE))
^
Makefile:1474: recipe for target 'ocpasswd.o' failed
make[6]: *** [ocpasswd.o] Error 1
make[6]: *** Waiting for unfinished jobs
make[6]: Leaving directory
'/home/lamby/temp/cdt.20151229001944.dwCnbR40tr/ocserv-0.10.10/src'
Makefile:1491: recipe for target 'all-recursive' failed
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory
'/home/lamby/temp/cdt.20151229001944.dwCnbR40tr/ocserv-0.10.10/src'
Makefile:1155: recipe for target 'all' failed
make[4]: *** [all] Error 2
make[4]: Leaving directory
'/home/lamby/temp/cdt.20151229001944.dwCnbR40tr/ocserv-0.10.10/src'
Makefile:1010: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
'/home/lamby/temp/cdt.20151229001944.dwCnbR40tr/ocserv-0.10.10'
Makefile:951: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory
'/home/lamby/temp/cdt.20151229001944.dwCnbR40tr/ocserv-0.10.10'
dh_auto_build: make -j8 returned exit code 2
debian/rules:28: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory
'/home/lamby/temp/cdt.20151229001944.dwCnbR40tr/ocserv-0.10.10'
debian/rules:15: recipe for target 'build' failed
make: *** [build] Error 2
[..]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
ocserv.0.10.10-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
> I'm not able to reproduce this problem in an up-to-date clean sid
> chroot
Nor can I now - closing bug (in BCC).
Regards,
--
,''`.
: :' : Chris
Bug#809764: [Debian-ha-maintainers] Bug#809764: libqb6-dev and libqb-dev: error when trying to install together
On Mon, 4 Jan 2016 17:40:11 +0100
Christoph Berg wrote:
> Re: Herbert Fortes 2016-01-04
> <20160104143601.f6eaed358afd42577db72...@ig.com.br>
> > > I agree that webcamoid is who should be adapted.
> > >
> > > Using 'Conflicts' is the easy way for me. I'm not sure
> > > in how to put the file in something like /usr/lib/*/webcamoid/
> > > (it was suggested). How do I do to the file be found.
> > >
> >
> > I have this on Qb/commons.pri:
> > isEmpty(PREFIX): PREFIX = /usr
> > isEmpty(EXECPREFIX): EXECPREFIX = $${PREFIX}
> > isEmpty(LIBDIR): LIBDIR = $${EXECPREFIX}/lib
> >
> > And in debian/rules:
> > "LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH)"
> >
> > Is the search recursive ?
>
> If there are "external" users of that library, you need to keep it in
> /usr/lib or /usr/lib/$triplet.
>
> If there's only "internal" users like plugins built from the same
> source or the like, you could move it to a sub directory and then use
> linker magic (rpath, etc) to point the loader there, but that's all
> going to be a maintenance burden.
>
I read this on debian-policy:
"In case several development versions of a
library exist, you may need to use dpkg's
Conflicts mechanism"
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-dev
Can this be a good argument ?
regards,
--
Herbert Parentes Fortes Neto (hpfn)
Bug#809570: roxterm: FTBFS: MaitchNotFoundError: Resource '[..]/debian/build/po/glade.pot'
block 809570 809846 thanks It looks like xgettext's support for glade has broken. If it doesn't get fixed soon I can probably work around it by using po4a to generate glade.pot.
Bug#795237: marked as done (gpsshogi FTBFS: "undefined reference to `osl::OslConfig::openingBook" and others)
Your message dated Mon, 04 Jan 2016 17:08:34 + with message-id and subject line Bug#795237: fixed in gpsshogi 0.6.0-3+nmu2 has caused the Debian Bug report #795237, regarding gpsshogi FTBFS: "undefined reference to `osl::OslConfig::openingBook" and others 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.) -- 795237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gpsshogi Severity: serious Version: 0.6.0-3+nmu1 gpsshogi FTBFS in current sid: | gpsusi.cc:906:48: warning: ignoring return value of 'FILE* freopen(const char*, const char*, FILE*)', declared with attribute warn_unused_result [-Wunused-result] | freopen(error_log_file.c_str(), "w", stderr); | ^ | g++ -Wl,--as-needed `dpkg-buildflags --get LDFLAGS` gpsshogi.o -lboost_thread -lboost_program_options -lpthread -losl -lboost_date_time -lboost_filesystem -lboost_serialization -lboost_iostreams -lboost_system -ltcmalloc_minimal -o gpssho | gi | /usr/bin/ld: warning: libboost_program_options.so.1.55.0, needed by /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so, may conflict with libboost_program_options.so.1.58.0 | /usr/bin/ld: warning: libboost_filesystem.so.1.55.0, needed by /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so, may conflict with libboost_filesystem.so.1.58.0 | /usr/bin/ld: warning: libboost_serialization.so.1.55.0, needed by /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so, may conflict with libboost_serialization.so.1.58.0 | /usr/bin/ld: warning: libboost_iostreams.so.1.55.0, needed by /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so, may conflict with libboost_iostreams.so.1.58.0 | /usr/bin/ld: warning: libboost_system.so.1.55.0, needed by /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so, may conflict with libboost_system.so.1.58.0 | gpsshogi.o: In function `makeWeightedBook()': | /«PKGBUILDDIR»/bin/gpsshogi.cc:53: undefined reference to `osl::OslConfig::openingBook(std::__cxx11::basic_string, std::allocator > const&)' | gpsshogi.o: In function `benchmark(osl::game_playing::SearchPlayer&, std::__cxx11::basic_string, std::allocator > const&, int)': | /«PKGBUILDDIR»/bin/benchmark.h:37: undefined reference to `osl::record::csa::CsaFile::CsaFile(std::__cxx11::basic_string, std::allocator > const&)' | /«PKGBUILDDIR»/bin/benchmark.h:47: undefined reference to `osl::record::csa::show[abi:cxx11](osl::Move)' | /«PKGBUILDDIR»/bin/benchmark.h:58: undefined reference to `osl::record::csa::show[abi:cxx11](osl::Move)' | gpsshogi.o: In function `play(int, char**)': | /«PKGBUILDDIR»/bin/gpsshogi.cc:153: undefined reference to `osl::OslConfig::configuration[abi:cxx11]()' | /«PKGBUILDDIR»/bin/gpsshogi.cc:266: undefined reference to `osl::record::csa::CsaFile::CsaFile(std::__cxx11::basic_string, std::allocator > const&)' | gpsshogi.o: In function `makeWeightedBook()': | /«PKGBUILDDIR»/bin/gpsshogi.cc:53: undefined reference to `osl::OslConfig::openingBook(std::__cxx11::basic_string, std::allocator > const&)' | /«PKGBUILDDIR»/bin/gpsshogi.cc:53: undefined reference to `osl::OslConfig::openingBook(std::__cxx11::basic_string, std::allocator > const&)' | /«PKGBUILDDIR»/bin/gpsshogi.cc:53: undefined reference to `osl::OslConfig::openingBook(std::__cxx11::basic_string, std::allocator > const&)' | /«PKGBUILDDIR»/bin/gpsshogi.cc:53: undefined reference to `osl::OslConfig::openingBook(std::__cxx11::basic_string, std::allocator > const&)' | gpsshogi.o: In function `OpeningOptions::OpeningOptions()': | /«PKGBUILDDIR»/bin/options.h:141: undefined reference to `osl::OslConfig::home(std::__cxx11::basic_string, std::allocator > const&)' | /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so: undefined reference to `boost::gregorian::greg_month::get_month_map_ptr()' | collect2: error: ld returned 1 exit status Full build log attached for convenience. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) gpsshogi_0.6.0-3+nmu1_amd64-20150812-0859.build.gz Description: application/gzip signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: gpsshogi Source-Version: 0.6.0-3+nmu2 We believe that the bug you reported is fixed in the latest version of gpsshogi, 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 th
Bug#809284: ocserv: FTBFS: ocpasswd-args.h:1:1: error: unterminated comment
Hi Chris, I'm not able to reproduce this problem in an up-to-date clean sid chroot, so what's wrong? Thanks, Aron
Bug#807019: tracking bin-num - broken unison due to binnmu upload
On 2016-01-04 17:24, Stéphane Glondu wrote: Le 22/12/2015 00:38, Mehdi Dogguy a écrit : The change done in unison 2.48 to overcome this looks pretty big... I'm not sure I'll be able/willing to provide a unison2.40.102 any more. Moreover, this package was created to provide compatibility with previous Debian releases, but another change in OCaml 4.02 makes it incompatible anyway (both communicating unisons need to be compiled with the same version of OCaml in practice, which won't be the case any more when one side is Debian stable, and the other Debian testing). IMHO, that's a design flaw in Unison that cannot be easily fixed. A possible way out for stable (and old-stable) users could be to use 2.48 from backports, when 2.48 will be packaged and migrated to testing. No, 2.48 from backports will be compiled with stable's version of OCaml (4.01.0) whereas 2.48 from testing will (eventually) be compiled with testing's version of OCaml (4.02.3), making both versions incompatible. Oh, my understanding was that newer versions of Unison were not bound on an OCaml version anymore and have had worked a synchronization format which will work well with any OCaml version. Sorry if this is not the case. Personally, what I do when dealing with inter-release synchronization involves using schroot... I heard of people copying binaries around, and others recompiling unison locally on one system. I don't know which solution is the best. The situation sucks. It is possible to backport OCaml 4.02.3 (and lablgtk2 :-/) and use that from backports to build a compatible version of Unison. I realize this is a lot of work though. Regards, -- Mehdi
Bug#809712: Bug#809825: libfltk1.3-dev: fltk-config setting hardening flags
Graham Inggs writes: > Notice the additional flags that have appeared between '-lODP' and > -lfltk_gl'. Thanks for the report. I see what went wrong, and plan to upload a fix tonight (US time). Specifically, recent changes for the sake of indep-only (-A) builds accidentally caused builds covering the full range of binary packages (i.e., my initial source+amd64+all upload) to clobber the special unhardened fltk-config that debian/rules arranges to prepare. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#808205: libc6: Unrecognized relocation when compiling
Dear all,
I am on Debian/Jessie, not sid nor Stretch, but I can reproduce the hello.c bug
as done by John Aston:
$ gcc hello.c -o hello
/usr/bin/ld:
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/crti.o: réadressage
inconnu (0x2a) dans la section « .init »
/usr/bin/ld: édition de lien finale en échec: Mauvaise valeur
collect2: error: ld returned 1 exit status
Packages:
--
sudo apt-cache show binutils
Package: binutils
Version: 2.25-5
Package: libc6-dev
Source: glibc
Version: 2.19-18+deb8u1
sudo apt-cache show libgcc1
Package: libgcc1
Source: gcc-4.9 (4.9.2-10)
Version: 1:4.9.2-10
sudo apt-cache show libc6
Package: libc6
Status: install ok installed
[…]
Source: glibc
Version: 2.21-1
[…]
-
Is there something wrong in my settings or is this related to the bug you are
describing in the testing versions of Debian?
I do not know what to do to fix the issue on my system.
On Thu, 17 Dec 2015 04:31:40 -0500 John Aston wrote:
> Package: libc6
> Version: 2.21-4
> Severity: important
>
> Dear Maintainer,
>
> When attempting to compile a simple C program, the link stage fails with an
> unrecognized relocation error.
>
> This problem seems to have appeared in the latest version, 2.21-4 (and is
> also present in 2.22-0experimental which I tested before submitting); it was
> not present in 2.19-22 which I was using prior to tonight. When using
> 2.19-22 (pinned to that version after installing the package from a CD), it
> works normally. When upgraded, it fails as per below.
>
> The problem manifested in a much more complicated build process, but I can
> duplicate it with a program as simple as this:
>
> #include
> int main() {
>fprintf(stdout, "Hello, world.\n");
>return(0);
> }
>
> When compiling, the following error happens:
>
> $ gcc hello.c -o hello
> /usr/bin/ld:
> /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o:
> unrecognized relocation (0x2a) in section `.init'
> /usr/bin/ld: final link failed: Bad value
> collect2: error: ld returned 1 exit status
>
> The expected behavior is for the program to compile normally without error.
>
>
> -- System Information:
> Debian Release: stretch/sid
> APT prefers testing
> APT policy: (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages libc6 depends on:
> ii libgcc1 1:5.2.1-23
>
> libc6 recommends no packages.
>
> Versions of packages libc6 suggests:
> ii debconf [debconf-2.0] 1.5.58
> pn glibc-doc
> ii libc-l10n 2.22-0experimental1
> ii locales2.21-4
>
> -- debconf information:
> glibc/disable-screensaver:
> glibc/restart-services:
> glibc/kernel-not-supported:
> * libraries/restart-without-asking: true
> glibc/restart-failed:
> glibc/upgrade: true
> glibc/kernel-too-old:
>
>
Processed: [bts-link] source package src:python-django-extensions
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package > src:python-django-extensions > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #806364 (http://bugs.debian.org/806364) > # Bug title: python-django-extensions: FTBFS with Django 1.9 > # * https://github.com/django-extensions/django-extensions/issues/796 > # * remote status changed: closed -> open > # * reopen upstream > tags 806364 - fixed-upstream Bug #806364 [src:python-django-extensions] python-django-extensions: FTBFS with Django 1.9 Removed tag(s) fixed-upstream. > usertags 806364 - status-closed Usertags were: status-closed. Usertags are now: . > usertags 806364 + status-open There were no usertags set. Usertags are now: status-open. > thanks Stopping processing here. Please contact me if you need assistance. -- 806364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809764: [Debian-ha-maintainers] Bug#809764: libqb6-dev and libqb-dev: error when trying to install together
Re: Herbert Fortes 2016-01-04
<20160104143601.f6eaed358afd42577db72...@ig.com.br>
> > I agree that webcamoid is who should be adapted.
> >
> > Using 'Conflicts' is the easy way for me. I'm not sure
> > in how to put the file in something like /usr/lib/*/webcamoid/
> > (it was suggested). How do I do to the file be found.
> >
>
> I have this on Qb/commons.pri:
> isEmpty(PREFIX): PREFIX = /usr
> isEmpty(EXECPREFIX): EXECPREFIX = $${PREFIX}
> isEmpty(LIBDIR): LIBDIR = $${EXECPREFIX}/lib
>
> And in debian/rules:
> "LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH)"
>
> Is the search recursive ?
If there are "external" users of that library, you need to keep it in
/usr/lib or /usr/lib/$triplet.
If there's only "internal" users like plugins built from the same
source or the like, you could move it to a sub directory and then use
linker magic (rpath, etc) to point the loader there, but that's all
going to be a maintenance burden.
Christoph
--
c...@df7cb.de | http://www.df7cb.de/
signature.asc
Description: PGP signature
Bug#809764: [Debian-ha-maintainers] Bug#809764: libqb6-dev and libqb-dev: error when trying to install together
> > >
> > > As I understand, 'Conflicts' can be a solution. The packages
> > > are for complete different use. And they are *-dev packages.
> >
> > Policy says Conflicts should be avoided if the packages are doing
> > something different. It would be bad user experience if a system
> > running pacemaker/corosync couldn't have the webcamoid stuff installed
> > in parallel.
> >
> > Though given the problem is only between -dev packages, I'd guess
> > using Conflicts would be okayish.
> >
> > As webcamoid is the newer package, the problem should probably first
> > fixed on that side. Herbert, can you arrange that?
> >
>
> I agree that webcamoid is who should be adapted.
>
> Using 'Conflicts' is the easy way for me. I'm not sure
> in how to put the file in something like /usr/lib/*/webcamoid/
> (it was suggested). How do I do to the file be found.
>
I have this on Qb/commons.pri:
isEmpty(PREFIX): PREFIX = /usr
isEmpty(EXECPREFIX): EXECPREFIX = $${PREFIX}
isEmpty(LIBDIR): LIBDIR = $${EXECPREFIX}/lib
And in debian/rules:
"LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH)"
Is the search recursive ?
regards,
--
Herbert Parentes Fortes Neto (hpfn)
Bug#809844: sosreport: Please backport CVE-2015-7529 to the stable release
Package: sosreport Version: 3.2-2 Severity: critical Tags: security Justification: root security hole -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sosreport depends on: ii python3-six 1.8.0-1 pn python3:any sosreport recommends no packages. sosreport suggests no packages. -- debconf information excluded
Bug#809764: [Debian-ha-maintainers] Bug#809764: libqb6-dev and libqb-dev: error when trying to install together
On Mon, 4 Jan 2016 11:12:06 +0100 Christoph Berg wrote: > Re: Herbert Fortes (hpfn) 2016-01-04 <5689ac0b.4050...@ig.com.br> > > >This is a serious bug as it makes installation fail, and violates > > >sections 7.6.1 and 10.1 of the policy. An optimal solution would > > >consist in only one of the packages installing that file, and renaming > > >or removing the file in the other package. Depending on the > > >circumstances you might also consider Replace relations or file > > >diversions. If the conflicting situation cannot be resolved then, as a > > >last resort, the two packages have to declare a mutual > > >Conflict. Please take into account that Replaces, Conflicts and > > >diversions should only be used when packages provide different > > >implementations for the same functionality. > > > > As I understand, 'Conflicts' can be a solution. The packages > > are for complete different use. And they are *-dev packages. > > Policy says Conflicts should be avoided if the packages are doing > something different. It would be bad user experience if a system > running pacemaker/corosync couldn't have the webcamoid stuff installed > in parallel. > > Though given the problem is only between -dev packages, I'd guess > using Conflicts would be okayish. > > As webcamoid is the newer package, the problem should probably first > fixed on that side. Herbert, can you arrange that? > I agree that webcamoid is who should be adapted. Using 'Conflicts' is the easy way for me. I'm not sure in how to put the file in something like /usr/lib/*/webcamoid/ (it was suggested). How do I do to the file be found. regards, -- Herbert Parentes Fortes Neto (hpfn)
Bug#809843: autopsy: maintainer address bounces
Source: autopsy Source-Version: 2.24-1.1 Tags: sid Severity: serious The maintainer address for autopsy bounces, see below. Ansgar Mail Delivery System writes: > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > martig...@debian.org > Unrouteable address > > -- This is a copy of the message, including all the headers. -- > [...] > To: Lorenzo Martignoni , Andreas Metzler > [...] > Subject: autopsy_2.24-1.1_amd64.changes ACCEPTED into unstable > Message-Id: > Date: Mon, 04 Jan 2016 13:48:49 + > > > > Accepted: > > Format: 1.8 > Date: Sun, 20 Dec 2015 14:02:36 +0100 > Source: autopsy > Binary: autopsy > Architecture: source all > Version: 2.24-1.1 > Distribution: unstable > Urgency: medium > Maintainer: Lorenzo Martignoni > Changed-By: Andreas Metzler > Description: > autopsy- graphical interface to SleuthKit > Closes: 803030 > Changes: > autopsy (2.24-1.1) unstable; urgency=medium > . >* Non-maintainer upload. >* Use "find -perm /x" instead of "find -perm +x". Closes: #803030 > Checksums-Sha1: > fb773608c2f05c00b655128e947f0ec6672f8bb6 1679 autopsy_2.24-1.1.dsc > f74dbb489b381c8c30a1642b3829566ba67ae631 15145 autopsy_2.24-1.1.diff.gz > 1ab49e0a0b826e0b737e870c1956a3d3f9566b43 335922 autopsy_2.24-1.1_all.deb > Checksums-Sha256: > 436232a66253ab4b21e2798c8a746ac48e8d2103e3bc6154c84a99e7d9b7721f 1679 > autopsy_2.24-1.1.dsc > 9f62099bac1a85a5a4941df12c9ffcf2360d6a7b077d2807737523466db377cd 15145 > autopsy_2.24-1.1.diff.gz > 3d0bafd82970a08c0f03c67772aa9c4942f55ac82c059ab8f23ef2c8bc83825e 335922 > autopsy_2.24-1.1_all.deb > Files: > 29e35b5081ef364448140d3a4dc1504f 1679 admin optional autopsy_2.24-1.1.dsc > c3c59d64e6c6cdd525e20bafe1f1787d 15145 admin optional > autopsy_2.24-1.1.diff.gz > 0e461602f3f72ea560c7490063fe5e8f 335922 admin optional > autopsy_2.24-1.1_all.deb > > > > Thank you for your contribution to Debian.
Bug#807019: tracking bin-num - broken unison due to binnmu upload
Le 22/12/2015 00:38, Mehdi Dogguy a écrit : >> The change done in unison 2.48 to overcome this looks pretty big... I'm >> not sure I'll be able/willing to provide a unison2.40.102 any more. >> Moreover, this package was created to provide compatibility with >> previous Debian releases, but another change in OCaml 4.02 makes it >> incompatible anyway (both communicating unisons need to be compiled with >> the same version of OCaml in practice, which won't be the case any more >> when one side is Debian stable, and the other Debian testing). IMHO, >> that's a design flaw in Unison that cannot be easily fixed. >> > > A possible way out for stable (and old-stable) users could be to use 2.48 > from backports, when 2.48 will be packaged and migrated to testing. No, 2.48 from backports will be compiled with stable's version of OCaml (4.01.0) whereas 2.48 from testing will (eventually) be compiled with testing's version of OCaml (4.02.3), making both versions incompatible. Personally, what I do when dealing with inter-release synchronization involves using schroot... I heard of people copying binaries around, and others recompiling unison locally on one system. I don't know which solution is the best. The situation sucks. Cheers, -- Stéphane
Bug#705092: Current state of this bug?
Dear Robin. I think that this bug is resolved after python-ase 3.8.1.3440-0.1. This is because all scripts were renamed from this version to "ase-" thanks. -- Regards, Hajime MIZUNO Key fingerprint = 9B07 B934 B70C 8482 8892 E276 502E 0713 4EEF 9E8D
Bug#809763: cabal-helper: no binary in cabal-helper package
Control: tag -1 + pending On Sun, 3 Jan 2016 20:52:52 +0100 Tomas Janousek wrote: > Package: cabal-helper > Version: 0.6.2.0-1 > Severity: grave > Justification: renders package unusable > > There's no cabal-helper binary in the package: > > > $ dpkg -L cabal-helper > > /. > > /usr > > /usr/share > > /usr/share/doc > > /usr/share/doc/cabal-helper > > /usr/share/doc/cabal-helper/changelog.Debian.gz > > /usr/share/doc/cabal-helper/buildinfo_i386.gz > > /usr/share/doc/cabal-helper/copyright > > Probably caused by the install file being called > debian/haskell-cabal-helper-utils.install but there being no mention of > "utils" anywhere in debian/control. Tank you for your report! Yes indeed, the file is missing. I think installing it to /usr/lib would be sensible, as Debian doesn't have /usr/libexec. > Also, ghc-mod seems to expect cabal-helper in /usr/libexec: > > > $ ghc-mod list > > ghc-mod: Could not find $libexecdir/cabal-helper-wrapper > > > > If you are a developer set the environment variable > > `cabal_helper_libexecdir' to override $libexecdir[1]. The following will > > work in the cabal-helper source tree: > > > > $ export cabal_helper_libexecdir=$PWD/dist/build/cabal-helper-wrapper > > > > [1]: /usr/libexec > > > > If you don't know what I'm talking about something went wrong with your > > installation. Please report this problem here: > > > > https://github.com/DanielG/cabal-helper/issues > > Shall I open another bug or can you check that as well? It would be good if you open another report for ghc-mod, so it won't migrate before its libexecdir is set to /usr/lib. Regards Sven pgpRtqrkYkSba.pgp Description: Digitale Signatur von OpenPGP
Bug#804558: [Python-modules-team] Bug#804558: tweepy: FTBFS: ImportError: No module named {unittest2, vcr}
On Jan 04, 2016, at 10:43 AM, Carl Chenet wrote: >We have a RC bug for Tweepy in Debian because the unittest2 and/or vcr >Python modules are not packaged for Debian Not correct. Both packages are in Debian for both Python 2 and 3. We have unittest2 1.1.0-6 and vcr 1.7.3-1 There must be some other build problem going on. >Tell me if I'm wrong but unittests executions are not mandatory by >Debian policy while building a Debian package. Probably not mandatory, but good practice. Sometimes it's not possible to run a package's test suite at build time for various reasons. In those cases, I think it's good practice to write a DEP-8 autopkgtest to at least test the installed package. Cheers, -Barry
Processed: Re: Bug#809763: cabal-helper: no binary in cabal-helper package
Processing control commands: > tag -1 + pending Bug #809763 [cabal-helper] cabal-helper: no binary in cabal-helper package Added tag(s) pending. -- 809763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#808466: update error at configure
Package: redmine Version: 3.0~20140825-8 Followup-For: Bug #808466 I believe this may be related to rails updating to 4.2.x in testing, whereas redmine seems to still be searching for 4.1.x given the error message? Hacking on /usr/share/redmine/Gemfile to change it to look for 4.2.x (making the unreasonable assumption that this is OK) then leads to: Could not find gem 'jquery-rails (~> 3.1.1) ruby' in any of the gem sources listed in your Gemfile or available on this machine. And indeed ruby-jquery-rails is now 4.0.x. Making another unreasonable assumption that hacking on that version in the Gemfile is OK allows the postint script to finish. I haven't done significant checking to see if all of redmine, esp. jquery related functionality, actually still works with this hacking done. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages redmine depends on: ii bundler 1.10.6-2 ii dbconfig-common 1.8.58 ii debconf [debconf-2.0] 1.5.58 ii libjs-scriptaculous 1.9.0-2 ii redmine-mysql 3.0~20140825-8 ii ruby1:2.2.4 ii ruby-actionpack-action-caching 1.1.1-4 ii ruby-awesome-nested-set 3.0.0-1 ii ruby-coderay1.1.0-4 ii ruby-i18n 0.7.0-2 ii ruby-jquery-rails 4.0.5-1 ii ruby-mime-types 2.6.1-1 ii ruby-net-ldap 0.8.0-1 ii ruby-openid 2.7.0debian-1 ii ruby-protected-attributes 1.1.3-1 ii ruby-rack 1.6.4-2 ii ruby-rack-openid1.4.2-1 ii ruby-rails 2:4.2.5-1 ii ruby-rails-observers0.1.2-1 ii ruby-redcarpet 3.3.2-1+b1 ii ruby-request-store 1.1.0-1 ii ruby-rmagick2.15.4-2+b1 ii ruby1.9.1 [ruby-interpreter]1.9.3.484-2 ii ruby2.0 [ruby-interpreter] 2.0.0.484+really457-3 ii ruby2.1 [ruby-interpreter] 2.1.5-4 ii ruby2.2 [ruby-interpreter] 2.2.3-2 Versions of packages redmine recommends: ii libfcgi-ruby1.9.1 0.9.2.1-1 ii ruby-fcgi [libfcgi-ruby1.9.1] 0.9.2.1-1+b6 ii ruby-passenger 5.0.22-1 Versions of packages redmine suggests: pn bzr ii cvs 2:1.12.13+real-15 pn darcs ii git 1:2.6.4-1 ii mercurial 3.5.2-2 pn subversion -- debconf information excluded
Bug#809765: ruby-racc and racc: error when trying to install together
Control: reassign -1 ruby-racc Control: found -1 ruby-racc/1.4.14-1 Control: retitle -1 duplicates existing `racc` package On Sun, Jan 03, 2016 at 08:53:59PM +0100, Ralf Treinen wrote: > Package: racc,ruby-racc > Version: racc/1.4.12-1 > Version: ruby-racc/1.4.14-1 > Severity: serious > User: trei...@debian.org > Usertags: edos-file-overwrite > > Date: 2016-01-03 > Architecture: amd64 > Distribution: sid > [...] > Unpacking ruby-racc (1.4.14-1) ... > dpkg: error processing archive > /var/cache/apt/archives/ruby-racc_1.4.14-1_amd64.deb (--unpack): > trying to overwrite '/usr/lib/ruby/vendor_ruby/racc.rb', which is also in > package racc 1.4.12-1 > Processing triggers for libc-bin (2.21-6) ... > Processing triggers for man-db (2.7.5-1) ... > Errors were encountered while processing: > /var/cache/apt/archives/ruby-racc_1.4.14-1_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) `ruby-racc` is a new package that duplicates `racc` which is in Debian for ages. ruby-racc should be removed. signature.asc Description: PGP signature
Processed: Re: Bug#809765: ruby-racc and racc: error when trying to install together
Processing control commands: > reassign -1 ruby-racc Bug #809765 [racc,ruby-racc] ruby-racc and racc: error when trying to install together Bug reassigned from package 'racc,ruby-racc' to 'ruby-racc'. Ignoring request to alter found versions of bug #809765 to the same values previously set Ignoring request to alter fixed versions of bug #809765 to the same values previously set > found -1 ruby-racc/1.4.14-1 Bug #809765 [ruby-racc] ruby-racc and racc: error when trying to install together Marked as found in versions ruby-racc/1.4.14-1. > retitle -1 duplicates existing `racc` package Bug #809765 [ruby-racc] ruby-racc and racc: error when trying to install together Changed Bug title to 'duplicates existing `racc` package' from 'ruby-racc and racc: error when trying to install together' -- 809765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809766: ruby-test-unit and ruby-rubysl-test-unit: error when trying to install together
Hello Andrew, On Sun, Jan 03, 2016 at 08:54:58PM +0100, Ralf Treinen wrote: > Package: ruby-rubysl-test-unit,ruby-test-unit > Version: ruby-rubysl-test-unit/2.0.3-1 > Version: ruby-test-unit/3.1.5-1 > Severity: serious > User: trei...@debian.org > Usertags: edos-file-overwrite > > Date: 2016-01-03 > Architecture: amd64 > Distribution: sid > > Hi, > > automatic installation tests of packages that share a file and at the > same time do not conflict by their package dependency relationships has > detected the following problem: > > [...] > trying to overwrite '/usr/lib/ruby/vendor_ruby/test/unit.rb', which is also > in package ruby-test-unit 3.1.5-1 > Processing triggers for libc-bin (2.21-6) ... > Processing triggers for man-db (2.7.5-1) ... > Errors were encountered while processing: > /var/cache/apt/archives/ruby-rubysl-test-unit_2.0.3-1_all.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) This should be expected. Why do we need ruby-rubysl-test-unit (and ruby-rubysl)? These rubysl* packages contain the Ruby standard library, and are mostly only used with rubinius, which is an alternative Ruby interpreter that we don't have in Debian¹, so I don't see why we would need them. ¹ I tried packaging rubinius myself at some point, but gave up when they split the standard library into a gazilion independent packages that would have to be packaged independently. -- Antonio Terceiro signature.asc Description: PGP signature
Processed: Re: Bug#809707: sprockets 3.3 cannot find favico.js
Processing control commands: > severity -1 important Bug #809707 [ruby-sprockets] sprockets 3.3 cannot find favico.js Severity set to 'important' from 'grave' -- 809707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809707 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809707: sprockets 3.3 cannot find favico.js
Control: severity -1 important On Sun, Jan 03, 2016 at 12:21:48PM +0530, Pirate Praveen wrote: > package: ruby-sprockets > version: 3.3.0-1 > severity: grave > justification: fails to find assets previously found by 2.12 > Sprockets::FileNotFound: couldn't find file 'favico.js' with type > 'application/javascript' > > It was noticed by autopkgtest in ruby-rails-assets-favico.js and > confirmed by checking gem installed rails-assets-favico.js from > rails-assets.org Unless this is happening with every single assets package -- and it does not seem to be the case -- `grave` is the wrong severity. > > rails new foo > cd foo > > cat >> app/assets/javascripts/application.js < # =require favico.js > EOF > > cat >> Gemfile < source "https://rails-assets.org"; do > gem 'rails-assets-favico.js' > end > EOF > > bundle install > bundle exec rake assets:precompile This seems to be https://github.com/rails/sprockets/issues/75 ? -- Antonio Terceiro signature.asc Description: PGP signature
Bug#809832: base: fails to inser modules ext2 or ext3
Package: base Severity: critical Justification: breaks unrelated software # LANG=C mount -o ro /dev/sdc1 /mnt/disk/ mount: unknown filesystem type 'ext2' # modprobe -vv ext2 insmod /lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko libkmod: INFO ../libkmod/libkmod-module.c:829 kmod_module_insert_module: Failed to insert module '/lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko': No such file or directory ERROR: could not insert 'ext2': Unknown symbol in module, or unknown parameter (see dmesg) libkmod: INFO ../libkmod/libkmod.c:319 kmod_unref: context 0x7fa6136ae210 released /var/log/kern.log: Jan 4 11:19:50 dbdev kernel: [1561590.271996] ext2: Unknown symbol __bread_gfp (err 0) Jan 4 11:19:50 dbdev kernel: [1561590.272039] ext2: Unknown symbol __getblk_gfp (err 0) -- System Information: Debian Release: 7.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash
Bug#809831: ext2 and ext3 modules: modprobe: ERROR: could not insert 'ext2': Unknown symbol in module, or unknown parameter
Package: base Severity: critical Justification: breaks unrelated software The same probles for insert ext2 or ext3 module. # LANG=C mount -o ro /dev/sdc1 /mnt/disk/ mount: unknown filesystem type 'ext2' # modprobe -vv ext2 insmod /lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko libkmod: INFO ../libkmod/libkmod-module.c:829 kmod_module_insert_module: Failed to insert module '/lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko': No such file or directory ERROR: could not insert 'ext2': Unknown symbol in module, or unknown parameter (see dmesg) libkmod: INFO ../libkmod/libkmod.c:319 kmod_unref: context 0x7fa6136ae210 released /var/log/kern.log: Jan 4 11:19:50 dbdev kernel: [1561590.271996] ext2: Unknown symbol __bread_gfp (err 0) Jan 4 11:19:50 dbdev kernel: [1561590.272039] ext2: Unknown symbol __getblk_gfp (err 0) -- System Information: Debian Release: 7.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash
Processed: closing 798678
Processing commands for cont...@bugs.debian.org: > close 798678 Bug #798678 [src:ruby2.1] ruby2.1: Contains file released under a nonfree license Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 798678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#798678: closing 798678
close 798678 thanks This is a non-issue. See #798680 for an explanation. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798680
Bug#809712: p4vasp: FTBFS: src/cp4vasp_wrap.cpp:1239: undefined reference to `PyErr_SetString'
There was an upload of fltk1.3 between the last successful reproducible build and the failed build. Something changed the output of 'fltk-config', the flags now include '-fPIE -fpie' which cause p4vasp to FTBFS. I have filed bug #809825 against libfltk1.3-dev.
Bug#809744: marked as done (/var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure')
Your message dated Mon, 4 Jan 2016 14:03:13 +0100 with message-id <20160104130313.gl4...@piware.de> and subject line Re: Processed: Re: Bug#809744: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure' has caused the Debian Bug report #809744, regarding /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure' 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.) -- 809744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: udev Version: 228-3 Severity: grave Package installation Race Condition? Also filed bug 809743. Unpacking libpam-systemd:i386 (228-3) over (228-2+b1) ... dpkg: considering deconfiguration of ifupdown, which would be broken by installation of systemd ... dpkg: yes, will deconfigure ifupdown (broken by systemd) Preparing to unpack .../systemd_228-3_i386.deb ... De-configuring ifupdown (0.8.4) ... Unpacking systemd (228-3) over (228-2+b1) ... dpkg: considering deconfiguration of udev, which would be broken by installation of ifupdown ... dpkg: yes, will deconfigure udev (broken by ifupdown) Preparing to unpack .../ifupdown_0.8.5_i386.deb ... De-configuring udev (228-2+b1) ... /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure' dpkg: error processing archive /var/cache/apt/archives/ifupdown_0.8.5_i386.deb (--unpack): subprocess installed pre-removal script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/ifupdown_0.8.5_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: Setting up libudev1:i386 (228-3) ... dpkg: dependency problems prevent configuration of ifupdown: systemd (228-3) breaks ifupdown (<< 0.8.5~) and is unpacked but not configured. Version of ifupdown to be configured is 0.8.4. udev (228-3) breaks ifupdown (<< 0.8.5~) and is unpacked but not configured. Version of ifupdown to be configured is 0.8.4. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured Setting up udev (228-3) ... --- End Message --- --- Begin Message --- Version: 228-3 Guus Sliepen [2016-01-04 13:05 +0100]: > > > reassign -1 ifupdown > > > forcemerge 809743 -1 > > Why did you do this? There is still an actual bug in the udev package, > namely the broken prerm script. So I'm reassigning 809744 back to udev. > 809743 will still be there to track the progress on the upgradability of > ifupdown+systemd+udev. I merged them as both this and 809743 are exactly the same bug -- the broken udev prerm script in < 228-3. But I don't mind much either way -- I'm closing the udev one as it did get fixed in 228-3. I'll mark 215-17 and 228-2 as affected instead. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature --- End Message ---
Processed: found 809744 in 215-17, found 809744 in 228-2
Processing commands for cont...@bugs.debian.org: > found 809744 215-17 Bug #809744 [udev] /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure' Marked as found in versions systemd/215-17. > found 809744 228-2 Bug #809744 [udev] /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure' Marked as found in versions systemd/228-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 809744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809575: [PKG-Openstack-devel] Bug#809575: horizon: FTBFS: ImportError: cannot import name importlib
django.utils.importlib has been removed in django 1.9 [1] and this is indeed the django release available in both stretch or sid: python-django: Installed: 1.9-2 Candidate: 1.9-2 Version table: *** 1.9-2 500 500 http://http.debian.net/debian sid/main amd64 Packages 100 /var/lib/dpkg/status 1.9-1 500 500 http://http.debian.net/debian stretch/main amd64 Packages Whereas OpenStack Horizon still depends on Django < 1.9 [2] Alberto [1] https://docs.djangoproject.com/en/1.9/internals/deprecation/#deprecation-removed-in-1-9 [2] https://github.com/openstack/horizon/blob/master/requirements.txt
Bug#809260: marked as done (cacti: Latest Squeeze LTS update of Cacti breaks graph viewing (graph preview still works))
Your message dated Mon, 04 Jan 2016 12:20:25 + with message-id and subject line Bug#809260: fixed in cacti 0.8.7g-1+squeeze9+deb6u13 has caused the Debian Bug report #809260, regarding cacti: Latest Squeeze LTS update of Cacti breaks graph viewing (graph preview still works) 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.) -- 809260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cacti Version: 0.8.7g-1+squeeze9+deb6u11 Severity: grave Tags: squeeze Justification: renders package unusable -- System Information: Debian Release: 6.0.10 APT prefers squeeze-lts APT policy: (500, 'squeeze-lts'), (500, 'oldoldstable-updates'), (500, 'oldoldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) 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 cacti depends on: ii apache22.2.16-6+squeeze15Apache HTTP Server metapackage ii apache2-mpm-prefor 2.2.16-6+squeeze15Apache HTTP Server - traditional n ii dbconfig-common1.8.46+squeeze.0 common framework for packaging dat ii debconf [debconf-2 1.5.36.1 Debian configuration management sy ii libapache2-mod-php 5.3.3.1-7+squeeze28 server-side, HTML-embedded scripti ii libphp-adodb 5.10-1The ADOdb database abstraction lay ii mysql-client-5.1 [ 5.1.73-1+deb6u1 MySQL database client binaries ii php5-cli 5.3.3.1-7+squeeze28 command-line interpreter for the p ii php5-mysql 5.3.3.1-7+squeeze28 MySQL module for php5 ii php5-snmp 5.3.3.1-7+squeeze28 SNMP module for php5 ii rrdtool1.4.3-1 time-series data storage and displ ii snmp 5.4.3~dfsg-2+squeeze1 SNMP (Simple Network Management Pr ii ucf3.0025+nmu1 Update Configuration File: preserv Versions of packages cacti recommends: ii iputils-ping 3:20100418-3Tools to test the reachability of ii logrotate3.7.8-6 Log rotation utility ii mysql-server 5.5.46-0+deb6u1 MySQL database server (metapackage ii mysql-server-5.1 [mysql- 5.1.73-1+deb6u1 MySQL database server binaries and Versions of packages cacti suggests: pn php5-ldap (no description available) -- debconf information: cacti/password-confirm: (password omitted) cacti/app-password-confirm: (password omitted) cacti/mysql/admin-pass: (password omitted) cacti/mysql/app-pass: (password omitted) cacti/purge: false cacti/db/app-user: cacti cacti/passwords-do-not-match: cacti/dbconfig-remove: cacti/mysql/admin-user: root * cacti/dbconfig-install: true cacti/upgrade-backup: true cacti/missing-db-package-error: abort cacti/install-error: abort * cacti/webserver: Apache2 cacti/internal/reconfiguring: false cacti/mysql/method: unix socket cacti/database-type: mysql cacti/remote/host: cacti/remove-error: abort cacti/db/dbname: cacti cacti/remote/port: cacti/dbconfig-reinstall: false cacti/upgrade-error: abort cacti/dbconfig-upgrade: true cacti/internal/skip-preseed: false cacti/remote/newhost: Graph preview that still works : http://server/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=14 Graph URL that doesn't work : http://server/cacti/graph.php?action=view&rra_id=all&local_graph_id=115 --- End Message --- --- Begin Message --- Source: cacti Source-Version: 0.8.7g-1+squeeze9+deb6u13 We believe that the bug you reported is fixed in the latest version of cacti, 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 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated cacti 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, 04 Jan 2016 11:37:24 + Source: cacti Binary: cacti Architecture: source all Version: 0.8.7g-1+squeeze9+deb6u13 Distribution: squeeze-lts Urgency: high Maintainer: Sean Finney Changed-By: Chris Lamb Description: cacti - Fronte
Processed: Re: Processed: Re: Bug#809744: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'
Processing commands for cont...@bugs.debian.org: > unmerge 809744 Bug #809744 [ifupdown] /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure' Bug #809658 [ifupdown] ifupdown: Upgrade 0.8.5 Removes 48 Unrelated Packages e.g. linux-image, xorg, udev (Sid Unstable) Bug #809743 [ifupdown] /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure' Disconnected #809744 from all other report(s). > reassign 809744 udev Bug #809744 [ifupdown] /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure' Bug reassigned from package 'ifupdown' to 'udev'. No longer marked as found in versions ifupdown/0.8.5. Ignoring request to alter fixed versions of bug #809744 to the same values previously set > severity 809744 serious Bug #809744 [udev] /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure' Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 809658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809658 809743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809743 809744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#768618: marked as done (pacemaker: FTBFS in jessie: build-dependency not installable: libqb-dev (>= 0.16.0.real))
Your message dated Mon, 04 Jan 2016 12:02:19 + with message-id and subject line Bug#768618: fixed in pacemaker 1.1.13-1 has caused the Debian Bug report #768618, regarding pacemaker: FTBFS in jessie: build-dependency not installable: libqb-dev (>= 0.16.0.real) 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.) -- 768618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pacemaker Version: 1.1.10+git20130802-4.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > ┌──┐ > │ Install pacemaker build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > 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: > sbuild-build-depends-pacemaker-dummy : Depends: libqb-dev (>= 0.16.0.real) > but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/pacemaker_1.1.10+git20130802-4.1_jessie.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: pacemaker Source-Version: 1.1.13-1 We believe that the bug you reported is fixed in the latest version of pacemaker, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ferenc Wágner (supplier of updated pacemaker 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: Wed, 23 Dec 2015 23:16:27 +0100 Source: pacemaker Binary: pacemaker pacemaker-cli-utils pacemaker-remote pacemaker-dbg pacemaker-doc libcib4 libcib-dev libcrmcluster4 libcrmcluster-dev libcrmcommon3 libcrmcommon-dev libcrmservice3 libcrmservice-dev liblrmd1 liblrmd-dev libpe-rules2 libpe-status4 libpengine4 libpengine-dev libstonithd2 libstonithd-dev libtransitioner2 Architecture: source amd64 all Version: 1.1.13-1 Distribution: unstable Urgency: medium Maintainer: Debian HA Maintainers Changed-By: Ferenc Wágner Description: libcib-dev - Development file for pacemaker's cib library libcib4- Pacemaker libraries - CIB libcrmcluster-dev - Development file for pacemaker's crm library libcrmcluster4 - Pacemaker libraries - CRM libcrmcommon-dev - Development file for pacemaker's common library libcrmcommon3 - Pacemaker libraries - common CRM libcrmservice-dev - Development file for pacemaker's crmservice library libcrmservice3 - Pacemaker libraries - crmservice liblrmd-dev - Development file for pacemaker's lrmd library liblrmd1 - Pacemaker libraries - lrmd libpe-rules2 - Pacemaker libraries - rules for P-Engine libpe-status4 - Pacemaker libraries - status for P-Engine libpengine-dev - Development file for pacemaker's pengine library libpengine4 - Pacemaker libraries - P-Engine libstonithd-dev - Development file for pacemaker's stonith library libstonithd2 - Pacemaker libraries - stonith libtransitioner2 - Pacemaker libraries - transitioner pacemaker -
