Bug#766869: marked as done (gtk-theme-switch: incomplete d/copyright)
Your message dated Mon, 27 Oct 2014 06:34:11 + with message-id e1xidsz-0006zt...@franck.debian.org and subject line Bug#766869: fixed in gtk-theme-switch 2.1.0-5 has caused the Debian Bug report #766869, regarding gtk-theme-switch: incomplete d/copyright to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 766869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gtk-theme-switch Version: 2.1.0-4 Severity: serious Justification: 4.5 Dear Maintainer, as Eriberto mentioned in an earlier review of your package [1], your d/copyright is incomplete. On a side note, please consider commments from reviewers, and do not file new RFS bugs -- it would have been appropiate here to reopen #739911. Not having accurate copyright information is a Policy violation, therefore this bug is RC. -- tobi [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739911#22 -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: gtk-theme-switch Source-Version: 2.1.0-5 We believe that the bug you reported is fixed in the latest version of gtk-theme-switch, 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 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marius Gavrilescu mar...@ieval.ro (supplier of updated gtk-theme-switch 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, 26 Oct 2014 18:35:53 +0200 Source: gtk-theme-switch Binary: gtk-theme-switch Architecture: source amd64 Version: 2.1.0-5 Distribution: unstable Urgency: medium Maintainer: Marius Gavrilescu mar...@ieval.ro Changed-By: Marius Gavrilescu mar...@ieval.ro Description: gtk-theme-switch - GTK+ theme switching utility Closes: 766869 Changes: gtk-theme-switch (2.1.0-5) unstable; urgency=medium . * Fix d/copyright (Closes: #766869) * Fix manpage title and remove end-of-line whitespace Checksums-Sha1: 6cece05064f595f46c598e28000ae56a5bfcb362 1905 gtk-theme-switch_2.1.0-5.dsc 613c95cbc7cb669e70a78ef8415b2b4c23e8e375 6788 gtk-theme-switch_2.1.0-5.debian.tar.xz Checksums-Sha256: 50ee29dcd37fdf9eda74d0c5b18fc8895f637317844497acbfe7a896dd730c27 1905 gtk-theme-switch_2.1.0-5.dsc 08d4f17f475fd236d99ede13541713eb7a23ca0dcdfdc2850a962c51bb6e430b 6788 gtk-theme-switch_2.1.0-5.debian.tar.xz Files: 54531a0e74a778b137c7a24a8fa5a22b 1905 x11 optional gtk-theme-switch_2.1.0-5.dsc ec2b3ee799b24bae2c363bdff4235d7c 6788 x11 optional gtk-theme-switch_2.1.0-5.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUTeX8AAoJEJFk+h0XvV02550P/A1IfhB2uaIJPT9PZKcOK+P4 Y4qbKwLp2yjtOId5t1uocy5Vaw+d4+nROAm4w7dXiSYxF1qIHqThzamFrKgMOESt QND7FYT1F0A9PVrEbrtZz7Ev7CQkGcfvA4kYlmSUVbv8Y1C9cn3Z2a6wencpbOPM b7JwqPFVmbbKnDSeexTxGQ4KqBeHahjcj3jK0oqjYm15DwoHOe235X9CYWLlLnPX 7VH0LGfaypZJaokIz9GTnClk0KhOwCeplGKyrD3+/kxGnirHB9nHGfd92uTBCHuZ HnNzk7CyPqshxO8qZzvN06TeAgZlKtYc26THgMotJHRwKko4jl8aqf63fvhIuCeA idi+W2nXu2Q2B/8t/gLgcp9TLPxCvXxTotIR/2yI1wmYVge2y4ee66xHh7Zn8KAG eWfsm6e1gaeVW9s+9JoOoM6doL5lEGCTJrbE7z7bKh3N3Jef/JJ9d3DUX0T2hC2p QoEmeAGlBfL+VeRk6tIRWUmM/R7T58AzvZs3cTYZHochtP1lnsxt+cLa/st82Tff xRTsz9bM2uF1EZKIm7ramSDiDJ7hH3mbZahVu+eQSl330Aiz6WxE3O64sJKuzlHy C2ml+Utc9mKxUTLsKELLn4rwUhG4ftBxUI+03kBuKNONZ7JQCjOLyJoQ9hsgxLiP liGH+apYlB4Jye0v38Qs =JzvA -END PGP SIGNATUREEnd Message---
Processed (with 1 errors): forcibly merging 735363 737128
Processing commands for cont...@bugs.debian.org:
forcemerge 735363 737128
Bug #735363 {Done: Daniel Kahn Gillmor d...@fifthhorseman.net} [gnupg] gnupg:
Fatal error/non-zero exit code returned when --trust-model=always used
Bug #737128 [gnupg] gpg exits with a fatal error about missing trustdb despite
successfully having imported a key
Failed to forcibly merge 735363: Not altering archived bugs; see unarchive.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
735363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735363
737128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737128
740316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 2 errors): your mail
Processing commands for cont...@bugs.debian.org: severity 763301 important Bug #763301 [xul-ext-zotero] xul-ext-zotero: broken with iceweasel 31.1.0esr-1 Severity set to 'important' from 'grave' Michele Cane, PhD. Unknown command or malformed arguments to command. Sent from my Android device. Unknown command or malformed arguments to command. End of message, stopping processing here. Please contact me if you need assistance. -- 763301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766920: initramfs-tools: update-initramfs makes system unbootable due to missing rootfs
On Mon, 27 Oct 2014 00:54:54 + Ben Hutchings b...@decadent.org.uk wrote: After a reboot, the system is unbootable due to a missing rootfs. [...] We support hexadecimal device numbers in the 'root=' kernel parameter when booting, but do not expect to see them at build time in the mount table. Please provide the output of 'mount' on one such system. Sorry, I forgot to mention that: # mount | grep 803 803 on / type ext4 (rw,noatime,nodiratime,discard,errors=remount-ro,data=ordered) (this is another system that had the same problem btw) You are recommended to specify the root device on the kernel command line using the syntax 'root=UUID=...' I use lilo: boot=/dev/sda root=/dev/sda3 map=/boot/map delay=20 compact prompt timeout=20 default=Linux image=/vmlinuz label=Linux read-only initrd=/initrd.img [..] I tried both, UUID= and /dev/sda3 in /etc/fstab, but the result was the same. I haven't tried lilo.conf yet. I'll let you know. BTW, UUID is great for mounting removable devices, but for fixed devices it may be problem: you cannot simply copy images to a disk without adapting the UUID. E.g.: I run a big number of devices and the disks are copies of a central image. Using UUID would make things more complex than using /dev/sdX in that case. R. -- ___ It is better to remain silent and be thought a fool, than to speak aloud and remove all doubt. +--+ | Richard Lucassen, Utrecht| +--+ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766910: marked as done (owfs: FTBFS[kfreebsd]: wrong ifdef __FreeBSD__)
Your message dated Mon, 27 Oct 2014 07:50:01 + with message-id e1xif3x-0007ps...@franck.debian.org and subject line Bug#766910: fixed in owfs 2.9p8-4 has caused the Debian Bug report #766910, regarding owfs: FTBFS[kfreebsd]: wrong ifdef __FreeBSD__ 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.) -- 766910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: owfs Version: 2.9p8-3 Severity: serious Tags: patch Hi, owfs still FTBFS on kfreebsd... In freebsd.patch, the #ifdefs need to be __FreeBSD_kernel__ instead. Please see attached. Then it builds fine on kfreebsd-amd64. (You have only 15 minutes left until dinstall though). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Better support for FreeBSD --- a/module/owfs/src/c/owfs.c +++ b/module/owfs/src/c/owfs.c @@ -17,6 +17,9 @@ #include owfs.h #include ow_connection.h +#ifdef __FreeBSD_kernel__ +#include sys/param.h +#endif #include sys/mount.h /* @@ -129,7 +132,11 @@ // Unmount just in case // No checks -- can fail without consequences +#ifdef __FreeBSD_kernel__ + unmount( Outbound_Control.head-name, 0); +#else umount( Outbound_Control.head-name ) ; +#endif Fuse_parse(fuse_mnt_opt, fuse_options); LEVEL_DEBUG(fuse_mnt_opt=[%s], fuse_mnt_opt); ---End Message--- ---BeginMessage--- Source: owfs Source-Version: 2.9p8-4 We believe that the bug you reported is fixed in the latest version of owfs, 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 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Danjean vdanj...@debian.org (supplier of updated owfs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 27 Oct 2014 08:18:46 +0100 Source: owfs Binary: owfs-common owfs libow-2.9-8 libowcapi-2.9-8 libow-dev libownet-2.9-8 libownet-dev owserver ow-shell ow-tools owfs-fuse owhttpd owftpd libow-php5 libownet-php libow-perl libownet-perl python-ow python-ownet libow-tcl owfs-doc owfs-dbg Architecture: all amd64 source Version: 2.9p8-4 Distribution: unstable Urgency: medium Maintainer: Vincent Danjean vdanj...@debian.org Changed-By: Vincent Danjean vdanj...@debian.org Closes: 766910 Description: libow-2.9-8 - 1-Wire File System full library libowcapi-2.9-8 - 1-Wire File System C library libow-dev - 1-Wire File System (development files) libownet-2.9-8 - owserver protocol library libownet-dev - owserver protocol library (development files) libownet-perl - Perl module for accessing 1-wire networks libownet-php - Dallas 1-wire support: PHP OWNet library libow-perl - Dallas 1-wire support: Perl5 bindings libow-php5 - Dallas 1-wire support: PHP5 bindings libow-tcl - Dallas 1-wire support: Tcl bindings owfs-common - common files used by any of the OWFS programs owfs - Dallas 1-wire support owfs-dbg - Debugging symbols for the OWFS packages owfs-doc - Dallas 1-wire support: Documentation for owfs owfs-fuse - 1-Wire filesystem owftpd - FTP daemon providing access to 1-Wire networks owhttpd- HTTP daemon providing access to 1-Wire networks owserver - Backend server for 1-Wire control ow-shell - shell utilities to talk to an 1-Wire owserver ow-tools - tools to monitor or inspect a ow-server link python-ow - Dallas 1-wire support: Python bindings python-ownet - Python module for accessing 1-wire networks Changes: owfs (2.9p8-4) unstable; urgency=medium . * Fix FTBFS[kfreebsd]: wrong ifdef __FreeBSD__ : using the good symbol, thanks Steven Chamberlain (Closes: #766910) Checksums-Sha1: 6105ae851383aab34306f8b4f7e92974c99da789 3001 owfs_2.9p8-4.dsc 9b935e718bc37e88caf3f94b74357c2c6ca1cb7d 25976 owfs_2.9p8-4.debian.tar.xz 7971570f62b09f3ca40728758ce8c41461b056ec 15768 owfs-common_2.9p8-4_all.deb 310fb1756b8a62d851abd40fafa57c86cbb0dbdd 7702 owfs_2.9p8-4_all.deb
Bug#766955: arcanist and arc: error when trying to install together
Package: arc,arcanist Version: arc/5.21q-1 Version: arcanist/0~git20141023-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-10-27 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 78% Extracting templates from packages: 100% Preconfiguring packages ... Selecting previously unselected package libdb5.3:amd64. (Reading database ... 10889 files and directories currently installed.) Preparing to unpack .../libdb5.3_5.3.28-6_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-6) ... Selecting previously unselected package libbsd0:amd64. Preparing to unpack .../libbsd0_0.7.0-2_amd64.deb ... Unpacking libbsd0:amd64 (0.7.0-2) ... Selecting previously unselected package libedit2:amd64. Preparing to unpack .../libedit2_3.1-20140620-2_amd64.deb ... Unpacking libedit2:amd64 (3.1-20140620-2) ... Selecting previously unselected package libgcrypt20:amd64. Preparing to unpack .../libgcrypt20_1.6.2-4_amd64.deb ... Unpacking libgcrypt20:amd64 (1.6.2-4) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libnettle4:amd64. Preparing to unpack .../libnettle4_2.7.1-3_amd64.deb ... Unpacking libnettle4:amd64 (2.7.1-3) ... Selecting previously unselected package libhogweed2:amd64. Preparing to unpack .../libhogweed2_2.7.1-3_amd64.deb ... Unpacking libhogweed2:amd64 (2.7.1-3) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2) ... Preparing to unpack .../libp11-kit0_0.20.7-1_amd64.deb ... Unpacking libp11-kit0:amd64 (0.20.7-1) over (0.18.5-3) ... Selecting previously unselected package libtasn1-6:amd64. Preparing to unpack .../libtasn1-6_4.2-2_amd64.deb ... Unpacking libtasn1-6:amd64 (4.2-2) ... Selecting previously unselected package libgnutls-deb0-28:amd64. Preparing to unpack .../libgnutls-deb0-28_3.3.8-3_amd64.deb ... Unpacking libgnutls-deb0-28:amd64 (3.3.8-3) ... Selecting previously unselected package libkeyutils1:amd64. Preparing to unpack .../libkeyutils1_1.5.9-5_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.9-5) ... Selecting previously unselected package libkrb5support0:amd64. Preparing to unpack .../libkrb5support0_1.12.1+dfsg-11_amd64.deb ... Unpacking libkrb5support0:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libk5crypto3:amd64. Preparing to unpack .../libk5crypto3_1.12.1+dfsg-11_amd64.deb ... Unpacking libk5crypto3:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libkrb5-3:amd64. Preparing to unpack .../libkrb5-3_1.12.1+dfsg-11_amd64.deb ... Unpacking libkrb5-3:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libgssapi-krb5-2:amd64. Preparing to unpack .../libgssapi-krb5-2_1.12.1+dfsg-11_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libsasl2-modules-db:amd64. Preparing to unpack .../libsasl2-modules-db_2.1.26.dfsg1-12_amd64.deb ... Unpacking libsasl2-modules-db:amd64 (2.1.26.dfsg1-12) ... Selecting previously unselected package libsasl2-2:amd64. Preparing to unpack .../libsasl2-2_2.1.26.dfsg1-12_amd64.deb ... Unpacking libsasl2-2:amd64 (2.1.26.dfsg1-12) ... Selecting previously unselected package libldap-2.4-2:amd64. Preparing to unpack .../libldap-2.4-2_2.4.40-2_amd64.deb ... Unpacking libldap-2.4-2:amd64 (2.4.40-2) ... Selecting previously unselected package libmagic1:amd64. Preparing to unpack .../libmagic1_1%3a5.20-1_amd64.deb ... Unpacking libmagic1:amd64 (1:5.20-1) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.2+dfsg1-1_amd64.deb ... Unpacking libxml2:amd64 (2.9.2+dfsg1-1) ... Selecting previously unselected package librtmp1:amd64. Preparing to unpack .../librtmp1_2.4+20131018.git79459a2-4_amd64.deb ... Unpacking librtmp1:amd64 (2.4+20131018.git79459a2-4) ... Selecting previously unselected package libssh2-1:amd64. Preparing to unpack .../libssh2-1_1.4.3-4_amd64.deb ... Unpacking libssh2-1:amd64 (1.4.3-4) ... Selecting previously unselected package libcurl3:amd64. Preparing to unpack .../libcurl3_7.38.0-2_amd64.deb ... Unpacking libcurl3:amd64 (7.38.0-2) ... Selecting previously unselected package libonig2:amd64. Preparing to unpack .../libonig2_5.9.5-2_amd64.deb ... Unpacking libonig2:amd64 (5.9.5-2) ... Selecting previously unselected package psmisc. Preparing to unpack .../psmisc_22.21-2_amd64.deb ... Unpacking psmisc (22.21-2) ... Selecting previously unselected package libperl4-corelibs-perl. Preparing to unpack .../libperl4-corelibs-perl_0.003-1_all.deb ... Unpacking libperl4-corelibs-perl (0.003-1) ... Selecting previously unselected package lsof.
Bug#766956: postgresql: 9.4 not released upstream
Package: postgresql Version: 9.4+163 Severity: serious Tags: upstream Justification: 5.a) Hi, since it is now less than 10 days from Nov 5th and upstream hasn't released PostgreSQL 9.4 just yet http://www.postgresql.org/docs/9.4/static/release-9-4.html I wonder what the rationale is for this metapackage to depend on 9.4 ? A catalog bump *did* happen between beta2 and beta3, for example. Karsten -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16-3-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages postgresql depends on: ii postgresql-9.4 9.4~beta3-3 postgresql recommends no packages. Versions of packages postgresql suggests: pn postgresql-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
Hi all, I'm being heavily bitten by this one as well and I'm mildly shocked to see it crop up this late in the release cycle. I'm not going to hide that I believe this ought to be reassigned to base-files. I'll try to elaborate below. Santiago Vila wrote: [...] In this particular case, I believe the reason for the failure (that didn't happen before) is some change in base-passwd, not something that base-files does differently now. I tend to disagree: base-passwd hasn't been touched since 2014-09-04, whereas debootstrap only started to fail last week, when base-files 7.7 was uploaded. It's this change I believe: http://sources.debian.net/src/base-files/7.7/debian/postinst.in/?hl=132,133,134#L132 Causing chown: invalid user: 'root:root' Admittedly, though, this just exposes a problem that had been lingering for a while as the calls to chown using root:root could have been invoked from several bits of the postinst script. In principle, every essential package may depend on any other, and the set of real dependencies may change over time, so it's natural that debootstrap needs minor adjustments from time to time. So would you expect some sort of versioned dependencies in debootstrap? As the upload of base-files 7.7 showed, it is changes in packages that suddenly require new hacks. And a key problem is that tools like debootstrap ought to work from within, e.g., stable release to bootstrap future releases like testing or unstable. Suggesting that a bootstrapping tool is changed due to updates in another package is going to cause a major dependency loop as at least testing efforts such as those of jenkins.d.n will be broken. In fact it would be easier to codify this in dpkg than in debootstrap, I believe, as dpkg would live in the same suite as the package to be installed. But this sounds like very bad design indeed. You will find a more complete explanation of this in the logs for Bug#760568 where I'm asked no less than to depend on base-passwd, which is essential! IMHO, this is definitely not the way to go. Using the essential! hammer doesn't sound like a great argument when your package is essential. It's past time to be untangling the Essential hairball. Correct dependency metadata is much more scalable than hacks in debootstrap. I agree that you may have a point here. In fact, in the aforementioned bug #760568 against cdebootstrap, which is very similar to this one, I suggested the idea that if the knowledge about right package ordering among essential packages were codified and written somewhere, other similar tools could use the same information without having to reinvent the wheel. I see now that the control file could be such common place to have that information, but I would like to see a little bit of *design* before doing anything which is not in policy yet. For example, we could use: * The same Depends field we are using for normal dependencies. * A new field for this particular purpose which dpkg and friends ignore under normal circumstances, and an environment variable which debootstrap may set to tell dpkg and friends that they should actually honor them instead of ignoring them. * An extension of the Depends field, much like !stage1 is used in Build-Depends for build profiles. So yes, we could consider to codify this metadata (the fact that base-files postinst uses chown and expect the root user to exist, for example) in *some* way... Stop being part of the problem, and add the dependency already.. ... but please let us think about it first. Starting to add Depends field here and there in a random fashion just because it makes debootstrap not to fail anymore is not something I will be happy with. I do fully agree that care must be taken, as dependency loops would obviously be a major problem. The Depends field is implicit among the set of essential packages. I'm not too sure about the among bit here? No doubt that this is implicit for any non-essential package, but among them I'm not sure whether any rules apply right now? If a tool like apt-get or dpkg really behaves in a different way when I add a Depends field which was already implicit, I think that there is something fundamentally wrong here. Does dpkg really add the essential information into its dependency information? Wouldn't this rather be seen as ah, essential, so it must be there? At least briefly looking at dpkg's source code I cannot seem to see dpkg considering this implicit dependency at all (unless attempting to remove an essential package). So, to summarize: I'm not opposed to modify policy when it says that we don't need to include dependencies on essential packages, but if we decide to go that route, please let us do it according to some *plan*, not in a random fashion, because otherwise, IMHO, *that* would be the real hack. I do appreciate being careful, but then bug fixes for a bug of normal severity (#763405) shouldn't
Bug#766459: debootstrap: should not try to configure
On Mon, Oct 27, 2014 at 08:35:14 +, Michael Tautschnig wrote: Hi all, I'm being heavily bitten by this one as well and I'm mildly shocked to see it crop up this late in the release cycle. I'm not going to hide that I believe this ought to be reassigned to base-files. I'll try to elaborate below. I agree this should be fixed in base-files. Santiago Vila wrote: [...] In this particular case, I believe the reason for the failure (that didn't happen before) is some change in base-passwd, not something that base-files does differently now. I tend to disagree: base-passwd hasn't been touched since 2014-09-04, whereas debootstrap only started to fail last week, when base-files 7.7 was uploaded. It's this change I believe: http://sources.debian.net/src/base-files/7.7/debian/postinst.in/?hl=132,133,134#L132 Causing chown: invalid user: 'root:root' Can't base-files call chown with 0:0 instead of root:root to sidestep this entirely? Cheers, Julien signature.asc Description: Digital signature
Bug#765285: anwser from MIPs team
Indeed, the mips team gave me an answer on issue [0] This implies modifications on sync methods. I have sent info upstream to see if they are willing to change that. [0] https://lists.debian.org/debian-mips/2014/10/msg8.html -- Olivier Sallou IRISA / University of Rennes 1 Campus de Beaulieu, 35000 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762782: marked as done (libprocps4-dev and libprocps3-dev: error when trying to install together)
Your message dated Mon, 27 Oct 2014 11:11:09 +0200 with message-id 20141027091109.GE18991@sid.nuvreauspam and subject line Re: Bug#762782: libprocps4-dev and libprocps3-dev: error when trying to install together has caused the Debian Bug report #762782, regarding libprocps4-dev and libprocps3-dev: 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.) -- 762782: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libprocps3-dev,libprocps4-dev Version: libprocps3-dev/1:3.3.9-7 Version: libprocps4-dev/1:3.3.10-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-09-25 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 libprocps3:amd64. (Reading database ... 10876 files and directories currently installed.) Preparing to unpack .../libprocps3_1%3a3.3.9-7_amd64.deb ... Unpacking libprocps3:amd64 (1:3.3.9-7) ... Selecting previously unselected package libprocps4:amd64. Preparing to unpack .../libprocps4_1%3a3.3.10-1_amd64.deb ... Unpacking libprocps4:amd64 (1:3.3.10-1) ... Selecting previously unselected package libprocps3-dev. Preparing to unpack .../libprocps3-dev_1%3a3.3.9-7_amd64.deb ... Unpacking libprocps3-dev (1:3.3.9-7) ... Selecting previously unselected package libprocps4-dev. Preparing to unpack .../libprocps4-dev_1%3a3.3.10-1_amd64.deb ... Unpacking libprocps4-dev (1:3.3.10-1) ... dpkg: error processing archive /var/cache/apt/archives/libprocps4-dev_1%3a3.3.10-1_amd64.deb (--unpack): trying to overwrite '/usr/include/proc/sysinfo.h', which is also in package libprocps3-dev 1:3.3.9-7 Errors were encountered while processing: /var/cache/apt/archives/libprocps4-dev_1%3a3.3.10-1_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 packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/include/proc/alloc.h /usr/include/proc/devname.h /usr/include/proc/escape.h /usr/include/proc/procps.h /usr/include/proc/pwcache.h /usr/include/proc/readproc.h /usr/include/proc/sig.h /usr/include/proc/slab.h /usr/include/proc/sysinfo.h /usr/include/proc/version.h /usr/include/proc/wchan.h /usr/include/proc/whattime.h /usr/lib/x86_64-linux-gnu/libprocps.a /usr/lib/x86_64-linux-gnu/libprocps.so /usr/lib/x86_64-linux-gnu/pkgconfig/libprocps.pc This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- On Du, 26 oct 14, 19:09:55, gregor herrmann wrote: On Thu, 25 Sep 2014 09:12:10 +0200, Ralf Treinen wrote: Package: libprocps3-dev,libprocps4-dev Version: libprocps3-dev/1:3.3.9-7 Version: libprocps4-dev/1:3.3.10-1 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: libprocps4-dev doesn't exist anymore, so I guess this bug can be closed. Done. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature ---End Message---
Bug#762782: libprocps4-dev and libprocps3-dev: error when trying to install together
On Mon, 27 Oct 2014 11:11:09 +0200, Andrei POPESCU wrote: libprocps4-dev doesn't exist anymore, so I guess this bug can be closed. Done. Great, thanks. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #420: Feature was not beta tested -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766956: marked as done (postgresql: 9.4 not released upstream)
Your message dated Mon, 27 Oct 2014 10:22:44 +0100 with message-id 20141027092244.ga21...@msg.df7cb.de and subject line Re: Bug#766956: postgresql: 9.4 not released upstream has caused the Debian Bug report #766956, regarding postgresql: 9.4 not released upstream 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.) -- 766956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: postgresql Version: 9.4+163 Severity: serious Tags: upstream Justification: 5.a) Hi, since it is now less than 10 days from Nov 5th and upstream hasn't released PostgreSQL 9.4 just yet http://www.postgresql.org/docs/9.4/static/release-9-4.html I wonder what the rationale is for this metapackage to depend on 9.4 ? A catalog bump *did* happen between beta2 and beta3, for example. Karsten -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16-3-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages postgresql depends on: ii postgresql-9.4 9.4~beta3-3 postgresql recommends no packages. Versions of packages postgresql suggests: pn postgresql-doc none -- no debconf information ---End Message--- ---BeginMessage--- Re: Karsten Hilbert 2014-10-27 20141027082547.22471.78277.report...@hermes.hilbert.loc since it is now less than 10 days from Nov 5th and upstream hasn't released PostgreSQL 9.4 just yet http://www.postgresql.org/docs/9.4/static/release-9-4.html I wonder what the rationale is for this metapackage to depend on 9.4 ? A catalog bump *did* happen between beta2 and beta3, for example. 9.4 will release soonish. It's unfortunate that 9.4.0 isn't out yet, but all new minor releases will be included in jessie as usual for PostgreSQL in all testing/stable releases. Christoph -- c...@df7cb.de | http://www.df7cb.de/---End Message---
Bug#766966: g++-4.9-arm-linux-gnueabihf: Cannot install package due to conflict with debian's gcc-4.9-base-4.9.1-19
Package: g++-4.9-arm-linux-gnueabihf Severity: grave Justification: renders package unusable Dear Maintainer, I cannot install gnueabihf for armhf toolchain on amd64 platform. g++-4.9-arm-linux-gnueabihf : Depends: gcc-4.9-base (= 4.9.1-18) but 4.9.1-19 is to be installed Depends: cpp-4.9-arm-linux-gnueabihf (= 4.9.1-18) but it is not going to be installed Depends: gcc-4.9-arm-linux-gnueabihf (= 4.9.1-18) but it is not going to be installed Depends: libstdc++-4.9-dev:armhf (= 4.9.1-18) but it is not going to be installed E: Unable to correct problems, you have held broken packages. I believe this is because current gcc-4.9-base in Debian is 4.9.1-19 which is in conflict with 4.9.1-18, and there is no existing package of gcc-4.9-base-4.9.1-18 for amd64 architecture in any repository. Solution would probably to update packages. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 armhf Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash
Bug#725372: marked as done (python-sqlkit should depend on python-babel, and not python-pybabel anymore)
Your message dated Mon, 27 Oct 2014 09:38:23 + with message-id e1xigkp-0005na...@franck.debian.org and subject line Bug#725372: fixed in sqlkit 0.9.6.1-1 has caused the Debian Bug report #725372, regarding python-sqlkit should depend on python-babel, and not python-pybabel anymore 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.) -- 725372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-sqlkit Version: 0.9.5-1 Severity: serious Hi, I would like to remove python-pybabel from the archive, as this is a transitional package. Please switch to python-pybabel for your dependency. Cheers, Thomas Goirand (zigo) ---End Message--- ---BeginMessage--- Source: sqlkit Source-Version: 0.9.6.1-1 We believe that the bug you reported is fixed in the latest version of sqlkit, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 725...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pietro Battiston m...@pietrobattiston.it (supplier of updated sqlkit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 26 Oct 2014 23:25:19 + Source: sqlkit Binary: python-sqlkit python-sqlkit-doc Architecture: source all Version: 0.9.6.1-1 Distribution: unstable Urgency: medium Maintainer: Pietro Battiston m...@pietrobattiston.it Changed-By: Pietro Battiston m...@pietrobattiston.it Description: python-sqlkit - Python tools and GUI application to view and edit databases conte python-sqlkit-doc - documentation for python-sqlkit and sqledit application Closes: 725372 Changes: sqlkit (0.9.6.1-1) unstable; urgency=medium . * Imported Upstream version 0.9.6.1 * Depend on python-babel rather than python-pybabel (Closes: #725372) * Updated Debian policy version (no change needed) * Specified BSD license version in debian/copyright * Install icons in /usr/share Checksums-Sha1: 49a8aa0a3c8aee5355c4d2f1cba8b6a4eddfbbd7 2067 sqlkit_0.9.6.1-1.dsc 575c6266c1d15a6ccb764296816612363f7fef89 4548382 sqlkit_0.9.6.1.orig.tar.gz 7b76e98c00faaee3af96e3497f15cc650a06f3af 7428 sqlkit_0.9.6.1-1.debian.tar.xz eeda7051ddc5f0ad22e19a9cccee89550e358732 217866 python-sqlkit_0.9.6.1-1_all.deb ff0809629357fa00853370612c1ba98684c6bef5 212784 python-sqlkit-doc_0.9.6.1-1_all.deb Checksums-Sha256: 46778a210d720ff395b40006c109ed14798eccc81a8702b459a56156f9f67bc1 2067 sqlkit_0.9.6.1-1.dsc 0a3562ed8f5520e6e012d12fa50be98f3f30381abe1a78c7afe69a61d5994f83 4548382 sqlkit_0.9.6.1.orig.tar.gz 320926e557b9f0344132353b73c8b21f413259ab7320f43e936005748e7575b7 7428 sqlkit_0.9.6.1-1.debian.tar.xz d82dacf087c459f171b8c70bd7d4bf09b75ee4e2d6e357c9d401ccd55f430426 217866 python-sqlkit_0.9.6.1-1_all.deb e0f9c791fcc74a2dc61023a65fe916abfb1437fb9da461b65b951e17dde3fb9b 212784 python-sqlkit-doc_0.9.6.1-1_all.deb Files: 8df3e42cfa52f8c2d9589703692d3ac4 2067 python optional sqlkit_0.9.6.1-1.dsc dfc9ff3277a6ac1e492c149111cf9a00 4548382 python optional sqlkit_0.9.6.1.orig.tar.gz 9126fe2ee7fe3bd1320e99502ff7f820 7428 python optional sqlkit_0.9.6.1-1.debian.tar.xz 73ed93d830d28f2dd1c203587ed13248 217866 python optional python-sqlkit_0.9.6.1-1_all.deb f2091803ab2dd949182eba954d7e71ec 212784 doc optional python-sqlkit-doc_0.9.6.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUTgzmAAoJEK728aKnRXZFouoQAJwg5+d63EUc6nXaAeGbpOX5 2Re+AmmF9N0F95IyZkLexZgQk2PtjX9ePgOujKdF+fsLaQQpZ9b5qEZ0ftZq18hC 2YHhMLoftDJPCa3iM4w8mjyrFhQzx2bA4WpX8Vy8lz8ZwAiDCDBo0MTf5JbmDxEY 0XkmJlnPuqlB0NyzPTP+UiODNJ0wtcn3wnr9WoDjv3tzO4Vne4neAn2sPYTPWQfe uZbqCYR1aTup204LOYf0Gn/O2tLXpBs7yxX56/pSk8i6yQiOlE8WBslL9N9WgP6n qi2wiil0fDMtMooEDZMUH4ZllkcbKPg1mlwIPYvsNxArGY9uT35eMiwyOdT5mput yOMMZD1XzMrtjL+5wOWOYb19uRGGYxHRJqiUP/GETKO3BIEKGT1nG+s0n/pb5Q7L AUUfYM2fuOjhdQg+D5J9pG+cqNi6izY4LD9sWvbW41OOEZEvEphJ2h4Z1Rt+6nbP FBqtvsQ/CRinX5x1PnKEQndd8bOwSehl8NmaNBoobIX0Vgdlv/nzksTgIoD1mNxw 0sMxtO15K98mSUDppMH76ziQqzsLo2WRAoYzaf4FFnkZ46YLDNVtFFB+0nOmkfoX 93weU/9+MBj4KkfvvHPuAaNuaxHxsfJKLAuzxdzCKnMQbDxnVEm8cr4KaeJHcvtZ BP6ySCYC+8ohRLB+UN3+ =9V8u -END PGP SIGNATUREEnd Message---
Bug#750557: pgadmin3: segmentation fault
Re: To bmorel 2014-09-11 20140911093144.ga7...@msg.df7cb.de Hi guys, I've just uploaded 1.20.0~beta1 to unstable. Could you check if you still see the pgadmin3 crashes there? It seems to work for me now. Packages on apt.postgresql.org should be available shortly in the *-pgdg-testing suites. Hi again, there's now 1.20.0~beta2-1 in unstable. Could you give that a try again? I don't see the crash in beta2 here. Also, would you say this bug makes pgadmin3 unusable, or is the rest of the functionality working just fine? I'm pondering downgrading the severity of this bug to just important so we at least have a mostly-working version of pgadmin3 in jessie. Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
I'm going to reply to Julien first, then to Michael. On Mon, 27 Oct 2014, Julien Cristau wrote: On Mon, Oct 27, 2014 at 08:35:14 +, Michael Tautschnig wrote: I agree this should be fixed in base-files. Bugs should be fixed where they are. If base-files, or any other package, essential or not, can't make a simple chown root:root, then it is a bug in whatever package was responsible for making sure that the root user exist in a Debian system, base-passwd and debootstrap in this case. This is regardless the fact that base-files could do things differently so that this bug remains hidden a few more months or a few more years. I am investigating the last option right now, but not as a way to fix bugs in debootstrap (which I believe they should be fixed anyway), but as a way to avoid our users to find this problem. BTW: At least once in the past I have made little changes to base-files to fix problems that happen when using debootstrap. I'm not opposed to that. See for example, changes in base-files 3.0.1 (yes, 12 years ago). But it will not be anything like adding a Depends on base-passwd. That would be a hack. chown: invalid user: 'root:root' Can't base-files call chown with 0:0 instead of root:root to sidestep this entirely? It's a little bit more complex than that. Sometimes it's root:root, sometimes is root:staff and sometimes is root:mail. See base-files postinst for details. This has worked for ages, and it should continue to work, because base-passwd is essential. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
On Mon, Oct 27, 2014 at 11:08:55 +0100, Santiago Vila wrote: This has worked for ages, and it should continue to work, because base-passwd is essential. That argument would work better if base-files wasn't also essential. Cheers, Julien signature.asc Description: Digital signature
Bug#750557: pgadmin3: segmentation fault
On Monday 27 October 2014 10:53:01 Christoph Berg wrote: Re: To bmorel 2014-09-11 20140911093144.ga7...@msg.df7cb.de Hi guys, I've just uploaded 1.20.0~beta1 to unstable. Could you check if you still see the pgadmin3 crashes there? It seems to work for me now. Packages on apt.postgresql.org should be available shortly in the *-pgdg-testing suites. Hi again, there's now 1.20.0~beta2-1 in unstable. Could you give that a try again? I don't see the crash in beta2 here. Also, would you say this bug makes pgadmin3 unusable, or is the rest of the functionality working just fine? I'm pondering downgrading the severity of this bug to just important so we at least have a mostly-working version of pgadmin3 in jessie. Christoph Hi Christoph, It seems the crash if fixed, I can't reproduce it anymore. Thanks! BogDan. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
On Mon, 27 Oct 2014, Michael Tautschnig wrote: In principle, every essential package may depend on any other, and the set of real dependencies may change over time, so it's natural that debootstrap needs minor adjustments from time to time. So would you expect some sort of versioned dependencies in debootstrap? No, not at all. I just expect debootstrap maintainers to cooperate with the release managers to ensure that the version in stable is able to debootstrap the testing distribution, whenever it is possible to do so. I've heard that the version in wheezy-backports does not have this problem. Maybe it could be just a matter of making an upload for the next point release. I don't know. [...] The Depends field is implicit among the set of essential packages. I'm not too sure about the among bit here? No doubt that this is implicit for any non-essential package, but among them I'm not sure whether any rules apply right now? I mean that the rule saying Package A does not need a Depends: B if B is essential does not say anything about the essentialness of *A*, which means the rule is valid regardless of A being essential or not. The fact that base-files is essential is quite irrelevent. A chown in the postinst should not fail, and if it does, there is a bug in debootstrap. If a tool like apt-get or dpkg really behaves in a different way when I add a Depends field which was already implicit, I think that there is something fundamentally wrong here. Does dpkg really add the essential information into its dependency information? Wouldn't this rather be seen as ah, essential, so it must be there? At least briefly looking at dpkg's source code I cannot seem to see dpkg considering this implicit dependency at all (unless attempting to remove an essential package). In the general case we don't have to worry about that because once that essential packages are properly installed and configured, they will continue to work all the time unless apt-get does some really weird things. But how are we expected to have all the essential packages properly installed and configured? Should base-files worry about base-passwd being properly installed and configured before making a chown? Certainly not, this is the work of debootstrap! [...] I do appreciate being careful, but then bug fixes for a bug of normal severity (#763405) shouldn't be causing RC bugs either. Fixing bugs in one package usually makes hidden bugs in other packages to become no longer hidden. This happens all the time and it's not a good argument to *not* fix the bugs where they are. In either case, I'm going to re-examine carefully what I did in base-files 7.7 and see if there is a simple workaround that may be done to avoid this problem. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766974: asterisk-espeak: FTBFS: fails to build with asterisk 13. Use latest version
Source: asterisk-espeak Version: 2.1-1+b1 Severity: grave asterisk-espeak fails to build with asterisk 13: gcc -pipe -fPIC -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -D_REENTRANT -D_GNU_SOURCE -g -O2 -c -o app_espeak.o app_espeak.c app_espeak.c: In function āespeak_execā: app_espeak.c:219:13: error: dereferencing pointer to incomplete type if (chan-_state != AST_STATE_UP) ^ app_espeak.c:221:47: error: dereferencing pointer to incomplete type res = ast_streamfile(chan, cachefile, chan-language); ^ app_espeak.c:224:12: error: dereferencing pointer to incomplete type chan-name); ^ app_espeak.c:331:10: error: dereferencing pointer to incomplete type if (chan-_state != AST_STATE_UP) ^ app_espeak.c:333:43: error: dereferencing pointer to incomplete type res = ast_streamfile(chan, raw_name, chan-language); ^ app_espeak.c:335:67: error: dereferencing pointer to incomplete type ast_log(LOG_ERROR, eSpeak: ast_streamfile failed on %s\n, chan-name); ^ Makefile:38: recipe for target 'app_espeak.o' failed make: *** [app_espeak.o] Error 1 This seems to have been fixed by upstream in https://github.com/zaf/Asterisk-eSpeak/commit/bf0c07f59b0b62a609a1e94dff40171c09f16e5d I would suggest to get the latest upstream version, which is verified to build with Asterisk 13. -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best tzaf...@debian.org|| friend -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
I'm hoping this is not going to be too philosophical, so I'll enlist the facts first (please let me know if I got any of them wrong): debootstrap'ing a system fails, because - chown root:root ... won't work when invoked from base-files' postinst - version 7.7 of base-files is the first to actually have this call when invoked from within (c)debootstrap - using root:root relies on /etc/passwd and /etc/group being in place and populated - /etc/passwd and /etc/group are provided by base-passwd, which is essential On Mon, Oct 27, 2014 at 11:08:55 +0100, Santiago Vila wrote: I'm going to reply to Julien first, then to Michael. On Mon, 27 Oct 2014, Julien Cristau wrote: On Mon, Oct 27, 2014 at 08:35:14 +, Michael Tautschnig wrote: I agree this should be fixed in base-files. Bugs should be fixed where they are. If base-files, or any other package, essential or not, can't make a simple chown root:root, then it is a bug in whatever package was responsible for making sure that the root user exist in a Debian system, base-passwd and debootstrap in this case. [...] This has worked for ages, and it should continue to work, because base-passwd is essential. So let's see what Debian Policy says in 3.8 Essential packages: [...] Since dpkg will not prevent upgrading of other packages while an essential package is in an unconfigured state, all essential packages must supply all of their core functionality even when unconfigured. If the package cannot satisfy this requirement it must not be tagged as essential, and any packages depending on this package must instead have explicit dependency fields as appropriate. [...] While base-passwd is essential, the question seems to be whether providing /etc/passwd and /etc/group are its core functionality. The description of base-passwd states: These are the canonical master copies of the user database files (/etc/passwd and /etc/group), containing the Debian-allocated user and group IDs. The package base-passwd, however, will only copy those files into place in its postinst script. It may thus be argued (if provision of the files is considered core functionality) that base-passwd violates policy. Yet it may be impossible for base-passwd to implement this bit of policy unless unconditionally overwriting /etc/passwd and /etc/group were deemed acceptable (which it surely isn't, unless we implement something like /etc/passwd.d/ and /etc/group.d/). A collection of possible ways forward - feel free to add more: - base-passwd should no longer be marked essential, but instead base-files should depend on it (making base-passwd implicitly essential), hence neither would base-passwd be violating policy nor would we any longer face the problems in base-files/(c)debootstrap. But maybe other issues arise, which I might not be aware of. - base-files should explicitly depend on base-passwd, because it uses functionality that is not considered core functionality of base-passwd. - We ignore the policy violation of base-passwd or consider the use of /etc/passwd in base-files use of non-core functionality and hence ignore the bug in base-files. Either ignorance will then require working around those bugs in (c)debootstrap. Best, Michael pgpptAtfcWCFP.pgp Description: PGP signature
Bug#766956: postgresql: 9.4 not released upstream
Re: Karsten Hilbert 2014-10-27 20141027094648.ga22...@hermes.hilbert.loc If I understand this correctly you are saying that even though Jessie may be frozen with PG 9.4.betaX there will still be PG 9.4 packages entering Jessie no matter which point along the release schedule Jessie happens to be - even after its release early next year ? Yes. If so that'd solve the apparent problem. It won't prevent the following scenario though: - Jessie is released with PG 9.4.betaX - PG releases 9.4.betaX+1 which requires a dump/restore cycle due to a catalog bump (PG doesn't guarantuee catalog stability across betas as much as across released minors) - now people running PG on Debian STABLE need to dump/restore their clusters This was the last 9.4 catversion bump. Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766975: asterisk-flite: FTBFS: fails to build with asterisk 13. Use latest version
Source: asterisk-flite Version: 2.1-1.1 Severity: grave asterisk-flite fails to build with asterisk 13: gcc -pipe -fPIC -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -D_REENTRANT -D_GNU_SOURCE -g -O2 -c -o app_flite.o app_flite.c app_flite.c: In function āflite_execā: app_flite.c:168:13: error: dereferencing pointer to incomplete type if (chan-_state != AST_STATE_UP) ^ app_flite.c:170:47: error: dereferencing pointer to incomplete type res = ast_streamfile(chan, cachefile, chan-language); ^ app_flite.c:173:12: error: dereferencing pointer to incomplete type chan-name); ^ app_flite.c:239:10: error: dereferencing pointer to incomplete type if (chan-_state != AST_STATE_UP) ^ app_flite.c:241:43: error: dereferencing pointer to incomplete type res = ast_streamfile(chan, tmp_name, chan-language); ^ app_flite.c:243:66: error: dereferencing pointer to incomplete type ast_log(LOG_ERROR, Flite: ast_streamfile failed on %s\n, chan-name); ^ Makefile:38: recipe for target 'app_flite.o' failed make: *** [app_flite.o] Error 1 This seems to have been fixed by upstream in https://github.com/zaf/Asterisk-Flite/commit/ee1b1a88b96dddf7a85f0f7b854501ecdcee1765 I would suggest to get the latest upstream version, which is verified to build with Asterisk 13. -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best tzaf...@debian.org|| friend -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
Apologies if I may be repeating information as we were concurrently working on those messages. On Mon, Oct 27, 2014 at 11:34:06 +0100, Santiago Vila wrote: [...] I just expect debootstrap maintainers to cooperate with the release managers to ensure that the version in stable is able to debootstrap the testing distribution, whenever it is possible to do so. This should, however, ideally work both ways: any package modification expected to break debootstrap would have to be communicated. But arguably this will not necessarily be obvious, as can be seen here. I've heard that the version in wheezy-backports does not have this problem. Maybe it could be just a matter of making an upload for the next point release. I don't know. That's because of the following workaround, which is being disputed: debootstrap (1.0.56) unstable; urgency=low . [ Tollef Fog Heen ] * Install base-passwd and base-files in two calls rather than one to avoid problems with home-built media with different ordering in Packages. Thanks to Jo Shields for pointing this out and providing the workaround. Closes: #601670. LP: #1001131. Though see my earlier mail: if debootstrap ends up being the package to finally close this bug, then, yes, this might be the route to go. [...] If a tool like apt-get or dpkg really behaves in a different way when I add a Depends field which was already implicit, I think that there is something fundamentally wrong here. Does dpkg really add the essential information into its dependency information? Wouldn't this rather be seen as ah, essential, so it must be there? At least briefly looking at dpkg's source code I cannot seem to see dpkg considering this implicit dependency at all (unless attempting to remove an essential package). In the general case we don't have to worry about that because once that essential packages are properly installed and configured, they will continue to work all the time unless apt-get does some really weird things. Yes and no: mind that that essential only provides guarantees for functionality being available as soon as the package is unpacked. The configured bit is irrelevant for features deemed essential. But how are we expected to have all the essential packages properly installed and configured? Should base-files worry about base-passwd being properly installed and configured before making a chown? Certainly not, this is the work of debootstrap! No. As you are using the base-passwd is essential argument, base-files can only rely on functionality provided by base-passwd when that is unpacked. The order of packages being configured is not covered by essential and neither should it be debootstrap's job to sort this out (but debootstrap 1.0.56 does do this). [...] In either case, I'm going to re-examine carefully what I did in base-files 7.7 and see if there is a simple workaround that may be done to avoid this problem. Much appreciated, but obviously we should, as you suggested, see what the right way of fixing this is. Best, Michael pgp5NSVGzzADW.pgp Description: PGP signature
Bug#766353:
b) It is (more than) a courtesy for users / developers who run testing I agree with that one, but it is too late now. e) Is there any problem of uploading libjpeg-progs just with the appropriate breaks/relationship? I think the RMs would have no problem accelerating this into testing. This would be pointless since the bug was in libjpeg-turbo-progs and is now fixed and is not more reproducible when starting from wheezy or current testing. The number of users still having the broken libjpeg-turbo-progs is smaller everyday. I had to fix this manually... I would had been thankful if I never had to dig into this bug. Why is too late? add the breaks/replace... remove it in some forthcoming upload in 6 months. Me think you can even break an specific version... so you could help those people with the broken package installed and no making it break the current version that is not broken... And that upload could be used to close this RC bug that is still open for the current version and needs to be fixed before jessie Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766956: postgresql: 9.4 not released upstream
On Mon, Oct 27, 2014 at 11:48:37AM +0100, Christoph Berg wrote: If so that'd solve the apparent problem. It won't prevent the following scenario though: - Jessie is released with PG 9.4.betaX - PG releases 9.4.betaX+1 which requires a dump/restore cycle due to a catalog bump (PG doesn't guarantuee catalog stability across betas as much as across released minors) - now people running PG on Debian STABLE need to dump/restore their clusters This was the last 9.4 catversion bump. Fingers crossed. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
On Mon, 27 Oct 2014, Michael Tautschnig wrote: I'm hoping this is not going to be too philosophical, so I'll enlist the facts first (please let me know if I got any of them wrong): debootstrap'ing a system fails, because - chown root:root ... won't work when invoked from base-files' postinst - version 7.7 of base-files is the first to actually have this call when invoked from within (c)debootstrap Regarding previous point, it should be noted that base-files postinst has a lot of chown calls. I would like to know how it is possible that only the recently added is the one that fails and not the others (if that's really the case). BTW: I don't know what is the proper way to debug this (private repository using reprepro?). Can anybody confirm that the chown that fails is exactly the one at the very end? So let's see what Debian Policy says in 3.8 Essential packages: [...] Since dpkg will not prevent upgrading of other packages while an essential package is in an unconfigured state, all essential packages must supply all of their core functionality even when unconfigured. If the package cannot satisfy this requirement it must not be tagged as essential, and any packages depending on this package must instead have explicit dependency fields as appropriate. [...] This is about dpkg when making upgrades. It means that once an essential package is properly configured, it should not stop working because of it being unconfigured by dpkg (whatever that means). I think it does not apply here. [ snipped philosophical stuff. I would much prefer to have free time to work on this rather than discuss about it. Really ]. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766868: haml-elisp: Fails to install with Emacs 24.4
Hi, Sven Joachim wrote: In toplevel form: haml-mode.el:30:1:Error: Symbol's function definition is void: apropos-macrop The offending line reads like this: (require 'css-mode nil t) and it is css-mode.el from the css-mode package which uses apropos-macrop. I would suggest that you remove this package, because Emacs has included its own css-mode.el since version 22.2[1]. Thanks for that hint. It's though not possible that easily as it has hard reverse dependencies: html-helper-mode depends on it. Then again, html-helper-mode has seen the last upload in 2006 and there's no new upstream release since then, too. So maybe I should check Emacs's own HTML mode(s?) once again. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766251: [pkg-fgfs-crew] Bug#766251: flightgear fails to start with *** stack smashing detected ***
On 10/22/2014 11:34 PM, Rebecca N. Palmer wrote: The debian/patches/series mechanism won't patch DOS-line-ending files Sure? It seems to have worked for me - as long as I keept the DOS-line-endings in the data section of the patch. See what I committed. Regards Markus -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766911: None (Justification: renders package unusable)
* What was the outcome of this action? this results in a a I/O error Please post the exact error message. Also, it might be useful you disclose the context by posting the output of the commands below : uname -a ntfs-3g -help cat /etc/fstab mount and, as root : fdisk -l ntfsfix -n /dev/sda1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
Hi, On Montag, 27. Oktober 2014, Santiago Vila wrote: I've heard that the version in wheezy-backports does not have this problem. yes. Maybe it could be just a matter of making an upload for the next point release. I don't know. the^wa fix is in the wheezy branch already: https://anonscm.debian.org/cgit/d-i/debootstrap.git/log/?h=wheezy cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#750557: Bug#754114: Bug#750557: pgadmin3: segmentation fault
-=| Bogdan Vatra, 27.10.2014 12:16:16 +0200 |=- On Monday 27 October 2014 10:53:01 Christoph Berg wrote: Re: To bmorel 2014-09-11 20140911093144.ga7...@msg.df7cb.de there's now 1.20.0~beta2-1 in unstable. Could you give that a try again? I don't see the crash in beta2 here. Also, would you say this bug makes pgadmin3 unusable, or is the rest of the functionality working just fine? I'm pondering downgrading the severity of this bug to just important so we at least have a mostly-working version of pgadmin3 in jessie. It seems the crash if fixed, I can't reproduce it anymore. Same here. No crashes. I notice a small glitch that may be related. After opening the database maintenance dialog, hovering over any of the checkboxes or the first radio button (VACUUM) changes the mouse pointer to a nw-se resizing arrow, which is not the standard resizing arrow for the graphical environment (GNOME) but something else. Not sure about the bug's severity. I use unstable, so I am not even sure the bug still applies to the version in jessie. There was an update of wx3.0 some weeks ago that may as well sbe fixing this bug. Thanks for bringing beta2 to unstable, dam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
Holger Levsen hol...@layer-acht.org (2014-10-27): Hi, On Montag, 27. Oktober 2014, Santiago Vila wrote: I've heard that the version in wheezy-backports does not have this problem. yes. Maybe it could be just a matter of making an upload for the next point release. I don't know. the^wa fix is in the wheezy branch already: https://anonscm.debian.org/cgit/d-i/debootstrap.git/log/?h=wheezy Well, from my cursory reading of this thread, this might just be papering over the issue, rather than fixing it. Mraw, KiBi. signature.asc Description: Digital signature
Bug#766911: ntfs-3g: .
severity 766911 important tags 766911 + moreinfo unreproducible thanks Hi Eric, On Sun, Oct 26, 2014 at 8:40 PM, Eric Moors bugrep...@someren.nl.eu.org wrote: * What led up to the situation? a simple apt-get upgrade Do you know which was the previous version? * What exactly did you do (or not do) that was effective (or ineffective)? mount the drive (mount -t ntfs-3g /dev/sda1 /mnt ls /mnt (also other actions, mkdir, mv, and cp fail with an I/O error) Please try them separate and post what's the mount output. * What was the outcome of this action? this results in a a I/O error Can it be that the disk is failing or the NTFS is dirty in any way? What happens if you reboot into windows? Kernel: Linux 2.6.32-trunk-486 Do you still have a 486 CPU? How comes that you have such an old kernel? Please upgrade to a more modern one and report back. It can be that ntfs-3g does not support such old kernels. Thanks, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#766911: ntfs-3g: .
Processing commands for cont...@bugs.debian.org: severity 766911 important Bug #766911 [ntfs-3g] ntfs-3g: . Severity set to 'important' from 'grave' tags 766911 + moreinfo unreproducible Bug #766911 [ntfs-3g] ntfs-3g: . Added tag(s) unreproducible and moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 766911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
On Mon, Oct 27, 2014 at 12:07:24 +0100, Santiago Vila wrote: On Mon, 27 Oct 2014, Michael Tautschnig wrote: I'm hoping this is not going to be too philosophical, so I'll enlist the facts first (please let me know if I got any of them wrong): debootstrap'ing a system fails, because - chown root:root ... won't work when invoked from base-files' postinst - version 7.7 of base-files is the first to actually have this call when invoked from within (c)debootstrap Regarding previous point, it should be noted that base-files postinst has a lot of chown calls. I would like to know how it is possible that only the recently added is the one that fails and not the others (if that's really the case). I suppose none of the others are being executed as all of them are guarded by some combination of checks? BTW: I don't know what is the proper way to debug this (private repository using reprepro?). Can anybody confirm that the chown that fails is exactly the one at the very end? Indeed it could be a very different one. I'm attaching a full log with the postinst script having set -evx. It might be obvious, but this is being run on a wheezy system. So let's see what Debian Policy says in 3.8 Essential packages: [...] Since dpkg will not prevent upgrading of other packages while an essential package is in an unconfigured state, all essential packages must supply all of their core functionality even when unconfigured. If the package cannot satisfy this requirement it must not be tagged as essential, and any packages depending on this package must instead have explicit dependency fields as appropriate. [...] This is about dpkg when making upgrades. It means that once an essential package is properly configured, it should not stop working because of it being unconfigured by dpkg (whatever that means). I think it does not apply here. Then maybe take the first sentence in 3.8 Essential packages instead: Essential is defined as the minimal set of functionality that must be available and usable on the system at all times, even when packages are in the Unpacked state. If not this one (and not the one above), which bit of policy are you then relying on when you do the chown calls? [ snipped philosophical stuff. I would much prefer to have free time to work on this rather than discuss about it. Really ]. As you please. I was just hoping to find potential options other than revert the change in base-files. Best, Michael root@mt-farm05:~# mkdir /srv/sid-base.cow root@mt-farm05:~# pbuilder create --aptcache /srv/jenkins-slave/aptcache --debootstrapopts --keyring=/usr/share/keyrings/debian-archive-keyring.gpg --buildplace /srv/sid-base.cow --mirror ftp://ftp.uk.debian.org/debian --distribution sid --no-targz --extrapackages cowdancer I: Running in no-targz mode I: Distribution is sid. I: Current time: Mon Oct 27 11:44:42 GMT 2014 I: pbuilder-time-stamp: 1414410282 I: Building the build environment I: running debootstrap /usr/sbin/debootstrap I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Found additional required dependencies: acl adduser dmsetup init-system-helpers insserv libaudit-common libaudit1 libbz2-1.0 libcap2 libcap2-bin libcryptsetup4 libdb5.3 libdebconfclient0 libdevmapper1.02.1 libgcrypt20 libgdbm3 libgpg-error0 libkmod2 libncursesw5 libprocps3 libsemanage-common libsemanage1 libslang2 libsystemd0 libudev1 libustr-1.0-1 perl perl-modules procps systemd systemd-sysv udev I: Found additional base dependencies: binutils bzip2 cpp cpp-4.9 debian-archive-keyring dpkg-dev g++ g++-4.9 gcc gcc-4.9 gnupg gpgv libapt-pkg4.12 libasan1 libatomic1 libc-dev-bin libc6-dev libcilkrts5 libcloog-isl4 libdpkg-perl libgcc-4.9-dev libgmp10 libgomp1 libisl10 libitm1 liblsan0 libmpc3 libmpfr4 libquadmath0 libreadline6 libstdc++-4.9-dev libstdc++6 libtimedate-perl libtsan0 libubsan0 libusb-0.1-4 linux-libc-dev make patch readline-common xz-utils I: Checking component main on ftp://ftp.uk.debian.org/debian... I: Retrieving acl I: Validating acl I: Retrieving libacl1 I: Validating libacl1 I: Retrieving adduser I: Validating adduser I: Retrieving apt I: Validating apt I: Retrieving libapt-pkg4.12 I: Validating libapt-pkg4.12 I: Retrieving libattr1 I: Validating libattr1 I: Retrieving libaudit-common I: Validating libaudit-common I: Retrieving libaudit1 I: Validating libaudit1 I: Retrieving base-files I: Validating base-files I: Retrieving base-passwd I: Validating base-passwd I: Retrieving bash I: Validating bash I: Retrieving binutils I: Validating binutils I: Retrieving build-essential I: Validating build-essential I: Retrieving bzip2 I: Validating bzip2 I: Retrieving libbz2-1.0 I: Validating
Bug#753135: Bug#750557: Bug#754114: Bug#750557: pgadmin3: segmentation fault
Version: 1.20.0~beta2-1 Re: Damyan Ivanov 2014-10-27 20141027112735.gb18...@ktnx.net -=| Bogdan Vatra, 27.10.2014 12:16:16 +0200 |=- On Monday 27 October 2014 10:53:01 Christoph Berg wrote: Re: To bmorel 2014-09-11 20140911093144.ga7...@msg.df7cb.de there's now 1.20.0~beta2-1 in unstable. Could you give that a try again? I don't see the crash in beta2 here. Also, would you say this bug makes pgadmin3 unusable, or is the rest of the functionality working just fine? I'm pondering downgrading the severity of this bug to just important so we at least have a mostly-working version of pgadmin3 in jessie. It seems the crash if fixed, I can't reproduce it anymore. Same here. No crashes. Ok, that's even better, thanks for confirming! I'll close the bug. I notice a small glitch that may be related. After opening the database maintenance dialog, hovering over any of the checkboxes or the first radio button (VACUUM) changes the mouse pointer to a nw-se resizing arrow, which is not the standard resizing arrow for the graphical environment (GNOME) but something else. Not sure about the bug's severity. I use unstable, so I am not even sure the bug still applies to the version in jessie. There was an update of wx3.0 some weeks ago that may as well sbe fixing this bug. Thanks for bringing beta2 to unstable, ... and now hopefully also to jessie :) Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737457: marked as done ([src:pnp4nagios] Sourceless file (minified) (jquery))
Your message dated Mon, 27 Oct 2014 12:00:14 + with message-id e1xiiy6-0006ce...@franck.debian.org and subject line Bug#737457: fixed in pnp4nagios 0.6.24+dfsg1-1 has caused the Debian Bug report #737457, regarding [src:pnp4nagios] Sourceless file (minified) (jquery) 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.) -- 737457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:pnp4nagios Version: 0.6.16-2 Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-javascript-object X-Debbugs-CC: ftpmas...@debian.org control: found -1 0.6.19-1 I could not find the source of: pnp4nagios 0.6.16-2 (source) share/pnp/media/js/jquery-ui.min.js share/pnp/media/js/jquery.imgareaselect.min.js Bastien ---End Message--- ---BeginMessage--- Source: pnp4nagios Source-Version: 0.6.24+dfsg1-1 We believe that the bug you reported is fixed in the latest version of pnp4nagios, 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 737...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Frosch lazyfro...@debian.org (supplier of updated pnp4nagios package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 26 Oct 2014 16:02:13 +0100 Source: pnp4nagios Binary: pnp4nagios pnp4nagios-bin pnp4nagios-web-config-icinga pnp4nagios-web-config-nagios3 pnp4nagios-web Architecture: source all amd64 Version: 0.6.24+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Nagios Maintainer Group pkg-nagios-de...@lists.alioth.debian.org Changed-By: Markus Frosch lazyfro...@debian.org Description: pnp4nagios - Nagios addon to create graphs from performance data pnp4nagios-bin - Nagios addon to create graphs from performance data (binaries) pnp4nagios-web - Nagios addon to create graphs from performance data (web interfac pnp4nagios-web-config-icinga - Nagios addon to create graphs from performance data (Nagios3 conf pnp4nagios-web-config-nagios3 - Nagios addon to create graphs from performance data (Icinga confi Closes: 669839 737457 739098 753457 Changes: pnp4nagios (0.6.24+dfsg1-1) unstable; urgency=medium . [ Sebastian Harl ] * [48a705e9] Merged branch 'configsplit'. * [bfcb36ca] README.Debian: Replaced cp'ed Nagios with Icinga. * [91a75610] README.Debian: Fixed typo (icingacfg ā icinga.cfg). * [9f1e4167] README.Debian: Improved typesetting a bit ;-) * [a7f12f2d] README.Debian: Fixed typo (nagios ā nagios3). Also, made the document a bit more DAU-proof ;-) * [009534c4] npcdmod.cfg: Fixed a few typos and improved wording. . [ Bernd Zeimetz ] * [832a9632] Refreshing patches. . [ Markus Frosch ] * [14693ff] Replace Sven Velt with Markus Frosch as secondary uploader (Closes: #739098) * [f2f01d4] Initial upstream branch * [29d5377] Imported Upstream version 0.6.21 * [d4a4cdb] DFSG cleaned upstream version 0.6.21+dfsg1 (Closes: #737457) (Closes: #753457) * [82701a7] Removed GBP config, we imported the tarball into GIT * [45e91cc] Changes for the DFSG tarball, JQuery depends, links and cleanup * [36ab52d] Switch to source format 3.0 (quilt) * [fafe97f] Update watch file for DFSG versions * [318fa21] Remove potential flattr code from documentation * [913caf2] Control, Lintian and Standards Cleanup * [28272e9] Add missing dependencies of config packages and fix arch * [ce4e5ae] Modernize and split Apache configuration (Closes: #669839) * [a79e4af] Prefer Icinga over Nagios3 * [cb1832a] Fill config packages * [2a2c4f6] Modernize rules * [0a244f8] Update copyright * [311c9c5] Include default build flags * [c37bcc4] Fix Apache configuration handling * [a65f63a] Revert DFSG cleaned upstream version 0.6.21+dfsg1 * [b542e4a] Imported Upstream version 0.6.24 * [b920288] DFSG cleaned upstream version 0.6.24+dfsg1 * [b87ba16] Update patch privacy-warning for 0.6.24 * [eed3190] Add patch install_opts to avoid setting owners on dh_auto_install * [46e24b7] Update README.Debian *
Bug#760350: marked as done ([pgadmin3] pgadmin crashes every time, 100% reproducible)
Your message dated Mon, 27 Oct 2014 12:58:54 +0100
with message-id 20141027115854.gh21...@msg.df7cb.de
and subject line Re: Bug#750557: Bug#754114: Bug#750557: pgadmin3: segmentation
fault
has caused the Debian Bug report #750557,
regarding [pgadmin3] pgadmin crashes every time, 100% reproducible
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.)
--
750557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: pgadmin3
Version: 1.18.1-3.pgdg70+1
Severity: important
--- Please enter the report below this line. ---
pgadmin crashes every time when I try to create a new DB:
Here is the bt:
(gdb) bt full
#0 __lll_unlock_elision (lock=0xf46110, private=0) at
../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
No locals.
#1 0x768790d9 in wxMutexInternal::Unlock() () from /usr/lib/x86_64-
linux-gnu/libwx_baseu-2.8.so.0
No symbol table info available.
#2 0x0062617a in frmMain::OnSelRightClick (this=0x19ee620, event=...)
at frm/events.cpp:751
item = {m_pItem = 0x1ba7c00}
#3 0x7687b61c in
wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const,
wxEvtHandler*, wxEvent) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
No symbol table info available.
#4 0x7687b6d3 in wxEventHashTable::HandleEvent(wxEvent,
wxEvtHandler*)
() from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
No symbol table info available.
#5 0x7687ba6b in wxEvtHandler::ProcessEvent(wxEvent) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
No symbol table info available.
#6 0x7687b9e0 in wxEvtHandler::ProcessEvent(wxEvent) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
No symbol table info available.
#7 0x772295f9 in wxWindowBase::TryParent(wxEvent) () from
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#8 0x7687b9e0 in wxEvtHandler::ProcessEvent(wxEvent) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
No symbol table info available.
#9 0x7726b386 in wxScrollHelperEvtHandler::ProcessEvent(wxEvent) ()
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#10 0x7727f8dd in wxGenericTreeCtrl::OnMouse(wxMouseEvent) () from
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#11 0x7687b61c in
wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const,
wxEvtHandler*, wxEvent) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
No symbol table info available.
#12 0x7687b6d3 in wxEventHashTable::HandleEvent(wxEvent,
wxEvtHandler*)
() from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
No symbol table info available.
#13 0x7687ba6b in wxEvtHandler::ProcessEvent(wxEvent) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
No symbol table info available.
#14 0x7687b9e0 in wxEvtHandler::ProcessEvent(wxEvent) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
No symbol table info available.
#15 0x7726b386 in wxScrollHelperEvtHandler::ProcessEvent(wxEvent) ()
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#16 0x7713983f in ?? () from /usr/lib/x86_64-linux-
gnu/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#17 0x7412101f in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-
x11-2.0.so.0
No symbol table info available.
#18 0x72edc415 in g_closure_invoke () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
No symbol table info available.
---Type return to continue, or q return to quit---
#19 0x72eee9dc in ?? () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
No symbol table info available.
#20 0x72ef6d16 in g_signal_emit_valist () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
No symbol table info available.
#21 0x72ef746f in g_signal_emit () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
No symbol table info available.
#22 0x7423140c in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-
x11-2.0.so.0
No symbol table info available.
#23 0x7411f774 in gtk_propagate_event () from /usr/lib/x86_64-linux-
gnu/libgtk-x11-2.0.so.0
No symbol table info available.
#24 0x7411fbeb in gtk_main_do_event () from /usr/lib/x86_64-linux-
gnu/libgtk-x11-2.0.so.0
No symbol table info available.
#25 0x73d9903c in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-
x11-2.0.so.0
No symbol table info available.
#26 0x72525ecd in g_main_context_dispatch () from
Bug#750557: marked as done (pgadmin: have random crashes ( memory corruption or double free ) )
Your message dated Mon, 27 Oct 2014 12:58:54 +0100 with message-id 20141027115854.gh21...@msg.df7cb.de and subject line Re: Bug#750557: Bug#754114: Bug#750557: pgadmin3: segmentation fault has caused the Debian Bug report #750557, regarding pgadmin: have random crashes ( memory corruption or double free ) 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.) -- 750557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pgadmin3 Version: 1.18.1-3 Severity: important File: pgadmin Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pgadmin3 depends on: ii libc6 2.18-7 ii libgcc1 1:4.9.0-5 ii libkrb5-3 1.12.1+dfsg-1 ii libpq5 9.3.4-1+b1 ii libssl1.0.0 1.0.1g-4 ii libstdc++6 4.9.0-5 ii libwxbase3.0-0 3.0.0-4 ii libwxgtk3.0-0 3.0.0-4 ii libxml2 2.9.1+dfsg1-3 ii libxslt1.1 1.1.28-2 ii pgadmin3-data 1.18.1-3 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages pgadmin3 recommends: pn pgagentnone ii postgresql-client-9.3 [postgresql-client] 9.3.4-1+b1 Versions of packages pgadmin3 suggests: ii postgresql-contrib 9.3+155 -- no debconf information ---End Message--- ---BeginMessage--- Version: 1.20.0~beta2-1 Re: Damyan Ivanov 2014-10-27 20141027112735.gb18...@ktnx.net -=| Bogdan Vatra, 27.10.2014 12:16:16 +0200 |=- On Monday 27 October 2014 10:53:01 Christoph Berg wrote: Re: To bmorel 2014-09-11 20140911093144.ga7...@msg.df7cb.de there's now 1.20.0~beta2-1 in unstable. Could you give that a try again? I don't see the crash in beta2 here. Also, would you say this bug makes pgadmin3 unusable, or is the rest of the functionality working just fine? I'm pondering downgrading the severity of this bug to just important so we at least have a mostly-working version of pgadmin3 in jessie. It seems the crash if fixed, I can't reproduce it anymore. Same here. No crashes. Ok, that's even better, thanks for confirming! I'll close the bug. I notice a small glitch that may be related. After opening the database maintenance dialog, hovering over any of the checkboxes or the first radio button (VACUUM) changes the mouse pointer to a nw-se resizing arrow, which is not the standard resizing arrow for the graphical environment (GNOME) but something else. Not sure about the bug's severity. I use unstable, so I am not even sure the bug still applies to the version in jessie. There was an update of wx3.0 some weeks ago that may as well sbe fixing this bug. Thanks for bringing beta2 to unstable, ... and now hopefully also to jessie :) Christoph -- c...@df7cb.de | http://www.df7cb.de/---End Message---
Bug#753135: marked as done (pgadmin3: pgadmin crahes quite often with assertion failure in ../src/common/wincmn.cpp(478))
Your message dated Mon, 27 Oct 2014 12:58:54 +0100 with message-id 20141027115854.gh21...@msg.df7cb.de and subject line Re: Bug#750557: Bug#754114: Bug#750557: pgadmin3: segmentation fault has caused the Debian Bug report #750557, regarding pgadmin3: pgadmin crahes quite often with assertion failure in ../src/common/wincmn.cpp(478) 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.) -- 750557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pgadmin3 Version: 1.18.1-3 Severity: normal Dear Maintainer, * What led up to the situation? Sometimes pgadmin crashes showing an error window with debug information (see below). Last time it happens while closing pgadmin (through x-icon from window decoration). Other times I remember it happend during data edit or calumn edit. * What was the outcome of this action? An error window showing: ASSERT INFO: ../src/common/wincmn.cpp(478): assert GetEventHandler() == this failed in ~wxWindowBase(): any pushed event handlers must have been removed BACKTRACE: [1] wxWindowBase::~wxWindowBase() [2] wxWindow::~wxWindow() [3] wxControlBase::~wxControlBase() [4] wxStyledTextCtrl::~wxStyledTextCtrl() [5] wxWindowBase::Destroy() [6] wxWindowBase::DestroyChildren() [7] wxWindow::~wxWindow() [8] wxGridWindow::~wxGridWindow() [9] wxWindowBase::Destroy() [10] wxWindowBase::DestroyChildren() [11] wxWindow::~wxWindow() [12] wxRegionBase::~wxRegionBase() [13] wxWindowBase::Destroy() [14] wxWindowBase::DestroyChildren() [15] wxWindow::~wxWindow() [16] wxTopLevelWindowGTK::~wxTopLevelWindowGTK() [17] wxFrameBase::~wxFrameBase() [18] wxRegionBase::~wxRegionBase() [19] wxRegionBase::~wxRegionBase() [20] wxAppConsoleBase::DeletePendingObjects() [21] wxAppConsoleBase::ProcessIdle() [22] wxAppBase::ProcessIdle() [23] wxApp::DoIdle() [24] g_main_context_dispatch [25] g_main_loop_run [26] gtk_main [27] wxGUIEventLoop::DoRun() [28] wxEventLoopBase::Run() [29] wxAppConsoleBase::MainLoop() [30] wxEntry(int, wchar_t**) [31] __libc_start_main If you need further information please do not hesitate to contact me. Best, Henning -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pgadmin3 depends on: ii libc6 2.19-3 ii libgcc1 1:4.9.0-7 ii libkrb5-3 1.12.1+dfsg-3 ii libpq5 9.3.4-2 ii libssl1.0.0 1.0.1h-3 ii libstdc++6 4.9.0-7 ii libwxbase3.0-0 3.0.1-1 ii libwxgtk3.0-0 3.0.1-1 ii libxml2 2.9.1+dfsg1-3 ii libxslt1.1 1.1.28-2 ii pgadmin3-data 1.18.1-3 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages pgadmin3 recommends: ii pgagent3.4.0-2 ii postgresql-client 9.3+157 ii postgresql-client-9.1 [postgresql-client] 9.1.11-1 ii postgresql-client-9.3 [postgresql-client] 9.3.4-2 Versions of packages pgadmin3 suggests: pn postgresql-contrib none -- no debconf information ---End Message--- ---BeginMessage--- Version: 1.20.0~beta2-1 Re: Damyan Ivanov 2014-10-27 20141027112735.gb18...@ktnx.net -=| Bogdan Vatra, 27.10.2014 12:16:16 +0200 |=- On Monday 27 October 2014 10:53:01 Christoph Berg wrote: Re: To bmorel 2014-09-11 20140911093144.ga7...@msg.df7cb.de there's now 1.20.0~beta2-1 in unstable. Could you give that a try again? I don't see the crash in beta2 here. Also, would you say this bug makes pgadmin3 unusable, or is the rest of the functionality working just fine? I'm pondering downgrading the severity of this bug to just important so we at least have a mostly-working version of pgadmin3 in jessie. It seems the crash if fixed, I can't reproduce it anymore. Same here. No crashes. Ok, that's even better, thanks for confirming! I'll close the bug. I notice a small glitch that may be related. After opening the database maintenance dialog, hovering over any of the checkboxes or the first radio button (VACUUM) changes the mouse pointer to a nw-se resizing arrow, which is not the standard resizing arrow for the graphical environment (GNOME) but something else. Not sure about the bug's severity. I use unstable, so I am not even sure the bug still applies to the version in jessie. There was an update of wx3.0 some weeks ago that may as well sbe fixing this bug.
Bug#754114: marked as done (pgadmin3 crashes: Unrecognised instruction __lll_unlock_elision)
Your message dated Mon, 27 Oct 2014 12:58:54 +0100 with message-id 20141027115854.gh21...@msg.df7cb.de and subject line Re: Bug#750557: Bug#754114: Bug#750557: pgadmin3: segmentation fault has caused the Debian Bug report #750557, regarding pgadmin3 crashes: Unrecognised instruction __lll_unlock_elision 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.) -- 750557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pgadmin3 Version: 1.18.1-3 Severity: grave pgadmin3 crashes with following error: 07:55:47 PM: Debug: Adding duplicate image handler for 'PNG file' Segmentation fault I can reproduce the crash with following steps: - start pgadmin3 - connect to a server - select a database - right click and select Maintenance Best regards Georgi -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pgadmin3 depends on: ii libc6 2.19-4 ii libgcc1 1:4.9.0-7 ii libkrb5-3 1.12.1+dfsg-3 ii libpq5 9.3.4-2 ii libssl1.0.0 1.0.1h-3 ii libstdc++6 4.9.0-7 ii libwxbase3.0-0 3.0.1-2 ii libwxgtk3.0-0 3.0.1-2 ii libxml2 2.9.1+dfsg1-3 ii libxslt1.1 1.1.28-2 ii pgadmin3-data 1.18.1-3 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages pgadmin3 recommends: ii pgagent3.4.0-2 ii postgresql-client-9.3 [postgresql-client] 9.3.4-2 Versions of packages pgadmin3 suggests: ii postgresql-contrib 9.3+157 -- no debconf information ---End Message--- ---BeginMessage--- Version: 1.20.0~beta2-1 Re: Damyan Ivanov 2014-10-27 20141027112735.gb18...@ktnx.net -=| Bogdan Vatra, 27.10.2014 12:16:16 +0200 |=- On Monday 27 October 2014 10:53:01 Christoph Berg wrote: Re: To bmorel 2014-09-11 20140911093144.ga7...@msg.df7cb.de there's now 1.20.0~beta2-1 in unstable. Could you give that a try again? I don't see the crash in beta2 here. Also, would you say this bug makes pgadmin3 unusable, or is the rest of the functionality working just fine? I'm pondering downgrading the severity of this bug to just important so we at least have a mostly-working version of pgadmin3 in jessie. It seems the crash if fixed, I can't reproduce it anymore. Same here. No crashes. Ok, that's even better, thanks for confirming! I'll close the bug. I notice a small glitch that may be related. After opening the database maintenance dialog, hovering over any of the checkboxes or the first radio button (VACUUM) changes the mouse pointer to a nw-se resizing arrow, which is not the standard resizing arrow for the graphical environment (GNOME) but something else. Not sure about the bug's severity. I use unstable, so I am not even sure the bug still applies to the version in jessie. There was an update of wx3.0 some weeks ago that may as well sbe fixing this bug. Thanks for bringing beta2 to unstable, ... and now hopefully also to jessie :) Christoph -- c...@df7cb.de | http://www.df7cb.de/---End Message---
Bug#761992: marked as done ([pgadmin3] Crashes trying to backup a database)
Your message dated Mon, 27 Oct 2014 12:58:54 +0100 with message-id 20141027115854.gh21...@msg.df7cb.de and subject line Re: Bug#750557: Bug#754114: Bug#750557: pgadmin3: segmentation fault has caused the Debian Bug report #750557, regarding [pgadmin3] Crashes trying to backup a database 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.) -- 750557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pgadmin3 Version: 1.20.0~beta1-1 Severity: important Dear Maintainer, I get random crashes, usually trying to perform a backup. A backtrace is provided. Best Regards, Manolo DĆaz --- BackTrace --- Starting program: /usr/bin/pgadmin3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. 16:47:03: Debug: Adding duplicate image handler for 'PNG file' [New Thread 0x7fffe1e8a700 (LWP 4998)] Program received signal SIGSEGV, Segmentation fault. IA__gdk_cursor_ref (cursor=cursor@entry=0x24ac850f0bfff00b) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gdk/gdkcursor.c:57 57 /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gdk/gdkcursor.c: No such file or directory. (gdb) bt #0 IA__gdk_cursor_ref (cursor=cursor@entry=0x24ac850f0bfff00b) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gdk/gdkcursor.c:57 #1 0x728a2ea1 in IA__gdk_window_set_cursor (window=0x1c48ea0, cursor=0x24ac850f0bfff00b) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gdk/gdkwindow.c:8219 #2 0x7636fb69 in wxWindow::GTKUpdateCursor (this=this@entry=0x1c4ce30, isBusyOrGlobalCursor=optimized out, isBusyOrGlobalCursor@entry=false, isRealize=isRealize@entry=false) at ../src/gtk/window.cpp:3768 #3 0x76372b84 in gtk_window_leave_callback (gdk_event=0x1e62590, win=0x1c4ce30) at ../src/gtk/window.cpp:1856 #4 0x72c4301f in _gtk_marshal_BOOLEAN__BOXED (closure=0x1c4d330, return_value=0x7fffe3a0, n_param_values=optimized out, param_values=0x7fffe450, invocation_hint=optimized out, marshal_data=0x0) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkmarshalers.c:86 #5 0x72620415 in g_closure_invoke (closure=0x1c4d330, return_value=0x7fffe3a0, n_param_values=2, param_values=0x7fffe450, invocation_hint=0x7fffe3f0) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gclosure.c:768 #6 0x726329dc in signal_emit_unlocked_R (node=node@entry=0x11bff40, detail=detail@entry=0, instance=instance@entry=0x1aca300, emission_return=emission_return@entry=0x7fffe500, instance_and_params=instance_and_params@entry=0x7fffe450) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gsignal.c:3551 #7 0x7263ad16 in g_signal_emit_valist (instance=optimized out, signal_id=optimized out, detail=optimized out, var_args=var_args@entry=0x7fffe5e0) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gsignal.c:3317 #8 0x7263b46f in g_signal_emit (instance=instance@entry=0x1aca300, signal_id=optimized out, detail=detail@entry=0) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gsignal.c:3363 #9 0x72d5340c in gtk_widget_event_internal (widget=widget@entry=0x1aca300, event=event@entry=0x1e62590) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkwidget.c:5010 #10 0x72d53701 in IA__gtk_widget_event (widget=widget@entry=0x1aca300, event=event@entry=0x1e62590) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkwidget.c:4807 #11 0x72c41cfc in IA__gtk_main_do_event (event=0x1e62590) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkmain.c:1698 #12 0x728bb03c in gdk_event_dispatch (source=optimized out, callback=optimized out, user_data=optimized out) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gdk/x11/gdkevents-x11.c:2403 #13 0x71edfecd in g_main_dispatch (context=0x11b8840) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./glib/gmain.c:3064 #14 g_main_context_dispatch (context=context@entry=0x11b8840) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./glib/gmain.c:3663 #15 0x71ee01b8 in g_main_context_iterate (context=0x11b8840, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./glib/gmain.c:3734 #16 0x71ee04e2 in g_main_loop_run (loop=0x127df60) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./glib/gmain.c:3928 #17 0x72c40bc7 in IA__gtk_main () at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkmain.c:1257 #18 0x76345825 in wxGUIEventLoop::DoRun (this=0x1217ae0) at ../src/gtk/evtloop.cpp:65 #19 0x7583ace0 in wxEventLoopBase::Run (this=0x1217ae0) at
Bug#766966: g++-4.9-arm-linux-gnueabihf: Cannot install package due to conflict with debian's gcc-4.9-base-4.9.1-19
+++ mateusz.ka...@gmail.com [2014-10-27 10:30 +0100]: Package: g++-4.9-arm-linux-gnueabihf Severity: grave Justification: renders package unusable Dear Maintainer, I cannot install gnueabihf for armhf toolchain on amd64 platform. g++-4.9-arm-linux-gnueabihf : Depends: gcc-4.9-base (= 4.9.1-18) but 4.9.1-19 is to be installed Ā Ā Depends: cpp-4.9-arm-linux-gnueabihf (= 4.9.1-18) but it is not going to be installed Ā Ā Depends: gcc-4.9-arm-linux-gnueabihf (= 4.9.1-18) but it is not going to be installed Ā Ā Depends: libstdc++-4.9-dev:armhf (= 4.9.1-18) but it is not going to be installed E: Unable to correct problems, you have held broken packages. I believe this is because current gcc-4.9-base in Debian is 4.9.1-19 which is in conflict with 4.9.1-18, and there is no existing package of gcc-4.9-base-4.9.1-18 for amd64 architecture in any repository. Solution would probably to update packages. Yes, these packages need to be rebuilt against gcc 4.9.1-19. However the gcc maintainer has disabled the behaviour that lets this package build in -19. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766924 That can be patched around for now, but last night there was also a new glibc building. Both have to be in sync on an arch before a rebuild can occur. That should be in a better state by now, so I hope to upload new toolchains today. The close assocation with gcc means that (lib) dependencies have to be exact version matches. Actually the gcc-4.9-base dependency (just copyright/docs) version requirements could be relaxed, but as the others stuff (built from the same version) have to be in sync anyway this makes no practical difference. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766251: patch line endings
dpkg-source --commit produced a patch with all Unix line endings, which failed; running that through unix2dos gave a patch with all DOS line endings, which also failed, with (Stripping trailing CRs from patch; use --binary to disable.) patching file Effects/model-combined-transparent.eff Hunk #1 FAILED at 12 (different line endings). 1 out of 1 hunk FAILED dpkg-source: info: the patch has fuzz which is not allowed, or is malformed dpkg-source: info: if patch '766251.patch' is correctly applied by quilt, use 'quilt refresh' to update it Evidently what is required is Unix in the headers and DOS in the actual patch lines. I consider it a bug that dpkg-source --commit doesn't produce that, but haven't yet reported it. Since this is an arch:all package, it only needs to build on your system. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
On Mon, 27 Oct 2014, Michael Tautschnig wrote: + [ ! -f /usr/info/dir ] + [ ! -f /usr/share/info/dir ] + install_from_default /usr/share/base-files/info.dir /usr/share/info/dir + [ ! -f /usr/share/info/dir ] + cp -p /usr/share/base-files/info.dir /usr/share/info/dir + chmod 644 /usr/share/info/dir + chown root:root /usr/share/info/dir chown: invalid user: 'root:root' Thanks a lot for this. I was mistaken/confused. The recently added three lines at the end of base-files postinst may not be the reason for debootstrap fail. I've moved them anyway to a better place. Now we have this chown root:root /usr/share/info/dir that fails. If this is the *only* place where it fails, this could be ommited because postinst is executed by root and the chown is not really required. Regarding previous point, it should be noted that base-files postinst has a lot of chown calls. I would like to know how it is possible that only the recently added is the one that fails and not the others (if that's really the case). I suppose none of the others are being executed as all of them are guarded by some combination of checks? I refer specifically to the big if block starting if [ $1 = configure ] [ $2 = ]; then There are a lot of install_directory calls there. If any of them fails because of the root user does not exist yet, all of them will fail. But those lines have been there since a long time, so after base-files_7.9 where I moved the lines that create /mnt on upgrades, I don't really see what recent change in base-files could be the reason (or better, the trigger) for debootstrap failure. It must be something else. As you please. I was just hoping to find potential options other than revert the change in base-files. I'm still open for options for the benefit of wheezy users not using backports. But I need to have a better view of why it's failing when it was not failing before, if that's really the case. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766988: Not installable?
Package: gstreamer0.10-ffmpeg Version: 0.10.13-5 Severity: grave Hi, it seems that gstreamer0.10-ffmpeg cannot be installed in unstable (let alone testing). Are there any plans to fix this? I'm currently trying to update the miro package to the latest upstream but since miro depends on gstreamer0.10-ffmpeg I probably won't be able to make a useful upload. I've seen there's a gstreamer1.0-libav package, but that would probably require all of miro to be ported to the gstreamer1.0 API, right? Not sure whether that's easily doable with a small patch, sounds like a bigger effort to me (though I could be wrong). Hence, it would be nice if there were a working gstreamer0.10-ffmpeg package in unstable/testing so that e.g. miro is still usable until a gstreamer1.0 porting has happened. Thanks for considering. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gstreamer0.10-ffmpeg depends on: ii libavcodec53 6:0.8.8-1 ii libavformat536:0.8.8-1 ii libavutil51 6:0.8.8-1 ii libc62.19-12 ii libglib2.0-0 2.42.0-2 ii libgstreamer-plugins-base0.10-0 0.10.36-2 ii libgstreamer0.10-0 0.10.36-1.4 ii liborc-0.4-0 1:0.4.22-1 ii libpostproc526:0.git20120821-4 ii libswscale2 6:10.3-1 gstreamer0.10-ffmpeg recommends no packages. gstreamer0.10-ffmpeg suggests no packages. -- no debconf information -- http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766784: libjson-pp-perl: can neither remove nor install newer version of this package: possible cause
Hello To get a similar error message while upgrading libjson-pp-perl, I had to create a bogus /usr/share/man/man1/json_pp.bundled.1.gz before upgrading libjson-pp-perl to version 2.27300-2: # echo foobar /usr/share/man/man1/json_pp.bundled.1.gz $ sudo aptitude install libjson-pp-perl/testing [ ok ] $ sudo aptitude install libjson-pp-perl The following packages will be upgraded: libjson-pp-perl 1 packages upgraded, 0 newly installed, 0 to remove and 712 not upgraded. Need to get 0 B/51.8 kB of archives. After unpacking 1,024 B will be used. Do you want to continue? [Y/n/?] Reading changelogs... Done (Reading database ... 365498 files and directories currently installed.) Preparing to unpack .../libjson-pp-perl_2.27300-2_all.deb ... Removing 'diversion of /usr/share/man/man1/json_pp.1.gz to /usr/share/man/man1/json_pp.1.bundled.gz by libjson-pp-perl' Leaving 'diversion of /usr/bin/json_pp to /usr/bin/json_pp.bundled by libjson- pp-perl' Adding 'diversion of /usr/share/man/man1/json_pp.1.gz to /usr/share/man/man1/json_pp.bundled.1.gz by libjson-pp-perl' dpkg-divert: error: rename involves overwriting `/usr/share/man/man1/json_pp.bundled.1.gz' with different file `/usr/share/man/man1/json_pp.1.gz', not allowed dpkg: error processing archive /var/cache/apt/archives/libjson-pp- perl_2.27300-2_all.deb (--unpack): subprocess new pre-installation script returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libjson-pp-perl_2.27300-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: I suspect that the error on your system comes from a similar cause. Could you: - purge libjson-pp-perl - remove any existing /usr/share/man/man1/json_pp.bundled.1.gz file (do *not* remove /usr/share/man/man1/json_pp.1.gz ) - install libjson-pp-perl Hope this helps -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736035: please build-depend on libtiff-dev, not libtiff4-dev
Package: src:openmeeg Followup-For: Bug #736035 This bug has been pending for a few months since libtiff4-dev (tiff3) was removeed from the archive, and is blocking builds on new arches as the package is no longer buildable. So I have NMUed the trivial fix needed, as described above, and in attached patch. To delayed/7 as you are not in the LOWthresholdNMU List (please add yourself if you are OK with things like this just being uploaded) https://wiki.debian.org/LowThresholdNmu -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.60-kvm-i386-20140609 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash diff -Nru openmeeg-2.0.0.dfsg/debian/changelog openmeeg-2.0.0.dfsg/debian/changelog --- openmeeg-2.0.0.dfsg/debian/changelog 2013-06-19 10:55:06.0 + +++ openmeeg-2.0.0.dfsg/debian/changelog 2014-10-27 01:36:10.0 + @@ -1,3 +1,10 @@ +openmeeg (2.0.0.dfsg-5.2) unstable; urgency=low + + * Non-maintainer upload. + * Transition libtiff dependencies away from libtiff4 (Closes: 736035) + + -- Wookey woo...@debian.org Mon, 27 Oct 2014 01:34:46 + + openmeeg (2.0.0.dfsg-5.1) unstable; urgency=low * Non-maintainer upload. diff -Nru openmeeg-2.0.0.dfsg/debian/control openmeeg-2.0.0.dfsg/debian/control --- openmeeg-2.0.0.dfsg/debian/control 2013-06-19 10:53:27.0 + +++ openmeeg-2.0.0.dfsg/debian/control 2014-10-27 02:18:23.0 + @@ -3,7 +3,7 @@ Priority: extra Maintainer: NeuroDebian Team t...@neuro.debian.net Uploaders: Yaroslav Halchenko deb...@onerussian.com, Michael Hanke michael.ha...@gmail.com -Build-Depends: debhelper (= 7.0.50~), cmake, doxygen, python-numpy, swig, python-dev (= 2.4), python-support (= 0.6), libatlas-base-dev, libvtk5-dev, libtiff4-dev | libtiff-dev, libmatio-dev (= 1.5) +Build-Depends: debhelper (= 7.0.50~), cmake, doxygen, python-numpy, swig, python-dev (= 2.4), python-support (= 0.6), libatlas-base-dev, libvtk5-dev, libtiff-dev, libmatio-dev (= 1.5) Standards-Version: 3.9.3 Homepage: http://www-sop.inria.fr/odyssee/software/OpenMEEG/ Vcs-Browser: http://git.debian.org/?p=pkg-exppsy/openmeeg.git
Bug#766459: debootstrap: should not try to configure
For the record, base-files postinst had three lines like this chown root:root whatever I've dropped all of them in base-files_7.10. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766934: marked as done (sympow: FTBFS - binary-arch/binary-indep install scheme failure)
Your message dated Mon, 27 Oct 2014 13:19:47 + with message-id e1xikd5-0005u5...@franck.debian.org and subject line Bug#766934: fixed in sympow 1.023-5 has caused the Debian Bug report #766934, regarding sympow: FTBFS - binary-arch/binary-indep install scheme failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 766934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sympow Version: 1.023-4 Severity: serious Justification: FTBFS It appears that the implemented binary-arch/binary-indep install machinery fails because the Makefile generated by the Configure script was not set up properly: this machinerie must be hardened. Thanks, Jerome -- System Information: Debian Release: Wheezy* APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.10-amd64-mbp62 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sympow depends on: ii libc62.13-38+deb7u6 ii pari-gp 2.7.2-1 ii sympow-data 1.023-4 sympow recommends no packages. sympow suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: sympow Source-Version: 1.023-5 We believe that the bug you reported is fixed in the latest version of sympow, 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 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit calcu...@rezozer.net (supplier of updated sympow package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 27 Oct 2014 03:02:48 + Source: sympow Binary: sympow sympow-data Architecture: source amd64 all Version: 1.023-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Jerome Benoit calcu...@rezozer.net Description: sympow - mathematical program for SYMmetric POWer elliptic curve L-functio sympow-data - mathematical program for SYMmetric POWer elliptic curve L-functio Closes: 766934 Changes: sympow (1.023-5) unstable; urgency=medium . * Debianization: - debian/patches/: - minor consistency correction; - binary-arch/binary-indep scheme, harden (Closes: #766934). Checksums-Sha1: 1ac34f9ebf2e467dcff2b682a6917dab546e672d 1701 sympow_1.023-5.dsc d7406d2123fff133973af9d9c8599ff8cc86c493 26688 sympow_1.023-5.debian.tar.xz 050a9e55b78600df0bbfdd2d442f008a4d65c541 107728 sympow_1.023-5_amd64.deb 754b2c05b42d72e217a5a5753b16e34d548f8337 8511562 sympow-data_1.023-5_all.deb Checksums-Sha256: 6ac91c0fc1b561fe2b1bdbaa3303ab81adc40511801828c3fbc525a1c2a85aa2 1701 sympow_1.023-5.dsc ef1f12064240037e6b8b17dd28a3e2215086c2615fc8edbad8ba9f435554a2f5 26688 sympow_1.023-5.debian.tar.xz 91a886b774dc4224e8d89164920c0b392e1480b75d8e79de9b4b6b84bee3891c 107728 sympow_1.023-5_amd64.deb 88fecae962f689cb8a6de66e334dff5d368d83b75d26d2d3724ec6c763d42cfb 8511562 sympow-data_1.023-5_all.deb Files: 418ebea8e5a2b46b00f99d3cef5a1380 1701 math optional sympow_1.023-5.dsc 07808c153aaa08375d6daf5724975a4d 26688 math optional sympow_1.023-5.debian.tar.xz 3d322206df593eb0ee6fddc739770b6c 107728 math optional sympow_1.023-5_amd64.deb 014b1cdd6ae7c30fb1ef2c226a0d53ea 8511562 math optional sympow-data_1.023-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUTkHnAAoJEImvgrc5zSF6REUH+wZfNlaTZvZBna1Rxwk7grrW 3oh/nUjNj00EsamD8iQxMTE9NY1KiXgC7vDcOmlO+GKpZakHvq5sXhMx8WzHkSLD /yw7TEpg9F6xZTFCGPXyUmS8uMp7VV8iW6YYmHgfN28jyFo5UhWkUKLrjaIBalm1 GxgZcuxX/+TLzXxLKfE2WLAFI9w++UX+Hohnf5Wa3sMSvbB8Lsx4Dcr6s6XxBfAq P+9FsHht3XBvSMohUIbJ4siJ8fjALSLREprNwdVR/+AEl6FkCcY9R5BKTP/w5bGX ZwT/txYG/n+f1LM9rKfiazHC8nkL0xuQghBYQuDeZdnjiEExtwZL39irP23jv0I= =hvcH -END PGP SIGNATUREEnd Message---
Bug#766195: [PATCH] ipv6: reuse ip6_frag_id from ip6_ufo_append_data
On Wed, 2014-10-22 at 01:02 +0100, Ben Hutchings wrote: I think this is the upstream change which would fix this. Please test this on top of the previous one, in case there are any more cases where ipv6_select_ident() may be called with a rt == NULL. However, it seems that with this change, when a VM offloads UDP/IPv6 fragmentation to us, we will always set the fragmentation ID to 0. I'm not sure whether that's a regression from 3.2.62, but I think it is. We should not be choosing fragment IDs for VMs, but currently they aren't telling us what to use! I've queried this upstream. I've now written and tested patches for that remaining regression. Source at: https://people.debian.org/~benh/packages/linux_3.2.63-2+deb7u1.dsc https://people.debian.org/~benh/packages/linux_3.2.63-2+deb7u1.debian.tar.xz Binary at: https://people.debian.org/~benh/packages/linux-image-3.2.0-4-amd64_3.2.63-2+deb7u1_amd64.deb There's a signed .changes file there as well, for verification (distribution=UNRELEASED in case you are wondering). Additional testing would be appreciated. Ben. -- Ben Hutchings Theory and practice are closer in theory than in practice. - John Levine, moderator of comp.compilers signature.asc Description: This is a digitally signed message part
Bug#766732: Attempting (failing) to load debugging symbols for glib-2.0-0
On 26/10/14 15:18, Brian Drummond wrote: BFD: /usr/lib/debug/.build-id/f4/bb3ff29b5a72f4c60cc4f76854a1bb47a3bc78.debug: unable to initialize decompress status for section .zdebug_aranges That's a bug in either libglib2.0-0-dbg, or gdb. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766732: Debugging : no useful results so far
On 26/10/14 14:59, Brian Drummond wrote:
gdb nautilus allows me to reproduce the segfault, but doesn't return
control to the debugger. So the pool (is it a process? I can't see it
in ps ax) containing the error must be elsewhere in the system.
You might need to make sure all nautilus processes have been killed
before starting one under gdb - nautilus probably has some single
instance logic going on.
The pool thread is not visible in ps, but it's visible in pstree: it's
probably the thread where miscellaneous background jobs that don't have
their own thread are scheduled. For instance:
% pstree -p
...
āānautilus(9073)āā¬ā{dconf worker}(9079)
āāā{gdbus}(9076)
āāā{gmain}(9078)
āāā{pool}(9077)
...
Process 9073 represents the nautilus process as a whole, and 9073 is
also the thread ID of its main thread; the children in {} are other
threads inside process 9073.
S
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#740998: rdnssd: merge-hook overwrites /etc/resolv.conf when /sbin/resolvconf is not installed
Processing control commands: severity -1 serious Bug #740998 [rdnssd] rdnssd: merge-hook overwrites /etc/resolv.conf when /sbin/resolvconf is not installed Severity set to 'serious' from 'normal' -- 740998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753135: Bug#750557: Bug#754114: Bug#750557: pgadmin3: segmentation fault
Le 27.10.2014 12:58, Christoph Berg a Ć©critĀ : Version: 1.20.0~beta2-1 Re: Damyan Ivanov 2014-10-27 20141027112735.gb18...@ktnx.net -=| Bogdan Vatra, 27.10.2014 12:16:16 +0200 |=- On Monday 27 October 2014 10:53:01 Christoph Berg wrote: Re: To bmorel 2014-09-11 20140911093144.ga7...@msg.df7cb.de there's now 1.20.0~beta2-1 in unstable. Could you give that a try again? I don't see the crash in beta2 here. Also, would you say this bug makes pgadmin3 unusable, or is the rest of the functionality working just fine? I'm pondering downgrading the severity of this bug to just important so we at least have a mostly-working version of pgadmin3 in jessie. It seems the crash if fixed, I can't reproduce it anymore. Same here. No crashes. Ok, that's even better, thanks for confirming! I'll close the bug. Sorry, I successfully reproduced the bug, or at least, a sigsegv. I am using a stable version of Debian, but since the upgrade needed a more recent version of libjpeg and libjpeg-turbo, I have installed them (from debian package). I also have updated pgadmin3-data, of course. Right-cliking on an entry in the menu still makes pgadmin having a segfault. Started from terminal: $ pgadmin3 15:33:00: Debug: Failed to connect to session manager: SESSION_MANAGER environment variable not defined 15:33:01: Debug: Adding duplicate image handler for 'PNG file' Erreur de segmentation The 2 first messages appears at start, the Erreur de segmentation (which means segmentation fault) comes when I right click on an entry (even when I'm not connected) after an event made the context menu to stop appearing (tried to click somewhere else and to use ESC key, same results). I notice a small glitch that may be related. After opening the database maintenance dialog, hovering over any of the checkboxes or the first radio button (VACUUM) changes the mouse pointer to a nw-se resizing arrow, which is not the standard resizing arrow for the graphical environment (GNOME) but something else. Not sure about the bug's severity. I use unstable, so I am not even sure the bug still applies to the version in jessie. There was an update of wx3.0 some weeks ago that may as well sbe fixing this bug. Thanks for bringing beta2 to unstable, ... and now hopefully also to jessie :) Christoph -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766459: debootstrap: should not try to configure
On Mon, 27 Oct 2014, Michael Tautschnig wrote: Then maybe take the first sentence in 3.8 Essential packages instead: Essential is defined as the minimal set of functionality that must be available and usable on the system at all times, even when packages are in the Unpacked state. If not this one (and not the one above), which bit of policy are you then relying on when you do the chown calls? My intrepretation of policy regarding essential packages is that *once* that they are configured for the first time, they should continue to work at all times even if they are unconfigured for a while in the middle of an upgrade. This is consistent with the usual meaning of bootstrap. It's something that you only need to do once, because after that, everything *keeps* working (but only *after* that). Your interpretation of policy is a little bit different. If you ask essential packages to provide its core functionality *even* when they have not been configured for the *first* time, I bet that we would have to rethink the whole essential thing from the beginning. For example, your interpretation would force base-passwd to lose its essential flag, because it can't provide its core functionality only when in unpacked state. Then, according to policy, base-files and *every* other package using any of the system users in any of its maintainer scripts would have to add a Depends: base-passwd, since they depend on functionality which is only available after base-passwd has been configured. Frankly, I don't think that's what we want. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726578: CVE-2013-4442 is not about /dev/random vs /dev/urandom
It looks like this bug does mischaracterize CVE-2013-4442. Unlike what's said here, using /dev/urandom instead of /dev/random (which contrary to popular wisdom is not an issue) but that, if opening of these two devices fail, pwgen falls back to using pids and time. On BSD and Linux/GNU, /dev/urandom is guaranteed so this might trigger if: * someone exhausts the system-wide descriptor limit * a chroot lacks the /dev entries * the admin writes a pathologically bad selinux policy Let's track this as a separate bug. I'd say that this is only a minor vulnerability, thus let's have it at important severity. pwgen has at least one RC issue, so it wouldn't be bad to fix for jessie but I don't find it as a must. -- // If you believe in so-called intellectual property, please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767009: cyphesis-cpp: FTBFS: B-D on old libreadline5-dev
Source: cyphesis-cpp Version: 0.6.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Automatic builds of cyphesis-cpp have been failng: The following packages have unmet dependencies: sbuild-build-depends-cyphesis-cpp-dummy : Depends: libreadline5-dev but it is not installable E: Unable to correct problems, you have held broken packages. The alternative build dependency on libreadline-dev makes no difference because, for the sake of maximum reproducibility, Debian's autobuilders are configured to consider alternatives only when forced to by explicit architecture restrictions. Could you please change that term to just libreadline-dev, which is now a (non-virtual) dummy package depending on the current real package (libreadline6-dev)? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740998: rdnssd: merge-hook overwrites /etc/resolv.conf when /sbin/resolvconf is not installed
Le lundi 27 octobre 2014, 15:20:37 Raphael Hertzog a Ć©crit : On Fri, 07 Mar 2014, Frank Heckenbach wrote: The merge-hook script overwrites /etc/resolv.conf when /sbin/resolvconf is not installed, thereby erasing additional entries in this file such as name etc. And it also erases non-IPv6 DNS servers that were present in that file before. Right now, this package got installed by default on a Jessie GNOME desktop and it really interacts badly with NetworkManager which was handling the file perfectly fine (i.e. it included already the IPv6 DNS servers identified by rdnsd). That *is* a problem. Indeed NetworkManager has gained support for RDNSS for a long time already, and thus made completely rdnssd redundant if not counter- productive on a system with NetworkManager. But as far as I know, whatever caused this default is not rdnssd itself. I believe that it should do something saner instead of overwriting. I must disagree. If resolvconf is absent, overwriting is the most sane, or least insane thing to do. There just is not a lot that can be done without mediation for writing the resolver configuration. It should verify if the file contains the DNS servers it detected and add them if they are missing. But it should definitely not blindly overwrite the file... There are currently no ways to know which entries were inserted by rdnssd (possibly by a previous incantation of it) and which by other tools. Furthermore, I doubt we can safely assume that all resolv.conf tools remove their entries when uninstalled. I think this suggestion is worse than the bug from a reliability perspective. Really, any pair of two tools writing resolv.conf will screw stuff up without resolvconf present and supported by both tools. That problem affects ppp, dhcp- client3, network-manager, wicd, connman, systemd(-networkd) just to name a few. And I donĀ“t dare mention most if not all VPN clients. -- RĆ©mi Denis-Courmont http://www.remlab.net/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766732: Attempting (failing) to load debugging symbols for glib-2.0-0
On Mon, 2014-10-27 at 14:12 +, Simon McVittie wrote: On 26/10/14 15:18, Brian Drummond wrote: BFD: /usr/lib/debug/.build-id/f4/bb3ff29b5a72f4c60cc4f76854a1bb47a3bc78.debug: unable to initialize decompress status for section .zdebug_aranges That's a bug in either libglib2.0-0-dbg, or gdb. Thanks, that's what I suspected. Evidence that it's not just me seeing these messages : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759361 freerdp-x11: Segfaults on too-long command line with old-style options lists the same error multiple times, on an entirely different package, suggesting this may be a gdb failure. (Or both packages are built incorrectly) - Brian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: remaining issues are non-bugs
Processing control commands: severity -1 important Bug #726578 [pwgen] pwgen: Multiple vulnerabilities in passwords generation Severity set to 'important' from 'grave' -- 726578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753135: Bug#750557: Bug#754114: Bug#750557: pgadmin3: segmentation fault
Le 27.10.2014 15:43, berenger.mo...@neutralite.org a Ć©critĀ : Le 27.10.2014 12:58, Christoph Berg a Ć©critĀ : Version: 1.20.0~beta2-1 Re: Damyan Ivanov 2014-10-27 20141027112735.gb18...@ktnx.net -=| Bogdan Vatra, 27.10.2014 12:16:16 +0200 |=- On Monday 27 October 2014 10:53:01 Christoph Berg wrote: Re: To bmorel 2014-09-11 20140911093144.ga7...@msg.df7cb.de there's now 1.20.0~beta2-1 in unstable. Could you give that a try again? I don't see the crash in beta2 here. Also, would you say this bug makes pgadmin3 unusable, or is the rest of the functionality working just fine? I'm pondering downgrading the severity of this bug to just important so we at least have a mostly-working version of pgadmin3 in jessie. It seems the crash if fixed, I can't reproduce it anymore. Same here. No crashes. Ok, that's even better, thanks for confirming! I'll close the bug. Sorry, I successfully reproduced the bug, or at least, a sigsegv. Hum... in facts, I was in a mix of stable, stable-bpo and testing. My problems might come from that mix, instead of from an actual bug in pgadmin3 (but it only show it pgadmin, and I'm sometimes using another wx3 application which is not impacted by it). I guess my last comment can be ignored. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726578: remaining issues are non-bugs
Control: severity -1 important I have split two parts into separate bugs, I think the remainder are ok: CVE-2013-4440 non-tty passwords are trivially weak by default * #725507, my assessment: grave CVE-2013-4441 Phonemes mode has heavy bias and is enabled by default * works as designed CVE-2013-4442 Silent fallback to insecure entropy * #767008, my assessment: important CVE-2013-4443 Secure mode has bias towards numbers and uppercase letters * REJECTED, actually improves security! CVE-2013-4443 has been rejected from the CVE database. So let's discuss CVE-2013-4441. Such a bias means the program does what it's designed to do: it produces pronounceable passwords rather than a pure line noise. These are not necessarily less secure -- you just need a longer length than on line noise. Recently this has been popularized as the correct horse battery staple issue: long passwords are far, far easier to memorize for a human than shorter but more complex ones, while being capable of providing as much or more entropy. What remains is that pwgen's default length, 8 characters, might been adequate when the program was written, but is insecure today. But let's discuss that elsewhere. So I think this bug should be closed. Being not a security expert myself, I'm merely degrading it to important for now, until someone else can confirm and close. I'll bump #725507 to grave after the next britney run. -- // If you believe in so-called intellectual property, please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package gdb
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package gdb # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #763518 (http://bugs.debian.org/763518) # Bug title: gdb --batch mode broken # * http://sourceware.org/bugzilla/show_bug.cgi?id=17446 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 763518 + fixed-upstream Bug #763518 [gdb] gdb --batch mode broken Added tag(s) fixed-upstream. usertags 763518 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 763518 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 763518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717636: [Debian-in-workers] Bug#717636: latex-sanskrit package
Hi,
Vasudev Kamath kamathvasu...@gmail.com writes:
On Mon, Oct 13, 2014 at 5:04 PM, intrigeri intrig...@debian.org wrote:
On current sid, with texlive-lang-indic installed:
$ t1disasm
/usr/share/texlive/texmf-dist/fonts/type1/public/sanskrit/sktb10.pfb | grep
start
dup 3 {systemdict /internaldict known not {pop 3} {1183615869
systemdict /internaldict get exec dup /startlock known {/startlock
get exec} {dup /strtlck known {/strtlck get exec} {pop 3} ifelse}
ifelse} ifelse} executeonly put
... seems to indicate that the bug is still present.
Did I miss anything, or are we misunderstanding each other?
Below is mail snippet between me Jaldhar and Norbert, probably
recorded in texlive mailing list.
===
Hi Vasudev,
We (me and Jaldhar) are planning to drop the latex-sanskrit package from
Ok.
Can you please drop the latex-sanskrit from depends/recommends of above
package in your next release?..
Sure. We will re-include the sanskrit part of TeX Live which
only ships the mf /pfb files and the source of the preprocessor.
Also I will file bug on above 3 packages if needed, I thought I will
first contact you guys before filing bug. Please let me know your
thoughts on this.
There is one thing we should think about: Transition for users of
latex-sanskrit.
If you think it is fine to drop the package completely without
any upgrade path, that is fine with me.
Otherwise we could build a transitional package latex-sanskrit
from texlive-lang that just depends on
texlive-lang-indic
and be gone.
That way you don't have to request removal either, since it is
just a change of maintainer, and at the end will be removed
at some point.
Let me know your opinion and I will implement it for TL 2014,
(which will probably never enter Debian if we don't get a new libpng)
===
We acked to drop binaries and only ship required source as part of
texlive-lang-indic. So yes the bug still holds right but not sure if
it should be reassigned to texlive-lang src or kept on latex-sanskrit.
Also bug is ignored for jessie!.
Sorry for not including this earlier conversation. I had to re-read it
to understand the concept
Any thing on this? Did I clarify? or any further clarification needed
From my side?
--
Vasudev Kamath
http://copyninja.info
Connect on ~friendica: copyni...@samsargika.copyninja.info
IRC nick: copyninja | vasudev {irc.oftc.net | irc.freenode.net}
GPG Key: C517 C25D E408 759D 98A4 C96B 6C8F 74AE 8770 0B7E
signature.asc
Description: PGP signature
Bug#752655: marked as done (tarantool-php is licensed under the PHP license and is not PHP)
Your message dated Mon, 27 Oct 2014 16:35:04 + with message-id e1xing4-0002pp...@franck.debian.org and subject line Bug#752655: fixed in tarantool-php 1.6-1 has caused the Debian Bug report #752655, regarding tarantool-php is licensed under the PHP license and is not PHP 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.) -- 752655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: php-gearman Severity: serious User: paul...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks From the REJECT faq: / | You have a PHP add-on package (any php script/app/thing, not PHP | itself) and it's licensed only under the standard PHP license. That | license, up to the 3.x which is actually out, is not really usable for | anything else than PHP itself. I've mailed our -legal list about that | and got only one response, which basically supported my view on this. | Basically this license talks only about PHP, the PHP Group, and includes | Zend Engine, so its not applicable to anything else. And even worse, | older versions include the nice ad-clause. | | One good solution here is to suggest a license change to your upstream, | as they clearly wanted a free one. LGPL or BSD seems to be what they | want. \ Sorry this made it through NEW, Hope you're well, and thanks for your work, Paul -- .''`. Paul Tagliamonte paul...@debian.org : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: tarantool-php Source-Version: 1.6-1 We believe that the bug you reported is fixed in the latest version of tarantool-php, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry E. Oboukhov un...@debian.org (supplier of updated tarantool-php package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 27 Oct 2014 18:46:34 +0300 Source: tarantool-php Binary: libtarantool-php Architecture: source amd64 Version: 1.6-1 Distribution: unstable Urgency: medium Maintainer: Dmitry E. Oboukhov un...@debian.org Changed-By: Dmitry E. Oboukhov un...@debian.org Description: libtarantool-php - PECL PHP driver for Tarantool/Box Closes: 752655 Changes: tarantool-php (1.6-1) unstable; urgency=medium . * New upstream version. * Relicensed as BSD. closes: #752655. Checksums-Sha1: b5b6add7ce3ccbed30ab10feb8c6bfce20229b4d 1866 tarantool-php_1.6-1.dsc 422baaf6e5e5a51df7c036e5405e49a0acfa72a7 563181 tarantool-php_1.6.orig.tar.gz 0be56d6cfd3654730a771dbcf46a61a93f753abf 2208 tarantool-php_1.6-1.debian.tar.xz 85b8837b861acd752a140864dfb1cce043fb3589 25608 libtarantool-php_1.6-1_amd64.deb Checksums-Sha256: 2a65b6f52e101d1bcd1847fa1cfe4665bf00a230bd8a7937492b87dd90dcd558 1866 tarantool-php_1.6-1.dsc 0a7f5940f9b4954e01a7a055eeb853d8c41e12a243260b1608e248819403c128 563181 tarantool-php_1.6.orig.tar.gz 9a032bf55c367639d04fa77f83b1c5df07616ec139f1ec3361ebf811c32783d1 2208 tarantool-php_1.6-1.debian.tar.xz 26c54ee2f0ae08f4b7ac820a9ebd94f1f84058335a824af7868f3374ab2921f6 25608 libtarantool-php_1.6-1_amd64.deb Files: 1f367e8dae163dd24fed3467353d39f9 1866 php optional tarantool-php_1.6-1.dsc 4cba439209ef4f71da86b9b82c396a42 563181 php optional tarantool-php_1.6.orig.tar.gz 7683faead0b2c4d34a8f159430852622 2208 php optional tarantool-php_1.6-1.debian.tar.xz 074f8975bf311d25e69f1d88e9a79b17 25608 php optional libtarantool-php_1.6-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUTnGUAAoJEI0flpoI7qdWCh4QANX9ZINaluusICnzY1djFuve GIgIGPk6kVWt5T6Vpm4VymQ2MGgEyC9YQpdHRfeRWnPsiWEe0L9MMOTblLXpv+Dq QCGZOlnSPkkVpFpqBpjAfmMY3mL+1XeD8IRzC9OttI8q2UtVxr8LeJh23P3OrdSm oePvzc8XR7dsqlA5OXG+wTmDXfZQW9m6T04KspZGNDWT9NEqqBgLSdXD3/P61T7M IFIR4hfxmqRf11Yzk/Un7Se3i/qJ1qTNS28seySMZHr9Ry4XuuHPHx54Dmi9uUwb G7bGe/TEv5ct4buEa+xro5grbNl6liGgwJxvAgvG6+63XiDeC89ySBAKbKlI1LUM
Bug#766732: Debugging : no useful results so far
On Mon, 2014-10-27 at 14:10 +, Simon McVittie wrote:
On 26/10/14 14:59, Brian Drummond wrote:
gdb nautilus allows me to reproduce the segfault, but doesn't return
control to the debugger. So the pool (is it a process? I can't see it
in ps ax) containing the error must be elsewhere in the system.
You might need to make sure all nautilus processes have been killed
before starting one under gdb - nautilus probably has some single
instance logic going on.
Thanks for these hints.
% pstree -p
...
āānautilus(9073)āā¬ā{dconf worker}(9079)
āāā{gdbus}(9076)
āāā{gmain}(9078)
āāā{pool}(9077)
I can now see
|---gdb(4450)---nautilus(4670)-+-{dconf worker}(4674)
|-{gdbus}(4671)
|-{gmain}(4673)
`-{pool}(4681)
but when I reproduce the segfault, dmesg reports
[24621.126174] pool[4704]: segfault at 0 ip 7f95c1e6da3a sp
7f95af7fdcb8 error 4 in libc-2.19.so[7f95c1dec000+19f000]
and gdb reports...
(nautilus:4670): Gtk-WARNING **: Refusing to add non-unique action
'TerminalNautilus:OpenFolderLocal' to action group 'ExtensionsMenuGroup'
[New Thread 0x7fffd082b700 (LWP 4688)]
[Thread 0x7fffd082b700 (LWP 4688) exited]
[Thread 0x7fffca980700 (LWP 4681) exited]
Gtk-Message: GtkDialog mapped without a transient parent.
So I believe the Nautilus thread pool closes and *something else* starts
another thread pool (4704) where the segfault occurs.
And ps ax shows...
4450 pts/0S 0:01 gdb nautilus
4476 ?Sl 0:00 /usr/lib/gvfs/gvfsd-smb-browse
--spawner :1.8 /org/gtk/gvfs/exec_spaw/4
4482 ?Sl 0:00 /usr/lib/gvfs/gvfsd-network
--spawner :1.8 /org/gtk/gvfs/exec_spaw/5
4500 ?Sl 0:00 /usr/lib/gvfs/gvfsd-dnssd
--spawner :1.8 /org/gtk/gvfs/exec_spaw/9
4520 pts/1Ss 0:00 /bin/bash
4542 ?Sl 0:35 /usr/bin/gedit --gapplication-service
4547 ?S 0:00 [kworker/1:2]
4670 pts/0Sl+0:08 /usr/bin/nautilus
4695 ?S 0:01 [kworker/3:0]
4752 pts/1R+ 0:00 ps ax
Quitting gdb confirms that 4670 is indeed the Nautilus spawned by gdb.
So I suspect that one of the gvfs services (4476,4482,4500 above) may be
creating this pool and failing.
Now, how would I go about closing those and restarting them under gdb
before starting Nautilus? Apologies if this is a ridiculously basic
question; it doesn't seem that way to me.
Incidentally this other pool[]: segfault in libc-2.xx bug also
appeared to be in or around gvfs.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707681
Didn't think it was related to mine, but it might be after all.
- Brian
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763220: Bug#766244: RFS: dwb/20140702hg-1.1 [RC]
On Sun, 26 Oct 2014 16:04:57 +0100, Mateusz Åukasik wrote: On 26.10.2014 15:27, Sebastian Ramacher wrote: * Patch work: - Add from Fedora: dwb-gtk-deprecated.patch --fix FTBFS. (Closes: #763220) Okay. Please send a message to #763220 saying that there is a patch available and that you intend to NMU. OK. Done Well, not really, there's only the note that the patch exists, but nothing about the NMU candidate on mentors and the sponsorship-bug. (I stumbled across #763220 while looking at RC bugs and the PTS told me about the package on mentors, and then I manually looked into the sponsorship-requests bugs ...) Anyway, original bug CC'd now to have the info there :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Arlo Guthrie: Somebody Turned On The Light signature.asc Description: Digital Signature
Processed: Re: logkeys: logfile is gibberish
Processing commands for cont...@bugs.debian.org: severity 732300 serious Bug #732300 [logkeys] logkeys: logfile is gibberish Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 732300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 761539 761170 ...
Processing commands for cont...@bugs.debian.org: forcemerge 761539 761170 Bug #761539 [src:libgit2] libgit2: FTBFS: Tests failures Bug #761170 [src:libgit2] libgit2: FTBFS on multiple architectures Unset Bug forwarded-to-address Severity set to 'serious' from 'important' Added tag(s) sid and jessie. Merged 761170 761539 forwarded 761539 https://github.com/libgit2/libgit2/issues/2580 Bug #761539 [src:libgit2] libgit2: FTBFS: Tests failures Bug #761170 [src:libgit2] libgit2: FTBFS on multiple architectures Set Bug forwarded-to-address to 'https://github.com/libgit2/libgit2/issues/2580'. Set Bug forwarded-to-address to 'https://github.com/libgit2/libgit2/issues/2580'. thanks Stopping processing here. Please contact me if you need assistance. -- 761170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761170 761539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: jessie
Processing commands for cont...@bugs.debian.org: tags 766955 + sid jessie Bug #766955 [arc,arcanist] arcanist and arc: error when trying to install together Added tag(s) sid and jessie. tags 766974 + sid jessie Bug #766974 [src:asterisk-espeak] asterisk-espeak: FTBFS: fails to build with asterisk 13. Use latest version Added tag(s) sid and jessie. tags 766975 + sid jessie Bug #766975 [src:asterisk-flite] asterisk-flite: FTBFS: fails to build with asterisk 13. Use latest version Added tag(s) sid and jessie. tags 766732 + sid jessie Bug #766732 [nautilus] libc: Segfault in libc (from process pool) accessing files shared via DAV across ethernet on another machine Added tag(s) sid and jessie. tags 766988 + sid jessie Bug #766988 [gstreamer0.10-ffmpeg] Not installable? Added tag(s) sid and jessie. tags 765812 + sid jessie Bug #765812 [evolution-data-server] evolution-data-server: Crash with SQLite 3.8.7 due to missing xFetch definition Added tag(s) sid and jessie. End of message, stopping processing here. Please contact me if you need assistance. -- 765812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765812 766732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766732 766955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766955 766974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766974 766975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766975 766988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766988 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767019: xscreensaver: postinst overwrites /etc/X11/app-defaults/XScreenSaver without asking
Package: xscreensaver Version: 5.30-1+b1 Severity: serious Justification: Policy 10.7.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This part of xscreensaver.postinst overwrites any locally modified /etc/X11/app-defaults/XScreenSaver configuration: # Use the correct app defaults cd /etc/X11/app-defaults if [ -f XScreenSaver-gl ]; then ln -sf XScreenSaver-gl XScreenSaver else ln -sf XScreenSaver-nogl XScreenSaver fi You should not do the above if an XScreenSaver file or symlink exists prior to installation BjĆørn - -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (700, 'stable'), (600, 'unstable'), (500, 'stable-updates'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-rc2 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xscreensaver depends on: ii libatk1.0-0 2.14.0-1 ii libc62.19-12 ii libcairo21.14.0-2 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglade2-0 1:2.6.4-2 ii libglib2.0-0 2.42.0-2 ii libgtk2.0-0 2.24.25-1 ii libice6 2:1.0.9-1 ii libpam0g 1.1.3-7.1 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpangoft2-1.0-01.36.8-2 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxi6 2:1.7.4-1 ii libxinerama1 2:1.1.3-1 ii libxml2 2.9.2+dfsg1-1 ii libxmu6 2:1.1.1-1 ii libxpm4 1:3.5.10-1 ii libxrandr2 2:1.4.2-1 ii libxrender1 1:0.9.8-1 ii libxt6 1:1.1.3-1+deb7u1 ii libxxf86vm1 1:1.1.3-1 ii xscreensaver-data5.15-3 Versions of packages xscreensaver recommends: ii libjpeg-progs 8d-1+deb7u1 ii perl [perl5] 5.20.1-2 ii wamerican [wordlist] 7.1-1 Versions of packages xscreensaver suggests: ii chromium [www-browser] 37.0.2062.120-1~deb7u1 pn fortune none pn gdm3 | kdm-gdmcompat none ii iceweasel [www-browser] 31.2.0esr-2 ii lynx-cur [www-browser] 2.8.8dev.12-2 ii opera [www-browser] 12.16.1860 pn qcam | streamer none ii w3m [www-browser]0.5.3-8 pn xdaliclock none pn xfishtanknone pn xscreensaver-gl none - -- no debconf information - -- debsums errors found: sh: 1: /usr/sbin/dpkg-divert: not found -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlROhA8ACgkQ10rqkowbIsmpZACfXv7OS9DERgkf2AjtuaAhQqL1 /KEAn2eDVbDBZ5sot0O0Mkcjly1xVKPy =R0bh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759745: gdm3: Unable to login post-upgrade without systemd-sysv installed
Confirmed that this bug is fixed with the following packages: ii cgmanager 0.33-2 amd64 Central cgroup manager daemon ii linux-image-3.17-1-amd643.17-1~exp1 amd64 Linux 3.17 for 64-bit PCs ii systemd-shim8-3 amd64 shim for systemd I just successfully tried this in a VM with the following versions, which are all in testing: ii cgmanager0.33-2 amd64 ii linux-image-3.16-3-amd64 3.16.5-1 amd64 ii systemd-shim 8-4 amd64 So this bug should be considered fixed IMHO. Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 765062
Processing commands for cont...@bugs.debian.org: tags 765062 + patch Bug #765062 [libapache-mod-auth-radius] libapache-mod-auth-radius: FTBFS - missing build dependency on libssl-dev Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 765062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690169: reportbug: incorrectly labels a binary package choice as Source:
On Tue, 05 Aug 2014 11:48:53 +0200, Fabian Greffrath wrote: Control: severity -1 critical Arguably this should even be considered RC and/or considered for a stable update (assuming the fix is not too intrusive), because a lot of bugs can get lost, including important ones (RC, transition blockers, etc.). Indeed, this destroys reportbug! Hm ... While I agreed that this bug is annoying, critical [0] seems a tad over the top. If it were my call, I'd stay with the previously used important severity. Cheers, gregor [0] makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Funny Van Dannen: Prinzessin der Freiheit signature.asc Description: Digital Signature
Bug#766459: debootstrap: should not try to configure
On Mon, Oct 27, 2014 at 16:36:42 +0100, Santiago Vila wrote: [...] For example, your interpretation would force base-passwd to lose its essential flag, because it can't provide its core functionality only when in unpacked state. Then, according to policy, base-files and *every* other package using any of the system users in any of its maintainer scripts would have to add a Depends: base-passwd, since they depend on functionality which is only available after base-passwd has been configured. Yes, indeed this is what I'd infer from policy. But I could easily be wrong. Frankly, I don't think that's what we want. I would say that at least we do not want this at this point in the release cycle as it appears be bear way too many risks. Admittedly, all that *I* want is a working debootstrap, so I'm also ok just having the changes in base-files for now (or maybe also in debootstrap). Best, Michael pgpQ7ep2m3ES5.pgp Description: PGP signature
Processed: marking this grave
Processing control commands: retitle -1 CVE-2013-4440: trivially weak passwords if no tty Bug #725507 [pwgen] generated passwords have more repetitions than expected Changed Bug title to 'CVE-2013-4440: trivially weak passwords if no tty' from 'generated passwords have more repetitions than expected' severity -1 grave Bug #725507 [pwgen] CVE-2013-4440: trivially weak passwords if no tty Severity set to 'grave' from 'important' tags -1 +patch Bug #725507 [pwgen] CVE-2013-4440: trivially weak passwords if no tty Added tag(s) patch. tags 726578 -patch Bug #726578 [pwgen] pwgen: Multiple vulnerabilities in passwords generation Removed tag(s) patch. -- 725507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725507 726578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764667: distcc: diff for NMU version 3.1-6.1
Control: tags 764667 + patch Control: tags 764667 + pending Dear maintainer, I've prepared an NMU for distcc (versioned as 3.1-6.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: The Eagles: Lyin' Eyes diff -Nru distcc-3.1/debian/changelog distcc-3.1/debian/changelog --- distcc-3.1/debian/changelog 2013-05-08 14:33:03.0 +0200 +++ distcc-3.1/debian/changelog 2014-10-27 19:19:18.0 +0100 @@ -1,3 +1,13 @@ +distcc (3.1-6.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix Trigger cycle causes dpkg to fail processing: +change triggers from interest to interest-noawait, as proposed by +Guillem Jover. +(Closes: #764667) + + -- gregor herrmann gre...@debian.org Mon, 27 Oct 2014 19:18:30 +0100 + distcc (3.1-6) unstable; urgency=low [ Daniel Hartwig ] diff -Nru distcc-3.1/debian/distcc.triggers.in distcc-3.1/debian/distcc.triggers.in --- distcc-3.1/debian/distcc.triggers.in 2013-01-10 11:55:32.0 +0100 +++ distcc-3.1/debian/distcc.triggers.in 2014-10-27 19:18:27.0 +0100 @@ -1,2 +1,2 @@ -interest /usr/lib/gcc -interest /usr/lib/%DEB_HOST_MULTIARCH%/gcc +interest-noawait /usr/lib/gcc +interest-noawait /usr/lib/%DEB_HOST_MULTIARCH%/gcc signature.asc Description: Digital Signature
Processed: distcc: diff for NMU version 3.1-6.1
Processing control commands: tags 764667 + patch Bug #764667 [distcc] distcc: Trigger cycle causes dpkg to fail processing Added tag(s) patch. tags 764667 + pending Bug #764667 [distcc] distcc: Trigger cycle causes dpkg to fail processing Added tag(s) pending. -- 764667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740998: rdnssd: merge-hook overwrites /etc/resolv.conf when /sbin/resolvconf is not installed
I believe that it should do something saner instead of overwriting. I must disagree. If resolvconf is absent, overwriting is the most sane, or least insane thing to do. There just is not a lot that can be done without mediation for writing the resolver configuration. Here I must disagree. I don't use NetworkManager, in case it matters. As I explained, rdnssd is unusable for me as-is. With my (fairly simple) patch, it at least works for me, so clearly there is something that can be done. It should verify if the file contains the DNS servers it detected and add them if they are missing. But it should definitely not blindly overwrite the file... There are currently no ways to know which entries were inserted by rdnssd (possibly by a previous incantation of it) and which by other tools. Maybe not by a previous incantation, but definitely be the current one. And if the current one contains only nameserver entries, it can just refrain from modifying/deleting any other kind of entries, whether they were generated by rdnssd previously (perhaps with a different configuration in order to query other data) or someone/something else. Indeed, my patch doesn't actually check the current entries, and hardcodes nameserver only, but that shouldn't be too hard to fix. If that's what you like I can try to amend my patch. Furthermore, I doubt we can safely assume that all resolv.conf tools remove their entries when uninstalled. I think this suggestion is worse than the bug from a reliability perspective. Do you think reliably wrong is better? (Well, as a programmer I'd actually kind of agree -- reliably wrong is better in order to find a bug, but now that we have found the bug, it's time to fix it. :) Really, any pair of two tools writing resolv.conf will screw stuff up without resolvconf present and supported by both tools. That problem affects ppp, dhcp- client3, network-manager, wicd, connman, systemd(-networkd) just to name a few. And I donĀ“t dare mention most if not all VPN clients. Or the admin, not to forget. For all I know, rdnssd doesn't own /etc/resolv.conf. In fact, for a file that resides in /etc, without a special notice, I'd expect that I can modify it as an admin (which I did, and then I had to debug what killed my changes). An alternative that would also work for me (not sure about combination with other tools) would be if merge-hook used some template to produce its output (which should then include a comment pointing to the template for manual changes), so I could put my local settings there instead. Frank -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759745: gdm3: Unable to login post-upgrade without systemd-sysv installed
Control: reassign -1 cgmanager Control: forcemenge 754850 -1 On Mon, Oct 27, 2014 at 06:50:51PM +0100, Christian Seiler wrote: Confirmed that this bug is fixed with the following packages: ii cgmanager 0.33-2 amd64 Central cgroup manager daemon ii linux-image-3.17-1-amd643.17-1~exp1 amd64 Linux 3.17 for 64-bit PCs ii systemd-shim8-3 amd64 shim for systemd I just successfully tried this in a VM with the following versions, which are all in testing: ii cgmanager0.33-2 amd64 ii linux-image-3.16-3-amd64 3.16.5-1 amd64 ii systemd-shim 8-4 amd64 So this bug should be considered fixed IMHO. Thanks. Marking this as a duplicate of bug #754850. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Processed (with 1 errors): Re: Bug#759745: gdm3: Unable to login post-upgrade without systemd-sysv installed
Processing control commands: reassign -1 cgmanager Bug #759745 [systemd-shim] gdm3: Unable to login post-upgrade without systemd-sysv installed Bug #760366 [systemd-shim] gdm3: Stopped showing any users, no way to log in Bug reassigned from package 'systemd-shim' to 'cgmanager'. Bug reassigned from package 'systemd-shim' to 'cgmanager'. Ignoring request to alter found versions of bug #759745 to the same values previously set Ignoring request to alter found versions of bug #760366 to the same values previously set Ignoring request to alter fixed versions of bug #759745 to the same values previously set Ignoring request to alter fixed versions of bug #760366 to the same values previously set forcemenge 754850 -1 Unknown command or malformed arguments to command. -- 759745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759745 760366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 754850 759745
Processing commands for cont...@bugs.debian.org:
forcemerge 754850 759745
Bug #754850 {Done: Serge Hallyn serge.hal...@ubuntu.com} [cgmanager]
regression: no suspend/hibernate on non-systemd systems
Bug #757348 {Done: Serge Hallyn serge.hal...@ubuntu.com} [cgmanager] systemd:
with SysV init, can no longer suspend and shutdown from lightdm
Bug #757698 {Done: Serge Hallyn serge.hal...@ubuntu.com} [cgmanager]
[network-manager] network-manager: Not authorized to control networking
Bug #758746 {Done: Serge Hallyn serge.hal...@ubuntu.com} [cgmanager]
kde-workspace-bin: Energy saving schemes have no effect
Bug #760281 {Done: Serge Hallyn serge.hal...@ubuntu.com} [cgmanager] xfce4:
cannot mount usb drive: Not authorized to perform operation
Bug #760366 [cgmanager] gdm3: Stopped showing any users, no way to log in
Marked Bug as done
Marked Bug as done
Removed indication that 760366 affects gdm3
Removed indication that 759745 affects gdm3
Marked as fixed in versions cgmanager/0.33-2.
Marked as fixed in versions cgmanager/0.33-2.
Added tag(s) sid, moreinfo, jessie, and patch.
Added tag(s) sid, moreinfo, jessie, and patch.
Bug #757348 {Done: Serge Hallyn serge.hal...@ubuntu.com} [cgmanager] systemd:
with SysV init, can no longer suspend and shutdown from lightdm
Bug #757698 {Done: Serge Hallyn serge.hal...@ubuntu.com} [cgmanager]
[network-manager] network-manager: Not authorized to control networking
Bug #758746 {Done: Serge Hallyn serge.hal...@ubuntu.com} [cgmanager]
kde-workspace-bin: Energy saving schemes have no effect
Bug #759745 {Done: Serge Hallyn serge.hal...@ubuntu.com} [cgmanager] gdm3:
Unable to login post-upgrade without systemd-sysv installed
Bug #760281 {Done: Serge Hallyn serge.hal...@ubuntu.com} [cgmanager] xfce4:
cannot mount usb drive: Not authorized to perform operation
Merged 754850 757348 757698 758746 759745 760281 760366
thanks
Stopping processing here.
Please contact me if you need assistance.
--
754850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754850
757348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757348
757698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757698
758746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758746
759745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759745
760281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760281
760366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748861: marked as done (miro: FTBFS due to Libav 10)
Your message dated Mon, 27 Oct 2014 19:05:32 +
with message-id e1xipbg-0005gc...@franck.debian.org
and subject line Bug#748861: fixed in miro 6.0-1
has caused the Debian Bug report #748861,
regarding miro: FTBFS due to Libav 10
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.)
--
748861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: miro
Version: 4.0.4-1.1
Severity: serious
Justification: fails to build from source
Tags: patch
Dear Maintainer,
miro currently fails to build in sid:
cc -I/usr/include/ffmpeg -c
/tmp/buildd/miro-4.0.4/linux/miro-segmenter.c -o
/tmp/buildd/miro-4.0.4/./build/miro-segmenter/tmp/buildd/miro-4.0.4/linux/miro-segmenter.o
/tmp/buildd/miro-4.0.4/linux/miro-segmenter.c: In function
'add_output_stream':
/tmp/buildd/miro-4.0.4/linux/miro-segmenter.c:81:92: error:
'CODEC_ID_MP3' undeclared (first use in this function)
if ((input_codec_context-block_align == 1
input_codec_context-codec_id == CODEC_ID_MP3) ||
input_codec_context-codec_id == CODEC_ID_AC3) {
^
/tmp/buildd/miro-4.0.4/linux/miro-segmenter.c:81:92: note: each
undeclared identifier is reported only once for each function it appears in
/tmp/buildd/miro-4.0.4/linux/miro-segmenter.c:81:142: error:
'CODEC_ID_AC3' undeclared (first use in this function)
if ((input_codec_context-block_align == 1
input_codec_context-codec_id == CODEC_ID_MP3) ||
input_codec_context-codec_id == CODEC_ID_AC3) {
^
error: command 'cc' failed with exit status 1
/usr/share/cdbs/1/class/python-distutils.mk:105: recipe for target
'debian/python-module-stampdir/miro' failed
make: *** [debian/python-module-stampdir/miro] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Attached is a patch fixing this problem.
Best regards,
Andreas
diff --git a/debian/patches/CodecID.patch b/debian/patches/CodecID.patch
new file mode 100644
index 000..4e59be1
--- /dev/null
+++ b/debian/patches/CodecID.patch
@@ -0,0 +1,19 @@
+Description: Rename CODEC_ID_* to AV_CODEC_ID_*
+
+Author: Andreas Cadhalpun andreas.cadhal...@googlemail.com
+Last-Update: 2014-05-21
+
+--- miro-4.0.4.orig/linux/miro-segmenter.c
miro-4.0.4/linux/miro-segmenter.c
+@@ -78,7 +78,11 @@ static AVStream *add_output_stream(AVFor
+ output_codec_context-sample_rate = input_codec_context-sample_rate;
+ output_codec_context-channels = input_codec_context-channels;
+ output_codec_context-frame_size = input_codec_context-frame_size;
++#if LIBAVCODEC_VERSION_MAJOR 54
++if ((input_codec_context-block_align == 1 input_codec_context-codec_id == AV_CODEC_ID_MP3) || input_codec_context-codec_id == AV_CODEC_ID_AC3) {
++#else
+ if ((input_codec_context-block_align == 1 input_codec_context-codec_id == CODEC_ID_MP3) || input_codec_context-codec_id == CODEC_ID_AC3) {
++#endif
+ output_codec_context-block_align = 0;
+ }
+ else {
diff --git a/debian/patches/series b/debian/patches/series
index d1cc606..a7b7305 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,3 +4,4 @@
120_miro.desktop.patch
130_libav9.patch
140_use_avconv.patch
+CodecID.patch
---End Message---
---BeginMessage---
Source: miro
Source-Version: 6.0-1
We believe that the bug you reported is fixed in the latest version of
miro, 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 748...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Uwe Hermann u...@debian.org (supplier of updated miro package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 27 Oct 2014 19:00:45 +0100
Source: miro
Binary: miro miro-data
Architecture: source all amd64
Version: 6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Uwe Hermann u...@debian.org
Changed-By: Uwe Hermann u...@debian.org
Description:
miro - GTK+ based RSS video aggregator
miro-data - GTK+ based RSS video aggregator data files
Closes: 532021 689826
Bug#754232: marked as done (Should miro be removed from the archive?)
Your message dated Mon, 27 Oct 2014 19:05:32 + with message-id e1xipbg-0005gi...@franck.debian.org and subject line Bug#754232: fixed in miro 6.0-1 has caused the Debian Bug report #754232, regarding Should miro be removed from the archive? 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.) -- 754232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: miro Severity: serious Should miro be removed from the archive? - Last maintainer upload 2.5 years ago - Removed from testing 9 months ago - Totally outdated (current upstream is 6) Unless some disagrees, I'll reassign to ftp.debian.org in a few weeks. Cheers, Moritz ---End Message--- ---BeginMessage--- Source: miro Source-Version: 6.0-1 We believe that the bug you reported is fixed in the latest version of miro, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Uwe Hermann u...@debian.org (supplier of updated miro package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 27 Oct 2014 19:00:45 +0100 Source: miro Binary: miro miro-data Architecture: source all amd64 Version: 6.0-1 Distribution: unstable Urgency: medium Maintainer: Uwe Hermann u...@debian.org Changed-By: Uwe Hermann u...@debian.org Description: miro - GTK+ based RSS video aggregator miro-data - GTK+ based RSS video aggregator data files Closes: 532021 689826 692482 748861 754232 764562 Changes: miro (6.0-1) unstable; urgency=medium . * Acknowledge NMU, thanks Sebastian Ramacher sramac...@debian.org. * New upstream release (Closes: #692482, #754232, #764562). + Drop linux/contrib/enmfp-codegen/* in upstream tarball, apparently there's no source code available for those files. + Now build-depends on libtag1-dev, libsqlite3-dev, and libboost1.55-dev. + Fixes Youtube/Vimeo download/scraping (Closes: #689826). * Standards-Version: 3.9.6 (no changes required). * debian/patches: + 10_movies_dir.patch: Update. + 50_miro_debug_fix.patch: Update. + 100_catch_keyerror_in_update_items.patch: Drop (obsolete). + 130_libav9.patch: Drop (fixed upstream). + 140_use_avconv.patch: Update, drop upstream-merged parts. + 150_codec_id.patch: Add, fixes FTBFS due to libav 10 (Closes: #748861). Thanks Andreas Cadhalpun andreas.cadhal...@googlemail.com. + 160_fixyoutubedl.patch: Fix another Youtube downloads/scraping issue. * Drop 'Recommends: python-psyco' (package no longer in the archive). * Move 'libav-tools' from 'Suggests' to 'Depends', miro will not properly start-up without it. * Move gstreamer0.10-ffmpeg from 'Depends' to 'Suggests' for now; the package is uninstallable atm (#766988) and seems to be optional for miro. * Temporary lintian overrides (use dh_python2 instead): + miro: depends-on-obsolete-package + miro source: build-depends-on-obsolete-package * Close long-obsolete request for lenny backport (Closes: #532021). Checksums-Sha1: 86cbebce79a21262a3f7f7bcc378f407f6552b8b 1265 miro_6.0-1.dsc da34166634a39015e08c464933c52da0048d5844 12848738 miro_6.0.orig.tar.gz 04cb7e3eeaabd716e02aa27e40ca1488a3458874 16100 miro_6.0-1.debian.tar.xz 88749c17733e3863f6ee0407c5714fa02e458939 1072762 miro-data_6.0-1_all.deb 0b936de7f32ed06e4a5616a33e81cdcb4853dd69 702424 miro_6.0-1_amd64.deb Checksums-Sha256: 3a457906e4b288b398c2f2a50066ba36ad2112c35869917e7985010958786992 1265 miro_6.0-1.dsc 9388ca3cc942d780c25d57c19ccf1e2b3ac9206cfe9fece6ea92843d9599ae46 12848738 miro_6.0.orig.tar.gz e13e98152d526b6ec1be7ab731945f7890fbf3510e2d17c90d81f85f23ce00f2 16100 miro_6.0-1.debian.tar.xz bccd56fc275f2d4e91424ce2b1e63f23b008747360f56a7a78bb22d0ff583e02 1072762 miro-data_6.0-1_all.deb 19d5905cf38311a9b809c297e930089a3a602bae3d9f6084107bf4a8ebe98a48 702424 miro_6.0-1_amd64.deb Files: 8229ae8fb28fe7c60774de2d47f9f907 1265 net extra miro_6.0-1.dsc 1ff5a36b3c8cead9aa39c6001986d44d 12848738 net extra miro_6.0.orig.tar.gz c21624105b9d58cad0fb8b652133cb74 16100 net
Processed: viewmol: /usr/bin/viewmol missing for most archs
Processing commands for cont...@bugs.debian.org: tags 763909 patch Bug #763909 [src:viewmol] viewmol: /usr/bin/viewmol missing for most archs Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 763909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763909: viewmol: /usr/bin/viewmol missing for most archs
tags 763909 patch
thanks
So 'getmachine' is looking in the non-multiarch directories for
libtiff, libpng, etc.
The attached patch works for me locally, but probably needs some more work.
If nobody takes this, I'll prepare an NMU at the end of this week.
--- a/source/getmachine
+++ b/source/getmachine
@@ -117,9 +117,9 @@
hint=1
# TIFF library
- if [ -f /usr/lib/libtiff.a ]
+ if [ -f /usr/lib/$DEB_HOST_MULTIARCH/libtiff.a ]
then
-libtiff=-L/usr/lib
+libtiff=-L/usr/lib/$DEB_HOST_MULTIARCH
elif [ -f /usr/local/lib/libtiff.a ]
then
libtiff=-L/usr/local/lib
@@ -135,12 +135,12 @@
echo LIBTIFF = ${libtiff} .config.$os
# TIFF include file
- if [ -f /usr/include/tiff.h ]
+ if [ -f /usr/include/$DEB_HOST_MULTIARCH/tiff.h ]
then
case $os in
CYGWIN*) tiffinclude=.
;;
- *) tiffinclude=/usr/include
+ *) tiffinclude=/usr/include/$DEB_HOST_MULTIARCH
;;
esac
elif [ -f /usr/local/include/tiff.h ]
@@ -154,9 +154,9 @@
echo TIFFINCLUDE = $tiffinclude .config.$os
# PNG library
- if [ -f /usr/lib/libpng.a -o -f /usr/lib/libpng12.a ]
+ if [ -f /usr/lib/$DEB_HOST_MULTIARCH/libpng.a -o -f /usr/lib/$DEB_HOST_MULTIARCH/libpng12.a ]
then
-libpng=-L/usr/lib
+libpng=-L/usr/lib/$DEB_HOST_MULTIARCH
elif [ -f /usr/local/lib/libpng.a ]
then
libpng=-L/usr/local/lib
Bug#766732: Debugging : no useful results so far
On Mon, 2014-10-27 at 14:10 +, Simon McVittie wrote: On 26/10/14 14:59, Brian Drummond wrote: gdb nautilus allows me to reproduce the segfault, but doesn't return control to the debugger. So the pool (is it a process? I can't see it in ps ax) containing the error must be elsewhere in the system. You might need to make sure all nautilus processes have been killed before starting one under gdb - nautilus probably has some single instance logic going on. Update re: gvfsd-smb-browse gvfsd-network gvfs/gvfsd-dnssd I think I managed to get these running under gdb (they certainly produce debugging output when I do things in Nautilus). However the segfault doesn't appear (i.e. return control to gdb) under any of them. So far I haven't managed to capture pstree -p containing a pool with PID that later matches the PID in the segfault. If I could, at least I'd know what created it. - Brian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766397: Bug#766395: emacs/gnus: Uses s_client to for SSL.
On 24/10/2014 11:01 +0400, Lars Magne Ingebrigtsen wrote: I grepped through the Emacs tree, and there seems to still be one in-tree usage -- mail-source.el. It uses imap.el to allow a simple download-from-IMAP thing. Which probably nobody uses, but should still be present, I think. If I understood right, you're talking about using 'imap element in mail-sources var - in that case I'm using it and find it very convenient. So either mail-source.el should be rewritten to use something else (and imap.el be obsoleted), or imap.el should be rewritten to use `open-network-stream' instead of futzing around with TLS primitives directly. -- Filipp -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690169: reportbug: incorrectly labels a binary package choice as Source:
On Lu, 27 oct 14, 19:07:24, gregor herrmann wrote: On Tue, 05 Aug 2014 11:48:53 +0200, Fabian Greffrath wrote: Control: severity -1 critical Arguably this should even be considered RC and/or considered for a stable update (assuming the fix is not too intrusive), because a lot of bugs can get lost, including important ones (RC, transition blockers, etc.). Indeed, this destroys reportbug! Hm ... While I agreed that this bug is annoying, critical [0] seems a tad over the top. If it were my call, I'd stay with the previously used important severity. Critical might be a tad too much, but definitely 'serious' (i.e. RC). Just as a data point, I get via unknown-package@ on average 1-2 bugs *per day* due to this bug. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#690169: reportbug: incorrectly labels a binary package choice as Source:
On Mon, 27 Oct 2014 21:46:50 +0200, Andrei POPESCU wrote: Hm ... While I agreed that this bug is annoying, critical [0] seems a tad over the top. If it were my call, I'd stay with the previously used important severity. Critical might be a tad too much, but definitely 'serious' (i.e. RC). Just as a data point, I get via unknown-package@ on average 1-2 bugs *per day* due to this bug. Wow, that's much more than I would have imagined. Thanks for this data point. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#766195: [PATCH] ipv6: reuse ip6_frag_id from ip6_ufo_append_data
On Mon, Oct 27, 2014 at 13:40:44 +, Ben Hutchings wrote: I've now written and tested patches for that remaining regression. Source at: https://people.debian.org/~benh/packages/linux_3.2.63-2+deb7u1.dsc https://people.debian.org/~benh/packages/linux_3.2.63-2+deb7u1.debian.tar.xz Binary at: https://people.debian.org/~benh/packages/linux-image-3.2.0-4-amd64_3.2.63-2+deb7u1_amd64.deb There's a signed .changes file there as well, for verification (distribution=UNRELEASED in case you are wondering). Additional testing would be appreciated. Installed your package on salieri.debian.org now. Anything we should look out for? Cheers, Julien signature.asc Description: Digital signature
Bug#767028: ovirt-guest-agent: fails to install
Package: ovirt-guest-agent Version: 1.0.10.1.dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): The following NEW packages will be installed: ovirt-guest-agent 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 39.0 kB of archives. After this operation, 92.2 kB of additional disk space will be used. Get:1 http://mirror.bm.debian.org/debian/ jessie/main ovirt-guest-agent all 1.0.10.1.dfsg-1 [39.0 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 39.0 kB in 0s (417 kB/s) Selecting previously unselected package ovirt-guest-agent. (Reading database ... 10034 files and directories currently installed.) Preparing to unpack .../ovirt-guest-agent_1.0.10.1.dfsg-1_all.deb ... Unpacking ovirt-guest-agent (1.0.10.1.dfsg-1) ... Setting up ovirt-guest-agent (1.0.10.1.dfsg-1) ... dpkg: error processing package ovirt-guest-agent (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: ovirt-guest-agent E: Sub-process /usr/bin/dpkg returned an error code (1) I'm aware that this looks pretty much similar to #754789 which was fixed in 1.0.10.1.dfsg-1, but now the /var/lib/dpkg/info/ovirt-guest-agent.postinst: line 4: udevadm: command not found is gone / not visible... cheers, Holger Start: 2014-10-17 20:22:43 UTC Package: ovirt-guest-agent Version: 1.0.10.1.dfsg-1 Installed-Size: 90 Maintainer: Laszlo Boszormenyi (GCS) g...@debian.org Architecture: all Depends: python:any (= 2.6.6-7~), udev, python-apt, python-dbus, python-ethtool, usermode, qemu-guest-agent Description: oVirt Guest Agent Homepage: http://www.ovirt.org/Ovirt_guest_agent Description-md5: 2737be45d3cf8eabb6d3a39e2d1df583 Section: utils Priority: extra Filename: pool/main/o/ovirt-guest-agent/ovirt-guest-agent_1.0.10.1.dfsg-1_all.deb Size: 38950 MD5sum: 43fb923a921b0e03625cc32fc34476ea SHA1: e91478c08a2efb71962451e1d81054857e251c30 SHA256: 9082bc2d770d356eea61f9e98ce12c07cca73eadff32fa7ee92c2fac451a0f3f Executing: sudo env PYTHONPATH=/srv/piuparts.debian.org/lib/python2.7/dist-packages timeout -s INT -k 5m 35m /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt ovirt-guest-agent=1.0.10.1.dfsg-1 0m0.0s INFO: -- 0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile. 0m0.0s INFO: FAQ available at https://wiki.debian.org/piuparts/FAQ 0m0.0s INFO: The FAQ also explains how to contact us in case you think piuparts is wrong. 0m0.0s INFO: -- 0m0.0s INFO: piuparts version 0.59 starting up. 0m0.0s INFO: Command line arguments: /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt ovirt-guest-agent=1.0.10.1.dfsg-1 0m0.0s INFO: Running on: Linux piu-slave-bm-a 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 0m0.0s DEBUG: Created temporary directory /srv/piuparts.debian.org/tmp/tmp2izDRR 0m0.0s DEBUG: Unpacking /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz into /srv/piuparts.debian.org/tmp/tmp2izDRR 0m0.0s DEBUG: Starting command: ['tar', '-C', '/srv/piuparts.debian.org/tmp/tmp2izDRR', '-zxf', '/srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz'] 0m2.1s DEBUG: Command ok: ['tar', '-C', '/srv/piuparts.debian.org/tmp/tmp2izDRR', '-zxf', '/srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz'] 0m2.1s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmp2izDRR', 'mount', '-t', 'proc', 'proc', '/proc'] 0m2.1s DEBUG: Command ok: ['chroot', '/srv/piuparts.debian.org/tmp/tmp2izDRR', 'mount', '-t', 'proc', 'proc', '/proc'] 0m2.1s DEBUG: sources.list: deb http://mirror.bm.debian.org/debian/ jessie main 0m2.2s DEBUG: Created policy-rc.d and chmodded it. 0m2.2s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmp2izDRR', 'apt-get', 'update'] 0m6.5s DUMP: Get:1 http://mirror.bm.debian.org jessie InRelease [191 kB] Get:2 http://mirror.bm.debian.org
Processed: Re: Bug#766370: Acknowledgement (login[5797]: segfault at ip sp error 14 in librt-2.19.so)
Processing control commands: tag -1 + moreinfo Bug #766370 [libc6] login[5797]: segfault at ip sp error 14 in librt-2.19.so Added tag(s) moreinfo. -- 766370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766370: Acknowledgement (login[5797]: segfault at ip sp error 14 in librt-2.19.so)
control: tag -1 + moreinfo On Wed, Oct 22, 2014 at 05:55:52PM +0200, smile...@gmail.com wrote: Am Wed, 22 Oct 2014 15:09:07 + schrieb ow...@bugs.debian.org (Debian Bug Tracking System): Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): GNU Libc Maintainers debian-gl...@lists.debian.org If you wish to submit further information on this problem, please send it to 766...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. Sorry for this, my computer is now down I can not login as root. I need a little bit help. Can you please give us more details about what you did (upgrade ?) for getting into this situation. Also please give use the full error message like the one you put in the subject of this bug, including the addresses. Im not shure, i think i must repaire the situation with a extern bootable usb-stick. Not necessarily. You might also boot your computer selecting the recovery mode in the grub entry. Unfortunately it's not possible to help you more without getting more details about the issue first. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: usertag piuparts for runit fails to install
Processing commands for cont...@bugs.debian.org: user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was hol...@layer-acht.org). usertag 766187 + piuparts There were no usertags set. Usertags are now: piuparts. affects 766187 git-daemon-run Bug #766187 [runit] runit: Fails to install runit after fresh install of jessie beta2 Added indication that 766187 affects git-daemon-run thanks Stopping processing here. Please contact me if you need assistance. -- 766187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 740509
Processing commands for cont...@bugs.debian.org: tags 740509 + pending Bug #740509 [glibc] ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address Bug #765882 [glibc] freebsd-net-tools: ifconfig ioctl siocaifaddr Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 740509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740509 765882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736035: marked as done (please build-depend on libtiff-dev, not libtiff4-dev)
Your message dated Mon, 27 Oct 2014 21:39:21 + with message-id e1xis0x-0007zx...@franck.debian.org and subject line Bug#736035: fixed in openmeeg 2.0.0.dfsg-5.2 has caused the Debian Bug report #736035, regarding please build-depend on libtiff-dev, not libtiff4-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 736035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: openmeeg Version: 2.0.0.dfsg-5.1 User: q...@debian.org Usertags: libtiff4-dev The libtiff4-dev package is a transitional package that is going to disappear soon. Please update your build dependency from libtiff4-dev to libtiff-dev. ---End Message--- ---BeginMessage--- Source: openmeeg Source-Version: 2.0.0.dfsg-5.2 We believe that the bug you reported is fixed in the latest version of openmeeg, 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 736...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Wookey woo...@debian.org (supplier of updated openmeeg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 27 Oct 2014 01:34:46 + Source: openmeeg Binary: libopenmeeg1 libopenmeeg-dev openmeeg-tools python-openmeeg Architecture: source Version: 2.0.0.dfsg-5.2 Distribution: unstable Urgency: low Maintainer: NeuroDebian Team t...@neuro.debian.net Changed-By: Wookey woo...@debian.org Description: libopenmeeg-dev - openmeeg library -- development files libopenmeeg1 - library for solving EEG and MEG forward and inverse problems openmeeg-tools - openmeeg library -- command line tools python-openmeeg - openmeeg library -- Python bindings Closes: 736035 Changes: openmeeg (2.0.0.dfsg-5.2) unstable; urgency=low . * Non-maintainer upload. * Transition libtiff dependencies away from libtiff4 (Closes: 736035) Checksums-Sha1: 5b66f5fbfd7180cb64b31e4f8b57c42db0d1f11f 2341 openmeeg_2.0.0.dfsg-5.2.dsc befcda62fc86bb7d301afaaae33dccc8dafa1609 15416 openmeeg_2.0.0.dfsg-5.2.debian.tar.xz Checksums-Sha256: 6f214fcf4ed0a782a2ef54b1217f2e0fae745a78b31bb05fa0b3cdf9bdc0666a 2341 openmeeg_2.0.0.dfsg-5.2.dsc c8fa08e62956795849f87ba0dc48a2c9dbf4c5f8067dd48023d66c4d6421f6e3 15416 openmeeg_2.0.0.dfsg-5.2.debian.tar.xz Files: e3b37b5d68ac1e28c9d237533201d0c1 2341 science extra openmeeg_2.0.0.dfsg-5.2.dsc 8b0a20acebefd8271db87fa5b1e005e1 15416 science extra openmeeg_2.0.0.dfsg-5.2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJUTkAjAAoJEPuGMlGob55HncUQAM4TjQBkJfHwPWL612m6uzIn xg99fj4u9omlDArrNvXm6iK7muGcMTSGs4F13gS0c2/D7sXdZ6G3j6sc3E1rr8r0 7ycWnyO58dJ3DIxg9HuZQhKILRqpl/PGCUsYcF8DQaJkoET53W9v1YjXT4YBoK+g cWCtlRl5KQs77tjJppzlBrKMnWCdQixUQSGU1LmBJeqa13dXAqIQVMZkr1o9Prop ubzLHxo86ulRJvGjZZQ26Me+Rdx+tw2Z+tOwXFsgEmd0JLQqDu+R3BtViEeTXROJ 8OQaAOGSL8XGpr2uvmsUeHqXxw59Xr6DsPbk6atZuEdWVsJbKx3nYvvvOchRvkum SVvKAz5/YR4OyP2Y9N4GJIdbhnCFjX+wXfFbJhMphPj3THRnQXOQOw5RkJPKa2x3 ACsiS3aJlLss4QQ/0mVReqKtL1oOcpSDIHLpRWyvKFDCflbVaZGl4m1Lfy+0vbDV /9W41MIc1TXv0tGieAsRnX5xoJhXFmujrzuhajF0owI+HyKWOHQqqQvyjwxiiX6X TCniq9VzLFfwi4CPvB2fMladnDDsXESJCfsPCyl87iRq9QCLHXtQ+JpfptoHX9eK DIz+fRsA8GT+kVPKrnGOiojJBompgdSFPsJsi1KnAbNo77UZcx1IfoIq10PPB2na 3cjlOVQ6G+YUkgLoiX2t =erYb -END PGP SIGNATUREEnd Message---
