Processed: Re: Bug#806488: view3dscene: FTBFS: v3dsceneraytrace.pas Error: Identifier not found "TImageFormat"
Processing control commands: > tags -1 pending patch Bug #806488 [src:view3dscene] view3dscene: FTBFS: v3dsceneraytrace.pas Error: Identifier not found "TImageFormat" Added tag(s) pending and patch. -- 806488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#804736: marked as done (libwfut: FTBFS: sigc++/object_slot.h: No such file or directory)
Your message dated Sat, 28 Nov 2015 10:21:19 + with message-idand subject line Bug#804736: fixed in libwfut 0.2.3-3 has caused the Debian Bug report #804736, regarding libwfut: FTBFS: sigc++/object_slot.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 804736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libwfut Version: 0.2.3-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, Olek. Automated builds of libwfut have been failing with errors of the form libtool: compile: g++ -DHAVE_CONFIG_H -I.. -I/usr/include/python2.7 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -O3 -DNDEBUG -DTIXML_USE_STL=1 -std=c++11 -I/usr/include/sigc++-2.0 -I/usr/lib/aarch64-linux-gnu/sigc++-2.0/include -c WFUT.cxx -fPIC -DPIC -o .libs/WFUT.o WFUT.cxx:3086:32: fatal error: sigc++/object_slot.h: No such file or directory compilation terminated. The only sigc++/object_slot.h I see is from sigc++ 1.2. Could you please take a look? Thanks! --- End Message --- --- Begin Message --- Source: libwfut Source-Version: 0.2.3-3 We believe that the bug you reported is fixed in the latest version of libwfut, 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. Olek Wojnar (supplier of updated libwfut 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, 21 Nov 2015 17:25:55 -0600 Source: libwfut Binary: libwfut-0.2-1 libwfut-0.2-1-dbg libwfut-0.2-dev python-libwfut-0.2 wfut Architecture: source amd64 Version: 0.2.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Olek Wojnar Description: libwfut-0.2-1 - WorldForge Update Tool (libraries) libwfut-0.2-1-dbg - WorldForge Update Tool (debugging libs) libwfut-0.2-dev - WorldForge Update Tool (development files) python-libwfut-0.2 - WorldForge Update Tool (Python bindings) wfut - WorldForge Update Tool (executable) Closes: 804736 Changes: libwfut (0.2.3-3) unstable; urgency=medium . * Add patch to remove references to sigc++ file object_slot.h -- File has been removed in newest sigc++ -- Fixes resulting build failures (Closes: #804736) * Remove auto-generated python/WFUT.cxx file from source tree * Update symbols Checksums-Sha1: b7305b22f9d5017fe010b1d40f1babb8cf5be007 2229 libwfut_0.2.3-3.dsc 94f9912f618850556d383578a06e0e3777887eb3 7392 libwfut_0.2.3-3.debian.tar.xz Checksums-Sha256: 89d27566a1332d3730381fad7fb107174f3756d312dd1172409a572d0f618340 2229 libwfut_0.2.3-3.dsc 354d59729cea35d582fca192a14a2ed8adacb6d2c98e893716d738fb5034487d 7392 libwfut_0.2.3-3.debian.tar.xz Files: c63a1c1acf5c5c1e040e9cc75858be1b 2229 libs optional libwfut_0.2.3-3.dsc 2a9c757e943b12db1260da951c4a4c67 7392 libs optional libwfut_0.2.3-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWWWhCAAoJEJFk+h0XvV02R5QQAIpVcVjeyZdopUVg3ImkvzEL jsqsDgwYTI3kF/4TxIrsmBxFDWCdsj/kDMFZnBLfPwlShrqBXLrCwuJKhuWaCHBP yIYsNfXLSlY+VVtfJCyCWtr8h6tyXJVwrxV4brW/fejVoOkAQXn5OUoKgOpi5Cs9 upyWXUCP+0pcy0vQDubrxXcIx72F99UTxx6+KwA13DPpWlRKfDS2x0lB0WZnxUmw MD9F5SxNqpaDQDCb1c95kBt1OO8aMUNN1iQrxOGUmqN6ccyIr2/zkMtYumVKeI/S 2RUlAHPUmF/5u9LPzgh7pGhrSIqJ//l75YYJiInLJqfSHSmWcagB3FhJR11r0wCw xhrMtSbgJh6WOd47l6TxitDbS/LwBLSI5UpEeqP/gSywniFoHFH9+sFXEK4j9xvl a0Vsbmx4lFmb6PN1NPB/25muN3mW4ZHHYu3Flw6YCwDZ4m371bjjx//XjuAGjdJm 9oQnpO0zIXoyi/Cu7BHU+URCisnSbq0JinYKlMw8g/WuNa5q1rLpl0noL26BNFXG CyrjBADMThnUyrBawXbmmPbwutOl+9behUBekLNk5WVVIAEdllzwbbaGWRLLJIgs ow92re9Veva6gQlQufUfIsrehTjO+UDP12FOJ0uu9jSZWXIO4eTqc14bxqrGfiId 31jX7xIl1cMBJE93b2rX =J6ID -END PGP SIGNATURE End Message ---
Bug#806518: (no subject)
I can confirm this bug, on amd64 sid. Downgrading package libept1.4.16 from version 1.0.14+b2 (in sid) to 1.0.14+b1 (which is in testing) solved the problem for me.
Processed: re: mathgl: FTBFS: json/Backend.hpp:6:1: error: expected class-name before '{' token
Processing commands for cont...@bugs.debian.org: > tags 803312 +patch Bug #803312 [src:mathgl] mathgl: FTBFS: json/Backend.hpp:6:1: error: expected class-name before '{' token Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 803312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806518: synaptic: libept.so.1.aptpkg4.16: cannot open shared object file: No such file or directory
Package: synaptic Version: 0.82 Severity: grave Dear maintainer, $ synaptic-pkexec /usr/sbin/synaptic: error while loading shared libraries: libept.so.1.aptpkg4.16: cannot open shared object file: No such file or directory I guess, it might be due to recent apt upgrade? $ locate libept.so /usr/lib/x86_64-linux-gnu/libept.so.1.aptpkg5.0 $ dpkg -S /usr/lib/x86_64-linux-gnu/libept.so.1.aptpkg5.0 libept1.4.16:amd64: /usr/lib/x86_64-linux-gnu/libept.so.1.aptpkg5.0 -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (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 synaptic depends on: ii hicolor-icon-theme 0.13-1 ii libapt-inst1.7 1.0.10.2 ii libapt-pkg4.16 1.0.10.2 ii libatk1.0-0 2.18.0-1 ii libc62.19-22 ii libcairo-gobject21.14.4-1 ii libcairo21.14.4-1 ii libept1.4.16 1.0.14+b2 ii libgcc1 1:5.2.1-26 ii libgdk-pixbuf2.0-0 2.32.2-1 ii libglib2.0-0 2.46.2-1 ii libgtk-3-0 3.18.5-1 ii libpango-1.0-0 1.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii libstdc++6 5.2.1-26 ii libvte-2.90-91:0.36.3-1 ii libx11-6 2:1.6.3-1 ii libxapian22v51.2.21-1.2 ii libxext6 2:1.3.3-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages synaptic recommends: ii libgtk2-perl 2:1.2496-3 ii policykit-10.105-14 ii rarian-compat 0.8.1-6 ii xdg-utils 1.1.1-1 Versions of packages synaptic suggests: pn apt-xapian-index ii deborphan1.7.28.8-0.2 pn dwww ii menu 2.1.47 pn software-properties-gtk ii tasksel 3.34 -- no debconf information
Processed (with 1 error): reassign 785185 to libapache2-mod-perl2, merging 803043 785185
Processing commands for cont...@bugs.debian.org: > reassign 785185 libapache2-mod-perl2 Bug #785185 [apache2-bin] apache2-bin: mpm_worker: segfaults in modperl_interp_unselect() Bug reassigned from package 'apache2-bin' to 'libapache2-mod-perl2'. Ignoring request to alter found versions of bug #785185 to the same values previously set Ignoring request to alter fixed versions of bug #785185 to the same values previously set > merge 803043 785185 Bug #803043 {Done: Niko Tyni} [libapache2-mod-perl2] mod_perl2 / Apache segfaults after upgrading from Wheezy to Jessie Unable to merge bugs because: severity of #785185 is 'important' not 'grave' done of #785185 is '' not 'Niko Tyni ' Failed to merge 803043: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 785185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785185 803043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 803043 785185
Processing commands for cont...@bugs.debian.org: > forcemerge 803043 785185 Bug #803043 {Done: Niko Tyni} [libapache2-mod-perl2] mod_perl2 / Apache segfaults after upgrading from Wheezy to Jessie Bug #785185 [libapache2-mod-perl2] apache2-bin: mpm_worker: segfaults in modperl_interp_unselect() Severity set to 'grave' from 'important' Marked Bug as done Marked as fixed in versions libapache2-mod-perl2/2.0.9~1624218-2+deb8u1 and libapache2-mod-perl2/2.0.9-1. Marked as found in versions libapache2-mod-perl2/2.0.9~1624218-2. Added tag(s) jessie. Merged 785185 803043 > thanks Stopping processing here. Please contact me if you need assistance. -- 785185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785185 803043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to xmltooling, tagging 797625
Processing commands for cont...@bugs.debian.org: > #xmltooling (1.5.6-1) unstable; urgency=medium > # > # * [c84795d] Rename libxmltooling6 package to libxmltooling6v5 > #(Closes: #797625) > # > limit source xmltooling Limiting to bugs with field 'source' containing at least one of 'xmltooling' Limit currently set to 'source':'xmltooling' > tags 797625 + pending Bug #797625 [src:xmltooling] xmltooling: transition needed for g++-5 ABIs Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 797625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#793911: groovy should not release with stretch
On Thu, 1 Oct 2015 23:38:11 +0800 =?UTF-8?B?5q635ZWf6IGw?=wrote: > On Tue, 28 Jul 2015 22:38:40 +0200 Moritz Muehlenhoff wrote: > > Package: groovy > > Severity: serious > > > > A separate source package groovy2 was uploaded, so reverse dependencies > > need to be migrated to that one and groovy removed. > > > > Cheers, > > Moritz > > > > > > Hi Moritz and all pkg-java members, > > I am wondering if it is better to upgrade groovy to the latest version > (2.4.5 as of now) and drop groovy2, and migrate all build-rdeps of old > Groovy 1.x to using a separate groovy-1.8 or groovy-1.9 package if > necessary. In the end that we get rid of groovy and remain a groovy2 > package seems odd. Anyway BND, Maven are under the similar transition. > Since GSoC I have been maintaining Gradle in Debian so I am happy and > willing to do the transition. Hi Kai-Chung, I think upgrading src:groovy to version 2.x is a good idea. Though it is more important that we upgrade all reverse dependencies of groovy 1.x to to groovy 2.x first, so that we can drop one source package before the Stretch release. These are the current reverse dependencies in unstable: freemind -> will be removed from Debian soon because we have a very similar package already (freeplane) libspring-java -> must be updated to a newer version jenkins -> unmaintainable, can be ignored red5 -> must be updated to a newer version If you want to update either libspring-java or red5, that would be a big help. Regards, Markus signature.asc Description: OpenPGP digital signature
Processed: forward 806335 to upstream
Processing commands for cont...@bugs.debian.org: > forwarded 806335 https://github.com/toastdriven/restless/issues/66 Bug #806335 [src:python-restless] python-restless: FTBFS: AttributeError: 'NoneType' object has no attribute 'set_close_callback' Set Bug forwarded-to-address to 'https://github.com/toastdriven/restless/issues/66'. > tags 806335 upstream Bug #806335 [src:python-restless] python-restless: FTBFS: AttributeError: 'NoneType' object has no attribute 'set_close_callback' Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 806335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806334: [Python-modules-team] Bug#806334: kombu: FTBFS: ImportError: cannot import name '_uuid_generate_random'
Brian Maywrites: > Don't think we can complain at Python though, looks like a private > symbol. Looks like this is a work around for a bug that was in Python 2.5. http://bugs.python.org/issue4607: >From kombu code: def uuid4(): # Workaround for http://bugs.python.org/issue4607 if ctypes and _uuid_generate_random: # pragma: no cover buffer = ctypes.create_string_buffer(16) _uuid_generate_random(buffer) return UUID(bytes=buffer.raw) return _uuid4() -- Brian May
Bug#804424: marked as done (django-localflavor: FTBFS: ImproperlyConfigured: Requested setting USE_I18N, but settings are not configured. )
Your message dated Sat, 28 Nov 2015 12:04:26 + with message-idand subject line Bug#804424: fixed in django-localflavor 1.2-1 has caused the Debian Bug report #804424, regarding django-localflavor: FTBFS: ImproperlyConfigured: Requested setting USE_I18N, but settings are not configured. 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.) -- 804424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: django-localflavor Version: 1.1-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, django-localflavor fails to build from source in unstable/amd64: [..] == ERROR: test_ZAProvinceSelect (tests.test_za.ZALocalFlavorTests) -- Traceback (most recent call last): File "tests/test_za.py", line 46, in test_ZAProvinceSelect self.assertHTMLEqual(f.render('province', 'EC'), out) File "/usr/lib/python2.7/dist-packages/django/forms/widgets.py", line 513, in render options = self.render_options(choices, [value]) File "/usr/lib/python2.7/dist-packages/django/forms/widgets.py", line 546, in render_options output.append(self.render_option(selected_choices, option_value, option_label)) File "/usr/lib/python2.7/dist-packages/django/forms/widgets.py", line 533, in render_option force_text(option_label)) File "/usr/lib/python2.7/dist-packages/django/utils/encoding.py", line 94, in force_text s = six.text_type(bytes(s), encoding, errors) File "/usr/lib/python2.7/dist-packages/django/utils/functional.py", line 143, in __bytes_cast return bytes(func(*self.__args, **self.__kw)) File "/usr/lib/python2.7/dist-packages/django/utils/translation/__init__.py", line 76, in gettext return _trans.gettext(message) File "/usr/lib/python2.7/dist-packages/django/utils/translation/__init__.py", line 56, in __getattr__ if settings.USE_I18N: File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 48, in __getattr__ self._setup(name) File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 42, in _setup % (desc, ENVIRONMENT_VARIABLE)) ImproperlyConfigured: Requested setting USE_I18N, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. -- Ran 207 tests in 0.783s FAILED (errors=175) E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd /build/django-localflavor-1.1/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover -v dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit code 13 debian/rules:5: recipe for target 'build' failed make: *** [build] Error 25 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/django-localflavor_1.1-1.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- django-localflavor.1.1-1.unstable.amd64.log.txt.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: django-localflavor Source-Version: 1.2-1 We believe that the bug you reported is fixed in the latest version of django-localflavor, 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. Orestis Ioannou (supplier of updated django-localflavor 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: Fri, 27 Nov 2015 21:05:36
Processed: Bug#806475 in apt marked as pending
Processing control commands: > tag 806475 pending Bug #806475 [apt] apt: Breaks debian-installer build, select with no read/write fds? Added tag(s) pending. -- 806475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806475: in apt marked as pending
Control: tag 806475 pending Hello, Bug #806475 in apt reported by you has been fixed in the Git repository. You can see the commit message below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/apt/apt.git/diff/?id=ebca2f2 (this message was generated automatically based on the git commit message) --- commit ebca2f254ca96ad7ad855dca6e76c9d1c792c4a0 Author: David KalnischkiesDate: Sat Nov 28 13:17:57 2015 +0100 disable privilege-drop verification by default as fakeroot trips over it Dropping privileges is an involved process for code and system alike so ideally we want to verify that all the work wasn't in vain. Stuff designed to sidestep the usual privilege checks like fakeroot (and its many alternatives) have their problem with this through, partly through missing wrapping (#806521), partly as e.g. regaining root from an unprivileged user is in their design. This commit therefore disables most of these checks by default so that apt runs fine again in a fakeroot environment. Closes: 806475
Bug#806488: view3dscene: FTBFS: v3dsceneraytrace.pas Error: Identifier not found "TImageFormat"
Control: tags -1 pending patch On 28-11-15 00:19, Michalis Kamburelis wrote: > Reason: view3dscene source code of version 3.15.0 is not compatible with > Castle Game Engine version 5.2.0. Ooo, shame on you as upstream of both ;) . But see below. > I removed the identifier TImageFormat from the public interface of > CastleImages unit. This makes me wonder, does fpc have any reasonable symbols tracking mechanism? I guess it does (at least in ppu files), so should we extend the Debian tooling dh_makeshlibs/dh_shlibsdeps to be able to handle the fpc situation? > The view3dscene sources in SVN are of course adjusted since a long > time, but there hasn't been a view3dscene release since some time. If you don't want to release newer version for these kind of incompatibilities, or if you want to go to something fully based on version control versions, than let's discuss. We can come up with working schemes if you want. I am not strict on having upstream tar balls (although it is nice that people can check the checksum of the Debian tar ball versus the one provided by upstream). So if you are more for rolling release, we could do that. > IOW, it's my fault, I broke Castle Game Engine API in 5.2.0. Could you at least communicate these kind of changes pro-active on this list or somewhere in your own domain where we can pick it up (via push communication). Or just a clear "THIS BREAKS API" note in some changelog, I scan all the changed between two versions during import of the tar ball. > I'm attaching a minimal patch that, when applied to view3dscene 3.15.0 > sources, makes them compile with Castle Game Engine 5.2.0:) Tested with > FPC 2.6.4. If possible, could you check also with 3.0.0. That was released last week and I am preparing the upload (to experimental) still. When we verified all reversed dependencies (help would be nice), I want to ask for a transition slot. Paul Paul signature.asc Description: OpenPGP digital signature
Bug#805499: treeview is marked for autoremoval from testing
Hi Sveinung, I came across this bug due to a reverse dependency which is in danger to become removed from testing. Please announce here if you have some trouble with uploading a fixed version. BTW, I strongly recommend to team maintain the package in the Debian Java team where other people could easily do team uploads. I'd volunteer to inject the packaging into pkg-java Git and do the upload if you want me to do so. If I do not hear from you until mid December I assume agreement from your side and move on to save the reverse dependency I'm interested in inside testing. Kind regards and thanks for maintaining libnanoxml2-java Andreas. On Fri, Nov 27, 2015 at 04:39:05AM +, Debian testing autoremoval watch wrote: > treeview 1.1.6.4+dfsg-1 is marked for autoremoval from testing on 2016-01-01 > > It (build-)depends on packages with these RC bugs: > 805499: libnanoxml2-java: FTBFS with bnd 2.1.0 > > > ___ > Debian-med-packaging mailing list > debian-med-packag...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging > -- http://fam-tille.de
Bug#803658: boot hangs before cryptsetup passphrase prompt
On Thu, Nov 26, 2015 at 11:41:55AM +0100, Stefano Zacchiroli wrote: > I'll eagerly wait feedback from the Plymouth maintainers on how to > help them debug this further :) [ Following up with information that Laurent asked via IRC. ] I've done "update-initramfs -k 3.16.0-4-amd64 -u" and I confirm that after that also 3.16 became broken: it hangs before asking the LUKS password, whereas it used to work before update-initramfs. Linux 4.1 still boots properly (asking the password via askpass), because I haven't update-initramfs'd it. So it is something that sneaks in upon initramfs creation, and that used not to sneak in with older plymouth versions. I can also confirm that the workaround of passing plymouth.enable=0 on the kernel cmdline sidesteps the problem. I'm now running 4.3 from experimental, which boots properly with plymouth.enable=0. Hope this helps, Cheers. -- Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Former Debian Project Leader . . . . . @zacchiro . . . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club »
Bug#788160: marked as done (elinks: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Sat, 28 Nov 2015 10:19:24 + with message-idand subject line Bug#788160: fixed in elinks 0.12~pre6-11 has caused the Debian Bug report #788160, regarding elinks: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 788160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elinks Version: 0.12~pre6-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.mainstscript. Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (usually somewhere in the middle...): 0m32.0s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/elinks/changelog.Debian.gz (elinks) != /usr/share/doc/elinks-data/changelog.Debian.gz (elinks-data) /usr/share/doc/elinks -> elinks-data /usr/share/doc/elinks/changelog.gz (elinks) != /usr/share/doc/elinks-data/changelog.gz (elinks-data) /usr/share/doc/elinks -> elinks-data /usr/share/doc/elinks/copyright (elinks) != /usr/share/doc/elinks-data/copyright (elinks-data) /usr/share/doc/elinks -> elinks-data /usr/share/doc/elinks/examples (elinks) != /usr/share/doc/elinks-data/examples (elinks-data) /usr/share/doc/elinks -> elinks-data /usr/share/doc/elinks/examples/elinks.config (elinks) != /usr/share/doc/elinks-data/examples/elinks.config (?) /usr/share/doc/elinks -> elinks-data cheers, Andreas elinks_0.12~pre6-7.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: elinks Source-Version: 0.12~pre6-11 We believe that the bug you reported is fixed in the latest version of elinks, 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 788...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Moritz Muehlenhoff (supplier of updated elinks 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, 28 Nov 2015 09:31:42 +0100 Source: elinks Binary: elinks elinks-data elinks-doc Architecture: source all amd64 Version: 0.12~pre6-11 Distribution: unstable Urgency: medium Maintainer: Moritz Muehlenhoff Changed-By: Moritz Muehlenhoff Description: elinks - advanced text-mode WWW browser elinks-data - advanced text-mode WWW browser - data files elinks-doc - advanced text-mode WWW browser - documentation Closes: 788160 Changes: elinks (0.12~pre6-11) unstable; urgency=medium . * Add maint script for dir_to_symlink (Closes: #788160) Checksums-Sha1: 6764b07926b2b6d21a1302835e67ff576cd138c6 2058 elinks_0.12~pre6-11.dsc
Processed: tagging 806326, tagging 806326, tagging 803472
Processing commands for cont...@bugs.debian.org: > tags 806326 + pending Bug #806326 [apache2] apache2: trying to overwrite '/etc/apache2/mods-available/macro.load', which is also in package libapache2-mod-macro 1.1.11-2 Added tag(s) pending. > tags 806326 + jessie Bug #806326 [apache2] apache2: trying to overwrite '/etc/apache2/mods-available/macro.load', which is also in package libapache2-mod-macro 1.1.11-2 Added tag(s) jessie. > tags 803472 + pending Bug #803472 [apache2-utils] apache2-utils: split-logfile crashes with vhost_combined logs Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 803472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803472 806326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#803312: mathgl: FTBFS: json/Backend.hpp:6:1: error: expected class-name before '{' token
tags 803312 +patch thanks mathgl fails to build from source in unstable/amd64: I just fixed this in raspbian, it was a simple case of a missing include. Debdiff at http://plugwash.raspbian.org/mathgl_2.3.3-3+rpi1.debdiff no intent to nmu in Debian.
Processed: tagging 806326
Processing commands for cont...@bugs.debian.org: > # Only marked as found in the jessie branch anyway > tags 806326 - jessie Bug #806326 [apache2] apache2: trying to overwrite '/etc/apache2/mods-available/macro.load', which is also in package libapache2-mod-macro 1.1.11-2 Removed tag(s) jessie. > thanks Stopping processing here. Please contact me if you need assistance. -- 806326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806541: diet: FTBFS with GCC 5: Gcc should (and does indeed) support inlining !
Source: diet Version: 2.8.0-1 Severity: serious Tags: sid Justification: fails to build from source (but built successfully in the past) diet FTBFS with GCC 5 in sid: [...] -- Checking C compiler for inlining support. -- Checking C compiler for inline. -- Checking C compiler for __inline__. -- Checking C compiler for __inline. CMake Error at Cmake/ConfigureCCompiler.cmake:27 (MESSAGE): Gcc should (and does indeed) support inlining ! Call Stack (most recent call first): CMakeLists.txt:336 (include) [...] Full build log attached. Andreas sid.build.gz Description: application/gzip
Bug#761568: diet: FTBFS: convert: unable to open file `/tmp/magick-229129QKrUoVzzgMw': No such file or directory @ error/constitute.c/ReadImage/540.
On Fri, 23 Oct 2015 06:40:02 +0100 David J C MacKay> This bug still exists on macos as of October 2015: [OS X Yosemite 10.10.3] > > using convert that was installed with ImageMagick by macport [version > number of convert shown below] > > It seems the error message is being caused by uniconvertor not being found. Which would imply something is missing a (Build-)Depends: python-uniconvertor but that package is orphaned and RC buggy. Andreas
Bug#806509: libept1.5.0 and libept1.4.16: error when trying to install together
Control: subscribe -1 j...@debian.org On Sat, Nov 28, 2015 at 08:26:45AM +0100, Ralf Treinen wrote: > Package: libept1.4.16,libept1.5.0 > Version: libept1.4.16/1.0.14+b2 > Version: libept1.5.0/1.1+nmu2 > Severity: serious > User: trei...@debian.org > Usertags: edos-file-overwrite > > Date: 2015-11-28 > 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: That got ugly temporarily due to a binNMU that went wrong and produced a library with the wrong soname. We could probably Replace libept1.4.16 (= 1.0.14+b2) or something (and conflict with that build). The broken libept binNMU was in unstable for less than 24 hours though (excluding non-Linux ports, for which it still exists, because the current build FTBFS due to O_PATH being undefined, which is easy to fix). What do you think? -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to (`inline'). Thank you.
Bug#806545: backintime-gnome,backintime-kde: transitional packages not installable
Package: backintime-gnome,backintime-kde Version: 1.1.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. backintime-gnome,backintime-kde are trnsitional packages depending on backintime-qt4, but that has Package: backintime-qt4 Version: 1.1.6-1 Replaces: backintime-gnome, backintime-kde, backintime-kde4 Conflicts: backintime-gnome, backintime-kde, backintime-kde4 rendering the transitional ones uninstallable. These should probably be versioned Breaks+Replaces instead: Breaks: backintime-gnome (<< 1.1.6), backintime-kde (<< 1.1.6) Replaces: backintime-gnome (<< 1.1.6), backintime-kde (<< 1.1.6), backintime-kde4 Conflicts: backintime-kde4 Andreas
Bug#804452: marked as done (httperf: FTBFS: Uses SSLv3 method)
Your message dated Sat, 28 Nov 2015 18:20:21 + with message-idand subject line Bug#804452: fixed in httperf 0.9.0-3 has caused the Debian Bug report #804452, regarding httperf: FTBFS: Uses SSLv3 method 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.) -- 804452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: httperf Version: 0.9.0-2 Severity: serious Control: block 797926 by -1 Hi, You have this code in httperf.c: /* for some strange reason, SSLv23_client_method () doesn't work here */ ssl_ctx = SSL_CTX_new (SSLv3_client_method ()); SSLv3 has been removed in unstable. Please use the SSLv23 method instead. I have no idea why it wouldn't work. Kurt --- End Message --- --- Begin Message --- Source: httperf Source-Version: 0.9.0-3 We believe that the bug you reported is fixed in the latest version of httperf, 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. Emanuele Rocca (supplier of updated httperf 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, 28 Nov 2015 18:30:31 +0100 Source: httperf Binary: httperf Architecture: source amd64 Version: 0.9.0-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Emanuele Rocca Description: httperf- HTTP server performance tester Closes: 804452 Changes: httperf (0.9.0-3) unstable; urgency=medium . * QA upload. * Use SSLv23_client_method instead of SSLv3_client_method (Closes: #804452) * Build with default Debian compiler flags. * Maintainer field set to QA Group. * Bump Standards-Version to 3.9.6. * Use dh_installman instead of dh_installmanpages. * Avoid starting synopsis with an article. * Add missing recommended debian/rules target: build-arch and build-indep. Checksums-Sha1: d2c9c39df3269a0e4473be3f454b6da91d176020 1851 httperf_0.9.0-3.dsc c77622579f66a525c6408a76956a0bf310eadc16 6052 httperf_0.9.0-3.diff.gz 5fa9c195304e93b31a70c4ba83e13e49f59c6405 66358 httperf_0.9.0-3_amd64.deb Checksums-Sha256: eb14e5ebcee77d95c125bd03043b9a16d8c27ff18253199b6ef1847e2ed5cc1b 1851 httperf_0.9.0-3.dsc e0608bc601faf81957d3b0ff61ae9fdb7fa01eb1b4ccfb69b97d9113b12c039c 6052 httperf_0.9.0-3.diff.gz ffdcae3f6cd357bcc878f7288243035640ff88fee79331b3302508e90e0394fc 66358 httperf_0.9.0-3_amd64.deb Files: b0861ab3c9d73c885c27a4094136fa19 1851 web optional httperf_0.9.0-3.dsc 14d443ad9d40cbb8c6567206acdb09cb 6052 web optional httperf_0.9.0-3.diff.gz ea9df0ee6b28a079d8ff1396c08be788 66358 web optional httperf_0.9.0-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWWenQAAoJENUIWgdQ/bej0tQP/0SWeP5IT21/iXNQHwTLPaWn HshqkBtkQbbol5UomSfZBGq3ixGLVR7ZeqNpDG2wX2XP2IjhLY3Qd2eBcG/2LMqv kIjILwqd5XDy35OL51wH+gnsfFiEhZmI6FL2VvgSKL5IM0KiP0VrOuHriM1KsR7j +4A0lQwsv/ga3gtj/p8/Kc/3Tg1IjJwa3SArFXsopRAr5PG1EOR5IdXJLNOU7osA rkxI0+U59Hr+FRy8u/4w/XKBb98X57PqMPcEe7JCwEP2uSzu2FtFc//shkTv1/os luIE9fOvNsJaDMV1hEB6CoM/jry99XZjDl5ro5Q8Nv1yKd8eB7tdJWk0qZ8uoB20 bmNIK+olvcIACfeH2qh1ZnEf7dmS6lOLom6+fWnvFXZP0nu3gFHUjC9oyylNOiTN rqXnHeJeb81itnULl82O5pZSke13onaTsYq8FZbqwdr6O5omFPGPSSS3MGtIog2E v4awlqso+AYQ76ePaHebX3B70HjTWgguLcrSilPzE14D/qbGwk+8SOcKjRTRjLdR 6hFSR4/DxH43S4dtJ6j609Zt3sIaoZRrq+XhVA72wYqNJ8l/N1NJyHKk7Bn6gPIV P8/aW3bnaTaJI1LpsvMsb3/rR7r3s/Q4LRg1tL7jiuZB2KAKv0LTTHHjiYwr4E7w c1H9dl5Lkst4ykVyLVey =iq58 -END PGP SIGNATURE End Message ---
Bug#794927: openstack-dashboard: fails to install: django_pyscss.compressor.DjangoScssFilter: not found
Followup-For: Bug #794927 Hi, is this bug fixed in sid? The bug metadata only considers it as fixed in stretch and blocks migration. This is caused by the stretch changelog entry not being part of the sid changelog. Andreas
Bug#801937: marked as done (python-django-tagging: Fails to build from source with Django 1.8)
Your message dated Sat, 28 Nov 2015 15:50:14 + with message-idand subject line Bug#801937: fixed in python-django-tagging 1:0.4-1 has caused the Debian Bug report #801937, regarding python-django-tagging: Fails to build from source with Django 1.8 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.) -- 801937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-django-tagging Version: 1:0.3.1-4 Severity: important User: python-dja...@packages.debian.org Usertags: django18 django18-ftbfs Hello, while preparing to upload Django 1.8 to unstable, I rebuilt all reverse build-dependencies of python-django. Among those I noticed that python-django-tagging fails to build. Please update your package to work with Django 1.8 as I will upload it to unstable at the start of November 2015 (and the same time raise the severity of this bug to serious). Django 1.8.5 is available in experimental so that you can easily try it out. The failing build log of your package is available here: https://people.debian.org/~hertzog/django18-rebuild/python-django-tagging_1:0.3.1-4 Thank you in advance! --- End Message --- --- Begin Message --- Source: python-django-tagging Source-Version: 1:0.4-1 We believe that the bug you reported is fixed in the latest version of python-django-tagging, 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 801...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Genannt (supplier of updated python-django-tagging 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, 28 Nov 2015 16:31:32 +0100 Source: python-django-tagging Binary: python-django-tagging Architecture: source all Version: 1:0.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Jonas Genannt Description: python-django-tagging - Generic tagging application for Django projects Closes: 801937 Changes: python-django-tagging (1:0.4-1) unstable; urgency=medium . * Team upload. [ Raphaël Hertzog ] * Drop myself from Uploaders. . [ Jonas Genannt ] * Imported Upstream version 0.4 (Closes: #801937) * d/control: - changed homepage - updated to pybuild - changed my email to @debian.org * d/watch: updated to pypi service * removed django-1.7-compat.patch * d/p/series: disabled patches * d/docs: install new docs Checksums-Sha1: c4541dbdf6c51147832f80e7cd21252d2b6c3add 2173 python-django-tagging_0.4-1.dsc 1f739d52ac2e4331e8b484ad3269b3900cd6d739 44225 python-django-tagging_0.4.orig.tar.gz 3734a066c2c50eea5fa4f683172cc323d3728c7a 5264 python-django-tagging_0.4-1.debian.tar.xz 7c478c5b0e97c82a4f1f6fc795ffbad48bb88c90 36614 python-django-tagging_0.4-1_all.deb Checksums-Sha256: 3b51e07e3a65c4945efc6ffdbd15cb7288a39ccfdd37a1a2b0323987fb54be65 2173 python-django-tagging_0.4-1.dsc 033e3d1b352f0dacdf8588dc83521ac602a020f34f4c1c389912eaff2915e557 44225 python-django-tagging_0.4.orig.tar.gz f376209fdb4fa2e2275a7a96e127bf86d2bfed724f453c0765e5a3bc534df68b 5264 python-django-tagging_0.4-1.debian.tar.xz 11e76aae80dd40f0f68726dd7c7978b234861116b6d59f7f608fe45d9783871d 36614 python-django-tagging_0.4-1_all.deb Files: ae56b919c14607f00bfe0606d67c37e0 2173 python optional python-django-tagging_0.4-1.dsc 66ce11896494171fef93bde65871bbd7 44225 python optional python-django-tagging_0.4.orig.tar.gz ace98bfcc61cb057fc0172777c9b0a2c 5264 python optional python-django-tagging_0.4-1.debian.tar.xz 9d7017f1760ebeb92a170440598a1f68 36614 python optional python-django-tagging_0.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWWcoAAAoJEPBM7/YBbP/QyhgP/RjXhnE5zIJF24l4k+dl4Icu rqP5ebVl9rGDoxjxtLs9GWQWB5hP6SfIfWsyJE1Dfw3IbrSJRS4Q4yAnnPy/h1L/ 4sS7gfpq16kQAGuEjk6UhUrbNPqiJCo6venx5p7Xm1Ns5U4/B96ZofUq4cp7e86r leh8koBOv2MuET+Nk6T4oAFNdrvN/eBlhOYsYH9gNNFOXlyDKTVDDrDz0jqnyjAF AC00RPH+Bw2YcBIbTjcAY5OdYKjV1UaXBPQK4NPpfPP4+05np6xsm4SxVfPdoJnz
Bug#805828: mysql-server-5.6: upgrade didn't work, package unusable, mysql does not start
Hi, Do you have steps to reproduce this please? What makes you think it is a bug in the packaging as opposed to a configuration problem on your system? On Sun, Nov 22, 2015 at 10:02:05PM +0100, jpp wrote: > The /var/lib/mysql is a symlinj to another location on another disk. I'm not aware of any path in the maintainer scripts that will create this as a symlink. Is this something you have configured yourself? > /etc/mysql/mysql.cnf [Errno 2] No such file or directory: > u'/etc/mysql/mysql.cnf' Again I'm not aware of a path that would cause this to not exist. IIRC it is a conffile shipped by mysql-server-5.6. > 2015-11-22 21:53:53 4936 [ERROR] Fatal error: Can't open and lock > privilege tables: Table 'mysql.user' doesn't exist This I have seen. I think upstream know more about it, but I don't recall the details. Have you ever installed MariaDB? Because the migration path from MySQL back to MariaDB isn't automatic. > Severity: critical > Justification: causes serious data loss I don't think this is justified until we can determine that this is really a bug. For that we need steps to reproduce please. You said that you found this on a test server. Can you restore the test server to find out what the state of the system was before you attempted the upgrade? Thanks, Robie
Bug#806544: libical-parser-sax-perl: FTBFS: t/01parse.t failure
Package: libical-parser-sax-perl Version: 1.09-3 Severity: serious Tags: sid Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=109258 This package fails to build on current sid/amd64. The first matching ci.debian.net autopkgtest failure happened on 2015-11-24, and reproducible.debian.net built the package successfully on 2015-11-17. Apparently stretch was still unaffected as of 2015-11-26. https://reproducible.debian.net/history/libical-parser-sax-perl.html http://ci.debian.net/packages/libi/libical-parser-sax-perl/unstable/amd64/ [rt.cpan.org #109258] blames DateTime-Event-Recurrence-0.18 and DateTime-Set-0.3600. The above timeline indeed matches libdatetime-event-recurrence-perl_0.18-1. # Failed test 'rrule' # at t/01parse.t line 19. # Found 6 differences with expected: # Rogue element 'dtend' in element '/ical[1]/events[1]/year[1]/month[1]/week[1]/day[5]/event[1]'. # Rogue element 'event' in element '/ical[1]/events[1]/year[1]/month[1]/week[1]/day[5]'. # Rogue element 'dtstamp' in element '/ical[1]/events[1]/year[1]/month[1]/week[1]/day[5]/event[1]'. # Rogue element 'hours' in element '/ical[1]/events[1]/year[1]/month[1]/week[1]/day[5]/event[1]'. # Rogue element 'summary' in element '/ical[1]/events[1]/year[1]/month[1]/week[1]/day[5]/event[1]'. # Rogue element 'dtstart' in element '/ical[1]/events[1]/year[1]/month[1]/week[1]/day[5]/event[1]'. # in processed XML: # wierd2004-11-13T21:47:342004-12-02T00:00:002004-12-02T01:00:001.001.002004-12-03T01:00:002004-12-03T00:00:002004-11-13T21:47:34wierd # Looks like you failed 1 test of 19. [...] Test Summary Report --- t/01parse.t (Wstat: 256 Tests: 19 Failed: 1) Failed test: 10 Non-zero exit status: 1 Files=2, Tests=21, 2 wallclock secs ( 0.03 usr 0.00 sys + 1.52 cusr 0.02 csys = 1.57 CPU) Result: FAIL
Processed: Bug#801937 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 801937 pending Bug #801937 [src:python-django-tagging] python-django-tagging: Fails to build from source with Django 1.8 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 801937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#801937: marked as pending
tag 801937 pending thanks Hello, Bug #801937 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-django-tagging.git;a=commitdiff;h=273bb48 --- commit 273bb4873a0a8457c724304bf09e37bc11596dc1 Author: Jonas GenanntDate: Sat Nov 28 16:36:13 2015 +0100 Releasing debian version 0.4-1. diff --git a/debian/changelog b/debian/changelog index 3993c44..fc00082 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,21 @@ -python-django-tagging (1:0.3.1-5) UNRELEASED; urgency=medium +python-django-tagging (1:0.4-1) unstable; urgency=medium + * Team upload. + [ Raphaël Hertzog ] * Drop myself from Uploaders. - -- Raphaël Hertzog Wed, 11 Feb 2015 10:11:51 +0100 + [ Jonas Genannt ] + * Imported Upstream version 0.4 (Closes: #801937) + * d/control: +- changed homepage +- updated to pybuild +- changed my email to @debian.org + * d/watch: updated to pypi service + * removed django-1.7-compat.patch + * d/p/series: disabled patches + * d/docs: install new docs + + -- Jonas Genannt Sat, 28 Nov 2015 16:31:32 +0100 python-django-tagging (1:0.3.1-4) unstable; urgency=medium
Bug#785867: morituri: Please update to GStreamer 1.x
Hi Moritz, Quoting Moritz Muehlenhoff (2015-11-14 23:18:21) > On Wed, May 20, 2015 at 04:03:06PM +0300, sl...@debian.org wrote: >> your package morituri currently still depends on GStreamer 0.10. >> >> GStreamer 0.10 is no longer maintained and supported by the upstream >> project since almost 3 years, and contains many known bugs that are >> fixed in the new 1.x release series of GStreamer. Next to many bug >> fixes, the new release series also contains many other improvements, >> new features and a more streamlined API. > > upstream doesn't seem to plan a port, are you planning to port it > yourself or shall we remove it for now (it can still be re-added if > fixed at a later point in time)? > > https://github.com/thomasvs/morituri/issues/47 Not sure what you propose here. If you mean drop from testing then that happened already 2 weeks before your email. If you mean drop from unstable, then I see no benefit in that, but a drawback is loss of bug tracking. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#806538: gnocchi-common: missing Depends: dbconfig-common
Package: gnocchi-common Version: 1.3.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package gnocchi-common. (Reading database ... (Reading database ... 14666 files and directories currently installed.) Preparing to unpack .../gnocchi-common_1.3.0-2_all.deb ... Unpacking gnocchi-common (1.3.0-2) ... Setting up gnocchi-common (1.3.0-2) ... /var/lib/dpkg/info/gnocchi-common.postinst: 702: .: Can't open /usr/share/dbconfig-common/dpkg/postinst dpkg: error processing package gnocchi-common (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: gnocchi-common cheers, Andreas gnocchi-common_1.3.0-2.log.gz Description: application/gzip
Bug#800276: marked as done (sysprofile: Please migrate a supported debhelper compat level)
Your message dated Sat, 28 Nov 2015 16:34:45 + with message-idand subject line Bug#800276: fixed in sysprofile 0.3.9 has caused the Debian Bug report #800276, regarding sysprofile: 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.) -- 800276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sysprofile Severity: important Usertags: deprecated-debhelper-compat-leq-3 Hi, The package sysprofile 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: sysprofile Source-Version: 0.3.9 We believe that the bug you reported is fixed in the latest version of sysprofile, 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. Emanuele Rocca (supplier of updated sysprofile 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, 28 Nov 2015 17:19:24 +0100 Source: sysprofile Binary: sysprofile syslogout Architecture: source all Version: 0.3.9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Emanuele Rocca Description: syslogout - Modularized system wide shell logout mechanism sysprofile - Modularized system wide shell configuration mechanism Closes: 800276 Changes: sysprofile (0.3.9) unstable; urgency=medium . * QA upload. * Maintainer field set to QA Group. * Set debhelper compatibility level to 9. (Closes: #800276) * Switch to dh(1). * Bump Standards-Version to 3.9.6. * Depend on ${misc:Depends} because of debhelper. * Point to /usr/share/common-licenses in copyright file. Checksums-Sha1: 3bd2eda1ce5f126b192c6f299d2a9f99ad339918 1445 sysprofile_0.3.9.dsc 965ac55d49c18a14eb9fd120f90653184ecb2e8b 20326 sysprofile_0.3.9.tar.gz 02ae509dcaf860a3f836f89f2b673649652e4f90 14282 syslogout_0.3.9_all.deb f38eb3216fba9510792823ff09c98d3dc4c9b12b 17806 sysprofile_0.3.9_all.deb Checksums-Sha256: 868d2889170ba248f47bf5cce3faf00fd36655e360ee171c609d3fac3bd56dec 1445 sysprofile_0.3.9.dsc 21baf225c4078afe13ab2955c380474596f03ec24e88676b68790d271536d431 20326 sysprofile_0.3.9.tar.gz 6b7422af8efc35a0a9fa568b860e29edd0100e552d67619a7eb04fa4ba09957d 14282 syslogout_0.3.9_all.deb de65ce801301218093246192a1b4a676fad8addd521873a6c51e482f40f3aa94 17806 sysprofile_0.3.9_all.deb Files: af13dac5f76fc75cd29921dbcb1cae19 1445 admin optional sysprofile_0.3.9.dsc eccda6a9582d37b53b3582e4e00985b2 20326 admin optional sysprofile_0.3.9.tar.gz 0f4687cbfe2f354da52b391f3c77eb94 14282 admin optional syslogout_0.3.9_all.deb 4d553fbd58febd41bffaaacbd7495422 17806 admin optional sysprofile_0.3.9_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1
Bug#806449: marked as done (request-tracker4: FTBFS: t/security/CVE-2011-5092-localizeddatetime.t locale warnings)
Your message dated Sat, 28 Nov 2015 17:49:23 + with message-idand subject line Bug#806449: fixed in request-tracker4 4.2.12-4 has caused the Debian Bug report #806449, regarding request-tracker4: FTBFS: t/security/CVE-2011-5092-localizeddatetime.t locale warnings 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.) -- 806449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: request-tracker4 Version: 4.2.12-3 Severity: serious Justification: FTBFS Tags: sid This package has started FTBFS with this output: Invalid locale code or name: en-us Invalid locale code or name: en-us # Failed test 'no warnings' # at /«PKGBUILDDIR»/lib/RT/Test.pm line 1780. # There were 1 warning(s) # Previous test 1 'Lang changed from (no value) to 'en-us'' # Invalid locale code or name: en-us # at /usr/share/perl5/Log/Dispatch/Perl.pm line 84. # Log::Dispatch::Perl::__ANON__("Invalid locale code or name: en-us\x{a}") called at /usr/share/perl5/Log/Dispatch/Output.pm line 50 # Log::Dispatch::Output::log(undef, "level", "critical", "message", "Invalid locale code or name: en-us\x{a}", "name", "rttest") called at /usr/share/perl5/Log/Dispatch.pm line 238 # Log::Dispatch::_log_to(Log::Dispatch=HASH(0x5d143d0), "level", "critical", "message", "Invalid locale code or name: en-us\x{a}", "name", "rttest") called at /usr/share/perl5/Log/Dispatch.pm line 190 # Log::Dispatch::_log_to_outputs(Log::Dispatch=HASH(0x5d143d0), "level", "critical", "message", "Invalid locale code or name: en-us\x{a}") called at /usr/share/perl5/Log/Dispatch.pm line 168 # Log::Dispatch::log(Log::Dispatch=HASH(0x5d143d0), "level", "critical", "message", "Invalid locale code or name: en-us\x{a}") called at /usr/share/perl5/Log/Dispatch.pm line 42 # Log::Dispatch::__ANON__(Log::Dispatch=HASH(0x5d143d0), "Invalid locale code or name: en-us\x{a}") called at /«PKGBUILDDIR»/lib/RT.pm line 389 # RT::__ANON__("Invalid locale code or name: en-us\x{a}") called at /usr/share/perl5/DateTime/Locale.pm line 234 # DateTime::Locale::load(undef, "en-us") called at /«PKGBUILDDIR»/lib/RT/Date.pm line 738 # RT::Date::LocaleObj(RT::Date=HASH(0x6786d08)) called at /«PKGBUILDDIR»/lib/RT/Date.pm line 772 # RT::Date::LocalizedDateTime(RT::Date=HASH(0x6786d08), "Format", "LocalizedDateTime", "Timezone", "user") called at /«PKGBUILDDIR»/lib/RT/Date.pm line 629 # RT::Date::Get(RT::Date=HASH(0x6786d08), "Timezone", "user", "Format", "LocalizedDateTime") called at /«PKGBUILDDIR»/lib/RT/Date.pm line 472 # RT::Date::AsString(RT::Date=HASH(0x6786d08), "Format", "LocalizedDateTime") called at t/security/CVE-2011-5092-localizeddatetime.t line 14 # # Some tests failed or we bailed out, tmp directory '/«PKGBUILDDIR»/t/tmp/security-CVE-2011-5092-localizeddatetime.t-SYQgqwoP' is not cleaned # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 2 just after 2. t/security/CVE-2011-5092-localizeddatetime.t ... According to https://reproducible.debian.net/history/request-tracker4.html this started happening somewhere between 2015-11-07 and 2015-11-16. Dominic. --- End Message --- --- Begin Message --- Source: request-tracker4 Source-Version: 4.2.12-4 We believe that the bug you reported is fixed in the latest version of request-tracker4, 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 806...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominic Hargreaves (supplier of updated request-tracker4 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, 28 Nov 2015 17:08:01 + Source: request-tracker4 Binary: request-tracker4 rt4-clients rt4-standalone rt4-fcgi rt4-apache2 rt4-db-postgresql rt4-db-mysql rt4-db-sqlite rt4-doc-html Architecture: source Version: 4.2.12-4 Distribution: unstable Urgency: medium Maintainer: Debian Request Tracker Group Changed-By: Dominic Hargreaves
Processed: violates Debian Policy 2.3 Copyright considerations
Processing commands for cont...@bugs.debian.org: > severity 704303 serious Bug #704303 [iceweasel] iceweasel: MPL license text is missing Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 704303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 806376 in 1.0.1-1
Processing commands for cont...@bugs.debian.org: > # mark as found in common anchestor > found 806376 1.0.1-1 Bug #806376 [src:redmine] redmine: CVE-2015-8346: Data disclosure on the time logging form Marked as found in versions redmine/1.0.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 806376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806537: extremetuxracer: fails to upgrade from 'sid' - trying to overwrite /usr/share/icons/hicolor/scalable/apps/etracericon.svg
Package: extremetuxracer Version: 0.6.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' 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...): Preparing to unpack .../extremetuxracer-data_0.6.0-2_all.deb ... Unpacking extremetuxracer-data (0.6.0-2) over (0.4-6) ... dpkg: error processing archive /var/cache/apt/archives/extremetuxracer-data_0.6.0-2_all.deb (--unpack): trying to overwrite '/usr/share/icons/hicolor/scalable/apps/etracericon.svg', which is also in package extremetuxracer 0.4-6 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../extremetuxracer_0.6.0-2_amd64.deb ... Unpacking extremetuxracer (0.6.0-2) over (0.4-6) ... Errors were encountered while processing: /var/cache/apt/archives/extremetuxracer-data_0.6.0-2_all.deb cheers, andreas extremetuxracer_0.6.0-2.log.gz Description: application/gzip
Bug#806500: quassel-client: Client configuration is world readable and contains password in plain text
>> This is a wrong assumption, just look at directory access permissions: >> >> $ LC_ALL=C ls -alp ~/.config/ | grep '\./' >> drwx-- 96 user user 4096 Nov 28 23:44 ./ >> drwx-- 192 user user 12288 Nov 28 22:39 ../ > > Mine are not the same: > > diederik@bagend:~$ LC_ALL=C ls -alp ~/.config/ | grep '\./' > drwxr-xr-x 45 diederik diederik 4096 Nov 28 19:29 ./ > drwxr-x--- 68 diederik diederik 12288 Nov 28 17:59 ../ > diederik@bagend:~$ ls -ld ~/.config/ > drwxr-xr-x 45 diederik diederik 4096 nov 28 19:29 /home/diederik/.config/ > diederik@bagend:~$ ls -ld ~/.config/quassel-irc.org/ > drwxr-xr-x 2 diederik diederik 4096 nov 28 11:10 > /home/diederik/.config/quassel-irc.org/ This should be enough I think: > drwxr-x--- 68 diederik diederik 12288 Nov 28 17:59 ../ Try something like this: $ LC_ALL=C su another-user -c 'ls -alp /home/diederik/.config' Password: ls: cannot access /home/diederik/.config: Permission denied Best wishes, Boris
Bug#806560: python3-udiskie/python-udiskie do not start
Subject: python3-udiskie/python-udiskie do not start Package: python3-udiskie Version: 1.3.2-1 Justification: renders package unusable Severity: grave Dear Maintainer, udiskie fails to start up; the icon appears in the system tray but no menu appears when I click on it. With python-udiskie, xsession-errors says the following: -- /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:50: RuntimeWarning: You have imported the Gtk 2.0 module. Because Gtk 2.0 was not designed for use with introspection some of the interfaces and API will fail. As such this is not supported by the pygobject development team and we encourage you to port your app to Gtk 3 or greater. PyGTK is the recomended python module to use with Gtk 2.0 warnings.warn(warn_msg, RuntimeWarning) /usr/lib/python2.7/dist-packages/udiskie/prompt.py:24: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '2.0') before import to ensure that the right version gets loaded. from gi.repository import Gtk Typelib for 'libnotify' is not available. Possible causes include: - libnotify is not installed - the typelib is provided by a separate package - libnotify was built with introspection disabled Starting udiskie without notifications. not mounting /org/freedesktop/UDisks2/block_devices/mmcblk0p1: already mounted "sni-qt/4318" WARN 22:14:33.168 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE [i3bar/src/xcb.c:679] ERROR: Window 0282 violates the XEMBED protocol, _XEMBED_INFO not set Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 319, in _activate self._popup_menu(icon, button=0, time=Gtk.get_current_event_time()) File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 325, in _popup_menu m.popup(parent_menu_shell=None, AttributeError: 'Menu' object has no attribute 'popup' Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 319, in _activate self._popup_menu(icon, button=0, time=Gtk.get_current_event_time()) File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 325, in _popup_menu m.popup(parent_menu_shell=None, AttributeError: 'Menu' object has no attribute 'popup' Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 319, in _activate self._popup_menu(icon, button=0, time=Gtk.get_current_event_time()) File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 325, in _popup_menu m.popup(parent_menu_shell=None, AttributeError: 'Menu' object has no attribute 'popup' Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 325, in _popup_menu m.popup(parent_menu_shell=None, AttributeError: 'Menu' object has no attribute 'popup' -- With python3-udiskie installed, xsession-errors have the following error: -- /usr/lib/python3/dist-packages/gi/overrides/Gtk.py:50: RuntimeWarning: You have imported the Gtk 2.0 module. Because Gtk 2.0 was not designed for use with introspection some of the interfaces and API will fail. As such this is not supported by the pygobject development team and we encourage you to port your app to Gtk 3 or greater. PyGTK is the recomended python module to use with Gtk 2.0 warnings.warn(warn_msg, RuntimeWarning) /usr/bin/udiskie:9: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '2.0') before import to ensure that the right version gets loaded. load_entry_point('udiskie==1.3.2', 'console_scripts', 'udiskie')() Typelib for 'libnotify' is not available. Possible causes include: - libnotify is not installed - the typelib is provided by a separate package - libnotify was built with introspection disabled Starting udiskie without notifications. not mounting /org/freedesktop/UDisks2/block_devices/mmcblk0p1: already mounted "sni-qt/5786" WARN 22:20:51.131 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE [i3bar/src/xcb.c:679] ERROR: Window 0282 violates the XEMBED protocol, _XEMBED_INFO not set -- It seems some package is not installed, but I don't know what is missing. Best, Greg -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-udiskie depends on: ii gettext0.19.6-1 ii gobject-introspection 1.46.0-2 ii python-notify 0.1.1-4 ii python3-docopt 0.6.2-1 ii python3-gi 3.18.2-2 ii python3-pkg-resources 18.4-2 ii python3-yaml 3.11-2+b1 ii
Bug#806509: marked as done (libept1.5.0 and libept1.4.16: error when trying to install together)
Your message dated Sat, 28 Nov 2015 22:19:10 + with message-idand subject line Bug#806509: fixed in libept 1.1+nmu3 has caused the Debian Bug report #806509, regarding libept1.5.0 and libept1.4.16: error when trying to install together 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.) -- 806509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libept1.4.16,libept1.5.0 Version: libept1.4.16/1.0.14+b2 Version: libept1.5.0/1.1+nmu2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-11-28 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: Selecting previously unselected package gcc-5-base:amd64. (Reading database ... 10925 files and directories currently installed.) Preparing to unpack .../gcc-5-base_5.2.1-26_amd64.deb ... Unpacking gcc-5-base:amd64 (5.2.1-26) ... Setting up gcc-5-base:amd64 (5.2.1-26) ... (Reading database ... 10932 files and directories currently installed.) Preparing to unpack .../libstdc++6_5.2.1-26_amd64.deb ... Unpacking libstdc++6:amd64 (5.2.1-26) over (4.8.2-19) ... Processing triggers for libc-bin (2.19-22) ... Setting up libstdc++6:amd64 (5.2.1-26) ... Processing triggers for libc-bin (2.19-22) ... (Reading database ... 10946 files and directories currently installed.) Preparing to unpack .../archives/apt_1.1.1_amd64.deb ... Unpacking apt (1.1.1) over (1.0.4) ... Selecting previously unselected package libapt-pkg5.0:amd64. Preparing to unpack .../libapt-pkg5.0_1.1.1_amd64.deb ... Unpacking libapt-pkg5.0:amd64 (1.1.1) ... Processing triggers for libc-bin (2.19-22) ... Processing triggers for man-db (2.7.5-1) ... Setting up libapt-pkg5.0:amd64 (1.1.1) ... Processing triggers for libc-bin (2.19-22) ... (Reading database ... 10979 files and directories currently installed.) Preparing to unpack .../aptitude_0.7.4-2_amd64.deb ... Unpacking aptitude (0.7.4-2) over (0.6.10-1) ... Preparing to unpack .../aptitude-common_0.7.4-2_all.deb ... Unpacking aptitude-common (0.7.4-2) over (0.6.10-1) ... Selecting previously unselected package libboost-iostreams1.58.0:amd64. Preparing to unpack .../libboost-iostreams1.58.0_1.58.0+dfsg-4_amd64.deb ... Unpacking libboost-iostreams1.58.0:amd64 (1.58.0+dfsg-4) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.19-22) ... (Reading database ... 10977 files and directories currently installed.) Removing libcwidget3:amd64 (0.5.17-1) ... Removing libsigc++-2.0-0c2a:amd64 (2.4.1-1) ... Processing triggers for libc-bin (2.19-22) ... Selecting previously unselected package libsigc++-2.0-0v5:amd64. (Reading database ... 10924 files and directories currently installed.) Preparing to unpack .../libsigc++-2.0-0v5_2.6.2-1_amd64.deb ... Unpacking libsigc++-2.0-0v5:amd64 (2.6.2-1) ... Selecting previously unselected package libcwidget3v5:amd64. Preparing to unpack .../libcwidget3v5_0.5.17-4_amd64.deb ... Unpacking libcwidget3v5:amd64 (0.5.17-4) ... Processing triggers for libc-bin (2.19-22) ... (Reading database ... 10977 files and directories currently installed.) Removing libept1.4.12:amd64 (1.0.12) ... Removing libxapian22 (1.2.17-1) ... Processing triggers for libc-bin (2.19-22) ... Selecting previously unselected package libxapian22v5. (Reading database ... 10964 files and directories currently installed.) Preparing to unpack .../libxapian22v5_1.2.21-1.2_amd64.deb ... Unpacking libxapian22v5 (1.2.21-1.2) ... Selecting previously unselected package libept1.4.16:amd64. Preparing to unpack .../libept1.4.16_1.0.14+b2_amd64.deb ... Unpacking libept1.4.16:amd64 (1.0.14+b2) ... Selecting previously unselected package libept1.5.0:amd64. Preparing to unpack .../libept1.5.0_1.1+nmu2_amd64.deb ... Unpacking libept1.5.0:amd64 (1.1+nmu2) ... dpkg: error processing archive /var/cache/apt/archives/libept1.5.0_1.1+nmu2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libept.so.1.aptpkg5.0', which is also in package libept1.4.16:amd64 1.0.14+b2 Processing triggers for libc-bin (2.19-22) ... Errors were encountered while processing: /var/cache/apt/archives/libept1.5.0_1.1+nmu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) 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
Bug#806500: quassel-client: Client configuration is world readable and contains password in plain text
Hi, > As I was trying to setup CertFP I had a look at > ~/.config/quassel-irc.org and noticed the following: > -rw-r--r-- 1 diederik diederik 8101 nov 28 03:01 quasselclient.conf > > Looking into that file I could easily see my password and that combined > with the security settings of that file did not make me happy. This is a wrong assumption, just look at directory access permissions: $ LC_ALL=C ls -alp ~/.config/ | grep '\./' drwx-- 96 user user 4096 Nov 28 23:44 ./ drwx-- 192 user user 12288 Nov 28 22:39 ../ Best wishes, Boris
Processed: Decrease a severity
Processing commands for cont...@bugs.debian.org: > severity 806500 wishlist Bug #806500 [quassel-client] quassel-client: Client configuration is world readable and contains password in plain text Severity set to 'wishlist' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 806500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#785867: morituri: Please update to GStreamer 1.x
On Sat, Nov 28, 2015 at 04:54:11PM +0100, Jonas Smedegaard wrote: > Hi Moritz, > > Quoting Moritz Muehlenhoff (2015-11-14 23:18:21) > > On Wed, May 20, 2015 at 04:03:06PM +0300, sl...@debian.org wrote: > >> your package morituri currently still depends on GStreamer 0.10. > >> > >> GStreamer 0.10 is no longer maintained and supported by the upstream > >> project since almost 3 years, and contains many known bugs that are > >> fixed in the new 1.x release series of GStreamer. Next to many bug > >> fixes, the new release series also contains many other improvements, > >> new features and a more streamlined API. > > > > upstream doesn't seem to plan a port, are you planning to port it > > yourself or shall we remove it for now (it can still be re-added if > > fixed at a later point in time)? > > > > https://github.com/thomasvs/morituri/issues/47 > > Not sure what you propose here. > > If you mean drop from testing then that happened already 2 weeks before > your email. > > If you mean drop from unstable, then I see no benefit in that, but a > drawback is loss of bug tracking. I'm not sure what you mean by "loss of bugtracking"? gstreamer 0.10 is scheduled for removal from _unstable_, so if upstream is unactive and none of the maintainers plans to port it themselves, it would be subject to removal as well. Cheers, Moritz
Bug#806500: quassel-client: Client configuration is world readable and contains password in plain text
On Sunday 29 November 2015 00:24:15 Boris Pek wrote: > This should be enough I think: > > drwxr-x--- 68 diederik diederik 12288 Nov 28 17:59 ../ > > Try something like this: > $ LC_ALL=C su another-user -c 'ls -alp /home/diederik/.config' > Password: > ls: cannot access /home/diederik/.config: Permission denied Indeed. Phew :-) diederik@bagend:~$ LC_ALL=C su quassel-test -c 'ls -alp /home/diederik/.config' Password: ls: cannot access /home/diederik/.config: Permission denied Sorry for the noise. signature.asc Description: This is a digitally signed message part.
Bug#806334: marked as done (kombu: FTBFS: ImportError: cannot import name '_uuid_generate_random')
Your message dated Sat, 28 Nov 2015 23:04:14 + with message-idand subject line Bug#806334: fixed in kombu 3.0.29-2 has caused the Debian Bug report #806334, regarding kombu: FTBFS: ImportError: cannot import name '_uuid_generate_random' 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.) -- 806334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kombu Version: 3.0.29-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, kombu fails to build from source in unstable/amd64: [..] == ERROR: Failure: ImportError (cannot import name '_uuid_generate_random') -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest raise self.exc_val.with_traceback(self.tb) File "/usr/lib/python3/dist-packages/nose/loader.py", line 420, in loadTestsFromName addr.filename, addr.module) File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/usr/lib/python3.5/imp.py", line 234, in load_module return load_source(name, filename, file) File "/usr/lib/python3.5/imp.py", line 172, in load_source module = _load(spec) File "", line 693, in _load File "", line 673, in _load_unlocked File "", line 662, in exec_module File "", line 222, in _call_with_frames_removed File "/home/lamby/temp/cdt.20151126161855.wFTxfhBSrz/kombu-3.0.29/kombu/tests/test_syn.py", line 9, in from kombu.tests.case import Case, patch, module_exists File "/home/lamby/temp/cdt.20151126161855.wFTxfhBSrz/kombu-3.0.29/kombu/tests/case.py", line 17, in from kombu.utils.encoding import ensure_bytes File "/home/lamby/temp/cdt.20151126161855.wFTxfhBSrz/kombu-3.0.29/kombu/utils/__init__.py", line 19, in from uuid import UUID, uuid4 as _uuid4, _uuid_generate_random ImportError: cannot import name '_uuid_generate_random' -- Ran 36 tests in 0.026s FAILED (errors=36) E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: python3.5 setup.py test dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.5 3.4 --system=custom --test-args={interpreter} setup.py test --dir . returned exit code 13 debian/rules:13: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 25 make[1]: Leaving directory '/home/lamby/temp/cdt.20151126161855.wFTxfhBSrz/kombu-3.0.29' debian/rules:6: 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 `- kombu.3.0.29-1.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Source: kombu Source-Version: 3.0.29-2 We believe that the bug you reported is fixed in the latest version of kombu, 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 806...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Brian May (supplier of updated kombu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 29 Nov 2015 09:34:41 +1100 Source: kombu Binary: python-kombu python3-kombu python-kombu-doc Architecture: source all Version: 3.0.29-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Brian May
Bug#793190: marked as done (madfuload: FTBFS with automake 1.14)
Your message dated Sat, 28 Nov 2015 23:19:06 + with message-idand subject line Bug#793190: fixed in madfuload 1.2-4.1 has caused the Debian Bug report #793190, regarding madfuload: FTBFS with automake 1.14 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.) -- 793190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: madfuload Version: 1.2-4 Severity: serious Tags: jessie stretch sid Justification: fails to build from source from a rebuild in jessie, same problem in sid: [...] debian/rules override_dh_auto_configure make[1]: Entering directory '/tmp/buildd/madfuload-1.2' autoreconf -f configure.ac:4: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see: configure.ac:4: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation configure.ac:7: error: required file './compile' not found configure.ac:7: 'automake --add-missing' can install 'compile' autoreconf: automake failed with exit status: 1 debian/rules:6: recipe for target 'override_dh_auto_configure' failed make[1]: *** [override_dh_auto_configure] Error 1 make[1]: Leaving directory '/tmp/buildd/madfuload-1.2' debian/rules:3: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Andreas --- End Message --- --- Begin Message --- Source: madfuload Source-Version: 1.2-4.1 We believe that the bug you reported is fixed in the latest version of madfuload, 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 793...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hideki Yamane (supplier of updated madfuload 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: Sat, 25 Jul 2015 11:28:56 +0900 Source: madfuload Binary: madfuload Architecture: source amd64 Version: 1.2-4.1 Distribution: unstable Urgency: medium Maintainer: Free Ekanayaka Changed-By: Hideki Yamane Description: madfuload - Firmware loader for M-Audio DFU audio devices Closes: 557406 736266 793190 Changes: madfuload (1.2-4.1) unstable; urgency=medium . * Non-maintainer upload. * debian/control - add dh-autoreconf and drop autoconf, automake, libtool, to fix FTBFS (Closes: #793190, #736266) - drop quilt (>=0.46-7), use source format 3.0 (quilt) instead. - fix typo (Closes: #557406) Thanks to Pascal De Vuyst for the report Checksums-Sha1: c739f1455b9ea62984cad295911d76be52fe7717 1735 madfuload_1.2-4.1.dsc 7eb8de7473f3a24a2df9a0143e7eb57b7f7f0dd4 madfuload_1.2-4.1.debian.tar.xz 0d39df16855ace31722e6c28f9e9ff1b91923ef4 22820 madfuload_1.2-4.1_amd64.deb Checksums-Sha256: 87ae62983ca2e17f7d60f924bc06cd795c0d2216f96bcf01da22895583b8653b 1735 madfuload_1.2-4.1.dsc f72dc416a84da7be2d50a44b892031287952e3938d91938c331c11bc23efb0dc madfuload_1.2-4.1.debian.tar.xz 6acb6c370baaf8d5f89704e6240b6c3bd2520214b5f4b69e55e553943109ee77 22820 madfuload_1.2-4.1_amd64.deb Files: 4f31e0d9095fceec4175a1c53ba26db2 1735 non-free/sound extra madfuload_1.2-4.1.dsc 73b4c316dd9207626f058ae55ca71e27 non-free/sound extra madfuload_1.2-4.1.debian.tar.xz d2d532ce20ba11175f949dd49d380ffd 22820 non-free/sound extra madfuload_1.2-4.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJWWjMGAAoJEF0yjQgqqrFAjM4QAKpPjN/aHqX1wfW/AU2Y4Roj C+IcAwU/hW6l/qyZuMmgdvzXd3+dXFRUEXewCqGwinEOva82/3HBLHshVD/l5LjS 9FSYJi3/lvD74fFo+FVE5ffgv1Vgq9DQl+jQ1TDxGBvlKc3Ovd0xhOVsLzFIZ7We CxBMFSk0eD+Tz8rJgYOz9z3BoXxu4vuluHhb6dNvZ5cPC83N9MlscoCNoQKb9P/W 6MipNmMydQAmWw5Xh/zKMqbaXP5ZzgePDml8UKnORFRCSbjc1wddr98XaXxTNvbn nb00qCk7g0CtXVV4/289GxQ2UcmsFsPez6WO7KqRZHU0fITZXia/iyxlwLCSHHuM EN93RXF6jM6fasrM1duj0V0H97Sz4JXsKc5wTA7k6N1CjxYMtBQTLCTKZddy4ZA8 RdbkPjThhq4Illjy7iyGKIvaK/X/Giawg1Od1t8GfzcRfJy7D6Xs4cBzkz3blnR8 EOJKPHIIk+k0jDjW3OeEvf8yO79iwBgoVwPOW89qzCy+4sVfkJb3LOkMHNbqcPbD
Bug#806333: marked as done (django-celery-transactions: FTBFS: ImportError: cannot import name '_uuid_generate_random')
Your message dated Sun, 29 Nov 2015 10:18:59 +1100 with message-id <87wpt1iufw@prune.linuxpenguins.xyz> and subject line Re: [Python-modules-team] Bug#806333: Bug#806333: django-celery-transactions: FTBFS: ImportError: cannot import name '_uuid_generate_random' has caused the Debian Bug report #806333, regarding django-celery-transactions: FTBFS: ImportError: cannot import name '_uuid_generate_random' 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.) -- 806333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: django-celery-transactions Version: 0.3.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, django-celery-transactions fails to build from source in unstable/amd64: [..] I: pybuild base:184: python3.5 runtests.py Traceback (most recent call last): File "runtests.py", line 61, in runtests() File "runtests.py", line 48, in runtests from celery import current_app File "/usr/lib/python3/dist-packages/celery/__init__.py", line 131, in from celery import five # noqa File "/usr/lib/python3/dist-packages/celery/five.py", line 153, in from kombu.utils.compat import OrderedDict # noqa File "/usr/lib/python3/dist-packages/kombu/utils/__init__.py", line 19, in from uuid import UUID, uuid4 as _uuid4, _uuid_generate_random ImportError: cannot import name '_uuid_generate_random' E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: python3.5 runtests.py dh_auto_test: pybuild --test -i python{version} -p 3.5 3.4 --dir . returned exit code 13 debian/rules:15: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 25 make[1]: Leaving directory '/home/lamby/temp/cdt.20151126154102.171TD3C52Y/django-celery-transactions-0.3.5' debian/rules:9: 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 `- django-celery-transactions.0.3.5-1.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Brian Maywrites: > This looks like Bug #806334 in Kombu to me. This should be fixed now. Closing. -- Brian May --- End Message ---
Bug#806488: marked as done (view3dscene: FTBFS: v3dsceneraytrace.pas Error: Identifier not found "TImageFormat")
Your message dated Sat, 28 Nov 2015 19:08:58 + with message-idand subject line Bug#806488: fixed in view3dscene 3.15.0-3 has caused the Debian Bug report #806488, regarding view3dscene: FTBFS: v3dsceneraytrace.pas Error: Identifier not found "TImageFormat" 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.) -- 806488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: view3dscene Version: 3.15.0-2 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: mkdir -p /view3dscene-3.15.0/debian/tmp/usr/lib/view3dscene/3.15.0 fpc -k"-z relro" -dRELEASE -Mobjfpc -Sh -Ci -Sm -Sc -Sg -Si -O2 -Xs -FU/view3dscene-3.15.0/debian/tmp/usr/lib/view3dscene/3.15.0 -FE/view3dscene-3.15.0/debian/tmp/usr/bin -Fu/usr/lib/x86_64-linux-gnu/fp-units-2.6.4/castle-game-engine-5.2.0/ view3dscene.lpr Compiling Release Version Free Pascal Compiler version 2.6.4+dfsg-8 [2015/08/14] for x86_64 Copyright (c) 1993-2014 by Florian Klaempfl and others Target OS: Linux for x86-64 Compiling view3dscene.lpr Compiling v3dscenetexturefilters.pas Compiling v3dscenelights.pas Compiling v3dscenefillmode.pas Compiling v3dsceneraytrace.pas Compiling v3dscenestatus.pas Compiling v3dscenewindow.pas v3dsceneraytrace.pas(135,26) Error: Identifier not found "TImageFormat" v3dsceneraytrace.pas(135,26) Error: Error in type definition v3dsceneraytrace.pas(144,29) Error: Identifier not found "MimeTypeToImageFormat" v3dsceneraytrace.pas(145,26) Error: Identifier not found "ifRGBE" v3dsceneraytrace.pas(380) Fatal: There were 4 errors compiling module, stopping Fatal: Compilation aborted Error: /usr/bin/ppcx64 returned an error exitcode (normal if you did not specify a source file to be compiled) Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/view3dscene.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) --- End Message --- --- Begin Message --- Source: view3dscene Source-Version: 3.15.0-3 We believe that the bug you reported is fixed in the latest version of view3dscene, 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 806...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated view3dscene 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, 28 Nov 2015 10:37:25 +0100 Source: view3dscene Binary: view3dscene Architecture: source Version: 3.15.0-3 Distribution: unstable Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Paul Gevers Description: view3dscene - VRML / X3D browser, and a viewer for other 3D model formats Closes: 806488 Changes: view3dscene (3.15.0-3) unstable; urgency=medium . * Fix FTBFS by adding debian/patches/view3dscene-fix-for-cge520.patch for changed API of cge (Closes: #806488) * Drop menu file since TC decision on bug #741573 Checksums-Sha1: 3f6d20e50b40b82a0a6264cd94419a8cc38bd04a 1964 view3dscene_3.15.0-3.dsc b85e2fb05507ba10275b78663eccdd7aa1195828 10412 view3dscene_3.15.0-3.debian.tar.xz Checksums-Sha256: 177c7dbf862a473672ec22b102fa2dbfc458bf36c0288c80f88565f2d905bf24 1964 view3dscene_3.15.0-3.dsc 3eb6bbfa4f7f75fb1e92949fcf57c6c0451aaffd628ead2d15df726605d23890 10412 view3dscene_3.15.0-3.debian.tar.xz Files: 6c28f5081e2c29c52563ba2630b21b30 1964 misc optional view3dscene_3.15.0-3.dsc 4f97f9a870789808a88be4806e4ee15e 10412 misc optional view3dscene_3.15.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJWWfdhAAoJEJxcmesFvXUK0HgIAIpEGEcttKDZ0EvzyHnh6iJo EVjM/+iwYCzUB7PxwrKtVGgpmgPwUCN9NZOtdeAIW0WacUeCFOD8Jzo1NWuCWQOv NW/dIgY41H3Azyn6PhAerX8qH6mhscQTUR0hQJHpc++agN7H2qMZF5f+oW7GMxnn Mv7Sww83nE03u/1RPPLPRrZ0BqXJ0NazoIc2MgEg35Cdr3+vW2bFWIb9tEuGML8h
Bug#801250: marked as done (jarisplayer: FTBFS: Player.hx:325: characters 8-13 : Capture variables must be lower-case)
Your message dated Sat, 28 Nov 2015 21:21:51 + with message-idand subject line Bug#801250: fixed in jarisplayer 2.0.17~dfsg-1 has caused the Debian Bug report #801250, regarding jarisplayer: FTBFS: Player.hx:325: characters 8-13 : Capture variables must be lower-case 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.) -- 801250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jarisplayer Version: 2.0.15+20131104~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, jarisplayer fails to build from source in unstable/amd64: [..] haxe -main jaris.Main -swf player.swf -cp src -D no-pattern-matching -dce full src/jaris/player/Player.hx:325: characters 8-13 : Capture variables must be lower-case debian/rules:66: recipe for target 'debian/stamp-swf-build' failed make: *** [debian/stamp-swf-build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/jarisplayer_2.0.15+20131104~dfsg-1.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Mon Oct 5 20:30:02 GMT+12 2015 I: pbuilder-time-stamp: 1444120202 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: Mounting /dev/shm I: Mounting /sys I: policy-rc.d already exists I: Installing the build-deps -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: cdbs, devscripts, debhelper, dh-buildinfo, haxe, libimage-exiftool-perl, libregexp-assemble-perl, libipc-system-simple-perl, lcdf-typetools dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 20294 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ... Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on cdbs; however: Package cdbs is not installed. pbuilder-satisfydepends-dummy depends on devscripts; however: Package devscripts is not installed. pbuilder-satisfydepends-dummy depends on dh-buildinfo; however: Package dh-buildinfo is not installed. pbuilder-satisfydepends-dummy depends on haxe; however: Package haxe is not installed. pbuilder-satisfydepends-dummy depends on libimage-exiftool-perl; however: Package libimage-exiftool-perl is not installed. pbuilder-satisfydepends-dummy depends on libregexp-assemble-perl; however: Package libregexp-assemble-perl is not installed. pbuilder-satisfydepends-dummy depends on libipc-system-simple-perl; however: Package libipc-system-simple-perl is not installed. pbuilder-satisfydepends-dummy depends on lcdf-typetools; however: Package lcdf-typetools is not installed. Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ... Reading package lists... Building dependency tree... Reading state information... Initializing package states... Writing extended state information... Building tag database... pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) The following NEW packages will be installed: aglfn{a} cdbs{a} devscripts{a} dh-buildinfo{a} dh-python{a} haxe{a} lcdf-typetools{a} libexpat1{a} libgc1c2{a}
Processed: reassign 806509 to libept1.5.0, found 805004 in 1:3.8~svn254193-1
Processing commands for cont...@bugs.debian.org: > reassign 806509 libept1.5.0 1.1+nmu2 Bug #806509 [libept1.4.16,libept1.5.0] libept1.5.0 and libept1.4.16: error when trying to install together Bug reassigned from package 'libept1.4.16,libept1.5.0' to 'libept1.5.0'. Ignoring request to alter found versions of bug #806509 to the same values previously set Ignoring request to alter fixed versions of bug #806509 to the same values previously set Bug #806509 [libept1.5.0] libept1.5.0 and libept1.4.16: error when trying to install together Marked as found in versions libept/1.1+nmu2. > found 805004 1:3.8~svn254193-1 Bug #805004 [clang-modernize-3.8] clang-modernize-3.8: uninstallable in sid Marked as found in versions llvm-toolchain-snapshot/1:3.8~svn254193-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 805004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805004 806509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806500: quassel-client: Client configuration is world readable and contains password in plain text
On Saturday 28 November 2015 23:57:38 Boris Pek wrote: > This is a wrong assumption, just look at directory access permissions: > > $ LC_ALL=C ls -alp ~/.config/ | grep '\./' > drwx-- 96 user user 4096 Nov 28 23:44 ./ > drwx-- 192 user user 12288 Nov 28 22:39 ../ Mine are not the same: diederik@bagend:~$ LC_ALL=C ls -alp ~/.config/ | grep '\./' drwxr-xr-x 45 diederik diederik 4096 Nov 28 19:29 ./ drwxr-x--- 68 diederik diederik 12288 Nov 28 17:59 ../ diederik@bagend:~$ ls -ld ~/.config/ drwxr-xr-x 45 diederik diederik 4096 nov 28 19:29 /home/diederik/.config/ diederik@bagend:~$ ls -ld ~/.config/quassel-irc.org/ drwxr-xr-x 2 diederik diederik 4096 nov 28 11:10 /home/diederik/.config/quassel-irc.org/ signature.asc Description: This is a digitally signed message part.
Bug#806483: marked as done (python-jsonrpc2: FTBFS: Can't locate Debian/Debhelper/Buildsystem/pybuild.pm in @INC)
Your message dated Sun, 29 Nov 2015 06:19:32 + with message-idand subject line Bug#806483: fixed in python-jsonrpc2 0.4.1-2 has caused the Debian Bug report #806483, regarding python-jsonrpc2: FTBFS: Can't locate Debian/Debhelper/Buildsystem/pybuild.pm in @INC to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-jsonrpc2 Version: 0.4.1-1 Severity: serious Justification: fails to build from source Tags: sid 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: debian/rules clean dh clean --with python2 --buildsystem=pybuild dh_testdir -O--buildsystem=pybuild dh_auto_clean -O--buildsystem=pybuild dh_auto_clean: unable to load build system class 'pybuild': Can't locate Debian/Debhelper/Buildsystem/pybuild.pm in @INC (you may need to install the Debian::Debhelper::Buildsystem::pybuild module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at (eval 2) line 2. BEGIN failed--compilation aborted at (eval 2) line 2. debian/rules:6: recipe for target 'clean' failed make: *** [clean] Error 2 dpkg-buildpackage: error: debian/rules clean gave error exit status 2 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/python-jsonrpc2.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) --- End Message --- --- Begin Message --- Source: python-jsonrpc2 Source-Version: 0.4.1-2 We believe that the bug you reported is fixed in the latest version of python-jsonrpc2, 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 806...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. TANIGUCHI Takaki (supplier of updated python-jsonrpc2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 29 Nov 2015 14:56:27 +0900 Source: python-jsonrpc2 Binary: python-jsonrpc2 Architecture: source all Version: 0.4.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: TANIGUCHI Takaki Description: python-jsonrpc2 - Python WSGI Framework for JSON RPC 2.0 (Python 2) Closes: 806483 Changes: python-jsonrpc2 (0.4.1-2) unstable; urgency=medium . * Bump Standards-Version to 3.9.6. * debian/control: Add dh-python and python-pastescript to Build-Depends. (Closes: #806483) Checksums-Sha1: fbc06910293b2c095a0c077b295f5083f5fa8859 2150 python-jsonrpc2_0.4.1-2.dsc 61a0f2afb381cb17b8002680008fdc71171f26b4 2576 python-jsonrpc2_0.4.1-2.debian.tar.xz 4b640fdf57299a0e94554aa17524ae3048537078 15986 python-jsonrpc2_0.4.1-2_all.deb Checksums-Sha256: 3ecebfb84b00afe2274f9e1ba0f788ab50236587b733bf486b938179ca8abec3 2150 python-jsonrpc2_0.4.1-2.dsc 1c211bf7e683a010b99dfc8293c4c5b40c3bc7c48a5d94c5aa8db5203a5e2b82 2576 python-jsonrpc2_0.4.1-2.debian.tar.xz d9bc63fee24c140471010878074826e8bb6661d527d283eea535b724b6117308 15986 python-jsonrpc2_0.4.1-2_all.deb Files: 57b1cf42981f50020e7956c66d995b92 2150 python extra python-jsonrpc2_0.4.1-2.dsc 338ad5d0154a8b84ab25f8c70056338f 2576 python extra python-jsonrpc2_0.4.1-2.debian.tar.xz 5ea97127897ba1282173b8e497dbbd29 15986 python extra python-jsonrpc2_0.4.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWWpPRAAoJEMwUn2wopeJXdg0QALnx4+5VPDfe0vZUPzR9/+pU hP4U9jy3ACdx+NxmMnRmygdKOIvaqWFObW65X0XoddsZoa3DarNv3WkutQe18t8U M1fMkxABIWyCxkusM1E97OcDwx4/JEmrWivB5uulCg0yOcyyDNDdqJvZAxS00zDq dg67PcX6nmdUaE3n87aqpPUNOB0JHLNhLi5n75zAOOB47nOLSd+v8dOetOIAEuyl jVQPlvUi/KFub4SVXRVRoLnJKa4RHsnrvkJFXPlOP0hjU6j4fapvTZAsOZhMvXUh
Bug#806477: marked as pending
tag 806477 pending thanks Hello, Bug #806477 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-activipy.git;a=commitdiff;h=36b2198 --- commit 36b21982a4dca0dc0b5ff4a4da1ef89395d4640b Author: W. Martin BorgertDate: Sat Nov 28 00:48:55 2015 +0100 fix build-dep, prepare 0.1-2 diff --git a/debian/changelog b/debian/changelog index 8b15a23..ba61284 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +python-activipy (0.1-2) unstable; urgency=low + + * Fix build-dep on pytest, thanks to Chris West (Closes: #806477). + + -- W. Martin Borgert Fri, 27 Nov 2015 23:31:27 + + python-activipy (0.1-1) unstable; urgency=low * Initial release (Closes: #803983).
Processed: Bug#806477 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 806477 pending Bug #806477 {Done: deba...@debian.org (W. Martin Borgert)} [src:python-activipy] python-activipy: FTBFS: /usr/bin/python2.7: No module named pytest Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 806477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#806537: extremetuxracer: fails to upgrade from 'sid' - trying to overwrite /usr/share/icons/hicolor/scalable/apps/etracericon.svg
Processing control commands: > severity -1 important Bug #806537 [extremetuxracer] extremetuxracer: fails to upgrade from 'sid' - trying to overwrite /usr/share/icons/hicolor/scalable/apps/etracericon.svg Severity set to 'important' from 'serious' -- 806537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806537: extremetuxracer: fails to upgrade from 'sid' - trying to overwrite /usr/share/icons/hicolor/scalable/apps/etracericon.svg
Control: severity -1 important Am 28.11.2015 um 16:54 schrieb Andreas Beckmann: > Package: extremetuxracer > Version: 0.6.0-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'sid' to 'experimental'. > It installed fine in 'sid', then the upgrade to 'experimental' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. Hi, thanks for the report but this is not release critical because we won't release the 0.6.0 series with Stretch. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#806518: synaptic: libept.so.1.aptpkg4.16: cannot open shared object file: No such file or directory
Package: synaptic Version: 0.82 Followup-For: Bug #806518 I can confirm downgrading to libept1.4.16 version 1.0.14+b1 fixed it too. Also just sudo synaptic had the same problem, in case you thought it was just invoking using the pkexec. - Craig -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages synaptic depends on: ii hicolor-icon-theme 0.13-1 ii libapt-inst1.7 1.0.10.2 ii libapt-pkg4.16 1.0.10.2 ii libatk1.0-0 2.18.0-1 ii libc62.19-22 ii libcairo-gobject21.14.4-1 ii libcairo21.14.4-1 ii libept1.4.16 1.0.14+b1 ii libgcc1 1:5.2.1-26 ii libgdk-pixbuf2.0-0 2.32.2-1 ii libglib2.0-0 2.46.2-1 ii libgtk-3-0 3.18.5-1 ii libpango-1.0-0 1.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii libstdc++6 5.2.1-26 ii libvte-2.90-91:0.36.3-1 ii libx11-6 2:1.6.3-1 ii libxapian22v51.2.21-1.2 ii libxext6 2:1.3.3-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages synaptic recommends: ii gksu 2.0.2-9 ii libgtk2-perl 2:1.2496-3 ii policykit-10.105-14 ii rarian-compat 0.8.1-6 ii xdg-utils 1.1.1-1 Versions of packages synaptic suggests: ii apt-xapian-index 0.47+nmu2 pn deborphan pn dwww ii menu 2.1.47 pn software-properties-gtk ii tasksel 3.34 -- no debconf information
Processed: Bug#806483 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 806483 pending Bug #806483 [src:python-jsonrpc2] python-jsonrpc2: FTBFS: Can't locate Debian/Debhelper/Buildsystem/pybuild.pm in @INC Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 806483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806483: marked as pending
tag 806483 pending thanks Hello, Bug #806483 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-jsonrpc2.git;a=commitdiff;h=5021492 --- commit 5021492489eb2837cdb739d690ce9d04051d9ed4 Author: TANIGUCHI TakakiDate: Sun Nov 29 14:56:54 2015 +0900 prepare release diff --git a/debian/changelog b/debian/changelog index 09e6f77..8091ac2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +python-jsonrpc2 (0.4.1-2) unstable; urgency=medium + + * Bump Standards-Version to 3.9.6. + * debian/control: Add dh-python and python-pastescript to Build-Depends. +(Closes: #806483) + + -- TANIGUCHI Takaki Sun, 29 Nov 2015 14:56:27 +0900 + python-jsonrpc2 (0.4.1-1) unstable; urgency=medium [ TANIGUCHI Takaki ]
Bug#806482: marked as pending
tag 806482 pending thanks Hello, Bug #806482 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-demjson.git;a=commitdiff;h=051c479 --- commit 051c47975e114236a1fcb158771f5b44f5629694 Author: TANIGUCHI TakakiDate: Sun Nov 29 16:24:48 2015 +0900 prepare release diff --git a/debian/changelog b/debian/changelog index a2f78b6..59257fd 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +python-demjson (2.2.3-2) unstable; urgency=medium + + * debian/*.install: Copy jsonlint from source tree. (Closes: #806482) + + -- TANIGUCHI Takaki Sun, 29 Nov 2015 16:24:41 +0900 + python-demjson (2.2.3-1) unstable; urgency=medium [ SVN-Git Migration ]
Bug#806476: marked as done (pyquery: FTBFS: ImportError: No module named 'setuptools')
Your message dated Sun, 29 Nov 2015 07:49:05 + with message-idand subject line Bug#806476: fixed in pyquery 1.2.9-2 has caused the Debian Bug report #806476, regarding pyquery: FTBFS: ImportError: No module named 'setuptools' 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.) -- 806476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyquery Version: 1.2.9-1 Severity: serious Justification: fails to build from source Tags: sid 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: running clean removing '/pyquery-1.2.9/.pybuild/pythonX.Y_2.7/build' (and everything under it) 'build/bdist.linux-x86_64' does not exist -- can't clean it 'build/scripts-2.7' does not exist -- can't clean it I: pybuild base:184: python3.5 setup.py clean Traceback (most recent call last): File "setup.py", line 7, in from setuptools import setup, find_packages ImportError: No module named 'setuptools' E: pybuild pybuild:274: clean: plugin distutils failed with: exit code=1: python3.5 setup.py clean dh_auto_clean: pybuild --clean -i python{version} -p 3.5 3.4 --dir . returned exit code 13 debian/rules:10: recipe for target 'clean' failed make: *** [clean] Error 25 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/pyquery.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) --- End Message --- --- Begin Message --- Source: pyquery Source-Version: 1.2.9-2 We believe that the bug you reported is fixed in the latest version of pyquery, 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 806...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. TANIGUCHI Takaki (supplier of updated pyquery package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 29 Nov 2015 16:35:45 +0900 Source: pyquery Binary: python-pyquery python3-pyquery Architecture: source all Version: 1.2.9-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: TANIGUCHI Takaki Description: python-pyquery - jQuery-like library for python 2 python3-pyquery - jQuery-like library for python 3 Closes: 806476 Changes: pyquery (1.2.9-2) unstable; urgency=medium . * debian/control: Add python-setuptools to Build-Depends. (Closes: #806476) Checksums-Sha1: c1b80d776ff3fd1b580ed2cd58634e5bd6bcd227 2090 pyquery_1.2.9-2.dsc 7181f8bca82afff8d08052b6937decb6412e800d 3048 pyquery_1.2.9-2.debian.tar.xz 8429f6d2d1eeccbff358150dad8909fd75983704 18350 python-pyquery_1.2.9-2_all.deb aa8702b5852dc0b2ecc5ae0c7fbe9d7fa029dabd 17922 python3-pyquery_1.2.9-2_all.deb Checksums-Sha256: d722702cc239eee21f34c072d6e1dffc0fb87ee694c1cb44080e29996035022a 2090 pyquery_1.2.9-2.dsc ce13e224306bc2124572479cf55d155e645515a9d7e7ed6fb814c4d9e0c55b9c 3048 pyquery_1.2.9-2.debian.tar.xz a43c278d29073d7f8726a7985b3e7aee488f21bb6a10f14c5bfae824c0b118d8 18350 python-pyquery_1.2.9-2_all.deb 47bddd52552f5e0120586f55e46aa6f8c1b425442ae232aa7c44c53bb89e0b7c 17922 python3-pyquery_1.2.9-2_all.deb Files: b2dba331ec9d44277692f3dc9d19fbc0 2090 python extra pyquery_1.2.9-2.dsc 6e497f8e9c27e2fc8266d1349ce36eee 3048 python extra pyquery_1.2.9-2.debian.tar.xz bebccf86446cda428b986583500cd607 18350 python extra python-pyquery_1.2.9-2_all.deb 5fa5e6e6bc6635b74dc7d5e6ce76ebfb 17922 python extra python3-pyquery_1.2.9-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWWqxCAAoJEMwUn2wopeJX48cP/idU5oUvX8YYubbIujTyCt00 OGNyTJwE7k2rhA+N3/m/Z1xmZWeTIEsgAsUfHO9CtBbXyEIHTHkHHtFvw1eB1uzo LQoCKnn9IVmgtaasCR+Ny5sqNff+ESUPRRQV4OXNPVDCf1b/5oi1pi+Y1g+/SoK4 VfUHFet+IWXpkHG/WVJa67jXDzlA6AHK3vBy+X4KhwqOeIuEeVUjKig2mXEbVf4X Dpa4be8BP9r3GQsWVoq/rAN4mIPi8vVrXNV1Ash2e/AWGb6ZDI0TeUiUnYYZoYAl LA0KlXWRwOoUkxHQZ+e3WiuQBzSs8Luik++NN85gNHe2wTkvhwbmX/sKGSwoQoew
Bug#806478: marked as pending
tag 806478 pending thanks Hello, Bug #806478 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-async.git;a=commitdiff;h=24acb0c --- commit 24acb0cf3783724f2c80c6b9eda573339735af87 Author: TANIGUCHI TakakiDate: Sun Nov 29 16:48:57 2015 +0900 prepare release diff --git a/debian/changelog b/debian/changelog index bc0360d..3b76a42 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +python-async (0.6.2-2) unstable; urgency=medium + + * debian/control: Add python-nose to Build-Depends. (Closes: #806478) + + -- TANIGUCHI Takaki Sun, 29 Nov 2015 16:48:49 +0900 + python-async (0.6.2-1) unstable; urgency=low [ Jakub Wilk ]
Processed: Bug#806478 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 806478 pending Bug #806478 [src:python-async] python-async: FTBFS: error: Could not find suitable distribution for Requirement.parse('nose') Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 806478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806488: [Pkg-pascal-devel] Bug#806488: view3dscene: FTBFS: v3dsceneraytrace.pas Error: Identifier not found "TImageFormat"
Paul Gevers wrote: > This makes me wonder, does fpc have any reasonable symbols > tracking mechanism? I guess it does (at least in ppu files), so > should we extend the Debian tooling dh_makeshlibs/dh_shlibsdeps to > be able to handle the fpc situation? ppu files indeed hold the 100% information about unit's interface (what symbols are exported, what other units are used etc.). You could probably use this information to automatically detect dependencies, or detect when something from the API was removed. But this would need writing and maintaining the tool to do this, which seems non-trivial, at least if I understand the desired usage. To check for API compatibility breakage (like in this case) --- it seems easier to just attempt recompiling and see what is required/broken:) Hm, although to detect dependencies between Pascal programs/libraries, using ppudump *.ppu | grep 'Uses unit' may be a useful solution... Going only a little further, this trivial snippet: find . -iname *.ppu -execdir ppudump '{}' ';' | grep 'Uses unit' | awk '{ print $3 }' | sort -u tells you what Pascal units are used by the project at a glance. Which I guess would be helpful to automatically fill what Debian packages 'fp-units-xxx' should be required. > >> The view3dscene sources in SVN are of course adjusted since a >> long time, but there hasn't been a view3dscene release since some >> time. > > If you don't want to release newer version for these kind of > incompatibilities, or if you want to go to something fully based > on version control versions, than let's discuss. We can come up > with working schemes if you want. I am not strict on having > upstream tar balls (although it is nice that people can check the > checksum of the Debian tar ball versus the one provided by > upstream). So if you are more for rolling release, we could do > that. > I think the current approach is OK. If you take the latest stable release of Castle Game Engine and view3dscene, they *should* be compatible, that's my goal. I always make extensive view3dscene tests together with CGE release (as they are related quite closely), so I always should release view3dscene with CGE. I simply forgot to do it this time... it's my human error, not a system error, I say:) > Could you at least communicate these kind of changes pro-active on > this list or somewhere in your own domain where we can pick it up > (via push communication). Or just a clear "THIS BREAKS API" note in > some changelog, I scan all the changed between two versions during > import of the tar ball. I try to document everything in the release notes. But sometimes I cut off from release notes changes that I consider "tiny", since the release notes are usually too long anyway. In case of my own programs, and *especially* in case of view3dscene, they often use obscure APIs of the engine, APIs that (I suspect) are not really used widely. That was the case with TImageFormat, and that's why it slipped from the changelog. Small API breakage that I thought would go unnoticed... until it got noticed:) Point taken, I'll try to communicate such breakage next time! And also, to always keep latest release CGE and view3dscene releases compatible. I can't avoid the fact that they are very tightly related (that's a feature actually, view3dscene being a "swiss army knife of the engine", important tool to inspect 3D and 2D files). But I always update them simultaneously in SVN, and so they should also be released together. > >> I'm attaching a minimal patch that, when applied to view3dscene >> 3.15.0 sources, makes them compile with Castle Game Engine >> 5.2.0:) Tested with FPC 2.6.4. > > If possible, could you check also with 3.0.0. That was released > last week and I am preparing the upload (to experimental) still. > When we verified all reversed dependencies (help would be nice), I > want to ask for a transition slot. > Tested: CGE 5.2.0 with view3dscene 3.15.0 (with my patched attached earlier) compile fine with FPC 3.0.0, on Linux x86_64 at least:) Same for CGE SVN with view3dscene SVN. Regards, Michalis
Bug#806482: marked as done (python-demjson: FTBFS: Failed to copy '/usr/bin/jsonlint': No such file or directory)
Your message dated Sun, 29 Nov 2015 07:34:33 + with message-idand subject line Bug#806482: fixed in python-demjson 2.2.3-2 has caused the Debian Bug report #806482, regarding python-demjson: FTBFS: Failed to copy '/usr/bin/jsonlint': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-demjson Version: 2.2.3-1 Severity: serious Justification: fails to build from source Tags: sid 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: writing dependency_links to demjson.egg-info/dependency_links.txt writing top-level names to demjson.egg-info/top_level.txt reading manifest file 'demjson.egg-info/SOURCES.txt' writing manifest file 'demjson.egg-info/SOURCES.txt' Copying demjson.egg-info to /python-demjson-2.2.3/debian/python3-demjson/usr/lib/python3.4/dist-packages/demjson-2.2.3.egg-info Skipping SOURCES.txt running install_scripts copying build/scripts-3.4/jsonlint -> /python-demjson-2.2.3/debian/python3-demjson/usr/bin changing mode of /python-demjson-2.2.3/debian/python3-demjson/usr/bin/jsonlint to 775 dh_install -O--buildsystem=pybuild Failed to copy '/usr/bin/jsonlint': No such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 50, <> line 1. dh_install: problem reading debian/python-demjson.install: debian/rules:7: recipe for target 'binary' failed make: *** [binary] Error 127 dpkg-buildpackage: error: debian/rules binary gave error exit status 2 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/python-demjson.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) --- End Message --- --- Begin Message --- Source: python-demjson Source-Version: 2.2.3-2 We believe that the bug you reported is fixed in the latest version of python-demjson, 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 806...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. TANIGUCHI Takaki (supplier of updated python-demjson package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 29 Nov 2015 16:24:41 +0900 Source: python-demjson Binary: python-demjson python3-demjson Architecture: source all Version: 2.2.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: TANIGUCHI Takaki Description: python-demjson - encoder, decoder, and lint/validator for JSON in Python python3-demjson - encoder, decoder, and lint/validator for JSON in Python Closes: 806482 Changes: python-demjson (2.2.3-2) unstable; urgency=medium . * debian/*.install: Copy jsonlint from source tree. (Closes: #806482) Checksums-Sha1: 43038f1642ed35b7377daf0366648bd22b871100 2154 python-demjson_2.2.3-2.dsc 233f3960e2cc2ec10e5218193e30f482c2129a25 3780 python-demjson_2.2.3-2.debian.tar.xz 98f89e00e9a48fbb2dcc0cb34ecd2708e0d0143d 70094 python-demjson_2.2.3-2_all.deb ec105590c7f18aeda2d8a4ea6b83c7e47c2ce54f 65526 python3-demjson_2.2.3-2_all.deb Checksums-Sha256: 8017e6cd3b9c948bed560ff238bbb74650ef959f032d8a824bce08e14934d4a5 2154 python-demjson_2.2.3-2.dsc 2d4b0d0409b45c8a3fb36bf6088487c3e3bb6c81471a6e7a85f85e35cd1286b3 3780 python-demjson_2.2.3-2.debian.tar.xz a4b9cb7c1c4360ae1e47656e347958ede2d499d4efbfaf7fa30bb7a0d2db8c0b 70094 python-demjson_2.2.3-2_all.deb 465787a8201fc82daa90f1255f0bb40c858392ef02b05f4a0a554d37f388b7d3 65526 python3-demjson_2.2.3-2_all.deb Files: 91b787e47c5cb72519f549d217f17a13 2154 python optional python-demjson_2.2.3-2.dsc 4e8e222f67168db9ddd156f4b3b1a1b8 3780 python optional python-demjson_2.2.3-2.debian.tar.xz 42c1d88c4c0006ad25079f072f85ac01 70094 python optional python-demjson_2.2.3-2_all.deb 010bd5f9f4e9ca7e0a57043122cbac1a 65526 python optional
Processed: Bug#806482 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 806482 pending Bug #806482 [src:python-demjson] python-demjson: FTBFS: Failed to copy '/usr/bin/jsonlint': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 806482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems