Bug#710410: marked as done (uninstallable: libbctsp-java unavailable)
Your message dated Fri, 31 May 2013 06:48:06 + with message-id e1uij8a-0005rl...@franck.debian.org and subject line Bug#710410: fixed in libitext-java 2.1.7-6 has caused the Debian Bug report #710410, regarding uninstallable: libbctsp-java unavailable 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.) -- 710410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libitext-java Version: 2.1.7-4 Severity: serious Hi, root@frodo:/# apt-get install libitext-java Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libitext-java : Depends: libbctsp-java but it is not installable E: Unable to correct problems, you have held broken packages. root@frodo:/# apt-get install libbctsp-java Reading package lists... Done Building dependency tree Reading state information... Done Package libbctsp-java is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'libbctsp-java' has no installation candidate Looks like bouncycastle dropped libbctsp-java (see http://packages.qa.debian.org/b/bouncycastle/news/20130406T010007Z.html) That one went into unstable on May 17 (http://packages.qa.debian.org/b/bouncycastle/news/20130517T054754Z.html) Actually I don't see a removal of libbctsp-java in removals.txt (only -doc and -gcj) and rmadison does still show it, but... I know that experimentals libitext-java *is* installable, though: root@frodo:/# apt-get -t experimental install libitext-java Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libbcmail-java libbcpkix-java libbcprov-java libexpat1 libffi6 libgcj-common libgnuinet-java libgnumail-java libpython2.7-minimal libpython2.7-stdlib libssl1.0.0 mime-support python python-minimal python2.7 python2.7-minimal Suggested packages: libbcmail-java-doc libbcmail-java-gcj libbcpkix-java-doc libbcpkix-java-gcj libbcprov-java-doc libbcprov-java-gcj libgnumail-java-doc libitext-java-gcj python-doc python-tk python2.7-doc binfmt-support Recommended packages: file The following NEW packages will be installed: libbcmail-java libbcpkix-java libbcprov-java libexpat1 libffi6 libgcj-common libgnuinet-java libgnumail-java libitext-java libpython2.7-minimal libpython2.7-stdlib libssl1.0.0 mime-support python python-minimal python2.7 python2.7-minimal 0 upgraded, 17 newly installed, 0 to remove and 28 not upgraded. Need to get 11.9 MB/12.3 MB of archives. After this operation, 31.3 MB of additional disk space will be used. Do you want to continue [Y/n]? That probably should just be uploaded to unstable asap. Regards, Rene -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-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 Versions of packages libitext-java depends on: ii libbcmail-java 1.48+dfsg-2 ii libbcprov-java 1.48+dfsg-2 ii libbctsp-java 1.46+dfsg-7 libitext-java recommends no packages. Versions of packages libitext-java suggests: pn libitext-java-gcj none -- no debconf information ---End Message--- ---BeginMessage--- Source: libitext-java Source-Version: 2.1.7-6 We believe that the bug you reported is fixed in the latest version of libitext-java, 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 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill tmanc...@debian.org (supplier of updated libitext-java 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
Bug#710474: libunibreak-dev and liblinebreak2-dev: error when trying to install together
Package: liblinebreak2-dev,libunibreak-dev Version: liblinebreak2-dev/2.1-1 Version: libunibreak-dev/1.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2013-05-31 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: WARNING: The following packages cannot be authenticated! liblinebreak2 liblinebreak2-dev libunibreak1 libunibreak-dev Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package liblinebreak2. (Reading database ... 10806 files and directories currently installed.) Unpacking liblinebreak2 (from .../liblinebreak2_2.1-1_amd64.deb) ... Selecting previously unselected package liblinebreak2-dev. Unpacking liblinebreak2-dev (from .../liblinebreak2-dev_2.1-1_amd64.deb) ... Selecting previously unselected package libunibreak1. Unpacking libunibreak1 (from .../libunibreak1_1.0-1_amd64.deb) ... Selecting previously unselected package libunibreak-dev. Unpacking libunibreak-dev (from .../libunibreak-dev_1.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libunibreak-dev_1.0-1_amd64.deb (--unpack): trying to overwrite '/usr/include/linebreakdef.h', which is also in package liblinebreak2-dev 2.1-1 Errors were encountered while processing: /var/cache/apt/archives/libunibreak-dev_1.0-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/linebreak.h /usr/include/linebreakdef.h 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/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709170: no option to set the SSL protocol version?
On 2013-05-30 11:18, Charles Cazabon wrote: If this does fix the issue, I'd really like to see Debian revert this broken patch -- breaking existing configs and reducing compatibility with correct servers is not a good tradeoff for trying to make MSexchange work. Well, the patch in only in Debian since 2013-05-17 and only in the unstable distribution. unstable is exactly for finding such problems and fixing them before the package reaches testing. Anyway, I would love to see a fix for MSexChange compatibility with the new SSL library, that does not break other IMAP servers. To my regret, the MS product has still a very high market share, notwithstanding much better free alternatives exist. Do you think, one could make the SSL version an option, defaulting, of course, to the original value? And with a check for the Python version? Or maybe the problem can be solved in a totally different manner. I only came to this solution by trial and error. (For Debian, versions before 2.7 are not relevant, because we target Debian 8.0 and maybe 7.0 via backports, which both have Python 2.7, even 6.0 had 2.6.) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 666820
Processing commands for cont...@bugs.debian.org: close 666820 Bug #666820 [php5] php5: sourceful transition towards Apache 2.4 Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 666820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#707208: Acknowledgement (open-vm-dkms: ftbfs with gcc-4.8 and Linux 3.8)
Processing commands for cont...@bugs.debian.org: severity 707208 grave Bug #707208 [open-vm-dkms] ftbfs with linux 3.8 Severity set to 'grave' from 'important' stop Stopping processing here. Please contact me if you need assistance. -- 707208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707208 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#710462: marked as done (haskell-gloss: FTBFS: needs libghc-opengl-dev 2.6.*, vs. 2.8.)
Your message dated Fri, 31 May 2013 09:35:35 +
with message-id e1uilkf-0008iy...@franck.debian.org
and subject line Bug#710462: fixed in haskell-gloss 1.7.8.3-1
has caused the Debian Bug report #710462,
regarding haskell-gloss: FTBFS: needs libghc-opengl-dev 2.6.*, vs. 2.8.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
710462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: haskell-gloss
Version: 1.7.8.2-2
Severity: serious
Justification: fails to build from source
As it stands, builds of haskell-gloss against the current unstable
suite fail because it specifically build-depends on libghc-opengl-dev
2.6.*, whereas haskell-opengl is now at 2.8.0.0-1. Could you please
fix it to work with that version?
Thanks!
---End Message---
---BeginMessage---
Source: haskell-gloss
Source-Version: 1.7.8.3-1
We believe that the bug you reported is fixed in the latest version of
haskell-gloss, 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 710...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Joachim Breitner nome...@debian.org (supplier of updated haskell-gloss
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 May 2013 15:25:02 +0200
Source: haskell-gloss
Binary: libghc-gloss-dev libghc-gloss-prof libghc-gloss-doc
Architecture: source all amd64
Version: 1.7.8.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian Haskell Group
pkg-haskell-maintain...@lists.alioth.debian.org
Changed-By: Joachim Breitner nome...@debian.org
Description:
libghc-gloss-dev - ${haskell:ShortDescription}${haskell:ShortBlurb}
libghc-gloss-doc - ${haskell:ShortDescription}${haskell:ShortBlurb}
libghc-gloss-prof - ${haskell:ShortDescription}${haskell:ShortBlurb}
Closes: 710462
Changes:
haskell-gloss (1.7.8.3-1) unstable; urgency=low
.
* New upstream release (Closes: #710462)
Checksums-Sha1:
ecd8cf0eac64ce76264f933cfaa4cf064654df29 1822 haskell-gloss_1.7.8.3-1.dsc
f12ff677c7d2367b018b64014547eba81ad2828c 41323
haskell-gloss_1.7.8.3.orig.tar.gz
5eb5bdc219e73410531fa38b7c2b389acc0fc55a 1899
haskell-gloss_1.7.8.3-1.debian.tar.gz
888b1e4a24b80fd616160b25d2d21603eb90d4b7 156208
libghc-gloss-doc_1.7.8.3-1_all.deb
c6c1b7f084c2e278339b2d7a6caca2a031719d84 458754
libghc-gloss-dev_1.7.8.3-1_amd64.deb
a74cbaa36b097cf684a95482bb0675b772b669ae 433472
libghc-gloss-prof_1.7.8.3-1_amd64.deb
Checksums-Sha256:
b236406dce96872aa7b729eb647f8af027966d12b0272a051e74b7e88fbbcc0b 1822
haskell-gloss_1.7.8.3-1.dsc
599e6447d37357d4de98f24182e988e7aca96a336fd9934d8f1f0e56fe427771 41323
haskell-gloss_1.7.8.3.orig.tar.gz
2b2767b6ca0812c1abd7a26e59a08305ac9fdcae3eca075837bf01b1424ebac4 1899
haskell-gloss_1.7.8.3-1.debian.tar.gz
c5a64db4321afff8ce508451831f5d83aba1a64a7fe951073ff187128d895e30 156208
libghc-gloss-doc_1.7.8.3-1_all.deb
0b00f3588373eb8dba9c5ca312b2f72cb70972b6da808002d005f6f4078731c9 458754
libghc-gloss-dev_1.7.8.3-1_amd64.deb
1714d5b494967b90a06760e86d7bdaf9ebdecbf79ec23e3250461574a2f43f4d 433472
libghc-gloss-prof_1.7.8.3-1_amd64.deb
Files:
e2ea75498c7ba6582e20c6636c04b0c2 1822 haskell extra haskell-gloss_1.7.8.3-1.dsc
3869e733ec8db135aef65c10df284a17 41323 haskell extra
haskell-gloss_1.7.8.3.orig.tar.gz
006c8bc55547ce34761e9732a7347e1a 1899 haskell extra
haskell-gloss_1.7.8.3-1.debian.tar.gz
82f82460f7b4cb66540a1d5a5dd8625c 156208 doc extra
libghc-gloss-doc_1.7.8.3-1_all.deb
27bcc7e4d88a09eab0faed18110167a9 458754 haskell extra
libghc-gloss-dev_1.7.8.3-1_amd64.deb
d43640dd2ef86b68695ad345dfb844d7 433472 haskell extra
libghc-gloss-prof_1.7.8.3-1_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlGoX6UACgkQ9ijrk0dDIGyk1gCgnrn3O0RWtdvqm47TvXTqf+dn
FAoAoIED2qhbAd9DdSE5kB07CLMi6/EC
=xTqu
-END PGP SIGNATUREEnd Message---
Bug#665605: marked as done (rasmol: Including individual glib headers no longer supported)
Your message dated Fri, 31 May 2013 09:38:09 + with message-id e1uilmj-0001jf...@franck.debian.org and subject line Bug#665605: fixed in rasmol 2.7.5.2-2 has caused the Debian Bug report #665605, regarding rasmol: Including individual glib headers no longer supported 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.) -- 665605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rasmol Version: 2.7.5.2-1 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: glib-single-include Hi, including invidiual glib headers has been deprecated for several years. Starting with glib 2.32 it is now mandatory to include glib.h instead of individual headers [1], or the compiler will generate an error. With the notable exception of: glib/gi18n.h glib/gi18n-lib.h glib/gprintf.h glib/gstdio.h Those header files are still meant to be included separately. Development releases of 2.32 (2.31.x) are available in experimental. During a test-rebuild rasmol failed to build with the new glib [2]. Please update rasmol at your earliest convenience, so once we move the glib version from experimental to unstable, your package will remain buildable. Usually, simply replacing #include glib/foo.h with #include glib.h is all that is needed (while keeping the above list of exceptions in mind) You can use the glib version from experimental to test if your package builds correctly. A simple shell script [3] has been written, that can help you generate a patch which should fix the includes in most cases. It's most likely not bug free and very limited, so please check the resulting patch carefully. Thanks! Michael, on behalf of the Debian GNOME team. [1] http://git.gnome.org/browse/glib/commit/?id=7455dd370eb37ce3b0b409ff6120501f37b50569 [2] http://people.debian.org/~biebl/glib-single-include/rasmol_2.7.5.2-1.log [3] http://people.debian.org/~biebl/fix-glib-includes.sh ---End Message--- ---BeginMessage--- Source: rasmol Source-Version: 2.7.5.2-2 We believe that the bug you reported is fixed in the latest version of rasmol, 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 665...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Teemu Ikonen tpiko...@gmail.com (supplier of updated rasmol 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 May 2013 17:31:54 +0200 Source: rasmol Binary: rasmol rasmol-doc Architecture: source amd64 all Version: 2.7.5.2-2 Distribution: unstable Urgency: low Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Teemu Ikonen tpiko...@gmail.com Description: rasmol - Visualize biological macromolecules rasmol-doc - Documentation for rasmol Closes: 665605 Changes: rasmol (2.7.5.2-2) unstable; urgency=low . [ Andreas Tille ] * renamed debian/upstream-metadata.yaml to debian/upstream * debian/upstream: Added DOI PMID . [ Teemu Ikonen ] * control: - Add build-dep to dpkg-dev (= 1.16.1~) - Update standards-version to 3.9.4 * rules: - Export dpkg-buildflags with all hardening options. - Run xmkmf only twice per build. * Patch imakefile: - Get CFLAGS and LDFLAGS from dpkg-buildflags - Prune LDLIBS to avoid unnecessary dependencies. * New patches: - glibsubheaders: Do not include individual glib headers. Thanks to Michael Biebl for the patch (closes: #665605). - format-security: Fix sprintf calls which fail when compiling with -werror=format-security Checksums-Sha1: 90cb2349668758ccd68bdd10d1fcff1194102d5c 1523 rasmol_2.7.5.2-2.dsc 97e7b73aafc43277213503818b79501091c23698 86861 rasmol_2.7.5.2-2.debian.tar.gz 42758a54ffb518311ad19649ced6500fa2ff 1688046 rasmol_2.7.5.2-2_amd64.deb d5fe43bbaf4b287869b7e8588e5625c1921cd49a 1301228 rasmol-doc_2.7.5.2-2_all.deb Checksums-Sha256: 9c380cf8273671819f6da15fba1a37c8092f3e818c2fa4a8e0a7630dd52b9b9a 1523 rasmol_2.7.5.2-2.dsc 2086b7b34e3b3d36db9dd615f4b68ad294701e2fa39824f99a589b07cdd8450a 86861 rasmol_2.7.5.2-2.debian.tar.gz
Processed: open-vm-tools
Processing commands for cont...@bugs.debian.org: retitle 707208 ftbfs with linux 3.8.11 onwards (fine with 3.8.5) Bug #707208 [open-vm-dkms] ftbfs with linux 3.8 Changed Bug title to 'ftbfs with linux 3.8.11 onwards (fine with 3.8.5)' from 'ftbfs with linux 3.8' close 707208 9.2.3-1031360-3 Bug #707208 [open-vm-dkms] ftbfs with linux 3.8.11 onwards (fine with 3.8.5) There is no source info for the package 'open-vm-dkms' at version '9.2.3-1031360-3' with architecture '' Unable to make a source version for version '9.2.3-1031360-3' Marked as fixed in versions 9.2.3-1031360-3. Bug #707208 [open-vm-dkms] ftbfs with linux 3.8.11 onwards (fine with 3.8.5) Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 707208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707208 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#666820: marked as done (php5: sourceful transition towards Apache 2.4)
Your message dated Fri, 31 May 2013 13:35:48 +0300
with message-id
caesznc4frd4iprvwzx1ugyw3anyjfqvtj1ol6oosxdtx1mq...@mail.gmail.com
and subject line Re: [php-maint] Bug#666820: Apache 2.4 upload date scheduled
for May 30
has caused the Debian Bug report #666820,
regarding php5: sourceful transition towards Apache 2.4
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.)
--
666820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: php5
Severity: important
User: debian-apa...@lists.debian.org
Usertags: apache24transition
Dear maintainer,
your package php5 is provding an Apache2 web server module.
We're upgrading Apache to the new upstream version 2.4 [1] (tracked
as transition bug #661958). This requires all modules to be rebuilt
due to ABI changes. Thus, you need to rebuild and reupload your
Apache2 module package in a version compatible to our new package
available in experimental [2]. Please note it is not enough to
simply rebuild the module - it needs some adaptions in the module
package metadata. We have written packaging guidelines for our
reverse dependencies [3]. Please read it carefully, it should be able
to answer most of your questions. Do also look at dh_apache2
(available through the dh-apache2 package) which can simplify
packaging Apache2 modules. In short, we want to highlight these
changes you need to be aware of.
* APIs changed for some cases [3]. Chances are your module needs some
adaptions, please get in touch with upstream or us if you need help
to port your module to Apache 2.4.
* MPM packages are gone. You cannot depend or conflict with a
particular MPM anymore. If your module does not work with a
particular module, make sure to make it abort with an error if
loaded together with an incompatible MPM. You can use our
apache2-maintscript-helper [4] to switch to the MPM of your choice
in your maintainer scripts.
* Do not build-depend on apache2-threaded-dev or apache2-prefork-dev
anymore. Just like MPMs are gone, are our MPM -dev packages as
well. All modules need to simply build-depend on apache2-dev.
* Do NOT depend on apache2, apache2-common or any other real apache2
package in your binary module package. Depend on our virtual
apache2-api-20120211 package only!
* Do NOT call a2enmod/a2dismod in your maintainer scripts. Use our
apache2-maintscript-helper [3] instead. This is required to get a
uniform and stateful handling of all Apache2 modules.
You can look at our Apache 2.4 packaging hints [5] for hands-on
tutorials. Please note: This bug is filed as important for now. As
the time goes by we plan make it a release critical severity. In the
consequences your module either needs an update or is going to be
removed from Wheezy. For the time being please tag the bug as pending
as soon as you have a package ready. We strongly recommend that at
least maintainers of complex module packages make an upload to
experimental as well. Of course, uploading simple modules to
experimental is welcome, too.
[1] https://lists.debian.org/debian-devel-announce/2012/03/msg00013.html
[2]
http://packages.debian.org/search?keywords=apache2searchon=sourcenamesexact=1suite=allsection=all
[3]
http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next
[4] http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html
[5] http://wiki.debian.org/Apache/PackagingFor24
---End Message---
---BeginMessage---
Version: 5.5.0~rc2+dfsg-1
Relevant changelog entries from experimental:
php5 (5.5.0~rc1-2) experimental; urgency=low
* Load Apache 2.4 maintainer script helper and conditionally define the
conditional function php5_enable if that succeeds (Closes: #707659)
-- Ondřej Surý ond...@debian.org Fri, 10 May 2013 08:21:48 +0200
[...]
php5 (5.5.0~beta4-3) experimental; urgency=low
[Thijs Kinkhorst]
* debian/control: Remove ${apache2:Depends} substvar to allow installing
the modules with Apache 2.4.
-- Ondřej Surý ond...@debian.org Mon, 06 May 2013 19:35:44 +0200
php5 (5.5.0~beta4-2) experimental; urgency=low
* Pull upstream git fixes to have the latest ext/gd tree
* Update patches on top of current php.git
* Update package to use Apache 2.4 (Closes: #666820)
* Update Build-Depends to apache2-dev (= 2.4)
* short_open_tag now defaults to Off (Closes: #142178)
* Add opcache.so to list of forbidden extensions in test run
-- Ondřej Surý ond...@debian.org Mon, 06 May 2013 19:35:25 +0200
Kaplan
On Thu, May 30, 2013 at 10:56 PM, Arno
Processed: Pending fixes for bugs in the libapache-singleton-perl package
Processing commands for cont...@bugs.debian.org: tag 666800 + pending Bug #666800 [libapache-singleton-perl] libapache-singleton-perl: sourceful transition towards Apache 2.4 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 666800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666800 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#666800: Pending fixes for bugs in the libapache-singleton-perl package
tag 666800 + pending thanks Some bugs in the libapache-singleton-perl package are closed in revision 5e473a3c7bcb7925b994ed89ef94b93a2957fc7b in branch 'master' by gregor herrmann The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libapache-singleton-perl.git;a=commitdiff;h=5e473a3 Commit message: Apache 2.4 transition: - build-depend on apache2-dev - add a minimal debian/apache2.conf to get necessary modules for the test suite - use it in debian/rules Closes: #666800 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666799: Apache 2.4 and the other libapache*-perl packages
Now that apache 2.4 and the new mod-perl is in unstable, I looked at the other libapache*-perl packages. They all fail the test suite because they don't find an MPM. I've now started to adapt libapache-singleton-perl, but some review would be welcome before I upload it and work on the other three. 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: Eric Clapton: I Shot The Sheriff signature.asc Description: Digital signature
Processed: Fixed upstream
Processing control commands: tags -1 + fixed-upstream Bug #709492 [src:numdiff] Numdiff doc is non free Added tag(s) fixed-upstream. -- 709492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709492 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#710496: qemu-system-x86: Package cannot be configured when kmod is missing.
31.05.2013 15:22, Hilko Bengen wrote: Package: qemu-system-x86 Severity: serious Um. Curious. Why do you think this bug deserves to be serious? Yes we fail to declare dependency on modprobe|kmod, but any system which runs qemu will, with 99.9% chances, have it installed anyway, so at least for 99.9% cases of users this is not a problem at all.. The init script that is called from postinst tries to load modules via modprobe. This fails if the kmod package is not installed: Setting up qemu-system-x86 (1.5.0+dfsg-2) ... update-alternatives: using /usr/bin/qemu-system-i386 to provide /usr/bin/qemu (q emu) in auto mode /etc/init.d/qemu-system-x86: 31: /etc/init.d/qemu-system-x86: modprobe: not found Module kvm_amd failed to load ... failed! Now, I'm not sure how to solve this, because you have a usage case which is apparently not something I'm familiar with. Do you want us to depend on kmod, or do you think we should check modprobe presence in initscript instead, and omit module loading if modprobe isn't found? Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709492: Fixed upstream
control: tags -1 + fixed-upstream bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710501: avinfo: FTBFS: ass.tab.h:104:5: error: conflicting types for 'yyparse'
Source: avinfo Version: 1.0.a15+20090102-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130529 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -c -Wall -g -O2 -funsigned-char ass.tab.c In file included from ass.y:26:0: ass.tab.h:104:5: error: conflicting types for 'yyparse' In file included from avinfo.h:75:0, from ass.y:24: ass.h:29:5: note: previous declaration of 'yyparse' was here make[2]: *** [ass.tab.o] Error 1 The full build log is available from: http://deiv.vzpla.net/logs/2013/05/29/avinfo_1.0.a15+20090102-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710507: nova-compute-xen: postinst uses /usr/share/doc content (Policy 12.3)
Package: nova-compute-xen Version: 2012.1.1-18 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: Packages must not require the existence of any files in /usr/share/doc/ in order to function. http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3 These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. From the attached log (scroll to the bottom...): Selecting previously unselected package nova-compute-xen. (Reading database ... 17944 files and directories currently installed.) Unpacking nova-compute-xen (from .../nova-compute-xen_2012.1.1-18_all.deb) ... Setting up nova-compute-xen (2012.1.1-18) ... Adding user nova to group nova cp: cannot stat '/usr/share/doc/nova-compute-xen/nova-compute.conf.dist': No such file or directory dpkg: error processing nova-compute-xen (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nova-compute-xen Cheers, Andreas nova-compute-xen_2012.1.1-18.log.gz Description: GNU Zip compressed data
Processed: typo3-dummy: fails to install, probably caused by apache 2.4 transition
Processing control commands: block 661958 with -1 Bug #661958 [release.debian.org] transition: apache2 2.4 661958 was blocked by: 669755 669834 666854 669775 666817 669735 666832 669825 669856 670973 669777 669814 707062 669743 669791 707066 669840 666848 666850 666806 666857 666811 669782 669884 666838 666825 666855 669812 669747 666863 669844 666799 666829 669769 669738 666815 669821 707060 669828 669749 669792 669842 669762 669785 666807 666862 666859 669823 666860 669745 669819 666796 669837 669733 666822 669757 669830 669854 666858 666820 666847 669959 707065 666835 669804 707063 669801 669741 666833 666801 669767 669798 669750 669761 666831 669788 669779 669808 669759 666830 669832 669827 666837 666856 666814 669787 669737 669773 666849 666818 666852 669826 669774 666810 669806 669855 669768 666809 666797 669796 669815 669742 666846 666805 669885 669752 669734 707061 666802 669754 669820 669776 669813 669845 669746 669739 669833 666826 669846 669781 666804 666840 669783 666853 669817 669764 666794 669770 666844 669822 669851 669841 666800 669843 669748 669790 666834 666813 669736 669824 669794 669763 669800 666808 669780 669857 669292 666842 666851 669802 669839 669805 669729 707064 669811 669818 669740 669803 666836 669756 666864 669829 666821 669772 669766 669809 669751 666839 669789 669799 669786 669797 669831 669836 669784 661958 was not blocking any bugs. Added blocking bug(s) of 661958: 710512 -- 661958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661958 710512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710512 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#710512: typo3-dummy: fails to install, probably caused by apache 2.4 transition
Package: typo3-dummy Version: 4.5.27+dfsg1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 661958 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package typo3-dummy. (Reading database ... 18991 files and directories currently installed.) Unpacking typo3-dummy (from .../typo3-dummy_4.5.27+dfsg1-1_all.deb) ... Setting up typo3-dummy (4.5.27+dfsg1-1) ... dbconfig-common: writing config to /etc/dbconfig-common/typo3-dummy.conf Creating config file /etc/dbconfig-common/typo3-dummy.conf with new version Creating config file /etc/typo3-dummy/debian-db.php with new version warning: database package not installed? dbconfig-common: flushing administrative password /var/lib/dpkg/info/typo3-dummy.postinst: line 54: a2ensite: command not found dpkg: error processing typo3-dummy (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: typo3-dummy This is probably caused by the apache 2.4 transition (#661958) cheers, Andreas typo3-dummy_4.5.27+dfsg1-1.log.gz Description: GNU Zip compressed data
Bug#709120: wicd-curses: wicd fails with AttributeError: can't set attribute for self.focus in curses_misc.py L352
Hi, isis agora lovecruft wrote: Package: wicd-curses Version: 1.7.2.4-4 Severity: grave Tags: upstream patch Justification: renders package unusable When attempting to run wicd-curses, I get the following traceback from an unhandled AttributeError: ∃!isisⒶwintermute:~ ∴ wicd-curses Traceback (most recent call last): File /usr/share/wicd/curses/wicd-curses.py, line 1063, in module main() File /usr/share/wicd/curses/wicd-curses.py, line 995, in main ui.run_wrapper(run) File /usr/local/lib/python2.7/dist-packages/urwid/raw_display.py, line 242, in run_wrapper return fn() File /usr/share/wicd/curses/wicd-curses.py, line 88, in wrapper return func(*args, **kargs) File /usr/share/wicd/curses/wicd-curses.py, line 1003, in run app = appGUI() File /usr/share/wicd/curses/wicd-curses.py, line 548, in __init__ self.wiredCB = urwid.Filler(WiredComboBox(wiredL)) File /usr/share/wicd/curses/wicd-curses.py, line 378, in __init__ self.__super.__init__(use_enter=False) File /usr/share/wicd/curses/curses_misc.py, line 352, in __init__ self.focus = focus AttributeError: can't set attribute While I could reproduce this last week on every wicd-curses invocation it now no more happens. Looks to me as if the bug was really in one of wicd-curses' dependencies and has been fixed in the meanwhile. which-pkg-broke wicd-curses (well, yes, it's used as which-pkg-fixed here ;-) reports for dates after the bug report: libselinux1:i386 Tue May 21 01:02:38 2013 libsepol1:i386 Tue May 21 01:02:46 2013 libsemanage-common Tue May 21 01:02:53 2013 libsemanage1:i386 Tue May 21 01:03:05 2013 python2.7 Tue May 21 01:03:35 2013 libpython2.7-stdlibTue May 21 01:03:44 2013 python2.7-minimal Tue May 21 01:03:46 2013 libpython2.7-minimal Tue May 21 01:03:49 2013 libacl1:i386 Tue May 21 15:03:03 2013 libssl1.0.0:i386 Wed May 22 22:22:46 2013 libsqlite3-0:i386 Wed May 22 22:22:50 2013 libnl-3-200:i386 Wed May 22 22:23:07 2013 libnl-genl-3-200:i386 Wed May 22 22:23:07 2013 libgnutls-openssl27:i386 Thu May 23 23:41:04 2013 libgnutls26:i386 Thu May 23 23:41:05 2013 libprocps1:i386Mon May 27 18:12:41 2013 procps Mon May 27 18:14:06 2013 isc-dhcp-clientTue May 28 14:25:10 2013 isc-dhcp-commonTue May 28 14:25:11 2013 python-urwid Thu May 30 01:24:10 2013 gcc-4.8-base:i386 Fri May 31 02:34:54 2013 libgcc1:i386 Fri May 31 02:35:19 2013 Then again, I downgraded python-urwid recently, too, to be able to install sat-xmpp-primitivus from unstable which currently depends on python-urwid's version in testing (likely because sat-xmpp-primitivus was built against that version and then had to wait in NEW for a while). I'll soon check if upgrading python-urwid again to unstable make wicd-curses bail out again. But then again, python-urwid 1.1.1-1 was uploaded one day after this bug report and the original report contained ii python-urwid 1.0.2-1. And all recent python2.7 changes don't sound as if they could cause such an issue. A new upstream version of python-urwid still sounds more realistic somehow. 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#693604: Hello, unfortunately, the avahi packages 0.6.31-2 from wheezy do not solve the problem for me. Still the same symptoms as with 0.6.31-1. Only with the patch applied to 0.6.-31-2, the probl
Bug#693604: Problem still present in wheezy with 0.6.31-2
Hello, (sorry for the mess in the previous message) Unfortunately (unloke for Hagen Fuchs) upgrading all *avahi*-packages to 0.6.31-2 in wheezy did not solve the problem for me. I have still the same symptoms I reported for 0.6.31-1. Only with the patch applied to 0.6-31-2, the problem goes away. Regards, Otmar
Bug#708110: marked as done (xsane: Segfault at startup since update to Jessie)
Your message dated Fri, 31 May 2013 16:43:31 +0100 with message-id 51a8c523.6020...@pblackman.plus.com and subject line Fixed elsewhere has caused the Debian Bug report #708110, regarding xsane: Segfault at startup since update to Jessie 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.) -- 708110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xsane Version: 0.998-4 Severity: grave Justification: renders package unusable Output: dh$listryx$:~ xsane (xsane:20901): GdkPixbuf-WARNING **: Error loading XPM image loader: Le type d'images « xpm » n'est pas pris en charge (xsane:20901): GdkPixbuf-WARNING **: Error loading XPM image loader: Le type d'images « xpm » n'est pas pris en charge (xsane:20901): Gdk-CRITICAL **: IA__gdk_drawable_unref: assertion `GDK_IS_DRAWABLE (drawable)' failed (xsane:20901): Gdk-CRITICAL **: IA__gdk_drawable_unref: assertion `GDK_IS_DRAWABLE (drawable)' failed WARNING: gnome-keyring:: couldn't connect to: /home/dh/.cache/keyring-LX256A/pkcs11: Aucun fichier ou dossier de ce type (xsane:20901): Gdk-CRITICAL **: IA__gdk_drawable_unref: assertion `GDK_IS_DRAWABLE (drawable)' failed (xsane:20901): Gdk-CRITICAL **: IA__gdk_drawable_unref: assertion `GDK_IS_DRAWABLE (drawable)' failed (xsane:20901): GdkPixbuf-WARNING **: Error loading XPM image loader: Le type d'images « xpm » n'est pas pris en charge zsh: segmentation fault xsane I created manually the folder keyring-LX256A with pkcs11 folder or file included, no changes Daniel -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-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 xsane depends on: ii libatk1.0-0 2.8.0-2 ii libc6 2.17-1 ii libcairo2 1.12.14-4 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1.1 ii libgdk-pixbuf2.0-0 2.28.1-1 ii libgimp2.0 2.8.4-1 ii libglib2.0-02.36.1-2build1 ii libgtk2.0-0 2.24.17-2 ii libjpeg88d-1 ii liblcms11.19.dfsg-1.2 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-4 ii libsane 1.0.22-7.4 ii libtiff43.9.6-11 ii xsane-common0.998-4 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages xsane recommends: ii chromium [www-browser] 26.0.1410.43-1 ii cups-client 1.5.3-5 ii iceweasel [www-browser] 17.0.5esr-1 ii links2 [www-browser] 2.7-1 ii w3m [www-browser]0.5.3-8 Versions of packages xsane suggests: ii gimp 2.8.4-1 pn gocr none pn gv none pn hylafax-client | mgetty-fax none -- no debconf information ---End Message--- ---BeginMessage--- Reporter states; Problem solved with latest updates 0.998-4 works fine for me BTW. Never seen this crash. Peter---End Message---
Processed: Re: Bug#666801: libapache2-mod-xsendfile: sourceful transition towards Apache 2.4
Processing control commands: tags -1 patch Bug #666801 [libapache2-mod-xsendfile] libapache2-mod-xsendfile: sourceful transition towards Apache 2.4 Added tag(s) patch. -- 666801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666801 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#666801: libapache2-mod-xsendfile: sourceful transition towards Apache 2.4
Control: tags -1 patch
Hi,
I have prepared a debdiff that implements the necessary
changes to make the package work with Apache 2.4.
Cheers,
Felix
diff -Nru libapache2-mod-xsendfile-0.12/debian/apache2 libapache2-mod-xsendfile-0.12/debian/apache2
--- libapache2-mod-xsendfile-0.12/debian/apache2 1970-01-01 01:00:00.0 +0100
+++ libapache2-mod-xsendfile-0.12/debian/apache2 2013-05-31 08:24:45.0 +0200
@@ -0,0 +1 @@
+mod debian/xsendfile.load
diff -Nru libapache2-mod-xsendfile-0.12/debian/changelog libapache2-mod-xsendfile-0.12/debian/changelog
--- libapache2-mod-xsendfile-0.12/debian/changelog 2011-07-15 20:02:11.0 +0200
+++ libapache2-mod-xsendfile-0.12/debian/changelog 2013-05-31 17:50:10.0 +0200
@@ -1,3 +1,11 @@
+libapache2-mod-xsendfile (0.12-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Transition towards Apache 2.4. (Closes: #666801)
+- Use apache2 dh helper.
+
+ -- Felix Geyer fge...@debian.org Fri, 31 May 2013 08:25:44 +0200
+
libapache2-mod-xsendfile (0.12-1) unstable; urgency=low
* [6537b3a] New upstream version 0.12
diff -Nru libapache2-mod-xsendfile-0.12/debian/control libapache2-mod-xsendfile-0.12/debian/control
--- libapache2-mod-xsendfile-0.12/debian/control 2011-07-15 20:02:11.0 +0200
+++ libapache2-mod-xsendfile-0.12/debian/control 2013-05-31 08:24:20.0 +0200
@@ -1,7 +1,7 @@
Source: libapache2-mod-xsendfile
Priority: extra
Maintainer: Marco Nenciarini mnen...@debian.org
-Build-Depends: debhelper (= 7.0.50~), apache2-threaded-dev (= 2.2.3)
+Build-Depends: debhelper (= 7.0.50~), apache2-dev (= 2.4)
Standards-Version: 3.9.2
Section: web
Vcs-Git: git://anonscm.debian.org/git/collab-maint/libapache2-mod-xsendfile.git
@@ -10,7 +10,7 @@
Package: libapache2-mod-xsendfile
Architecture: any
-Depends: apache2.2-common (= 2.2.3), ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
Description: Serve large static files efficiently from web applications
This package provides the xsendfile module for the Apache 2 webserver.
xsendfile is a small Apache2 module that processes X-SENDFILE header
diff -Nru libapache2-mod-xsendfile-0.12/debian/install libapache2-mod-xsendfile-0.12/debian/install
--- libapache2-mod-xsendfile-0.12/debian/install 2011-07-15 20:02:11.0 +0200
+++ libapache2-mod-xsendfile-0.12/debian/install 2013-05-31 08:24:58.0 +0200
@@ -1,2 +1 @@
.libs/mod_xsendfile.so usr/lib/apache2/modules
-debian/xsendfile.load etc/apache2/mods-available
diff -Nru libapache2-mod-xsendfile-0.12/debian/postinst libapache2-mod-xsendfile-0.12/debian/postinst
--- libapache2-mod-xsendfile-0.12/debian/postinst 2011-07-15 20:02:11.0 +0200
+++ libapache2-mod-xsendfile-0.12/debian/postinst 1970-01-01 01:00:00.0 +0100
@@ -1,19 +0,0 @@
-#!/bin/sh
-
-set -e
-
-case $1 in
-configure)
-a2enmod xsendfile
-;;
-abort-upgrade|abort-remove|abort-deconfigure)
-;;
-*)
-echo postinst called with unknown argument \`$1' 2
-exit 1
-;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff -Nru libapache2-mod-xsendfile-0.12/debian/prerm libapache2-mod-xsendfile-0.12/debian/prerm
--- libapache2-mod-xsendfile-0.12/debian/prerm 2011-07-15 20:02:11.0 +0200
+++ libapache2-mod-xsendfile-0.12/debian/prerm 1970-01-01 01:00:00.0 +0100
@@ -1,21 +0,0 @@
-#!/bin/sh
-
-set -e
-
-case $1 in
-remove|purge)
-if which a2dismod /dev/null 21; then
-a2dismod xsendfile || true
-fi
-;;
-upgrade|deconfigure|failed-upgrade)
-;;
-*)
-echo prerm called with unknown argument \`$1' 2
-exit 1
-;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff -Nru libapache2-mod-xsendfile-0.12/debian/rules libapache2-mod-xsendfile-0.12/debian/rules
--- libapache2-mod-xsendfile-0.12/debian/rules 2011-07-15 20:02:11.0 +0200
+++ libapache2-mod-xsendfile-0.12/debian/rules 2013-05-31 08:28:18.0 +0200
@@ -5,7 +5,7 @@
#export DH_VERBOSE=1
%:
- dh $@
+ dh $@ --with apache2
override_dh_auto_build:
apxs2 -c mod_xsendfile.c
Bug#666832: marked as done (gridsite: sourceful transition towards Apache 2.4)
Your message dated Fri, 31 May 2013 16:18:12 + with message-id e1uis1s-0003rl...@franck.debian.org and subject line Bug#666832: fixed in gridsite 1.7.21-2 has caused the Debian Bug report #666832, regarding gridsite: sourceful transition towards Apache 2.4 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.) -- 666832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gridsite Severity: important User: debian-apa...@lists.debian.org Usertags: apache24transition Dear maintainer, your package gridsite is provding an Apache2 web server module. We're upgrading Apache to the new upstream version 2.4 [1] (tracked as transition bug #661958). This requires all modules to be rebuilt due to ABI changes. Thus, you need to rebuild and reupload your Apache2 module package in a version compatible to our new package available in experimental [2]. Please note it is not enough to simply rebuild the module - it needs some adaptions in the module package metadata. We have written packaging guidelines for our reverse dependencies [3]. Please read it carefully, it should be able to answer most of your questions. Do also look at dh_apache2 (available through the dh-apache2 package) which can simplify packaging Apache2 modules. In short, we want to highlight these changes you need to be aware of. * APIs changed for some cases [3]. Chances are your module needs some adaptions, please get in touch with upstream or us if you need help to port your module to Apache 2.4. * MPM packages are gone. You cannot depend or conflict with a particular MPM anymore. If your module does not work with a particular module, make sure to make it abort with an error if loaded together with an incompatible MPM. You can use our apache2-maintscript-helper [4] to switch to the MPM of your choice in your maintainer scripts. * Do not build-depend on apache2-threaded-dev or apache2-prefork-dev anymore. Just like MPMs are gone, are our MPM -dev packages as well. All modules need to simply build-depend on apache2-dev. * Do NOT depend on apache2, apache2-common or any other real apache2 package in your binary module package. Depend on our virtual apache2-api-20120211 package only! * Do NOT call a2enmod/a2dismod in your maintainer scripts. Use our apache2-maintscript-helper [3] instead. This is required to get a uniform and stateful handling of all Apache2 modules. You can look at our Apache 2.4 packaging hints [5] for hands-on tutorials. Please note: This bug is filed as important for now. As the time goes by we plan make it a release critical severity. In the consequences your module either needs an update or is going to be removed from Wheezy. For the time being please tag the bug as pending as soon as you have a package ready. We strongly recommend that at least maintainers of complex module packages make an upload to experimental as well. Of course, uploading simple modules to experimental is welcome, too. [1] https://lists.debian.org/debian-devel-announce/2012/03/msg00013.html [2] http://packages.debian.org/search?keywords=apache2searchon=sourcenamesexact=1suite=allsection=all [3] http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next [4] http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html [5] http://wiki.debian.org/Apache/PackagingFor24 ---End Message--- ---BeginMessage--- Source: gridsite Source-Version: 1.7.21-2 We believe that the bug you reported is fixed in the latest version of gridsite, 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 666...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattias Ellert mattias.ell...@fysast.uu.se (supplier of updated gridsite 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: Fri, 31 May 2013 13:59:38 +0200 Source: gridsite Binary: gridsite libgridsite1.7 gridsite-clients gridsite-gsexec libgridsite-dev gridsite-doc gridsite-dbg Architecture: source all amd64 Version: 1.7.21-2 Distribution: unstable Urgency: low Maintainer: Mattias Ellert
Processed: Re: Bug#666801: libapache2-mod-xsendfile: sourceful transition towards Apache 2.4
Processing commands for cont...@bugs.debian.org: tags 666801 + pending Bug #666801 [libapache2-mod-xsendfile] libapache2-mod-xsendfile: sourceful transition towards Apache 2.4 Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 666801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666801 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#635317: make 3.82 breaks kernel module build: 'mixed implicit and normal rules' in linux-headers-*
Hi guys, On Sun, Mar 04, 2012 at 02:28:48AM +, Ben Hutchings wrote: The Linux kernel build rules were fixed in Linux 2.6.36 and 2.6.32.21. So this would only affect rebuilding the kernel in oldstable, and mixing oldstable with unstable is not supported anyway. However, I would guess there are many other makefiles which can be broken by the stricter behaviour of make. So I think that make 3.82 will have to wait until after wheezy. But if someone can do an archive-wide rebuild with the new version now, that would allow maintainers to start preparing. Any news regards this? I'd love to have make 3.82, it fixes a few issues that I'm having, but nvidia-kernel-dkms prevent me from upgrading. :-( Thanks! -- Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709170: marked as done (operation error (socket sslerror during connect ([Errno 1] _ssl.c:504: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure)))
Your message dated Fri, 31 May 2013 16:48:15 + with message-id e1uisux-0002gx...@franck.debian.org and subject line Bug#709170: fixed in getmail4 4.40.3-3 has caused the Debian Bug report #709170, regarding operation error (socket sslerror during connect ([Errno 1] _ssl.c:504: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake 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.) -- 709170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: getmail4 Version: 4.40.3-2 Severity: important $ setlock -n /tmp/getmail.lock getmail getmail version 4.40.3 Copyright (C) 1998-2012 Charles Cazabon. Licensed under the GNU GPL version 2. SimpleIMAPSSLRetriever:jidan...@m.jidanni.org:993: getmailrc: operation error (socket sslerror during connect ([Errno 1] _ssl.c:504: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure)) 0 messages (0 bytes) retrieved, 0 skipped ---End Message--- ---BeginMessage--- Source: getmail4 Source-Version: 4.40.3-3 We believe that the bug you reported is fixed in the latest version of getmail4, 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 709...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Osamu Aoki os...@debian.org (supplier of updated getmail4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 01 Jun 2013 00:43:40 +0900 Source: getmail4 Binary: getmail4 Architecture: source all Version: 4.40.3-3 Distribution: unstable Urgency: low Maintainer: Osamu Aoki os...@debian.org Changed-By: Osamu Aoki os...@debian.org Description: getmail4 - mail retriever with support for POP3, IMAP4 and SDPS Closes: 709170 Changes: getmail4 (4.40.3-3) unstable; urgency=low . * Remove Fredrik Steen from uploader. * Revert Microsoft Exchange Server 2003 patch. Closes: #709170 Checksums-Sha1: 4092c2627042bebca87177ab150071709c8c9229 1229 getmail4_4.40.3-3.dsc bac356d5c99155004be828a6a2ee8fd21dcc7c9a 8138 getmail4_4.40.3-3.debian.tar.gz e1e632650c0b1e32772ebd0c7aea9ab8dac8affb 189798 getmail4_4.40.3-3_all.deb Checksums-Sha256: 05708406443862af2725042bf2a7389210705c32692b3976f07f5d363fd9466f 1229 getmail4_4.40.3-3.dsc cba7776d7bd03314cd1b8b863ffc0c6924881fcdea2f72d28e2881bf0a47356b 8138 getmail4_4.40.3-3.debian.tar.gz 2440fbefec03cbf01c044d29487d3c7a230199fccc9fb50019ecac720c551ae4 189798 getmail4_4.40.3-3_all.deb Files: d60c3d50f462c1264b240ca1ce32af7c 1229 mail optional getmail4_4.40.3-3.dsc 1fd4d1a541c9467e3659f07b7bb1969c 8138 mail optional getmail4_4.40.3-3.debian.tar.gz dfa1f0543f970c6669dcddffaf5fc1c0 189798 mail optional getmail4_4.40.3-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlGozYAACgkQ6A/EwagGHzIe/gCfRvk8ANs/rEo7tZ1pexBv7JOx P8EAn06WEvJqImLhCmvBIy5QrOQrWvG1 =ugCq -END PGP SIGNATUREEnd Message---
Processed (with 1 errors): Re: Bug#710474: libunibreak-dev and liblinebreak2-dev: error when trying to install together
Processing control commands: -1 + confirmed Unknown command or malformed arguments to command. reassign -1 libunibreak-dev Bug #710474 [liblinebreak2-dev,libunibreak-dev] libunibreak-dev and liblinebreak2-dev: error when trying to install together Bug reassigned from package 'liblinebreak2-dev,libunibreak-dev' to 'libunibreak-dev'. Ignoring request to alter found versions of bug #710474 to the same values previously set Ignoring request to alter fixed versions of bug #710474 to the same values previously set -- 710474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710474 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#710474: libunibreak-dev and liblinebreak2-dev: error when trying to install together
Control: -1 + confirmed Control: reassign -1 libunibreak-dev 2013-05-31 08:50, Ralf Treinen: Package: liblinebreak2-dev,libunibreak-dev Version: liblinebreak2-dev/2.1-1 Version: libunibreak-dev/1.0-1 [...] 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/linebreak.h /usr/include/linebreakdef.h [...] Note for bug squashers: liblinebreak (libunibreak's predecessor) will be removed from the archive from jessie once its reverse dependency fbreader is rebuilt against libunibreak; libunibreak will be fixed to include the needed Conflicts. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++ GNU/Linux userspace developer, Debian Developer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to libunibreak, tagging 710474
Processing commands for cont...@bugs.debian.org:
#libunibreak (1.0-2~) UNRELEASED; urgency=low
#
# * debian/control:
#- Added missing conflicts with liblinebreak{,2}-dev. (Closes: #710474)
#
limit source libunibreak
Limiting to bugs with field 'source' containing at least one of 'libunibreak'
Limit currently set to 'source':'libunibreak'
tags 710474 + pending
Bug #710474 [libunibreak-dev] libunibreak-dev and liblinebreak2-dev: error when
trying to install together
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
710474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710474
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#709921: im-config: cannot detect IM module files correctly
On Wed, May 29, 2013 at 8:47 PM, Osamu Aoki os...@debian.org wrote: I uploaded one for unstable. Please check what I am doing is right. If it is good, I will backport this. Osamu Seems GTK_IM_MODULE still show up as xim, and QT4_IM_MODULE is correct. But I don't know what's wrong with GTK. I tried to add some echo to 22_fcitx.rc and it shows that the two `ls` command returns nothing to the variable, while it works for Qt... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710496: qemu-system-x86: Package cannot be configured when kmod is missing.
* Michael Tokarev: Do you want us to depend on kmod, or do you think we should check modprobe presence in initscript instead, and omit module loading if modprobe isn't found? I just retried after installing kmod (but no kernel) to the chroot. Setting up qemu-system-x86 (1.5.0+dfsg-2) ... update-alternatives: using /usr/bin/qemu-system-i386 to provide /usr/bin/qemu (qemu) in auto mode libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/3.8-1-amd64/modules.dep.bin' Module kvm_amd failed to load ... failed! invoke-rc.d: initscript qemu-system-x86, action start failed. dpkg: error processing qemu-system-x86 (--configure): subprocess installed post-installation script returned error exit status 1 I don't quite see what benefits exiting from the init script with exit code 1 has. Changing that to log_failure_msg Module $module failed to load exit 0 would still produce the error message and allow the package to be configured. The bug may not be as severe as I originally thought: Apparently, I had set up my sid-i386 chroot differently from the sid-amd64 chroot (on which everything builds just fine): My sid-i386 chroot lacked a /usr/sbin/policy-rc.d script that prevents init scripts from being run. I think that it would still be a good idea if this issue was fixed. One wouldn't want the package installation to fail if the user uses his own kernel without KVM support. After all, qemu-system still has support for TCG, doesn't it? Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710540: php5-apcu: fails to install: ERROR: /etc/php5/mods-available/apc.ini does not exist
Package: php5-apcu Version: 4.0.1-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...): Selecting previously unselected package php5-apcu. (Reading database ... 8470 files and directories currently installed.) Unpacking php5-apcu (from .../php5-apcu_4.0.1-1_amd64.deb) ... Setting up php5-apcu (4.0.1-1) ... ERROR: /etc/php5/mods-available/apc.ini does not exist dpkg: error processing php5-apcu (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: php5-apcu cheers, Andreas php5-apcu_4.0.1-1.log.gz Description: GNU Zip compressed data
Bug#710543: libzeep: FTBFS on s390: call of overloaded 'object(size_t)' is ambiguous
Source: libzeep
Version: 3.0.0-1
Severity: serious
Justification: fails to build from source
The s390 build of libzeep failed with
src/webapp-el.cpp: In member function 'zeep::http::el::object
zeep::http::el::interpreter::parse_primary_expr()':
src/webapp-el.cpp:1550:37: error: call of overloaded 'object(size_t)' is
ambiguous
src/webapp-el.cpp:1550:37: note: candidates are:
src/webapp-el.cpp:585:1: note: zeep::http::el::object::object(const string)
near match
src/webapp-el.cpp:585:1: note: no known conversion for argument 1 from
'size_t {aka long unsigned int}' to 'const string {aka const
std::basic_stringchar}'
src/webapp-el.cpp:578:1: note: zeep::http::el::object::object(const char*)
near match
src/webapp-el.cpp:578:1: note: no known conversion for argument 1 from
'size_t {aka long unsigned int}' to 'const char*'
src/webapp-el.cpp:573:1: note: zeep::http::el::object::object(double)
src/webapp-el.cpp:568:1: note: zeep::http::el::object::object(float)
src/webapp-el.cpp:563:1: note: zeep::http::el::object::object(uint64)
src/webapp-el.cpp:558:1: note: zeep::http::el::object::object(int64)
src/webapp-el.cpp:553:1: note: zeep::http::el::object::object(uint32)
src/webapp-el.cpp:548:1: note: zeep::http::el::object::object(int32)
src/webapp-el.cpp:543:1: note: zeep::http::el::object::object(uint16)
src/webapp-el.cpp:538:1: note: zeep::http::el::object::object(int16)
src/webapp-el.cpp:533:1: note: zeep::http::el::object::object(uint8)
src/webapp-el.cpp:528:1: note: zeep::http::el::object::object(int8)
src/webapp-el.cpp:522:1: note: zeep::http::el::object::object(bool)
src/webapp-el.cpp:478:1: note:
zeep::http::el::object::object(zeep::http::el::detail::object_impl*) near
match
src/webapp-el.cpp:478:1: note: no known conversion for argument 1 from
'size_t {aka long unsigned int}' to 'zeep::http::el::detail::object_impl*'
src/webapp-el.cpp:483:1: note: zeep::http::el::object::object(const
zeep::http::el::object)
make[2]: *** [obj/webapp-el.o] Error 1
It seems that s390 is one of those 32-bit architectures on which size_t
is formally unsigned long whereas uint32 is formally unsigned int; even
though both types are equivalent in practice, the compiler insists on
treating them as distinct, leading to that error. To compensate, I'd
suggest casting result.count() to uint64 on line 1550; all the variants
of object's constructor that take integral types ultimately widen them
to 64 bits anyway.
Could you please take a look?
Thanks!
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710545: libguestfs: FTBFS on i386 - needs qemu-system-i486, vs. -i386
Source: libguestfs Version: 1:1.20.7-2 Severity: serious Justification: fails to build from source (but built successfully in the past) The i386 build of libguestfs failed with configure: error: qemu must be installed checking for qemu-system-i486... no because qemu-system-x86 just supplies qemu-system-i386 (and -x86_64), not -i486. Could you please arrange to specify the correct executable name? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710545: libguestfs: FTBFS on i386 - needs qemu-system-i486, vs. -i386
fixed 710545 1.20.7-3 thank you * Aaron M. Ucko: The i386 build of libguestfs failed with configure: error: qemu must be installed checking for qemu-system-i486... no I just uploaded a fixed version. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#710545: libguestfs: FTBFS on i386 - needs qemu-system-i486, vs. -i386
Processing commands for cont...@bugs.debian.org: fixed 710545 1.20.7-3 Bug #710545 [src:libguestfs] libguestfs: FTBFS on i386 - needs qemu-system-i486, vs. -i386 The source 'libguestfs' and version '1.20.7-3' do not appear to match any binary packages Marked as fixed in versions libguestfs/1.20.7-3. thank you Stopping processing here. Please contact me if you need assistance. -- 710545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#710093: postgresql: not started automatically after installation in chroot
Processing control commands: tags -1 - moreinfo Bug #710093 [postgresql] postgresql: not started automatically after installation in chroot Removed tag(s) moreinfo. severity -1 serious Bug #710093 [postgresql] postgresql: not started automatically after installation in chroot Severity set to 'serious' from 'important' -- 710093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710093 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#710540: marked as done (php5-apcu: fails to install: ERROR: /etc/php5/mods-available/apc.ini does not exist)
Your message dated Fri, 31 May 2013 21:23:33 + with message-id e1uiwnn-00046f...@franck.debian.org and subject line Bug#710540: fixed in php-apcu 4.0.1-2 has caused the Debian Bug report #710540, regarding php5-apcu: fails to install: ERROR: /etc/php5/mods-available/apc.ini does not exist 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.) -- 710540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: php5-apcu Version: 4.0.1-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...): Selecting previously unselected package php5-apcu. (Reading database ... 8470 files and directories currently installed.) Unpacking php5-apcu (from .../php5-apcu_4.0.1-1_amd64.deb) ... Setting up php5-apcu (4.0.1-1) ... ERROR: /etc/php5/mods-available/apc.ini does not exist dpkg: error processing php5-apcu (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: php5-apcu cheers, Andreas php5-apcu_4.0.1-1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: php-apcu Source-Version: 4.0.1-2 We believe that the bug you reported is fixed in the latest version of php-apcu, 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 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý ond...@debian.org (supplier of updated php-apcu 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: Fri, 31 May 2013 21:12:45 +0200 Source: php-apcu Binary: php5-apcu php-apc Architecture: source amd64 all Version: 4.0.1-2 Distribution: experimental Urgency: low Maintainer: Debian PHP Maintainers pkg-php-ma...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: php-apc- APC User Cache for PHP 5 (transitional package) php5-apcu - APC User Cache for PHP 5 Closes: 710540 Changes: php-apcu (4.0.1-2) experimental; urgency=low . * Fix typo in php5enmod apc - apcu (Closes: #710540) Checksums-Sha1: 29e182e435391e0cbce575420d44fe5182f23268 1361 php-apcu_4.0.1-2.dsc e2dd2d18807f675175125487df58eb2075c7706e 5673 php-apcu_4.0.1-2.debian.tar.gz ca9c883b0f421b67c3bf952d488c8641be696f73 58192 php5-apcu_4.0.1-2_amd64.deb d5477379ce4e8959fd38a65844304a2a4b3f2fe8 902 php-apc_4.0.1-2_all.deb Checksums-Sha256: c07749204712df854bef575f52c8c83a4591ad4d52945a71d866ee16a4e0725f 1361 php-apcu_4.0.1-2.dsc 19346529cef7e3c4a532df2dbdafeb969e26ec7be806c31d1911f4f645e4a4ac 5673 php-apcu_4.0.1-2.debian.tar.gz e7339617c507034361ba32ab5c21e5cb276fa949c003bdb8242a2166a5f2f7d0 58192 php5-apcu_4.0.1-2_amd64.deb e4580815a83c9431baad65b611a8bddc12257d85a0ceea6039c0196665d6d63d 902 php-apc_4.0.1-2_all.deb Files: 0dbd01fecd671b69ac674b06deefa10e 1361 php optional php-apcu_4.0.1-2.dsc a35d4c0812e21a3f4262218e4753c37e 5673 php optional php-apcu_4.0.1-2.debian.tar.gz 66af3f4489c87cbcb2bab244cbce301e 58192 php optional php5-apcu_4.0.1-2_amd64.deb 3dbff4ccb8f817063f9e53940ffa88c3 902 oldlibs extra php-apc_4.0.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlGo/s8ACgkQ9OZqfMIN8nMbYgCfQcJlEfVcYzrbE01OW8HHImvS PgUAnR8VbTTxuNarIHvSfn9Q3eJ+JDu+ =Cpfh -END PGP SIGNATUREEnd Message---
Bug#710566: libjpeg-turbo: FTBFS on Hurd and kFreeBSD: missing nasm or yasm
Source: libjpeg-turbo
Version: 1.2.90-2
Severity: serious
Justification: fails to build from source
Builds of libjpeg-turbo on kFreeBSD and the Hurd in minimal
environments (as on the autobuilders) have been failing:
checking if we have SIMD optimisations for cpu type... yes (i386)
checking for nasm... no
checking for nasmw... no
checking for yasm... no
dh_auto_configure: ./configure --build=i486-gnu --prefix=/usr
--includedir=${prefix}/include --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--libdir=${prefix}/lib/i386-gnu --libexecdir=${prefix}/lib/i386-gnu
--disable-maintainer-mode --disable-dependency-tracking returned exit code 1
make: *** [build-arch] Error 255
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
It looks like upstream's configure script checks for an assembler on
any x86 architecture, whereas the Debian packaging declares a build
dependency only on x86 *Linux*. Could you please adjust it to read
nasm [any-amd64 any-i386]?
Thanks!
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710568: libkolabxml: FTBFS on powerpc: corrupt php_kolabformat.h (race?)
Source: libkolabxml Version: 0.8.4-3 Severity: serious Justification: fails to build from source libkolabxml failed to build on powerpc with errors suggesting a race between generating and using php_kolabformat.h: /«PKGBUILDDIR»/obj-powerpc-linux-gnu/src/php/php_kolabformat.h:186:5: warning: null character(s) ignored [enabled by default] [...] /«PKGBUILDDIR»/obj-powerpc-linux-gnu/src/php/php_kolabformat.h:186:1: error: 'ZEND' does not name a type I see you're using parallel make (-j6) here; turning it off might help. Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
Hi, On Sat, Jun 01, 2013 at 01:21:57AM +0800, Aron Xu wrote: On Wed, May 29, 2013 at 8:47 PM, Osamu Aoki os...@debian.org wrote: I uploaded one for unstable. Please check what I am doing is right. If it is good, I will backport this. Osamu Seems GTK_IM_MODULE still show up as xim, and QT4_IM_MODULE is correct. But I don't know what's wrong with GTK. I tried to add some echo to 22_fcitx.rc and it shows that the two `ls` command returns nothing to the variable, while it works for Qt... Please run im-config with -d) # debug trace mode :-) undocumented. IM_CONFIG_SETMODE=-x set $IM_CONFIG_SETMODE and send us the log. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707226: marked as done (package wine does not insall wine on amd64)
Your message dated Fri, 31 May 2013 19:25:58 -0400 with message-id CANTw=mmi37pvd_9feoj2ezwb+onejt8nwuvcmklostybeok...@mail.gmail.com and subject line Re: [pkg-wine-party] Bug#707226: package wine does not insall wine on amd64 has caused the Debian Bug report #707226, regarding package wine does not insall wine on amd64 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.) -- 707226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wine Severity: grave On a freshly installed Debian stable (wheezy) on amd64, installing a frontend like q4wine and wine seems to succeed, but running it produces strange errors. The reason: Actually, no wine binaries or libs were installed. Please add some debconf script to the wine-bin:amd64 package that does actually pull in wine-bin:i386 package. If i386 is not enabled, these are the steps such a script needs to perform: dpkg --add-architecture i386 apt-get update apt-get install wine-bin:i386 ---End Message--- ---BeginMessage--- On Wed, May 8, 2013 at 7:01 AM, wrote: Package: wine Severity: grave On a freshly installed Debian stable (wheezy) on amd64, installing a frontend like q4wine and wine seems to succeed, but running it produces strange errors. The reason: Actually, no wine binaries or libs were installed. Please add some debconf script to the wine-bin:amd64 package that does actually pull in wine-bin:i386 package. If i386 is not enabled, these are the steps such a script needs to perform: dpkg --add-architecture i386 apt-get update apt-get install wine-bin:i386 If you install the wine package instead of wine-bin, you will get the wine64-bin package, which will present the above helpful info to the user. Best wishes, Mike---End Message---
Processed: limit source to libapache-authenhook-perl, tagging 666807
Processing commands for cont...@bugs.debian.org: #libapache-authenhook-perl (2.00-04+pristine-5) UNRELEASED; urgency=low # # * Apache 2.4: #- debian/control: build-depend on apache2-dev #- add debian/apache2.conf and use it in debian/rules for the test suite #- add a patch to set DefaultRuntimeDir for the tests. Otherwise mod_digest # tries to write to /var/run and fails #Closes: #666807 # limit source libapache-authenhook-perl Limiting to bugs with field 'source' containing at least one of 'libapache-authenhook-perl' Limit currently set to 'source':'libapache-authenhook-perl' tags 666807 + pending Bug #666807 [libapache-authenhook-perl] libapache-authenhook-perl: sourceful transition towards Apache 2.4 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 666807: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666807 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#710566: marked as done (libjpeg-turbo: FTBFS on Hurd and kFreeBSD: missing nasm or yasm)
Your message dated Fri, 31 May 2013 23:48:23 +
with message-id e1uiz3x-0001ag...@franck.debian.org
and subject line Bug#710566: fixed in libjpeg-turbo 1.3.0-1
has caused the Debian Bug report #710566,
regarding libjpeg-turbo: FTBFS on Hurd and kFreeBSD: missing nasm or yasm
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.)
--
710566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libjpeg-turbo
Version: 1.2.90-2
Severity: serious
Justification: fails to build from source
Builds of libjpeg-turbo on kFreeBSD and the Hurd in minimal
environments (as on the autobuilders) have been failing:
checking if we have SIMD optimisations for cpu type... yes (i386)
checking for nasm... no
checking for nasmw... no
checking for yasm... no
dh_auto_configure: ./configure --build=i486-gnu --prefix=/usr
--includedir=${prefix}/include --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--libdir=${prefix}/lib/i386-gnu --libexecdir=${prefix}/lib/i386-gnu
--disable-maintainer-mode --disable-dependency-tracking returned exit code 1
make: *** [build-arch] Error 255
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
It looks like upstream's configure script checks for an assembler on
any x86 architecture, whereas the Debian packaging declares a build
dependency only on x86 *Linux*. Could you please adjust it to read
nasm [any-amd64 any-i386]?
Thanks!
---End Message---
---BeginMessage---
Source: libjpeg-turbo
Source-Version: 1.3.0-1
We believe that the bug you reported is fixed in the latest version of
libjpeg-turbo, 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 710...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel sunwea...@debian.org (supplier of updated libjpeg-turbo package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 01 Jun 2013 01:25:00 +0200
Source: libjpeg-turbo
Binary: libturbojpeg1 libturbojpeg1-dev libjpeg-turbo-test
Architecture: source amd64
Version: 1.3.0-1
Distribution: sid
Urgency: low
Maintainer: Debian TigerVNC Packaging Team
pkg-tigervnc-de...@lists.alioth.debian.org
Changed-By: Mike Gabriel sunwea...@debian.org
Description:
libjpeg-turbo-test - Program for testing libjpeg-turbo
libturbojpeg1 - TurboJPEG runtime library - SIMD optimized
libturbojpeg1-dev - Development files for the turbo JPEG library
Closes: 710566
Changes:
libjpeg-turbo (1.3.0-1) unstable; urgency=low
.
* New upstream release.
* /debian/control:
+ B-D: nasm [any-amd64 any-i386]. Fix FTBFS on hurd and kFreeBSD. (Closes:
#710566).
* Lintian issues:
+ Adapt shlib-calls-exit lintian override to new upstream version.
Checksums-Sha1:
c3d1729417bcf6a91913dd69509b3acc3a8b956e 2218 libjpeg-turbo_1.3.0-1.dsc
1792c964b35604cebd3a8846f1ca6de5976e9c28 1361603
libjpeg-turbo_1.3.0.orig.tar.gz
57c4fcf2f2de4b1d6f15a90695c7a4c6d19680ca 8621
libjpeg-turbo_1.3.0-1.debian.tar.gz
6c911eebf83bf7680d480b2403240027c6a10694 175780 libturbojpeg1_1.3.0-1_amd64.deb
35578a143959fb268315a34c0d1c7c06686f0b39 178930
libturbojpeg1-dev_1.3.0-1_amd64.deb
20357b573e4fb9dc72f17687922a6a9dfb8faeac 23796
libjpeg-turbo-test_1.3.0-1_amd64.deb
Checksums-Sha256:
351c7c4f3645992c49a49fb6ddec1aedf4da40d5c09302801f8f196342a826e5 2218
libjpeg-turbo_1.3.0-1.dsc
2657008cfc08aadbaca065bd9f8964b8a2c0abd03e73da5b5f09c1216be31234 1361603
libjpeg-turbo_1.3.0.orig.tar.gz
0da83217678aad2981f98860ebf10dd2744987b8521962bbac524c8e60f7dbff 8621
libjpeg-turbo_1.3.0-1.debian.tar.gz
43350e5394f6aaab3f7a1c371299a82949a71cbadb8bbb5f290181c3bde901b0 175780
libturbojpeg1_1.3.0-1_amd64.deb
b1ba139e683358aaf3199b735e82c3ab26f139b732537fdbc6ceadcc318ec374 178930
libturbojpeg1-dev_1.3.0-1_amd64.deb
2c11826cdd05cfe5c324aee2e0b42af0de7f6361405a56fe922b82412702df84 23796
libjpeg-turbo-test_1.3.0-1_amd64.deb
Files:
7eaf08e22664d74a963de522ab9fe0b7 2218 graphics optional
libjpeg-turbo_1.3.0-1.dsc
e1e65cc711a1ade1322c06ad4a647741 1361603 graphics optional
Processed: limit source to libapache2-reload-perl, tagging 666799
Processing commands for cont...@bugs.debian.org: #libapache2-reload-perl (0.12-2) UNRELEASED; urgency=low # # * Apache 2.4: #- debian/control: build-depend on apache2-dev #- add a minimal debian/apache2.conf and use it in debian/rules for the #test suite #Closes: #666799 # limit source libapache2-reload-perl Limiting to bugs with field 'source' containing at least one of 'libapache2-reload-perl' Limit currently set to 'source':'libapache2-reload-perl' tags 666799 + pending Bug #666799 [libapache2-reload-perl] libapache2-reload-perl: sourceful transition towards Apache 2.4 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 666799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666799 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#710576: python-heatclient: fails to build from source without internet access
Package: python-heatclient Version: 0.2.2-1 Severity: serious Justification: fails to build from source User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu saucy python-heatclient 0.2.2-1 fails to build from source in a clean chroot without internet access. Download error on http://pypi.python.org/simple/setuptools-git/: [Errno 110] Connection timed out -- Some packages may not be found! Download error on http://pypi.python.org/simple/setuptools-git/: [Errno 110] Connection timed out -- Some packages may not be found! Couldn't find index page for 'setuptools-git' (maybe misspelled?) Download error on http://pypi.python.org/simple/: [Errno 110] Connection timed out -- Some packages may not be found! No local packages or download links found for setuptools-git=0.4 Thanks, Jeremy - -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'raring'), (100, 'saucy-backports') python-heatclient_0.2.2-1_amd64-20130531-1953.build Description: Binary data
Bug#701439: marked as done (ircd-hybrid: ftbfs with eglibc-2.17)
Your message dated Sat, 01 Jun 2013 00:18:00 + with message-id e1uizwc-0001q7...@franck.debian.org and subject line Bug#701439: fixed in ircd-hybrid 1:8.0.9.dfsg.1-2 has caused the Debian Bug report #701439, regarding ircd-hybrid: ftbfs with eglibc-2.17 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.) -- 701439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:ircd-hybrid Version: 1:7.2.2.dfsg.2-10 Severity: important Tags: sid jessie User: debian-gl...@lists.debian.org Usertags: ftbfs-glibc-2.17 The package fails to build in a test rebuild on at least amd64 with eglibc-2.17, but succeeds to build with eglibc-2.13. The severity of this report may be raised before the jessie release. The test rebuild was done together with GCC-4.8, so some issues might be caused by the updated GCC as well. s_bsd_sigio.c:220:18: error: storage size of 'si' isn't known The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/ircd-hybrid_7.2.2.dfsg.2-10_unstable_gcc48.log The last lines of the build log are at the end of this report. To install eglibc from experimental, apt-get -t experimental install libc6-dev To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev [...] gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c parse.c parse.c: In function 'parse': parse.c:189:7: warning: variable 'mpara' set but not used [-Wunused-but-set-variable] int mpara = 0; ^ parse.c:188:7: warning: variable 'paramcount' set but not used [-Wunused-but-set-variable] int paramcount; ^ gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c restart.c gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c resv.c gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c s_auth.c gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c s_bsd.c gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c s_conf.c gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c s_gline.c gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c s_log.c s_log.c: In function 'log_user_exit': s_log.c:248:6: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 10 has type 'uint64_t' [-Wformat=] source_p-localClient-recv.bytes10); ^ s_log.c:248:6: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 11 has type 'uint64_t' [-Wformat=] gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c s_misc.c gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c s_serv.c gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c s_stats.c gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c s_user.c s_user.c: In function 'change_simple_umode': s_user.c:862:18: warning: variable 'client_p' set but not used [-Wunused-but-set-variable] struct Client *client_p; ^ gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c send.c gcc -I../include -I/usr/include/pcre -D_FORTIFY_SOURCE=2 -Wall -O2 -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
Bug#666799: Apache 2.4 and the other libapache*-perl packages
On Fri, 31 May 2013 13:38:50 +0200, gregor herrmann wrote: Now that apache 2.4 and the new mod-perl is in unstable, I looked at the other libapache*-perl packages. They all fail the test suite because they don't find an MPM. I've now started to adapt libapache-singleton-perl, but some review would be welcome before I upload it and work on the other three. Update: I've now also looked at the 3 other packages. Status: - libapache-singleton-perl, libapache-authenhook-perl, libapache2-reload-perl build, reviews/tests still welcome - libapache2-authcookie-perl explodes in the test suite, and I have no idea how to fix it (and if the problem is somewhere between tests and packaging or if we have a more fundamental problem re. apache auth* changes in general) 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: Joint Venture: Der Jesus von Oberpleis signature.asc Description: Digital signature
Processed: severity of 707960 is serious
Processing commands for cont...@bugs.debian.org: severity 707960 serious Bug #707960 [nfs-common] rpc.gssd segfaults when mounting a nfsv4 volume Bug #705507 [nfs-common] nfs-common: rpc.gssd crashes when performing nfs4 mount Bug #709525 [nfs-common] nfs-common: After upgrade to 1.2.8-2, rpc.gssd segfaults on startup Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 705507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705507 707960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707960 709525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709525 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#707960: marked as done (rpc.gssd segfaults when mounting a nfsv4 volume)
Your message dated Sat, 01 Jun 2013 01:18:00 + with message-id e1uiasg-00016h...@franck.debian.org and subject line Bug#707960: fixed in nfs-utils 1:1.2.8-3 has caused the Debian Bug report #707960, regarding rpc.gssd segfaults when mounting a nfsv4 volume 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.) -- 707960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-common Version: 1:1.2.8-1 Severity: grave (elided):/ /media/nfs nfs4noauto,soft,intr,sec=krb5p 0 0 [2262594.734234] rpc.gssd[2729]: segfault at 1 ip f74714ba sp ff830170 error 4 in libgssglue.so.1.0.0[f746e000+8000] Reverting nfs-common to 1:1.2.6-3 fixes the issue. BTW: /usr/share/bug/nfs-common/script: 5: /usr/share/bug/nfs-common/script: rpcinfo: not found -- Package-specific info: -- rpcinfo -- -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-41 ii libc6 2.17-1 ii libcap2 1:2.22-1.2 ii libcomerr2 1.42.5-1.1 ii libdevmapper1.02.1 2:1.02.77-1 ii libevent-2.0-5 2.0.19-stable-3 ii libgssglue1 0.4-2 ii libk5crypto31.10.1+dfsg-5 ii libkeyutils11.5.5-7 ii libkrb5-3 1.10.1+dfsg-5 ii libmount1 2.20.1-5.3 ii libnfsidmap20.25-4 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-24 ii lsb-base4.1+Debian9 ii rpcbind 0.2.0-8 ii ucf 3.0025+nmu3 Versions of packages nfs-common recommends: ii python 2.7.3-4 Versions of packages nfs-common suggests: pn open-iscsi none pn watchdognone -- no debconf information -- ciao, Marco signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: nfs-utils Source-Version: 1:1.2.8-3 We believe that the bug you reported is fixed in the latest version of nfs-utils, 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 707...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek vor...@debian.org (supplier of updated nfs-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 31 May 2013 17:59:53 -0700 Source: nfs-utils Binary: nfs-kernel-server nfs-common Architecture: source amd64 Version: 1:1.2.8-3 Distribution: unstable Urgency: low Maintainer: Debian kernel team debian-ker...@lists.debian.org Changed-By: Steve Langasek vor...@debian.org Description: nfs-common - NFS support files common to client and server nfs-kernel-server - support for NFS kernel server Closes: 707960 Changes: nfs-utils (1:1.2.8-3) unstable; urgency=low . * Add myself as comaintainer, per 518fcece.7050...@debian.org. * Build --with-libgssglue, which was the default prior to 1.2.8; this fixes a regression that makes rpc.gssd (and hence, all Kerberos-authenticated mounts) completely useless, because objects are being incorrectly passed between multiple gss implementations (by way of libtirpc). Closes: #707960. Checksums-Sha1: a5e816978271e8017e3a0686d9dc1d62d36193e8 2299 nfs-utils_1.2.8-3.dsc 2f3061ea5113f629356e5380305cf7a7f4b9594a 38222 nfs-utils_1.2.8-3.debian.tar.bz2 d4ab41f87745802c95fcf7211e0d78bfa770c14b 144894 nfs-kernel-server_1.2.8-3_amd64.deb 9e8bad1822d988d3b61109bc9b1cfe38e337f1a6 273982 nfs-common_1.2.8-3_amd64.deb Checksums-Sha256: 054a091d404cef6af5bc2ac80f30870817e960ec1c2533984cc1b39333441c49 2299 nfs-utils_1.2.8-3.dsc c7292742c21800a5522b5e265cc988046df29758d8314b79038bd3076b95cd97 38222 nfs-utils_1.2.8-3.debian.tar.bz2 508c876da8b3b324bdaf0c3b32d287c42ddb7f6af93e3cab0eb37b97136f6444 144894 nfs-kernel-server_1.2.8-3_amd64.deb 215824d11cc2f3e8b62ce73e806fa70d76df31591f19998fd1e90d8fee5235bb 273982
Bug#705507: marked as done (nfs-common: rpc.gssd crashes when performing nfs4 mount)
Your message dated Sat, 01 Jun 2013 01:18:00 + with message-id e1uiasg-00016h...@franck.debian.org and subject line Bug#707960: fixed in nfs-utils 1:1.2.8-3 has caused the Debian Bug report #707960, regarding nfs-common: rpc.gssd crashes when performing nfs4 mount 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.) -- 707960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-common Version: 1:1.2.6-3 Severity: normal Mounting a kerberos-protected nfs4 export is unsuccsessfull on powerpcspe. nfs-common initializes without error, and rpc.gssd appears to be running. Upon a mount attempt, the following error message was displayed: mount: fstab path: /etc/fstab mount: mtab path: /etc/mtab mount: lock path: /etc/mtab~ mount: temp path: /etc/mtab.tmp mount: UID:0 mount: eUID: 0 mount: spec: nfsserver:/home/yesterday mount: node: /home mount: types: nfs4 mount: opts: noatime,sec=krb5 mount: external mount: argv[0] = /sbin/mount.nfs4 mount: external mount: argv[1] = nfsserver:/home/yesterday mount: external mount: argv[2] = /home mount: external mount: argv[3] = -v mount: external mount: argv[4] = -o mount: external mount: argv[5] = rw,noatime,sec=krb5 mount.nfs4: timeout set for Mon Apr 15 17:35:12 2013 mount.nfs4: trying text-based options 'sec=krb5,addr=192.168.1.2,clientaddr=192.168.1.3' mount.nfs4: mount(2): Broken pipe mount.nfs4: Broken pipe After this message, rpc.gssd is no longer running. Further mount attempts timeout with the following: mount: fstab path: /etc/fstab mount: mtab path: /etc/mtab mount: lock path: /etc/mtab~ mount: temp path: /etc/mtab.tmp mount: UID:0 mount: eUID: 0 mount: spec: titansteel:/home/yesterday mount: node: /home mount: types: nfs4 mount: opts: noatime,sec=krb5 mount: external mount: argv[0] = /sbin/mount.nfs4 mount: external mount: argv[1] = titansteel:/home/yesterday mount: external mount: argv[2] = /home mount: external mount: argv[3] = -v mount: external mount: argv[4] = -o mount: external mount: argv[5] = rw,noatime,sec=krb5 mount.nfs4: timeout set for Mon Apr 15 17:37:21 2013 mount.nfs4: trying text-based options 'sec=krb5,addr=192.168.1.2,clientaddr=192.168.1.3' mount.nfs4: mount(2): Permission denied mount.nfs4: access denied by server while mounting nfsserver:/home/yesterday A gdb trace of rpc.gssd reveals the following: Program received signal SIGSEGV, Segmentation fault. 0x0ffd9154 in __gss_get_mechanism_cred () from /lib/powerpc-linux-gnuspe/libtirpc.so.1 (gdb) where #0 0x0ffd9154 in __gss_get_mechanism_cred () from /lib/powerpc-linux-gnuspe/libtirpc.so.1 #1 0x0ffd845c in gss_add_cred () from /lib/powerpc-linux-gnuspe/libtirpc.so.1 #2 0x0fb4dc38 in gss_acquire_cred (minor_status=0xbfc5f2fc, desired_name=0x0, time_req=0, desired_mechs=optimized out, cred_usage=1, output_cred_handle=0xbfc5f1f4, actual_mechs=0x0, time_rec=0xbfc5f1ec) at ../../../../src/lib/gssapi/mechglue/g_acquire_cred.c:152 #3 0x0ffd8588 in gss_add_cred () from /lib/powerpc-linux-gnuspe/libtirpc.so.1 #4 0x0ffd8af8 in gss_acquire_cred () from /lib/powerpc-linux-gnuspe/libtirpc.so.1 #5 0x10007b90 in ?? () #6 0x10004e04 in ?? () #7 0x100054d0 in ?? () #8 0x10005d14 in ?? () #9 0x10003b6c in ?? () #10 0x10002590 in ?? () #11 0x0fcaadcc in generic_start_main (main=optimized out, argc=optimized out, ubp_av=optimized out, auxvec=optimized out, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=optimized out) at ../csu/libc-start.c:228 #12 0x0fcaaf84 in __libc_start_main ( argc=error reading variable: value has been optimized out, ubp_av=error reading variable: value has been optimized out, ubp_ev=optimized out, auxvec=error reading variable: value has been optimized out, rtld_fini=error reading variable: value has been optimized out, stinfo=optimized out, stack_on_entry=error reading variable: value has been optimized out) at ../sysdeps/unix/sysv/linux/powerpc/libc-start.c:105 #13 0x in ?? () (gdb) I have not verified this as a problem with the same package versions on any other architecture, but I suspect this is an architecture specific problem. -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper
Bug#709525: marked as done (nfs-common: After upgrade to 1.2.8-2, rpc.gssd segfaults on startup)
Your message dated Sat, 01 Jun 2013 01:18:00 + with message-id e1uiasg-00016h...@franck.debian.org and subject line Bug#707960: fixed in nfs-utils 1:1.2.8-3 has caused the Debian Bug report #707960, regarding nfs-common: After upgrade to 1.2.8-2, rpc.gssd segfaults on startup 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.) -- 707960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-common Version: 1:1.2.8-2 Severity: important Dear Maintainer, After upgrading to 1.2.8-2 as part of normal Jessie upkeep, rpc.gssd started segfaulting immediately on startup, and I'm not really able to wrap my head around just why. The crash happens in libgssglue, in __gss_get_mechanism_cred, called by gss_init_sec_context, at g_init_sec_context.c:153 (still in libgssglue). It is rather clear that the crash happens because the copy of mglueP.h that is shipped with the source of libgssglue does not match that which is shipped with libkrb5. In the latter, the struct `gss_union_cred_t' has gained a new field called `loopback', and lost its `auxinfo' field, and when inspecting the gss_union_cred_t that has been passed to __gss_get_mechanism_cred, it clearly matched the definition from libkrb5. However, the fault does not seem to be lying with libgssglue, since the segafult only happens when nfs-common is upgraded, and downgrading nfs-common back to 1.2.6-3 makes it start working again. A simple guess from my side is that nfs-common has (erroneously?) been compiled against libkrb5 in some place where it should be compiled against libgssglue, perhaps? The structure and dependencies between the various packages involved is, however, far from obvious to me. (At the face of it, it seems like a hack, to begin with, that libgssglue has a local copy of a private header file from MIT Kerberos.) Whatever the problem is, it makes rpc.gssd, and therefore Kerberized NFS mounts, entirely unusable. Fix pl0x. :) -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000211 udp 33453 nlockmgr 1000213 udp 33453 nlockmgr 1000214 udp 33453 nlockmgr 1000211 tcp 54248 nlockmgr 1000213 tcp 54248 nlockmgr 1000214 tcp 54248 nlockmgr 172 udp708 ypbind 171 udp708 ypbind 172 tcp709 ypbind 171 tcp709 ypbind 1000241 udp 38590 status 1000241 tcp 43595 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD=yes NEED_GSSD=yes -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = dolda2000.com [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- home.nfs:/home /home nfs4sec=krb5i 0 0 home.nfs:/usr/site /usr/site nfs hard,intr,tcp 0 0 home.nfs:/video /home/pub/video nfs4sec=krb5i 0 0 -- /proc/mounts -- home.nfs:/home /home nfs4 rw,relatime,vers=4,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.1.181,minorversion=0,local_lock=none,addr=192.168.1.1 0 0 home.nfs:/usr/site /usr/site nfs rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.1,mountvers=3,mountport=50152,mountproto=tcp,local_lock=none,addr=192.168.1.1 0 0 home.nfs:/video /home/pub/video nfs4 rw,relatime,vers=4,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.1.181,minorversion=0,local_lock=none,addr=192.168.1.1 0 0 rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (99, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-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 nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-41 ii libc6 2.17-3 ii libcap2 1:2.22-1.2 ii
Bug#704121: marked as done (Debian cpio info pages totally gone)
Your message dated Sat, 01 Jun 2013 03:18:00 + with message-id e1uicko-0003xw...@franck.debian.org and subject line Bug#695717: fixed in cpio 2.11+dfsg-1 has caused the Debian Bug report #695717, regarding Debian cpio info pages totally gone 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.) -- 695717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- X-debbugs-Cc: bug-c...@gnu.org Package: cpio Version: 2.11+dfsg-0.1 The Debian cpio info pages are totally gone. So one turns to http://www.gnu.org/software/cpio/manual/cpio.html to find out what cpio -o returning exit code $?=2 means, but that isn't there either. ---End Message--- ---BeginMessage--- Source: cpio Source-Version: 2.11+dfsg-1 We believe that the bug you reported is fixed in the latest version of cpio, 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 695...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anibal Monsalve Salazar ani...@debian.org (supplier of updated cpio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Jun 2013 08:54:41 +1000 Source: cpio Binary: cpio cpio-win32 Architecture: source all amd64 Version: 2.11+dfsg-1 Distribution: unstable Urgency: low Maintainer: Ruben Molina rmol...@udea.edu.co Changed-By: Anibal Monsalve Salazar ani...@debian.org Description: cpio - GNU cpio -- a program to manage archives of files cpio-win32 - GNU cpio -- a program to manage archives of files (win32 build) Closes: 689612 695717 Changes: cpio (2.11+dfsg-1) unstable; urgency=low . * Standards Version is 3.9.4 * Remove reference to texinfo documntation in cpio man page Update debian/patches/695717-no-cpio.info.patch Closes: #695717 * Build depends on autotools-dev Autoconf update for arm64 building Drop debian/patches/autoconfupdate.patch Closes: #689612 * Update debian/watch Checksums-Sha1: c2295d6284d9339cbbe3ab8827661c5135701c37 1964 cpio_2.11+dfsg-1.dsc 77451a22d766b47a595a9f2423e2761f75611db7 13739 cpio_2.11+dfsg-1.debian.tar.bz2 475986a0d421b67f5812ce3ae860a136ac0c862c 74220 cpio-win32_2.11+dfsg-1_all.deb dfbf354e59bc0ed8158cdb1e80e1b18a75b0cb33 263240 cpio_2.11+dfsg-1_amd64.deb Checksums-Sha256: 1072ef69b636cdc458ba84c37853a96ca12016d161784d8ff546ae4452b0933b 1964 cpio_2.11+dfsg-1.dsc b0b7ea0d37e0ae659cbc25cc55f45247c3671169f4fcf709dc6b7525f163d3e3 13739 cpio_2.11+dfsg-1.debian.tar.bz2 60f9ba6adab4fb4dd21d08b50681a92f37e085aa7355a8b809acf6d8c82e02d4 74220 cpio-win32_2.11+dfsg-1_all.deb c167f6ec29c3177eb293f75123b6dde87ce05d37067d55d14f9ffc3517671061 263240 cpio_2.11+dfsg-1_amd64.deb Files: 2ba99dc7caa4e7e76d63ec8ca40ae386 1964 utils important cpio_2.11+dfsg-1.dsc 4c2d9aa3d75ec213ad35654470f2feb4 13739 utils important cpio_2.11+dfsg-1.debian.tar.bz2 cc7d7aed521af1dedf7aa1de638515d7 74220 utils extra cpio-win32_2.11+dfsg-1_all.deb c3f2a487bfe983ae69195b5725eda2d5 263240 utils important cpio_2.11+dfsg-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRqVpCAAoJEHxWrP6UeJfYG8oP/3O2Foz6ZseghKPMId1NtLc5 I/0nEEQ3LBy9t1lpJQUEuCjWhet0fF7BWVzoLteHzmSk/BqYr2dauG2ZXtBnJiV9 w0yo84OEti0EMm01ocoAzgULQ4vbUJxCDbSXdE9XHb1dpPIjyzK9YFvHJZvY6jtp 1DipK9gu5a4lWSOhyqNODHCnHsF1y+xb2JHBR6PoFQCqwVBR4CCEvMIMQa74Ij8C DZVhJ48Rn7Vj8qb9+JrYvHzwVMEiOghx8dEt/etkGadlQSm44sd0S0y+TUR5kAsU QiigUGk8bWburPs7czuIGsUf2ULk3C4zPbmsJvyImK8pqF080NJ1eJt5V83y2FTj MOnqNq0qHFS/2Dv32TUPJGcE8yP3x73lMPgi+/03RqgsXwkgh82rbdDtCtjrd6X2 XufiUg0LK3QXtTGBTwumco2R39Az4dCC4pGmfsXNZbwkUTrXhm5vQoHwJRPzT/KB zEeW5ALPRB5SayG0Ws1EKPasu347Xz7Y0ETmQ0pVb1ZcKA0EPan8sjsEGNpYPj4h JYV3VRTPJjP8YCUH7iaZqbB8uDdKYLCmXFL4qN8qJIVdUyo+tvNIMyAyvITyn6Ey GKDStgKw3iqyGR4Xvfm/paVzdZYuoZNJdNdcaiYsKqeXMHdss7JOKAR/NYoBzJpc s3wzQPy1W0gTDdQt+3PU =7b9R -END PGP SIGNATUREEnd Message---
Bug#710093: postgresql: not started automatically after installation in chroot
Re: Andreas Beckmann 2013-05-31 51a8feac.5090...@debian.org Fwiw, which services/packages come with out-of-the-box usable PostgreSQL support? For me, dbconfig-common sort of never works... For piuparts, dbconfig-common seems to work for most packages. DEBIAN_FRONTEND=noninteractive, all defaults. No clue if the services are working, but their package installation passes (and usually fails if the db server is not available). :-) Heh. Can you check /var/log/postgresql/ if there's any error messages for the first startup? there is only an empty /var/log/postgresql/postgresql-9.1-main.log I can reproduce this manually with pbuilder in the minimal chroot created by piuparts. But not in my regular pbuilder chroot. (postgresql is running there if permitted by policy-rc.d). Btw, can you share this policy-rc.d? I can fix this in the piuparts chroot if I install devscripts first and postgresql afterwards - now the daemon is running. I'd bet this is a bug in the chroot, like no localhost interface, or failure to resolve localhost. Or the 5432 is not available, but that should be a different error message. (Fwiw, I disagree with this bug being serious, as it apparently doesn't affect anyone but piuparts.) PS: I noticed that pg uses ports 5433, 5434, ... if 5432 is not available during installation - is there a way (preferrably via preseeding) that forces it to use 5432 (as that is expected by many other packages) and just fail if that is not available? For postgresql-common = 142, you could try port = 5432 in /etc/postgresql-common/createcluster.conf, that should work. Or just don't create a default cluster and use pg_createcluster -p 5432. Why is that port unavailable there anyway? Shouldn't that be a clean testbed for the upgrade tests? (On the same ticket I don't really see the need for preseeding here, 5432 should not be used by anyone else at installation time.) 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#709368: marked as done (wine-bin-unstable, libwine-unstable: wine expects some files to be located in /usr/share/wine/ instead of /usr/share/wine-untable/.)
Your message dated Sat, 01 Jun 2013 03:20:29 + with message-id e1uicmn-0006pl...@franck.debian.org and subject line Bug#709368: fixed in wine-unstable 1.5.7-7 has caused the Debian Bug report #709368, regarding wine-bin-unstable, libwine-unstable: wine expects some files to be located in /usr/share/wine/ instead of /usr/share/wine-untable/. 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.) -- 709368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libwine-unstable wine-bin-unstable Version: 1.5.7-6 Severity: grave Justification : renders package unusable Dear Maintainer, wine expects various files to be in the /usr/share/wine/ directory, but these files are actually installed in the /usr/share/wine-unstable/ directory. While this doesn’t render the package unusable for an existing wine installation, this does cause wine to not be able to create a new wine prefix for a user, because it can’t locate the wine.inf file. It also won’t be able to update an existing outdated wine prefix or display certain fonts. While I didn’t test it, there is a PPD file in /usr/share/wine-unstable/, so wine might not be able to print anything at the moment. Linking to every entry of /usr/share/wine-unstable/ from /usr/share/wine/ solved the issue. Regards, -- Sylvain Boilard signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: wine-unstable Source-Version: 1.5.7-7 We believe that the bug you reported is fixed in the latest version of wine-unstable, 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 709...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert mgilb...@debian.org (supplier of updated wine-unstable 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 May 2013 04:26:28 + Source: wine-unstable Binary: wine-unstable wine-bin-unstable libwine-dbg-unstable libwine-dev-unstable libwine-unstable libwine-alsa-unstable libwine-bin-unstable libwine-capi-unstable libwine-cms-unstable libwine-gl-unstable libwine-gphoto2-unstable libwine-ldap-unstable libwine-openal-unstable libwine-oss-unstable libwine-print-unstable libwine-sane-unstable Architecture: source i386 Version: 1.5.7-7 Distribution: unstable Urgency: low Maintainer: Debian Wine Party pkg-wine-pa...@lists.alioth.debian.org Changed-By: Michael Gilbert mgilb...@debian.org Description: libwine-alsa-unstable - Windows API implementation - ALSA sound module libwine-bin-unstable - Windows API implementation - system services libwine-capi-unstable - Windows API implementation - ISDN module libwine-cms-unstable - Windows API implementation - color management module libwine-dbg-unstable - Windows API implementation - debugging symbols libwine-dev-unstable - Windows API implementation - development files libwine-gl-unstable - Windows API implementation - OpenGL module libwine-gphoto2-unstable - Windows API implementation - camera module libwine-ldap-unstable - Windows API implementation - LDAP module libwine-openal-unstable - Windows API implementation - OpenAL module libwine-oss-unstable - Windows API implementation - OSS sound module libwine-print-unstable - Windows API implementation - printing module libwine-sane-unstable - Windows API implementation - scanner module libwine-unstable - Windows API implementation - library wine-bin-unstable - Windows API implementation - binary loader wine-unstable - Windows API implementation - standard suite Closes: 709368 Changes: wine-unstable (1.5.7-7) unstable; urgency=low . * Correct references to /usr/share/wine-unstable (closes: #709368). Checksums-Sha1: 21e33ebc6c7dd1df21dd6923e8ff2608a6b91a40 4983 wine-unstable_1.5.7-7.dsc b4693d6c981a5f0470bd59b9782eb50b61255ae5 63831 wine-unstable_1.5.7-7.diff.gz 15f98aa0bd8e67eeb154f0466f30203708c78793 54494 wine-unstable_1.5.7-7_i386.deb 3275c8f61f834b6a8d741daa03525dd812530983 83470 wine-bin-unstable_1.5.7-7_i386.deb f8b7e5038c4de27925d231f1b43a25cfa814bb94 52566 libwine-dbg-unstable_1.5.7-7_i386.deb
Bug#695717: marked as done (cpio: includes non-free documentation (GFDL with unmodifiable sections))
Your message dated Sat, 01 Jun 2013 03:18:00 + with message-id e1uicko-0003xw...@franck.debian.org and subject line Bug#695717: fixed in cpio 2.11+dfsg-1 has caused the Debian Bug report #695717, regarding cpio: includes non-free documentation (GFDL with unmodifiable sections) 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.) -- 695717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: cpio Version: 2.11-8 Severity: serious Justification: Policy 2.2.1 Usertags: gfdl doc/cpio.* has the following license: | Permission is granted to copy, distribute and/or modify this document | under the terms of the GNU Free Documentation License, Version 1.2 or | any later version published by the Free Software Foundation; with no | Invariant Sections, with the Front-Cover texts being ``A GNU Manual'', | and with the Back-Cover Texts as in (a) below. A copy of the license | is included in the section entitled ``GNU Free Documentation License''. | | (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify | this GNU Manual, like GNU software. Copies published by the Free | Software Foundation raise funds for GNU development.'' As per GR 2006-001, works licensed under GFDL with unmodifiable sections are not suitable for main: http://www.debian.org/vote/2006/vote_001 -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: cpio Source-Version: 2.11+dfsg-1 We believe that the bug you reported is fixed in the latest version of cpio, 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 695...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anibal Monsalve Salazar ani...@debian.org (supplier of updated cpio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Jun 2013 08:54:41 +1000 Source: cpio Binary: cpio cpio-win32 Architecture: source all amd64 Version: 2.11+dfsg-1 Distribution: unstable Urgency: low Maintainer: Ruben Molina rmol...@udea.edu.co Changed-By: Anibal Monsalve Salazar ani...@debian.org Description: cpio - GNU cpio -- a program to manage archives of files cpio-win32 - GNU cpio -- a program to manage archives of files (win32 build) Closes: 689612 695717 Changes: cpio (2.11+dfsg-1) unstable; urgency=low . * Standards Version is 3.9.4 * Remove reference to texinfo documntation in cpio man page Update debian/patches/695717-no-cpio.info.patch Closes: #695717 * Build depends on autotools-dev Autoconf update for arm64 building Drop debian/patches/autoconfupdate.patch Closes: #689612 * Update debian/watch Checksums-Sha1: c2295d6284d9339cbbe3ab8827661c5135701c37 1964 cpio_2.11+dfsg-1.dsc 77451a22d766b47a595a9f2423e2761f75611db7 13739 cpio_2.11+dfsg-1.debian.tar.bz2 475986a0d421b67f5812ce3ae860a136ac0c862c 74220 cpio-win32_2.11+dfsg-1_all.deb dfbf354e59bc0ed8158cdb1e80e1b18a75b0cb33 263240 cpio_2.11+dfsg-1_amd64.deb Checksums-Sha256: 1072ef69b636cdc458ba84c37853a96ca12016d161784d8ff546ae4452b0933b 1964 cpio_2.11+dfsg-1.dsc b0b7ea0d37e0ae659cbc25cc55f45247c3671169f4fcf709dc6b7525f163d3e3 13739 cpio_2.11+dfsg-1.debian.tar.bz2 60f9ba6adab4fb4dd21d08b50681a92f37e085aa7355a8b809acf6d8c82e02d4 74220 cpio-win32_2.11+dfsg-1_all.deb c167f6ec29c3177eb293f75123b6dde87ce05d37067d55d14f9ffc3517671061 263240 cpio_2.11+dfsg-1_amd64.deb Files: 2ba99dc7caa4e7e76d63ec8ca40ae386 1964 utils important cpio_2.11+dfsg-1.dsc 4c2d9aa3d75ec213ad35654470f2feb4 13739 utils important cpio_2.11+dfsg-1.debian.tar.bz2 cc7d7aed521af1dedf7aa1de638515d7 74220 utils extra cpio-win32_2.11+dfsg-1_all.deb c3f2a487bfe983ae69195b5725eda2d5 263240 utils important cpio_2.11+dfsg-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRqVpCAAoJEHxWrP6UeJfYG8oP/3O2Foz6ZseghKPMId1NtLc5 I/0nEEQ3LBy9t1lpJQUEuCjWhet0fF7BWVzoLteHzmSk/BqYr2dauG2ZXtBnJiV9 w0yo84OEti0EMm01ocoAzgULQ4vbUJxCDbSXdE9XHb1dpPIjyzK9YFvHJZvY6jtp 1DipK9gu5a4lWSOhyqNODHCnHsF1y+xb2JHBR6PoFQCqwVBR4CCEvMIMQa74Ij8C DZVhJ48Rn7Vj8qb9+JrYvHzwVMEiOghx8dEt/etkGadlQSm44sd0S0y+TUR5kAsU
