Bug#761619: Acknowledgement (installation-reports: Disk scan hangs)
blkid info /dev/bcache0: LABEL=btrfs0 UUID=df532815-f9df-42a3-9f4f-3cdf3bb3d2d9 UUID_SUB=79f8e311-3000-438c-9d95-08dc07b328b0 TYPE=btrfs /dev/mapper/megaraid-root: LABEL=debroot UUID=b3f534ce-5509-4ab9-88ca-feb4a3041131 TYPE=ext4 /dev/mapper/S830--512A-CentOS5: LABEL=sandboxes UUID=8bde1219-e609-4fc0-aff0-be4c3e7da578 SEC_TYPE=ext2 TYPE=ext3 /dev/mapper/S830--512A-root: UUID=52ad8d8f-5c0c-4d7d-9bb0-aad9b25fa559 TYPE=ext4 /dev/mapper/vg--debHD-home: UUID=fef87605-40e0-44bd-b2e9-4202891b08a4 TYPE=ext4 /dev/mapper/vg--debHD-root: UUID=2fc7a241-7504-4ead-9509-ce22577a9849 TYPE=ext4 /dev/mapper/vg--debHD-swap: UUID=0d5a3423-cb9b-4e23-acaa-a108e24406ff TYPE=swap /dev/sda2: LABEL=boot UUID=efdcfb4c-8644-48f0-adee-936741dae73b TYPE=ext2 /dev/sda3: UUID=KxCXGk-ELu4-2su6-8o60-PVf4-xSWC-rMu2JK TYPE=LVM2_member /dev/sda4: UUID=008c20b6-8055-4bb8-8a52-adceaf9de75b TYPE=swap /dev/sdb1: LABEL=System Reserved UUID=968699FA8699DB57 TYPE=ntfs /dev/sdb2: UUID=02FE9C1FFE9C0D53 TYPE=ntfs /dev/sdb3: UUID=fd14c1fb-99f7-4205-a825-a2701a93f55c TYPE=ext4 /dev/sdb5: UUID=f034f2ef-eaad-40af-8530-83f3b4691b6d UUID_SUB=af9b7cc6-afe7-48fd-b297-f69aa3b82c72 TYPE=btrfs /dev/sdc1: UUID=74ee9800-2a3e-4d5f-b768-803faccf99c2 TYPE=ext2 /dev/sdc5: UUID=9W92nI-hA9c-sjtk-DuQz-miR0-WrVK-oDDmWI TYPE=LVM2_member /dev/sde1: UUID=72a7d6d8-9c7c-47a3-8949-6cc3ced78153 TYPE=ext4 /dev/sde2: UUID=07f88f79-abfa-4b0a-88f8-0891e2333db4 TYPE=swap /dev/sde5: UUID=LWWgc9-Beyf-6v55-F3I9-ePeP-7K05-wlAEdw TYPE=LVM2_member /dev/sdf1: LABEL=SeagateBackup UUID=3f8b489c-c294-415a-abb9-ac1baeed22bb UUID_SUB=cb7983a7-a516-48a2-b989-f67871332a72 TYPE=btrfs /dev/sdg1: LABEL=SeagateBackup UUID=3f8b489c-c294-415a-abb9-ac1baeed22bb UUID_SUB=7eeb3143-5d9a-4f32-a058-18e29fa23d74 TYPE=btrfs /dev/sdh1: LABEL=Debian jessie-DI-b1 amd64 1 TYPE=iso9660 /dev/sdh2: SEC_TYPE=msdos UUID=378E-F825 TYPE=vfat /dev/sdj1: UUID=2C55-1C1F TYPE=vfat
Bug#761619: installation-reports: Disk scan hangs
parted info (sdd1 is the bcache partition) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761619: Acknowledgement (installation-reports: Disk scan hangs)
parted info. sdd1 is the bcache partition. parted Description: Binary data
Bug#754280: marked as done (ganeti-2.11 - gnt-cluster upgrade writes config backup in /var/lib)
Your message dated Mon, 15 Sep 2014 06:48:50 + with message-id e1xtq5i-0002b7...@franck.debian.org and subject line Bug#754280: fixed in ganeti 2.11.5-2 has caused the Debian Bug report #754280, regarding ganeti-2.11 - gnt-cluster upgrade writes config backup in /var/lib 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.) -- 754280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ganeti-2.11 Version: 2.11.2-1~bpo70+1 Severity: normal gnt-cluster upgrade writes the config backup into /var/lib instead of /var/backups. | Stopping daemons everywhere. | Backing up configuration as /var/lib/ganeti1404909992.tar | Switching to version 2.11 on all nodes /var/backups is not specified by the FHS, but a Debian specific directory. But on the other hand the FHS mandates to use a sub-directory. | An application (or a group of inter-related applications) must use a | subdirectory of /var/lib for its data. Bastian -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: ganeti Source-Version: 2.11.5-2 We believe that the bug you reported is fixed in the latest version of ganeti, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Apollon Oikonomopoulos apoi...@debian.org (supplier of updated ganeti package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Aug 2014 18:09:13 -0700 Source: ganeti Binary: ganeti2 ganeti ganeti-2.11 ganeti-haskell-2.11 ganeti-htools ganeti-htools-2.11 ganeti-doc python-ganeti-rapi Architecture: source all amd64 Version: 2.11.5-2 Distribution: unstable Urgency: medium Maintainer: Debian Ganeti Team pkg-ganeti-de...@lists.alioth.debian.org Changed-By: Apollon Oikonomopoulos apoi...@debian.org Description: ganeti - cluster virtualization manager ganeti-2.11 - cluster virtualization manager - Python components ganeti-doc - cluster virtualization manager - documentation ganeti-haskell-2.11 - cluster virtualization manager - Haskell components ganeti-htools - cluster virtualization manager - tools (stand-alone) ganeti-htools-2.11 - cluster virtualization manager - tools for Ganeti 2.11 ganeti2- transitional dummy package python-ganeti-rapi - cluster virtualization manager - RAPI client library Closes: 754280 Changes: ganeti (2.11.5-2) unstable; urgency=medium . * d/rules: set config backup dir to /var/backups at ./configure time (Closes: #754280) * d/control: recommend drbd-utils and fall back to drbd8-utils * d/copyright: rename the BSD license paragraph to BSD-2-Clause, to match the SPDX identifier. Checksums-Sha1: 3f8ef082a2ca615ad32195a6b8114a09f054ec61 2974 ganeti_2.11.5-2.dsc d876c76eef3ad3b6885a8bbf369d5f7aca64bb5f 31300 ganeti_2.11.5-2.debian.tar.xz c28d713baacfdbdc8e9070131e3f98734f30ac09 63756 ganeti2_2.11.5-2_all.deb 1e3dded24975469bae34cc87d3a330dcabe6b9b5 80378 ganeti_2.11.5-2_all.deb d259445ec33fe0f7464abdbeb5c810da0dfdde62 766610 ganeti-2.11_2.11.5-2_all.deb b8ce03cb551d4776a59efdcf52475f6723d3447e 5087592 ganeti-haskell-2.11_2.11.5-2_amd64.deb b452488d3aed08ccc772e4f2b395006054432b21 16572 ganeti-htools_2.11.5-2_all.deb 31351baacbf18e10cb10fc758560605e50e0ebc0 1502464 ganeti-htools-2.11_2.11.5-2_amd64.deb 3ad0c7862b517a70145f8e1983775b54333bf35a 890096 ganeti-doc_2.11.5-2_all.deb fd5cc7a66bc016b483ad6c8d122a05368c55a980 28734 python-ganeti-rapi_2.11.5-2_all.deb Checksums-Sha256: 9464f2555c79312a2e0734996866d11b7eca3dd6f87a93520ed8402fdbbc7426 2974 ganeti_2.11.5-2.dsc 991baf3252fff26a9efcb322cd8c9a09a07610e296bcab80cd7f909b776047c7 31300 ganeti_2.11.5-2.debian.tar.xz 25c21df5a0609d79116231aef71fb0431cd4b23b97cff9d304a060b4e3eb95ae 63756
Bug#761356: marked as done (openjpeg-tools and libopenjp2-tools: error when trying to install together)
Your message dated Mon, 15 Sep 2014 09:16:27 +0200 with message-id ca+7wusyoe6c603p+_km33atat3pmfydruini6jffs8clsuv...@mail.gmail.com and subject line Fwd: has caused the Debian Bug report #761356, regarding openjpeg-tools and libopenjp2-tools: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 761356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libopenjp2-tools,openjpeg-tools Version: libopenjp2-tools/2.1.0-1 Version: openjpeg-tools/2.0.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-09-13 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libjpeg8:amd64. (Reading database ... 10869 files and directories currently installed.) Preparing to unpack .../libjpeg8_8d1-1_amd64.deb ... Unpacking libjpeg8:amd64 (8d1-1) ... Selecting previously unselected package liblcms2-2:amd64. Preparing to unpack .../liblcms2-2_2.6-3_amd64.deb ... Unpacking liblcms2-2:amd64 (2.6-3) ... Selecting previously unselected package libpng12-0:amd64. Preparing to unpack .../libpng12-0_1.2.50-2_amd64.deb ... Unpacking libpng12-0:amd64 (1.2.50-2) ... Selecting previously unselected package libjbig0:amd64. Preparing to unpack .../libjbig0_2.1-3_amd64.deb ... Unpacking libjbig0:amd64 (2.1-3) ... Selecting previously unselected package libtiff5:amd64. Preparing to unpack .../libtiff5_4.0.3-10_amd64.deb ... Unpacking libtiff5:amd64 (4.0.3-10) ... Selecting previously unselected package libopenjp2-7:amd64. Preparing to unpack .../libopenjp2-7_2.1.0-1_amd64.deb ... Unpacking libopenjp2-7:amd64 (2.1.0-1) ... Selecting previously unselected package libopenjpeg6:amd64. Preparing to unpack .../libopenjpeg6_2.0.0-1_amd64.deb ... Unpacking libopenjpeg6:amd64 (2.0.0-1) ... Selecting previously unselected package libopenjp2-tools. Preparing to unpack .../libopenjp2-tools_2.1.0-1_amd64.deb ... Unpacking libopenjp2-tools (2.1.0-1) ... Selecting previously unselected package openjpeg-tools. Preparing to unpack .../openjpeg-tools_2.0.0-1_amd64.deb ... Unpacking openjpeg-tools (2.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/openjpeg-tools_2.0.0-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/opj_decompress.1.gz', which is also in package libopenjp2-tools 2.1.0-1 Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: /var/cache/apt/archives/openjpeg-tools_2.0.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/bin/opj_compress /usr/bin/opj_decompress /usr/bin/opj_dump /usr/share/man/man1/opj_compress.1.gz /usr/share/man/man1/opj_decompress.1.gz /usr/share/man/man1/opj_dump.1.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Control: tags -1 wontfix openjpeg-tools (from src:openjpeg2) never reached testing. closing as wontfix.---End Message---
Bug#761355: marked as done (libopenjpeg6-dev and libopenjp2-7-dev: error when trying to install together)
Your message dated Mon, 15 Sep 2014 09:15:46 +0200 with message-id CA+7wUszDbfouH+k5+A7A+VYwh=WWwHN03ZJy_Lk49+=n+qp...@mail.gmail.com and subject line has caused the Debian Bug report #761355, regarding libopenjpeg6-dev and libopenjp2-7-dev: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 761355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libopenjp2-7-dev,libopenjpeg6-dev Version: libopenjp2-7-dev/2.1.0-1 Version: libopenjpeg6-dev/2.0.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-09-13 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libopenjp2-7:amd64. (Reading database ... 10869 files and directories currently installed.) Preparing to unpack .../libopenjp2-7_2.1.0-1_amd64.deb ... Unpacking libopenjp2-7:amd64 (2.1.0-1) ... Selecting previously unselected package libopenjpeg6:amd64. Preparing to unpack .../libopenjpeg6_2.0.0-1_amd64.deb ... Unpacking libopenjpeg6:amd64 (2.0.0-1) ... Selecting previously unselected package libopenjp2-7-dev. Preparing to unpack .../libopenjp2-7-dev_2.1.0-1_amd64.deb ... Unpacking libopenjp2-7-dev (2.1.0-1) ... Selecting previously unselected package libopenjpeg6-dev:amd64. Preparing to unpack .../libopenjpeg6-dev_2.0.0-1_amd64.deb ... Unpacking libopenjpeg6-dev:amd64 (2.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libopenjpeg6-dev_2.0.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopenjp2.so', which is also in package libopenjp2-7-dev 2.1.0-1 Errors were encountered while processing: /var/cache/apt/archives/libopenjpeg6-dev_2.0.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/lib/x86_64-linux-gnu/libopenjp2.so This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Control: tags -1 wontfix libopenjpeg6-dev never reached testing. closing as wontfix.---End Message---
Bug#761357: marked as done (openjp3d-tools and libopenjp3d-tools: error when trying to install together)
Your message dated Mon, 15 Sep 2014 09:16:57 +0200 with message-id CA+7wUsw_FL=qjezoqykm_qhoobp3kjfh1zrhv3cdskj1pga...@mail.gmail.com and subject line Fwd: has caused the Debian Bug report #761357, regarding openjp3d-tools and libopenjp3d-tools: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 761357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libopenjp3d-tools,openjp3d-tools Version: libopenjp3d-tools/2.1.0-1 Version: openjp3d-tools/2.0.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-09-13 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libopenjp3d6:amd64. (Reading database ... 10869 files and directories currently installed.) Preparing to unpack .../libopenjp3d6_2.0.0-1_amd64.deb ... Unpacking libopenjp3d6:amd64 (2.0.0-1) ... Selecting previously unselected package libopenjp3d7:amd64. Preparing to unpack .../libopenjp3d7_2.1.0-1_amd64.deb ... Unpacking libopenjp3d7:amd64 (2.1.0-1) ... Selecting previously unselected package libopenjp3d-tools. Preparing to unpack .../libopenjp3d-tools_2.1.0-1_amd64.deb ... Unpacking libopenjp3d-tools (2.1.0-1) ... Selecting previously unselected package openjp3d-tools. Preparing to unpack .../openjp3d-tools_2.0.0-1_amd64.deb ... Unpacking openjp3d-tools (2.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/openjp3d-tools_2.0.0-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/opj_jp3d_decompress', which is also in package libopenjp3d-tools 2.1.0-1 Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: /var/cache/apt/archives/openjp3d-tools_2.0.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/bin/opj_jp3d_compress /usr/bin/opj_jp3d_decompress This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Control: tags -1 wontfix openjp3d-tools never reached testing. closing as wontfix.---End Message---
Bug#761540: marked as done (bridge-method-injector: FTBFS: Missing required artifact: asm:asm-debug-all:jar:debian)
Your message dated Mon, 15 Sep 2014 07:18:32 +
with message-id e1xtqys-00064a...@franck.debian.org
and subject line Bug#761540: fixed in bridge-method-injector 1.13-1
has caused the Debian Bug report #761540,
regarding bridge-method-injector: FTBFS: Missing required artifact:
asm:asm-debug-all:jar:debian
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.)
--
761540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: bridge-method-injector
Version: 1.8-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140913 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
debian/rules build
test -x debian/rules
mkdir -p .
/usr/share/maven-debian-helper/copy-repo.sh /«PKGBUILDDIR»/debian
mh_patchpoms -plibbridge-method-injector-java --debian-build
--keep-pom-version --maven-repo=/«PKGBUILDDIR»/debian/maven-repo
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to
check if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi
cd . /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties
-Dclassworlds.conf=/etc/maven2/m2-debian.conf
org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
-Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo install
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Bridge Method Injection Parent POM
[INFO] Bridge method injection annotations
[INFO] bridge-method-injector
[INFO]
[INFO] Building Bridge Method Injection Parent POM
[INFO]task-segment: [install]
[INFO]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/com/infradna/tool/bridge-method-injector-parent/1.8/bridge-method-injector-parent-1.8.pom
[INFO]
[INFO] Building Bridge method injection annotations
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/«PKGBUILDDIR»/annotation/src/main/resources
[INFO] [compiler:compile {execution: default-compile}]
[WARNING] File encoding has not been set, using platform encoding
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] Compiling 2 source files to /«PKGBUILDDIR»/annotation/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/«PKGBUILDDIR»/annotation/src/test/resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[INFO] [surefire:test {execution: default-test}]
[INFO] No tests to run.
[INFO] Surefire report directory:
/«PKGBUILDDIR»/annotation/target/surefire-reports
---
T E S T S
---
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/«PKGBUILDDIR»/annotation/target/bridge-method-annotation-1.8.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/«PKGBUILDDIR»/annotation/target/bridge-method-annotation-1.8.jar to
/«PKGBUILDDIR»/debian/maven-repo/com/infradna/tool/bridge-method-annotation/1.8/bridge-method-annotation-1.8.jar
[INFO]
[INFO] Building bridge-method-injector
Bug#761562: osmosis: FTBFS: Execution failed for task ':osmosis-osm-binary:compileJava'.
Control: forwarded -1 https://trac.openstreetmap.org/ticket/5228 Hi David, Thanks for your rebuild work and reporting this issue. It looks like the recent update of protobuf from 2.5.0 to 2.6.0 introduced a signature change for the parseUnknownField method which breaks the osmosis build. I've forwarded this issue upstream which can hopefully help resolve it. Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- 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#761562: osmosis: FTBFS: Execution failed for task ':osmosis-osm-binary:compileJava'.
Processing control commands: forwarded -1 https://trac.openstreetmap.org/ticket/5228 Bug #761562 [src:osmosis] osmosis: FTBFS: Execution failed for task ':osmosis-osm-binary:compileJava'. Set Bug forwarded-to-address to 'https://trac.openstreetmap.org/ticket/5228'. -- 761562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761562 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#761629: spatialite-gui: segfaulting when it's built with wxwidgets3.0
Package: spatialite-gui Version: 1.7.1-4.1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Started using Spatialite-gui. * What exactly did you do (or not do) that was effective (or ineffective)? I created a new database, and started to import some shapefiles, nothing exotic. * What was the outcome of this action? Segmentation fault * What outcome did you expect instead? To function, without crash. toni@arheo:~$ gdb spatialite-gui GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from spatialite-gui...Reading symbols from /usr/lib/debug /.build-id/d9/fa742608e5c06d96524f4aabc444e6b6265d90.debug...done. done. (gdb) run Starting program: /usr/bin/spatialite-gui [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffea497700 (LWP 25575)] [New Thread 0x7fffe9c96700 (LWP 25576)] [New Thread 0x7fffe9278700 (LWP 25577)] [New Thread 0x7fffe8a77700 (LWP 25578)] [Thread 0x7fffe8a77700 (LWP 25578) exited] [New Thread 0x7fffe8a77700 (LWP 25586)] [New Thread 0x7fffd66fc700 (LWP 25587)] [Thread 0x7fffe9278700 (LWP 25577) exited] [Thread 0x7fffe8a77700 (LWP 25586) exited] [New Thread 0x7fffe8a77700 (LWP 25595)] [New Thread 0x7fffe9278700 (LWP 25596)] [Thread 0x7fffe8a77700 (LWP 25595) exited] [Thread 0x7fffe9278700 (LWP 25596) exited] [New Thread 0x7fffe9278700 (LWP 25632)] [New Thread 0x7fffe8a77700 (LWP 25633)] [Thread 0x7fffe9278700 (LWP 25632) exited] [Thread 0x7fffe8a77700 (LWP 25633) exited] [New Thread 0x7fffe8a77700 (LWP 25642)] [Thread 0x7fffd66fc700 (LWP 25587) exited] [New Thread 0x7fffd66fc700 (LWP 25671)] [Thread 0x7fffd66fc700 (LWP 25671) exited] [Thread 0x7fffe8a77700 (LWP 25642) exited] [New Thread 0x7fffe8a77700 (LWP 25792)] [New Thread 0x7fffd66fc700 (LWP 25877)] [New Thread 0x7fffe9278700 (LWP 25878)] [Thread 0x7fffe9278700 (LWP 25878) exited] [Thread 0x7fffe8a77700 (LWP 25792) exited] Program received signal SIGSEGV, Segmentation fault. std::basic_stringwchar_t, std::char_traitswchar_t, std::allocatorwchar_t ::assign (this=this@entry=0x7fff99f0, __str=error reading variable: Cannot access memory at address 0xffe8) at /scratch/packages/gcc/4.9/gcc-4.9-4.9.1/build/x86_64-linux- gnu/libstdc++-v3/include/bits/basic_string.tcc:249 249 /scratch/packages/gcc/4.9/gcc-4.9-4.9.1/build/x86_64-linux- gnu/libstdc++-v3/include/bits/basic_string.tcc: Nincs ilyen fájl vagy könyvtár. After this, i rebuilded the package with wxwidgets2.8 and everything it's ok now. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages spatialite-gui depends on: ii libc6 2.19-10 ii libfreexl11.0.0g-1 ii libgaiagraphics1 0.5-2 ii libgcc1 1:4.9.1-12 ii libgeos-c13.4.2-5 ii libproj0 4.8.0-5 ii libspatialite54.1.1-10 ii libsqlite3-0 3.8.6-1 ii libstdc++64.9.1-12 ii libwxbase2.8-02.8.12.1+dfsg2-2 ii libwxgtk2.8-0 2.8.12.1+dfsg2-2 ii libxml2 2.9.1+dfsg1-4 spatialite-gui recommends no packages. spatialite-gui suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761290: thermald 1.3-3 conflicts with kernel 3.14-2-rt-amd64
@Srivivas, I was also able to reproduce this issue. I've applied this patch and tested it out and I no longer see the problem. I will upload the fixed thermald today. Thank you for the fast turn around on the fix. Colin On 12/09/14 19:28, Pandruvada, Srinivas wrote: On Fri, 12 Sep 2014 09:23:46 -0500 Rafael Vega rv...@elsoftwarehamuerto.org wrote: Package: thermald Version: 1.3-3 Severity: critical Justification: breaks the whole system Dear Maintainer, * What exactly did you do (or not do) that was effective (or ineffective)? Installed thermald 1.3-3 from testing repos and booted into realtime kernel (3.12-4-rt-amd64) * What was the outcome of this action? Sometimes the system will stop responding completely, no keyboard or mouse is accepted, not even switching to ttys. A hard shutdown is required and it has lead to file system corruption. Inspecting dmesg logs, I found this: [ 39.776121] BUG: scheduling while atomic: Xorg/1007/0x00010001 [ 39.776123] BUG: scheduling while atomic: swapper/2/0/0x00010002 . [ 39.776221] CPU: 1 PID: 1007 Comm: Xorg Tainted: P O 3.14-2-rt- amd64 #1 Debian 3.14.15-2 [ 39.776222] Hardware name: Apple Inc. MacBookPro8,1/Mac-94245B3640C91C81, BIOSMBP81.88Z.0047.B27.1201241646 01/24/12 [ 39.776223] 88026401db20 814e04fc 88026401db20 814dce83 [ 39.776224] 814e2cd8 00065340 00065340 88026392ffd8 [ 39.776225] 88026401db20 880267083ee0 88026401e278 88026401db20 [ 39.776225] Call Trace: [ 39.776230] IRQ [814e04fc] ? dump_stack+0x4a/0x75 [ 39.776232] [814dce83] ? __schedule_bug+0x96/0xa3 [ 39.776234] [814e2cd8] ? __schedule+0x5f8/0x670 [ 39.776235] [814e2d77] ? schedule+0x27/0xa0 [ 39.776237] [814e4335] ? rt_spin_lock_slowlock+0xb5/0x220 [ 39.776240] [a0cf8ada] ? pkg_temp_thermal_platform_thermal_notify+0x3a/0x126 [x86_pkg_temp_thermal] [ 39.776242] [8103b140] ? therm_throt_process+0x10/0x140 [ 39.776243] [8103b471] ? intel_thermal_interrupt+0x201/0x240 [ 39.776244] [8103b4f8] ? smp_thermal_interrupt+0x18/0x40 [ 39.776247] [814edadd] ? thermal_interrupt+0x6d/0x80 [ 39.776249] EOI [814ec9fd] ? system_call_fast_compare_end+0x10/0x15 [ 39.776251] CPU: 2 PID: 0 Comm: swapper/2 Tainted: PW O 3.14-2-rt- amd64 #1 Debian 3.14.15-2 [ 39.776252] Hardware name: Apple Inc. MacBookPro8,1/Mac-94245B3640C91C81, BIOSMBP81.88Z.0047.B27.1201241646 01/24/12 [ 39.776253] 8802655c32a0 814e04fc 8802655c32a0 814dce83 [ 39.776254] 814e2cd8 00065340 00065340 8802655f5fd8 [ 39.776255] 8802655c32a0 880267103ee0 8802655c39f8 8802655c32a0 [ 39.776255] Call Trace: Looks like scheduling issue with PREEMP_RT config. Short term solution is change in .config. Thermald will fallback to coretemp driver # CONFIG_X86_PKG_TEMP_THERMAL is is not set I have to look at the fixing driver bug when PREEMT_RT is defined. I am not much familiar at scheduling in RT context except here spin_lock_irq_save is preemptable. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761371: virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds
On 13/09/14 21:04, Steven Chamberlain wrote: On 13/09/14 11:38, Emilio Pozuelo Monfort wrote: Note how there were errors about /dev/mem in previous successful builds, netstat would either need to be either setuid or have capabilities set, to be able to read from /dev/mem. Previously I'd patched the virtuoso tests to still run even if 'netstat -nl' didn't show if the server was running yet after the timeout. I guess they've added some new tests since. So what should we do here? Should that patch be updated on virtuoso-opensource? Or can netstat be fixed on kbsd? This is blocking the imagemagick transition. Emilio -- 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#761102: libbladerf0: depends on libusb-1.0-0 on !linux
Processing control commands: reassign -1 libbladerf0 0.2014.09~rc2-4 Bug #761102 [src:libbladerf0] libbladerf0: depends on libusb-1.0-0 on !linux Warning: Unknown package 'src:libbladerf0' Bug reassigned from package 'src:libbladerf0' to 'libbladerf0'. No longer marked as found in versions libbladerf0/0.2014.09~rc2-4. Ignoring request to alter fixed versions of bug #761102 to the same values previously set Bug #761102 [libbladerf0] libbladerf0: depends on libusb-1.0-0 on !linux Marked as found in versions bladerf/0.2014.09~rc2-4. -- 761102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761102 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#756908: [Debichem-devel] Bug#756908: ergo: FTBFS on mips, mipsel, powerpc, s390x: test suite failures
On Mon, Sep 15, 2014 at 01:42:04AM +0200, Michael Banck wrote: Hi, On Sun, Aug 03, 2014 at 01:53:00PM +0200, Cyril Brulebois wrote: Source: ergo Version: 3.4.0-1 Severity: serious Justification: FTBFS Hi, everything is in the subject, full summary: https://buildd.debian.org/status/package.php?p=ergosuite=sid Direct links to failing build logs: https://buildd.debian.org/status/fetch.php?pkg=ergoarch=mipsver=3.4.0-1stamp=1406494180 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=mipselver=3.4.0-1stamp=1406450302 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=powerpcver=3.4.0-1stamp=1406399761 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=s390xver=3.4.0-1stamp=1406400721 So mips and s390x have built fine now, and I just tried on the powerpc porterbox (partch) without issues. As this was a timeout during the test suite, a simple rebuild might helpe, preferably on a speedy machine. CCing the powerpc and mipsel buildd maintainers for that. Done for powerpc. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#761101: python-xstatic-angular-cookies: not installable in sid
Processing control commands: reassign -1 src:python-xstatic-angular-cookies 1.2.16.1-2 Bug #761101 [python-xstatic-cookies] python-xstatic-angular-cookies: not installable in sid Warning: Unknown package 'python-xstatic-cookies' Bug reassigned from package 'python-xstatic-cookies' to 'src:python-xstatic-angular-cookies'. No longer marked as found in versions 1.2.16.1-2. Ignoring request to alter fixed versions of bug #761101 to the same values previously set Bug #761101 [src:python-xstatic-angular-cookies] python-xstatic-angular-cookies: not installable in sid Marked as found in versions python-xstatic-angular-cookies/1.2.16.1-2. -- 761101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761101 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#761102: libbladerf0: depends on libusb-1.0-0 on !linux
Control: reassign -1 libbladerf0 0.2014.09~rc2-4 On Mi, 10 sep 14, 20:56:57, Emilio Pozuelo Monfort wrote: Source: libbladerf0 Version: 0.2014.09~rc2-4 Severity: serious Your package introduced a hardcoded dependency on libusb-1.0-0, making it uninstallable on !linux, see e.g.: https://buildd.debian.org/status/package.php?p=gr-osmosdr Dependency installability problem for gr-osmosdr on kfreebsd-amd64 and kfreebsd-i386: gr-osmosdr build-depends on: - libbladerf-dev libbladerf-dev depends on: - libbladerf0 (= 0.2014.09~rc2-4) libbladerf0 depends on missing: - libusb-1.0-0 (= 1.0.12) Emilio -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#761101: python-xstatic-angular-cookies: not installable in sid
Control: reassign -1 src:python-xstatic-angular-cookies 1.2.16.1-2 On Mi, 10 sep 14, 20:56:25, Ralf Treinen wrote: Package: python-xstatic-cookies Affects: python3-xstatic-cookies Version: 1.2.16.1-2 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hello, python-xstatic-cookies is currently not installable in sid since it depends on libjs-angularjs ( 1.2.17). However, we have libjs-angularjs version 1.2.23-1 in sid since 2014-08-23. The same holds for the python3-xstatic-angular-cookies package in the same source package. The dependency is hard-coded in debian/control. Cheers -Ralf. -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#761383: marked as done (python-xstatic-angular-cookies: not installable in sid)
Your message dated Mon, 15 Sep 2014 09:22:14 + with message-id e1xtsua-0005hp...@franck.debian.org and subject line Bug#761383: fixed in python-xstatic-angular-cookies 1.2.24.1-1 has caused the Debian Bug report #761383, regarding python-xstatic-angular-cookies: not installable in sid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 761383: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-xstatic-angular-cookies Affects: python3-xstatic-angular-cookies Version: 1.2.16.1-2 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hello PKG OpenStack team, it seams that I forgot to send in this bug report: python-xstatic-angular-cookies is currently not installable in sid since it depends on libjs-angularjs ( 1.2.17). However, we have libjs-angularjs version 1.2.23-1 in sid since 2014-08-23. The same holds for the python3-xstatic-angular-cookies package in the same source package. Cheers -Ralf. ---End Message--- ---BeginMessage--- Source: python-xstatic-angular-cookies Source-Version: 1.2.24.1-1 We believe that the bug you reported is fixed in the latest version of python-xstatic-angular-cookies, 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated python-xstatic-angular-cookies package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 14 Sep 2014 17:15:30 + Source: python-xstatic-angular-cookies Binary: python-xstatic-angular-cookies python3-xstatic-angular-cookies Architecture: source all Version: 1.2.24.1-1 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: python-xstatic-angular-cookies - Angular JS Cookies XStatic support - Python 2.x python3-xstatic-angular-cookies - Angular JS Cookies XStatic support - Python 3.x Closes: 761383 Changes: python-xstatic-angular-cookies (1.2.24.1-1) unstable; urgency=medium . * Following the version of the new libjs-angularjs, and fixed dependencies accordingly (Closes: #761383). * Fixed long description. * Fixed the BASE_DIR to the correct location. Checksums-Sha1: cc5b20abb47e77c418ae3dbdd216c0a7669f71f1 2387 python-xstatic-angular-cookies_1.2.24.1-1.dsc 54ae68cec550df7513b8e72b8909bf09446003cc 3732 python-xstatic-angular-cookies_1.2.24.1.orig.tar.xz a8ef4d4b6e7e3e6e6f90e7f517e7857341020b49 3196 python-xstatic-angular-cookies_1.2.24.1-1.debian.tar.xz c60f7f9e101b943e95ad4bb405aa4460b71264fa 4716 python-xstatic-angular-cookies_1.2.24.1-1_all.deb 4a4f0a7613e0b15d4dd66d1b70319b800c617a54 4586 python3-xstatic-angular-cookies_1.2.24.1-1_all.deb Checksums-Sha256: 5bc14ce9850819740d7461c0f91538397177962f0342de250a6b016d3989f2ed 2387 python-xstatic-angular-cookies_1.2.24.1-1.dsc a468d3e945b7aa02784781839dbccb626aa8a9b8f5b7f8c1579d3bbf583bbba2 3732 python-xstatic-angular-cookies_1.2.24.1.orig.tar.xz 5aba282a201f43bf0385dea0083bc99124aef5fd316f5d19819fc3a4da4f 3196 python-xstatic-angular-cookies_1.2.24.1-1.debian.tar.xz 2364d781986675d63b257d04ed4769870dca3da2b530f76929dc2fdc7effb0ce 4716 python-xstatic-angular-cookies_1.2.24.1-1_all.deb f3bfbe3be502372309c45a879f702805f926d3ea11d6b15f2404615b69f00563 4586 python3-xstatic-angular-cookies_1.2.24.1-1_all.deb Files: 8b6c93be7992b85b6cb9605e84607e56 4716 python optional python-xstatic-angular-cookies_1.2.24.1-1_all.deb 5e5481688f84d8bb60a0496b5cdc4b1d 4586 python optional python3-xstatic-angular-cookies_1.2.24.1-1_all.deb 31f6e87776e3b6ab6039c3acdd63fa9f 2387 python optional python-xstatic-angular-cookies_1.2.24.1-1.dsc 028c57c65229096adda2ade59d41dac5 3732 python optional python-xstatic-angular-cookies_1.2.24.1.orig.tar.xz a88662e89858ad9f5009ccb970540f40 3196 python optional python-xstatic-angular-cookies_1.2.24.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUFqSOAAoJENQWrRWsa0P+WmgQAIEVIg+hS9nB+fmchCRkiGsQ
Bug#761290: marked as done (thermald 1.3-3 conflicts with kernel 3.14-2-rt-amd64)
Your message dated Mon, 15 Sep 2014 09:22:40 + with message-id e1xtsua-0005vq...@franck.debian.org and subject line Bug#761290: fixed in thermald 1.3-5 has caused the Debian Bug report #761290, regarding thermald 1.3-3 conflicts with kernel 3.14-2-rt-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.) -- 761290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: thermald Version: 1.3-3 Severity: critical Justification: breaks the whole system Dear Maintainer, * What exactly did you do (or not do) that was effective (or ineffective)? Installed thermald 1.3-3 from testing repos and booted into realtime kernel (3.12-4-rt-amd64) * What was the outcome of this action? Sometimes the system will stop responding completely, no keyboard or mouse is accepted, not even switching to ttys. A hard shutdown is required and it has lead to file system corruption. Inspecting dmesg logs, I found this: [ 39.776121] BUG: scheduling while atomic: Xorg/1007/0x00010001 [ 39.776123] BUG: scheduling while atomic: swapper/2/0/0x00010002 . [ 39.776221] CPU: 1 PID: 1007 Comm: Xorg Tainted: P O 3.14-2-rt- amd64 #1 Debian 3.14.15-2 [ 39.776222] Hardware name: Apple Inc. MacBookPro8,1/Mac-94245B3640C91C81, BIOSMBP81.88Z.0047.B27.1201241646 01/24/12 [ 39.776223] 88026401db20 814e04fc 88026401db20 814dce83 [ 39.776224] 814e2cd8 00065340 00065340 88026392ffd8 [ 39.776225] 88026401db20 880267083ee0 88026401e278 88026401db20 [ 39.776225] Call Trace: [ 39.776230] IRQ [814e04fc] ? dump_stack+0x4a/0x75 [ 39.776232] [814dce83] ? __schedule_bug+0x96/0xa3 [ 39.776234] [814e2cd8] ? __schedule+0x5f8/0x670 [ 39.776235] [814e2d77] ? schedule+0x27/0xa0 [ 39.776237] [814e4335] ? rt_spin_lock_slowlock+0xb5/0x220 [ 39.776240] [a0cf8ada] ? pkg_temp_thermal_platform_thermal_notify+0x3a/0x126 [x86_pkg_temp_thermal] [ 39.776242] [8103b140] ? therm_throt_process+0x10/0x140 [ 39.776243] [8103b471] ? intel_thermal_interrupt+0x201/0x240 [ 39.776244] [8103b4f8] ? smp_thermal_interrupt+0x18/0x40 [ 39.776247] [814edadd] ? thermal_interrupt+0x6d/0x80 [ 39.776249] EOI [814ec9fd] ? system_call_fast_compare_end+0x10/0x15 [ 39.776251] CPU: 2 PID: 0 Comm: swapper/2 Tainted: PW O 3.14-2-rt- amd64 #1 Debian 3.14.15-2 [ 39.776252] Hardware name: Apple Inc. MacBookPro8,1/Mac-94245B3640C91C81, BIOSMBP81.88Z.0047.B27.1201241646 01/24/12 [ 39.776253] 8802655c32a0 814e04fc 8802655c32a0 814dce83 [ 39.776254] 814e2cd8 00065340 00065340 8802655f5fd8 [ 39.776255] 8802655c32a0 880267103ee0 8802655c39f8 8802655c32a0 [ 39.776255] Call Trace: [ 39.776257] IRQ [814e04fc] ? dump_stack+0x4a/0x75 [ 39.776259] [814dce83] ? __schedule_bug+0x96/0xa3 [ 39.776260] [814e2cd8] ? __schedule+0x5f8/0x670 [ 39.776261] [814e2d77] ? schedule+0x27/0xa0 [ 39.776263] [814e4335] ? rt_spin_lock_slowlock+0xb5/0x220 [ 39.776266] [a0cf8ada] ? pkg_temp_thermal_platform_thermal_notify+0x3a/0x126 [x86_pkg_temp_thermal] [ 39.776267] [8103b140] ? therm_throt_process+0x10/0x140 [ 39.776268] [8103b471] ? intel_thermal_interrupt+0x201/0x240 [ 39.776269] [8103b4f8] ? smp_thermal_interrupt+0x18/0x40 [ 39.776271] [814edadd] ? thermal_interrupt+0x6d/0x80 [ 39.776274] EOI [813b8b6a] ? cpuidle_enter_state+0x4a/0xc0 [ 39.776276] [813b8b63] ? cpuidle_enter_state+0x43/0xc0 [ 39.776277] [813b8c89] ? cpuidle_idle_call+0xa9/0x220 [ 39.776279] [8101e1c5] ? arch_cpu_idle+0x5/0x30 [ 39.776281] [810b86c1] ? cpu_startup_entry+0x91/0x280 [ 39.776284] [810434e7] ? start_secondary+0x1d7/0x280 full dmesg output at https://gist.github.com/rvega/c72883dc1de40857b7ac I then uninstalled thermald and all those messages went away. Then, I installed the latest version in master branch from https://github.com/01org/thermal_daemon and the messages are not present. I have not had any crashes since (still waiting to see if one happens). Note: real time kernel is very important to my music production workflow. Software based musical instruments need low latencies. -- System Information: Debian Release: jessie/sid APT prefers testing-updates
Bug#761390: libdvb: should not be released with jessie
On Sat, Sep 13, 2014 at 3:03 PM, Sebastian Ramacher sramac...@debian.org wrote: If nobody disagrees with me, I'll reassign this bug to ftp.debian.org before the jessie freeze starts. Please go ahead. -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751218: [ipheth-utils] Segmentation fault on using iPhone hotspot
severity 751218 serious thanks AIUI, this makes the package completely unusable, thus raising the priority of the bug. Samuel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [ipheth-utils] Segmentation fault on using iPhone hotspot
Processing commands for cont...@bugs.debian.org: severity 751218 serious Bug #751218 [ipheth-utils] [ipheth-utils] Segmentation fault on using iPhone hotspot Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 751218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751218 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#761483: marked as done (libstarpu-1.1-7 and libstarpu-1.1-6: error when trying to install together)
Your message dated Mon, 15 Sep 2014 10:04:32 + with message-id e1xtt96-0005yh...@franck.debian.org and subject line Bug#761483: fixed in starpu-contrib 1.1.3+dfsg-2 has caused the Debian Bug report #761483, regarding libstarpu-1.1-7 and libstarpu-1.1-6: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 761483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libstarpu-1.1-6,libstarpu-1.1-7 Version: libstarpu-1.1-6/1.1.2+dfsg-1+b1 Version: libstarpu-1.1-7/1.1.3+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-09-14 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libamd2.3.1:amd64. (Reading database ... 10869 files and directories currently installed.) Preparing to unpack .../libamd2.3.1_1%3a4.2.1-3_amd64.deb ... Unpacking libamd2.3.1:amd64 (1:4.2.1-3) ... Selecting previously unselected package libcolamd2.8.0:amd64. Preparing to unpack .../libcolamd2.8.0_1%3a4.2.1-3_amd64.deb ... Unpacking libcolamd2.8.0:amd64 (1:4.2.1-3) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libltdl7:amd64. Preparing to unpack .../libltdl7_2.4.2-1.10_amd64.deb ... Unpacking libltdl7:amd64 (2.4.2-1.10) ... Selecting previously unselected package libglpk36:amd64. Preparing to unpack .../libglpk36_4.55-1_amd64.deb ... Unpacking libglpk36:amd64 (4.55-1) ... Selecting previously unselected package libnuma1:amd64. Preparing to unpack .../libnuma1_2.0.10~rc2-1_amd64.deb ... Unpacking libnuma1:amd64 (2.0.10~rc2-1) ... Selecting previously unselected package libhwloc5:amd64. Preparing to unpack .../libhwloc5_1.9.1-1_amd64.deb ... Unpacking libhwloc5:amd64 (1.9.1-1) ... Selecting previously unselected package ocl-icd-libopencl1:amd64. Preparing to unpack .../ocl-icd-libopencl1_2.1.3-5_amd64.deb ... Unpacking ocl-icd-libopencl1:amd64 (2.1.3-5) ... Selecting previously unselected package libstarpu-1.1-6. Preparing to unpack .../libstarpu-1.1-6_1.1.2+dfsg-1+b1_amd64.deb ... Unpacking libstarpu-1.1-6 (1.1.2+dfsg-1+b1) ... Selecting previously unselected package libstarpu-1.1-7. Preparing to unpack .../libstarpu-1.1-7_1.1.3+dfsg-1_amd64.deb ... Unpacking libstarpu-1.1-7 (1.1.3+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libstarpu-1.1-7_1.1.3+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libstarpu-1.1.so.7', which is also in package libstarpu-1.1-6 1.1.2+dfsg-1+b1 Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: /var/cache/apt/archives/libstarpu-1.1-7_1.1.3+dfsg-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/lib/libstarpu-1.1.so.7 This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Source: starpu-contrib Source-Version: 1.1.3+dfsg-2 We believe that the bug you reported is fixed in the latest version of starpu-contrib, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous
Bug#756908: marked as done (ergo: FTBFS on mips, mipsel, powerpc, s390x: test suite failures)
Your message dated Mon, 15 Sep 2014 12:04:14 +0200 with message-id 20140915100413.gj18...@raptor.chemicalconnection.dyndns.org and subject line Re: [Debichem-devel] Bug#756908: ergo: FTBFS on mips, mipsel, powerpc, s390x: test suite failures has caused the Debian Bug report #756908, regarding ergo: FTBFS on mips, mipsel, powerpc, s390x: test suite failures 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.) -- 756908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ergo Version: 3.4.0-1 Severity: serious Justification: FTBFS Hi, everything is in the subject, full summary: https://buildd.debian.org/status/package.php?p=ergosuite=sid Direct links to failing build logs: https://buildd.debian.org/status/fetch.php?pkg=ergoarch=mipsver=3.4.0-1stamp=1406494180 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=mipselver=3.4.0-1stamp=1406450302 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=powerpcver=3.4.0-1stamp=1406399761 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=s390xver=3.4.0-1stamp=1406400721 Mraw, KiBi. ---End Message--- ---BeginMessage--- On Mon, Sep 15, 2014 at 11:04:34AM +0200, Aurelien Jarno wrote: On Mon, Sep 15, 2014 at 01:42:04AM +0200, Michael Banck wrote: Hi, On Sun, Aug 03, 2014 at 01:53:00PM +0200, Cyril Brulebois wrote: Source: ergo Version: 3.4.0-1 Severity: serious Justification: FTBFS Hi, everything is in the subject, full summary: https://buildd.debian.org/status/package.php?p=ergosuite=sid Direct links to failing build logs: https://buildd.debian.org/status/fetch.php?pkg=ergoarch=mipsver=3.4.0-1stamp=1406494180 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=mipselver=3.4.0-1stamp=1406450302 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=powerpcver=3.4.0-1stamp=1406399761 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=s390xver=3.4.0-1stamp=1406400721 So mips and s390x have built fine now, and I just tried on the powerpc porterbox (partch) without issues. As this was a timeout during the test suite, a simple rebuild might helpe, preferably on a speedy machine. CCing the powerpc and mipsel buildd maintainers for that. Done for powerpc. Thanks to everybody, seems all arches built fine now. Michael---End Message---
Bug#761483: marked as done (libstarpu-1.1-7 and libstarpu-1.1-6: error when trying to install together)
Your message dated Mon, 15 Sep 2014 10:19:54 + with message-id e1xttny-0002kd...@franck.debian.org and subject line Bug#761483: fixed in starpu 1.1.3+dfsg-2 has caused the Debian Bug report #761483, regarding libstarpu-1.1-7 and libstarpu-1.1-6: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 761483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libstarpu-1.1-6,libstarpu-1.1-7 Version: libstarpu-1.1-6/1.1.2+dfsg-1+b1 Version: libstarpu-1.1-7/1.1.3+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-09-14 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libamd2.3.1:amd64. (Reading database ... 10869 files and directories currently installed.) Preparing to unpack .../libamd2.3.1_1%3a4.2.1-3_amd64.deb ... Unpacking libamd2.3.1:amd64 (1:4.2.1-3) ... Selecting previously unselected package libcolamd2.8.0:amd64. Preparing to unpack .../libcolamd2.8.0_1%3a4.2.1-3_amd64.deb ... Unpacking libcolamd2.8.0:amd64 (1:4.2.1-3) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libltdl7:amd64. Preparing to unpack .../libltdl7_2.4.2-1.10_amd64.deb ... Unpacking libltdl7:amd64 (2.4.2-1.10) ... Selecting previously unselected package libglpk36:amd64. Preparing to unpack .../libglpk36_4.55-1_amd64.deb ... Unpacking libglpk36:amd64 (4.55-1) ... Selecting previously unselected package libnuma1:amd64. Preparing to unpack .../libnuma1_2.0.10~rc2-1_amd64.deb ... Unpacking libnuma1:amd64 (2.0.10~rc2-1) ... Selecting previously unselected package libhwloc5:amd64. Preparing to unpack .../libhwloc5_1.9.1-1_amd64.deb ... Unpacking libhwloc5:amd64 (1.9.1-1) ... Selecting previously unselected package ocl-icd-libopencl1:amd64. Preparing to unpack .../ocl-icd-libopencl1_2.1.3-5_amd64.deb ... Unpacking ocl-icd-libopencl1:amd64 (2.1.3-5) ... Selecting previously unselected package libstarpu-1.1-6. Preparing to unpack .../libstarpu-1.1-6_1.1.2+dfsg-1+b1_amd64.deb ... Unpacking libstarpu-1.1-6 (1.1.2+dfsg-1+b1) ... Selecting previously unselected package libstarpu-1.1-7. Preparing to unpack .../libstarpu-1.1-7_1.1.3+dfsg-1_amd64.deb ... Unpacking libstarpu-1.1-7 (1.1.3+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libstarpu-1.1-7_1.1.3+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libstarpu-1.1.so.7', which is also in package libstarpu-1.1-6 1.1.2+dfsg-1+b1 Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: /var/cache/apt/archives/libstarpu-1.1-7_1.1.3+dfsg-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/lib/libstarpu-1.1.so.7 This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Source: starpu Source-Version: 1.1.3+dfsg-2 We believe that the bug you reported is fixed in the latest version of starpu, 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
Bug#760780: lazygal: fails to generate gallery: list index out of range
1) After an update one of lazygal's dependencies, the following
program fails. Maybe it is not good to mix gi bindings with old ones.
This is a change in either Gstreamer or GObject.
$ cat gst-import-error.py
#!/usr/bin/env python
from gi.repository import GObject
import gobject
import pygst
pygst.require('0.10')
import gst
$ ./gst-import-error.py
Traceback (most recent call last):
File ./gst-import-error.py, line 7, in module
import gst
File /usr/lib/python2.7/dist-packages/gst-0.10/gst/__init__.py,
line 193, in module
from _gst import *
ImportError: could not import gobject (could not find _PyGObject_API object)
2) The failure to import gst highlighted a bug in lazygal (fix: [1])
and I just released 0.8.5 to fix this. But video transcoding still
won't work.
0.8.6 restore lazygal working without gobject.
Alex
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761383: marked as done (python-xstatic-angular-cookies: not installable in sid)
Your message dated Mon, 15 Sep 2014 11:00:08 + with message-id e1xtu0u-ng...@franck.debian.org and subject line Bug#761383: fixed in python-xstatic-jquery.bootstrap.wizard 1.0.0.1-1 has caused the Debian Bug report #761383, regarding python-xstatic-angular-cookies: not installable in sid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 761383: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-xstatic-angular-cookies Affects: python3-xstatic-angular-cookies Version: 1.2.16.1-2 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hello PKG OpenStack team, it seams that I forgot to send in this bug report: python-xstatic-angular-cookies is currently not installable in sid since it depends on libjs-angularjs ( 1.2.17). However, we have libjs-angularjs version 1.2.23-1 in sid since 2014-08-23. The same holds for the python3-xstatic-angular-cookies package in the same source package. Cheers -Ralf. ---End Message--- ---BeginMessage--- Source: python-xstatic-jquery.bootstrap.wizard Source-Version: 1.0.0.1-1 We believe that the bug you reported is fixed in the latest version of python-xstatic-jquery.bootstrap.wizard, 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated python-xstatic-jquery.bootstrap.wizard 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, 06 Sep 2014 17:49:46 +0800 Source: python-xstatic-jquery.bootstrap.wizard Binary: python-xstatic-jquery.bootstrap.wizard python3-xstatic-jquery.bootstrap.wizard Architecture: source all Version: 1.0.0.1-1 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: python-xstatic-jquery.bootstrap.wizard - JQuery.Bootstrap.Wizard XStatic support - Python 2.x python3-xstatic-jquery.bootstrap.wizard - JQuery.Bootstrap.Wizard XStatic support - Python 3.x Closes: 761383 Changes: python-xstatic-jquery.bootstrap.wizard (1.0.0.1-1) unstable; urgency=medium . * Initial release (Closes: #761383). Checksums-Sha1: 1574c251899ae6072d3a37408f98e82f695bcf70 2492 python-xstatic-jquery.bootstrap.wizard_1.0.0.1-1.dsc b569b3aa284f371cf2add9843df05567a11cd10e 4136 python-xstatic-jquery.bootstrap.wizard_1.0.0.1.orig.tar.xz 883f166956a34ca35cc5f6fc1e8eb7a025a2683e 3320 python-xstatic-jquery.bootstrap.wizard_1.0.0.1-1.debian.tar.xz 2b788a0db7d7ba19a2d6e9a9af1e5ba8c1bd14df 5008 python-xstatic-jquery.bootstrap.wizard_1.0.0.1-1_all.deb d2c0d15da33bef7caeaf33dc0135c3365df18078 4896 python3-xstatic-jquery.bootstrap.wizard_1.0.0.1-1_all.deb Checksums-Sha256: 7ddac5156cf6429b684a2d6a56fdba01871bc57e9afbaaf9a8cc81f45d6b8483 2492 python-xstatic-jquery.bootstrap.wizard_1.0.0.1-1.dsc 3562f96f58b783fd089c5774c2e34661ae6070169c90039ac2dd3bbfd8434cf6 4136 python-xstatic-jquery.bootstrap.wizard_1.0.0.1.orig.tar.xz 0d8001f544d34eb02f7a7e8686e75fbff37d6a022b9ed0141678c139d169ac09 3320 python-xstatic-jquery.bootstrap.wizard_1.0.0.1-1.debian.tar.xz f1c4a7f1e97eceeb7ea74e6aa2ac722b81dad8aee0a3a649f2c206cd5710b8d6 5008 python-xstatic-jquery.bootstrap.wizard_1.0.0.1-1_all.deb c3fb523292815356ee1a445025d8a62e42dca8457bdd435597f2ef7c47fd8ad7 4896 python3-xstatic-jquery.bootstrap.wizard_1.0.0.1-1_all.deb Files: 0ae67a7ab3a151b8859468eba602f8fb 5008 python optional python-xstatic-jquery.bootstrap.wizard_1.0.0.1-1_all.deb eee4116da4cae4466fd8ca988e0578c4 4896 python optional python3-xstatic-jquery.bootstrap.wizard_1.0.0.1-1_all.deb 0ec6a0cb7319cc19bc5e7dcc6db89ae5 2492 python optional python-xstatic-jquery.bootstrap.wizard_1.0.0.1-1.dsc b23b222f082d1d931f891a4a577322f9 4136 python optional python-xstatic-jquery.bootstrap.wizard_1.0.0.1.orig.tar.xz 5871cf1731e60f097e62422863a5b976 3320 python optional python-xstatic-jquery.bootstrap.wizard_1.0.0.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1
Bug#761529: soundscaperenderer: FTBFS: misc.h:102:41: internal compiler error: in convert_move, at expr.c:331
hi.
thanks for your bug-report.
however, ...
On 2014-09-14 17:09, David Suárez wrote:
Source: soundscaperenderer
Version: 0.4.2~dfsg-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140913 qa-ftbfs
Justification: FTBFS on amd64
[...]
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/09/13/soundscaperenderer_0.4.2~dfsg-1_unstable.log
..., when i check the build-logs, i see:
/«PKGBUILDDIR»/./src/../apf/apf/misc.h:102:41: internal compiler error: in
convert_move, at expr.c:331
, _old{std::forwardArgs(args)...}
^
Please submit a full bug report,
with preprocessed source if appropriate.
See file:///usr/share/doc/gcc-4.9/README.Bugs for instructions.
Preprocessed source stored into /tmp/cctt0rFc.out file, please attach
this to
your bugreport.
make[3]: *** [ssr_binaural.o] Error 1
which indicates, that the problem is not related to
soundscaperenderer, but either is an internal problem of the compiler
(as the error message indicates) or a problem with the build-host.
fgmasdr
IOhannes
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761646: zemberek-server: missing dependency on dbus
Package: zemberek-server Version: 0.7.1-12.1 Severity: serious Even after fixing #706928, zemberek-server does not start: org.freedesktop.dbus.exceptions.DBusException: Failed to connect to bus No such file or directory at org.freedesktop.dbus.DBusConnection.init(DBusConnection.java:304) at org.freedesktop.dbus.DBusConnection.getConnection(DBusConnection.java:282) at net.zemberekserver.server.dbus.ZemberekDbus.start(Unknown Source) at net.zemberekserver.server.ZemberekServer.initDBusServer(Unknown Source) at net.zemberekserver.server.ZemberekServer.main(Unknown Source) Installing dbus fixes the problem. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-1-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages zemberek-server depends on: ii adduser 3.113+nmu3 ii default-jre-headless 2:1.7-52 ii libcommons-logging-java 1.2-1 ii libdbus-java 2.8-5 ii libmatthew-debug-java0.7.3-1 ii libmina-java 1.1.7.dfsg-11 ii libslf4j-java1.7.7-1 ii libunixsocket-java 0.7.3-1 ii libzemberek-java 2.1.1-8.1 ii libzemberek-tr-java 2.1.1-8.1 Versions of packages zemberek-server recommends: pn zpspell none -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726799: #726799: not a shared-mime-info bug726...@bugs.debian.org
On Sun, Sep 14, 2014 at 01:44:01PM +0200, Pino Toscano wrote: On 2014-09-14 13:28, Yann Dirson wrote: On Sun, Sep 14, 2014 at 10:12:41AM +0200, Pino Toscano wrote: Hi, first of all, the behaviour of update-mime-database is correct: it deletes files in *generated* directories. Yes, the various application, audio, text, subdirectories under /usr/share/mime are business of update-mime-database, where it places the XML mimetypes generated from the XML definitions in /usr/share/mime/packages. It is exactly in this directory where applications should install XML definitions of mime types to have them registered in the XDG mime type system. Installing stuff directly to e.g. /usr/share/mime/text is like installing to, say, /var/cache (i.e., you shouldn't). Furthermore, qgo is installing wrong things, and I will send the proper explanation and fix to #749582. This is not a bug in shared-mime-info, hence closing. Ah, that's interesting. But then: * why are those directories in /usr/ and not in /var/ in the first place ? Isn't this part of the shared-mime-info spec against the spirit of the FHS ? Possibly, although changing at this point is not exactly an easy task. Well, if it's just a cache, there should not be too much problems, I guess. If any of this has to be used externally (ie. has been made part of an official API), then probably symlinks to /var would have to be generated for some transition period - but we've been through a number of more disruptive transitions, I'd say :) * if it is deemed the right place for generated files, then we surely want a lintian check to spot the problem early Feel free to file a wishlist bug for lintian. Done. * the update-mime-database manpage is quite terse, and does not explain that different parts of MIME-DIR have different roles. It is awkward to have to read the spec to get such important information I guess you are referring to the update-mime-database man page, right? This seems just specific to the tool itself, so IMHO what it lacks is pointers to the specifications. Another option would be having the specifications themselves as man page. -- Pino Toscano -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761650: llvm-toolchain-3.5: FTBFS on kfreebsd
Source: llvm-toolchain-3.5 Version: 1:3.5-1 Severity: serious Justification: fails to build from source Hi, your package no longer builds on kfreebsd: debian/rules override_dh_install make[1]: Entering directory '/«PKGBUILDDIR»' dh_install --fail-missing cp: cannot stat 'debian/tmp/usr/lib/llvm-3.5/bin/lldb-mi': No such file or directory dh_install: cp -a debian/tmp/usr/lib/llvm-3.5/bin/lldb-mi debian/lldb-3.5//usr/lib/llvm-3.5/bin/ returned exit code 1 make[1]: *** [override_dh_install] Error 2 debian/rules:362: recipe for target 'override_dh_install' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [binary-arch] Error 2 debian/rules:129: recipe for target 'binary-arch' failed Cheers, Julien signature.asc Description: Digital signature
Bug#761650: llvm-toolchain-3.5: FTBFS on kfreebsd
On 15/09/2014 14:14, Julien Cristau wrote: Source: llvm-toolchain-3.5 Version: 1:3.5-1 Severity: serious Justification: fails to build from source Hi, your package no longer builds on kfreebsd: debian/rules override_dh_install make[1]: Entering directory '/«PKGBUILDDIR»' dh_install --fail-missing cp: cannot stat 'debian/tmp/usr/lib/llvm-3.5/bin/lldb-mi': No such file or directory dh_install: cp -a debian/tmp/usr/lib/llvm-3.5/bin/lldb-mi debian/lldb-3.5//usr/lib/llvm-3.5/bin/ returned exit code 1 make[1]: *** [override_dh_install] Error 2 debian/rules:362: recipe for target 'override_dh_install' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [binary-arch] Error 2 debian/rules:129: recipe for target 'binary-arch' failed I have a pending patch for that. I was waiting for other potential bugs before uploading a fix. Cheers, Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761650: llvm-toolchain-3.5: FTBFS on kfreebsd
On Mon, Sep 15, 2014 at 14:20:18 +0200, Sylvestre Ledru wrote: On 15/09/2014 14:14, Julien Cristau wrote: Source: llvm-toolchain-3.5 Version: 1:3.5-1 Severity: serious Justification: fails to build from source Hi, your package no longer builds on kfreebsd: debian/rules override_dh_install make[1]: Entering directory '/«PKGBUILDDIR»' dh_install --fail-missing cp: cannot stat 'debian/tmp/usr/lib/llvm-3.5/bin/lldb-mi': No such file or directory dh_install: cp -a debian/tmp/usr/lib/llvm-3.5/bin/lldb-mi debian/lldb-3.5//usr/lib/llvm-3.5/bin/ returned exit code 1 make[1]: *** [override_dh_install] Error 2 debian/rules:362: recipe for target 'override_dh_install' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [binary-arch] Error 2 debian/rules:129: recipe for target 'binary-arch' failed I have a pending patch for that. I was waiting for other potential bugs before uploading a fix. Great, thanks. We (well, Andreas Boll) noticed because it causes FTBFS for mesa/experimental, as the build pulls in the old svn version from the snapshot package. Cheers, Julien signature.asc Description: Digital signature
Bug#759971: marked as done (plastimatch: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libhdf5.so', needed by 'bragg_curve'. Stop.)
Your message dated Mon, 15 Sep 2014 14:34:32 +0200 with message-id 20140915123432.ga6...@an3as.eu and subject line Closing the bug since it builds fine has caused the Debian Bug report #759971, regarding plastimatch: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libhdf5.so', needed by 'bragg_curve'. Stop. 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.) -- 759971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: plastimatch Version: 1.5.16+dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[3]: Entering directory '/«BUILDDIR»/plastimatch-1.5.16+dfsg/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /«BUILDDIR»/plastimatch-1.5.16+dfsg/obj-x86_64-linux-gnu/CMakeFiles 8 make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libhdf5.so', needed by 'dlib_train'. Stop. [ 83%] Building CXX object src/plastimatch/cli/CMakeFiles/landmark_warp.dir/landmark_warp_main.cxx.o make[3]: *** Waiting for unfinished jobs cd /«BUILDDIR»/plastimatch-1.5.16+dfsg/obj-x86_64-linux-gnu/src/plastimatch/cli /usr/bin/c++ -DITK_IO_FACTORY_REGISTER_MANAGER -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/cli -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/obj-x86_64-linux-gnu/src/plastimatch -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/util -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/sys -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/segment -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/register/cuda -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/register -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/reconstruct/cuda -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/reconstruct -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/qt -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/opencl -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/cuda -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/dose -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/clp -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/base -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/obj-x86_64-linux-gnu -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/obj-x86_64-linux-gnu/ITKIOFactoryRegistration -I/home/steve/Packages/debian-med/trunk/packages/insighttoolkit/build-area/insighttoolkit4-4.6.0/BUILD/Modules/ThirdParty/HDF5/src -I/usr/include/dcmtk -I/usr/include/dcmtk/oflog -I/usr/include/dcmtk/ofstd -I/usr/include/dcmtk/dcmtls -I/usr/include/dcmtk/dcmsr -I/usr/include/dcmtk/dcmsign -I/usr/include/dcmtk/dcmqrdb -I/usr/include/dcmtk/dcmpstat -I/usr/include/dcmtk/dcmnet -I/usr/include/dcmtk/dcmjpls -I/usr/include/dcmtk/dcmjpeg -I/usr/include/dcmtk/dcmimgle -I/usr/include/dcmtk/dcmimage -I/usr/include/dcmtk/dcmdata -I/usr/include/dcmtk/config -I/usr/include/x86_64-linux-gnu -I/usr/include/gdcm-2.4 -I/usr/include/ITK-4.6 -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/itk-3.20.0 -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/demons_itk_insight -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/demons_itk_insight/DiffeomorphicDemons -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/demons_itk_insight/FastSymmetricForces -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/demons_itk_insight/LOGDomainDemons -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/nSIFT -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/bstrlib-05122010 -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/dlib-17.46 -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/liblbfgs-1.9/include -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/ransac -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/ransac/Common -I/«BUILDDIR»/plastimatch-1.5.16+dfsg/libs/lua-5.1.4/src-o CMakeFiles/landmark_warp.dir/landmark_warp_main.cxx.o -c /«BUILDDIR»/plastimatch-1.5.16+dfsg/src/plastimatch/cli/landmark_warp_main.cxx [ 84%] Building CXX object src/plastimatch/standalone/CMakeFiles/compute_distance.dir/compute_distance.cxx.o cd /«BUILDDIR»/plastimatch-1.5.16+dfsg/obj-x86_64-linux-gnu/src/plastimatch/standalone /usr/bin/c++ -DITK_IO_FACTORY_REGISTER_MANAGER -g -O2 -fstack-protector-strong
Bug#761371: virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds
On 15/09/14 09:40, Emilio Pozuelo Monfort wrote: So what should we do here? Should that patch be updated on virtuoso-opensource? Or can netstat be fixed on kbsd? This is blocking the imagemagick transition. Hi; I've attached an updated patch for virtuoso-opensource. (There were two new tests needing this change). There's no simple 'fix' for netstat as implemented right now, because there are still cases (e.g in chroot jail) where reading /dev/mem is not expected to be allowed, even with setuid root. Regards, -- Steven Chamberlain ste...@pyro.eu.org Author: Steven Chamberlain ste...@pyro.eu.org Author: José Manuel SantamarÃa Lema panfa...@gmail.com Description: This patch avoids FTBFSes on any architecture whose netstat -an output is not what we expect or just wrong, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663010 NOTE: While this patch at a first sight looks a bit dangerous it isn't that bad: if virtuoso couldn't actually start in these make_vad.sh scripts, some *.vad files wouldn't be genereated; these *.vad files are being installed by the package, therefore if one of them is missing the package would fail to build anyway. --- a/binsrc/rdf_mappers/make_vad.sh +++ b/binsrc/rdf_mappers/make_vad.sh @@ -278,8 +278,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG ***FAILED: Could not start Virtuoso Server within $timeout seconds - exit 1 + LOG ***WARNING: Could not start Virtuoso Server within $timeout seconds + return 1 fi done } --- a/binsrc/bpel/make_vad.sh +++ b/binsrc/bpel/make_vad.sh @@ -281,8 +281,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG ***FAILED: Could not start Virtuoso Server within $timeout seconds - exit 1 + LOG ***WARNING: Could not start Virtuoso Server within $timeout seconds + return 1 fi done } --- a/binsrc/b3s/make_vad.sh +++ b/binsrc/b3s/make_vad.sh @@ -231,8 +231,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG ***FAILED: Could not start Virtuoso Server within $timeout seconds - exit 1 + LOG ***WARNING: Could not start Virtuoso Server within $timeout seconds + return 1 fi done } --- a/binsrc/tutorial/make_vad.sh +++ b/binsrc/tutorial/make_vad.sh @@ -131,8 +131,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG ***FAILED: Could not start $SERVER within $timeout seconds - exit 1 + LOG ***WARNING: Could not start $SERVER within $timeout seconds + return 1 fi done } --- a/binsrc/yacutia/mkvad.sh +++ b/binsrc/yacutia/mkvad.sh @@ -178,8 +178,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then -ECHO ***FAILED: Could not start Virtuoso Server within $timeout seconds -exit 1 +ECHO ***WARNING: Could not start Virtuoso Server within $timeout seconds +return 1 fi done } --- a/binsrc/samples/demo/mkdoc.sh +++ b/binsrc/samples/demo/mkdoc.sh @@ -191,8 +191,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - ECHO ***FAILED: Could not start Virtuoso DOC Server within $timeout seconds - exit 1 + ECHO ***WARNING: Could not start Virtuoso DOC Server within $timeout seconds + return 1 fi done fi --- a/binsrc/samples/sparql_demo/make_vad.sh +++ b/binsrc/samples/sparql_demo/make_vad.sh @@ -141,8 +141,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG ***FAILED: Could not start $SERVER within $timeout seconds - exit 1 + LOG ***WARNING: Could not start $SERVER within $timeout seconds + return 1 fi done } --- a/binsrc/sync/make_vad.sh +++ b/binsrc/sync/make_vad.sh @@ -131,8 +131,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG ***FAILED: Could not start Virtuoso Server within $timeout seconds - exit 1 + LOG ***WARNING: Could not start Virtuoso Server within $timeout seconds + return 1 fi done } --- a/binsrc/isparql/make_vad.sh +++ b/binsrc/isparql/make_vad.sh @@ -144,8 +144,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG ***FAILED: Could not start $SERVER within $timeout seconds - exit 1 + LOG ***WARNING: Could not start $SERVER within $timeout seconds + return 1 fi done } --- a/appsrc/ODS-Addressbook/make_vad.sh +++ b/appsrc/ODS-Addressbook/make_vad.sh @@ -170,8 +170,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG ***FAILED: Could not start $SERVER within $timeout seconds - exit 1 + LOG ***WARNING: Could not start $SERVER within $timeout seconds + return 1 fi done } --- a/appsrc/ODS-Bookmark/make_vad.sh +++ b/appsrc/ODS-Bookmark/make_vad.sh @@ -170,8 +170,8
Bug#761040: [libqtwebkit4] Browsers based on Webkit crash on loading pages
Version: 2.3.2.dfsg-4 Both qtwebkit and phonon-backend-gstreamer have been updated to use GStreamer 1.0, so this should have been fixed by this. I'm so closing this bug. Please feel free to submit another bug if after upgrading your system you can still find issues (a new bug here will mean reportbug will give us some data we need). Thanks for your bug report! -- I wish to be cremated. One tenth of my ashes shall be given to my agent, as written in our contract. -- Groucho Marx Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#761040: marked as done ([libqtwebkit4] Browsers based on Webkit crash on loading pages)
Your message dated Mon, 15 Sep 2014 10:55:15 -0300 with message-id 4952273.bjR9St42ao@luna and subject line Re: Bug#761040: [libqtwebkit4] Browsers based on Webkit crash on loading pages has caused the Debian Bug report #761040, regarding [libqtwebkit4] Browsers based on Webkit crash on loading pages 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.) -- 761040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libqtwebkit4 Version: 2.3.2.dfsg-3 Severity: grave From several days ago browsers based on webkit I use (Konqueror and Qupzilla) crashed when loading pages. I confirm that this package are main suspect because both browsers used it and it's his only common dependency. Furthermore, change Konqueror to use Khtml as web engine make it don't crash. I attach a crash-log from Qupzilla. A briefly crash run: - Open default blank start page, browsers are ok. Try to load any page, start to load and then, suddenly, crash. - On Konqueror, I can use it as file manager without problems. If you want I make some more test, please, ask for them. Thanks so much. Best regards. Salud y Revolución. Lobo. --- System information. --- Architecture: powerpc Kernel: Linux 3.16-1-powerpc Debian Release: jessie/sid 500 unstableftp2.fr.debian.org 500 unstableftp.es.debian.org 500 unstableftp.de.debian.org 1 experimentalftp2.fr.debian.org 1 experimentalftp.es.debian.org --- Package information. --- Depends(Version) | Installed -+-= libc6 (= 2.4) | 2.19-10 libgcc1 (= 1:4.2.1) | 1:4.9.1-13 libglib2.0-0 (= 2.31.8) | 2.40.0-5 libgstreamer-plugins-base0.10-0 (= 0.10.31) | 0.10.36-1.3 libgstreamer0.10-0 (= 0.10.31) | 0.10.36-1.4 libqt4-network (= 4:4.8.1) | 4:4.8.6+git64-g5dc8b2b+dfsg-2 libqtcore4 (= 4:4.8.4) | 4:4.8.6+git64-g5dc8b2b+dfsg-2 libqtgui4 (= 4:4.8.1) | 4:4.8.6+git64-g5dc8b2b+dfsg-2 libsqlite3-0 (= 3.5.9) | 3.8.6-1 libstdc++6(= 4.1.1) | 4.9.1-13 libx11-6 | 2:1.6.2-3 libxrender1 | 1:0.9.8-1 Package's Recommends field is empty. Package's Suggests field is empty. -- Libertad es poder elegir en cualquier momento. Ahora yo elijo GNU/Linux, para no atar mis manos con las cadenas del soft propietario. Porque la libertad no es tu derecho, es tu responsabilidad. http://www.mucharuina.com - Desde El Ejido, en Almería, usuario registrado Linux #294013 http://www.counter.li.org Time: mié sep 10 10:33:45 2014 Qt version: 4.8.6 (compiled with 4.8.6) QupZilla version: 1.6.6 WebKit version: 537.21 == BACKTRACE == #0: qupzilla(+0x2798) [0x20559798] #1: linux-vdso32.so.1(__kernel_sigtramp32+0) [0x100394] #2: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0x1b44e00) [0x1f67ae00] #3: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0x1b46990) [0x1f67c990] #4: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0x1b2ca70) [0x1f662a70] #5: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0x1be7d54) [0x1f71dd54] #6: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0x3de150) [0x1df14150] #7: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0x3de538) [0x1df14538] #8: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0x66bdc8) [0x1e1a1dc8] #9: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0x8c52a0) [0x1e3fb2a0] #10: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0x8c590c) [0x1e3fb90c] #11: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0x8c5ea4) [0x1e3fbea4] #12: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0x8af524) [0x1e3e5524] #13: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0xa457e8) [0x1e57b7e8] #14: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0xa4b35c) [0x1e58135c] #15: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0xac9198) [0x1e5ff198] #16: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0xab996c) [0x1e5ef96c] #17: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0xf72e04) [0x1eaa8e04] #18: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0xf725dc) [0x1eaa85dc] #19: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0xf72744) [0x1eaa8744] #20: /usr/lib/powerpc-linux-gnu/libQtWebKit.so.4(+0xf72828) [0x1eaa8828] #21: /usr/lib/powerpc-linux-gnu/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x328) [0x1c819e58]
Bug#761371: virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds
On Monday 15 September 2014 14:33:33 Steven Chamberlain wrote: On 15/09/14 09:40, Emilio Pozuelo Monfort wrote: So what should we do here? Should that patch be updated on virtuoso-opensource? Or can netstat be fixed on kbsd? This is blocking the imagemagick transition. Hi; I've attached an updated patch for virtuoso-opensource. (There were two new tests needing this change). There's no simple 'fix' for netstat as implemented right now, because there are still cases (e.g in chroot jail) where reading /dev/mem is not expected to be allowed, even with setuid root. Steven: if I understand your patch correctly the tests will suceed even if failing on archs which don't suffer from this bug. If that's the case this is not a solution, the bug lies in netstat. But I would certainly don't mind this for virtuoso. Kinds regards, Lisandro. -- In college, I cooked some hot dogs by putting metal forks in each end of the hot dog and running 120 volts through it. Hot dogs have just enough conductivity so that this works well greenroom(576281) - on a truly geeky way to cook hot dogs. Posted in Slashdot, also found in The Open Source Cookbook for Geeks. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#758650: marked as done (SciDAVis violates DFSG)
Your message dated Sun, 14 Sep 2014 23:52:17 +0200 with message-id 20140914215217.ga30...@georges.khaznadar.fr and subject line Scidavis does not use nrutil.cpp has caused the Debian Bug report #758650, regarding SciDAVis violates DFSG 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.) -- 758650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: scidavis Version: 0.2.4-3.3 Severity: serious The files scidavis/src/nrutil.cpp and .h in SciDAVis (a QtiPlot fork) contain substantial verbatim portions of code from the Numerical Recipes book. The license of the code from the Numerical Recipes book blatantly conflicts with Debian DFSG, by explicitly restricting or forbidding distribution of the source code. License text of Numerical Recipes, for reference: http://www.nr.com/aboutNR3license.html At the time of writing, using the following terms in the Google search engine, a version of the Numerical Recipes book can be found, which can perhaps be used to verify how the code in nrutil.cpp contains verbatim copies of substantial portions of the code in the book: Numerical Recipes filetype:pdf Possible fixes: - Its parent project QtiPlot had the same problem, and that part of the code has been rewritten somewhere between version 0.9.6.2 and 0.9.8.8 to use the free GSL library instead (GNU Scientific Library, included in Debian). Merge the changes from QtiPlot to SciDAVis, to get rid of the file. - Remove the functionality that nrutil.cpp provides. Such functionality includes at least the Savitzky-Golay smoothing method, and possibly more. - Remove the package entirely from Debian. ---End Message--- ---BeginMessage--- I could chack that beginning with the version 1.D5 of scidavis, there are no longer files like nrutil.* in the upstream package. So the bugreport can be closed for scidavis = 1.D5 Best regards, Georges. -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: Digital signature ---End Message---
Bug#761371: virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds
On Monday 15 September 2014 10:58:36 Lisandro Damián Nicanor Pérez Meyer wrote: On Monday 15 September 2014 14:33:33 Steven Chamberlain wrote: On 15/09/14 09:40, Emilio Pozuelo Monfort wrote: So what should we do here? Should that patch be updated on virtuoso-opensource? Or can netstat be fixed on kbsd? This is blocking the imagemagick transition. Hi; I've attached an updated patch for virtuoso-opensource. (There were two new tests needing this change). There's no simple 'fix' for netstat as implemented right now, because there are still cases (e.g in chroot jail) where reading /dev/mem is not expected to be allowed, even with setuid root. Steven: if I understand your patch correctly the tests will suceed even if failing on archs which don't suffer from this bug. If that's the case this is not a solution, the bug lies in netstat. But I would certainly don't mind this for virtuoso. OK, Maxy just explained me that this patch will still work, although the time spent on the builds will be too much :-/ (netstat is there to speed up this). -- 4: Que es un icono * Un caballono Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#761371: virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds
On 15/09/14 15:04, Lisandro Damián Nicanor Pérez Meyer wrote: OK, Maxy just explained me that this patch will still work, although the time spent on the builds will be too much :-/ (netstat is there to speed up this). On arches where `netstat -ntlp` is working as non-privileged user, this should still be fast, with this patch. Only where netstat is not working, yes it will be slow, but eventually run the tests (instead of the build failing, on kfreebsd). Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Bug#759973: marked as done (nifti2dicom: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libhdf5.so', needed by 'src/core/nifti2dicom'. Stop.)
Your message dated Mon, 15 Sep 2014 16:19:26 +0200 with message-id 5416f56e.2090...@gmail.com and subject line Re: Bug#759973: nifti2dicom: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libhdf5.so', needed by 'src/core/nifti2dicom'. Stop. has caused the Debian Bug report #759973, regarding nifti2dicom: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libhdf5.so', needed by 'src/core/nifti2dicom'. Stop. 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.) -- 759973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: nifti2dicom Version: 0.4.8-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 3 [ 47%] Building CXX object src/core/CMakeFiles/nifti2dicom.dir/nifti2dicom.cxx.o cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/core /usr/bin/g++ -DITK_IO_FACTORY_REGISTER_MANAGER -DvtkFiltersFlowPaths_AUTOINIT=1(vtkFiltersParallelFlowPaths) -DvtkIOExodus_AUTOINIT=1(vtkIOParallelExodus) -DvtkIOGeometry_AUTOINIT=1(vtkIOMPIParallel) -DvtkIOImage_AUTOINIT=1(vtkIOMPIImage) -DvtkIOSQL_AUTOINIT=2(vtkIOMySQL,vtkIOPostgreSQL) -DvtkRenderingCore_AUTOINIT=4(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingFreeTypeOpenGL,vtkRenderingOpenGL) -DvtkRenderingFreeType_AUTOINIT=2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib) -DvtkRenderingLIC_AUTOINIT=1(vtkRenderingParallelLIC) -DvtkRenderingVolume_AUTOINIT=1(vtkRenderingVolumeOpenGL) -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -Wno-deprecated -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/ITKIOFactoryRegistration -I/home/steve/Packages/debian-med/trunk/packages/insighttoolkit/build-area/insighttoolkit4-4.6.0/BUILD/Modules/ThirdParty/HDF5/src -I/usr/include/dcmtk -I/usr/include/dcmtk/oflog -I/usr/include/dcmtk/ofstd -I/usr/include/dcmtk/dcmtls -I/usr/include/dcmtk/dcmsr -I/usr/include/dcmtk/dcmsign -I/usr/include/dcmtk/dcmqrdb -I/usr/include/dcmtk/dcmpstat -I/usr/include/dcmtk/dcmnet -I/usr/include/dcmtk/dcmjpls -I/usr/include/dcmtk/dcmjpeg -I/usr/include/dcmtk/dcmimgle -I/usr/include/dcmtk/dcmimage -I/usr/include/dcmtk/dcmdata -I/usr/include/dcmtk/config -I/usr/include/x86_64-linux-gnu -I/usr/include/gdcm-2.4 -I/usr/include/ITK-4.6 -I/usr/include/vtk-6.1 -I/usr/include/python2.7 -I/usr/include/freetype2 -I/usr/include/jsoncpp -I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi -I/usr/include/hdf5/serial -I/usr/include/libxml2 -I/usr/include/tcl -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu-o CMakeFiles/nifti2dicom.dir/nifti2dicom.cxx.o -c /«PKGBUILDDIR»/src/core/nifti2dicom.cxx make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libhdf5.so', needed by 'src/core/nifti2dicom'. Stop. make[3]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu' make[2]: *** [src/core/CMakeFiles/nifti2dicom.dir/all] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/08/30/nifti2dicom_0.4.8-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. The build was done with DEB_BUILD_OPTIONS=parallel=4, so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure. ---End Message--- ---BeginMessage--- X-CrossAssassin-Score: 41563---End Message---
Processed: Retitle
Processing commands for cont...@bugs.debian.org: retitle 761418 netstat needs to be able to read from /dev/mem Bug #761418 [freebsd-net-tools] virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds Changed Bug title to 'netstat needs to be able to read from /dev/mem' from 'virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds' thanks Stopping processing here. Please contact me if you need assistance. -- 761418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761418 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#759576: sflphone does not start
Hi, On Thu, Aug 28, 2014 at 01:07:12PM -0500, Carlos Prieto wrote: Source: sflphone Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I tried to start sflphone, from the graphic interface and from the command line. * What exactly did you do (or not do) that was effective (or ineffective)? The program did not start. * What was the outcome of this action? The console kept waiting for about 20 seconds. After that, the shell prompt started again, without any message. * What outcome did you expect instead? The program should start Thanks for your report According to Upstream, this issue has been fixed in version 1.4.0. Version 1.4.1 should be released in a few days and it makes sense to wait for it. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758778: Lilypond-doc
Hi! On Sat, 2014-09-13 at 15:41:04 +, Golden Chariot Charterers wrote: Thank you for all the detailed explanations and your efforts. 3.Please kindly point me to how we can get this fixed or what is the next course of action. Please, upgrade to lilypond-doc 2.18.2-1, which fixes this issue. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 753643 is serious
Processing commands for cont...@bugs.debian.org: severity 753643 serious Bug #753643 [munge] slurm-llnl: Package not installable on unstable Bug #761651 [munge] munge: post-installation fails with systemd Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 753643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753643 761651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761651 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: blocks
Processing commands for cont...@bugs.debian.org: block 756017 with 673727 Bug #756017 [wnpp] RFP: bokeh -- interactive visualization for web browsers 756017 was not blocked by any bugs. 756017 was not blocking any bugs. Added blocking bug(s) of 756017: 673727 block 756017 with 699435 Bug #756017 [wnpp] RFP: bokeh -- interactive visualization for web browsers 756017 was blocked by: 673727 756017 was not blocking any bugs. Added blocking bug(s) of 756017: 699435 thanks Stopping processing here. Please contact me if you need assistance. -- 756017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756017 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#761484: marked as done (git-annex: FTBFS on several architectures)
Your message dated Mon, 15 Sep 2014 15:21:20 + with message-id e1xty5g-hp...@franck.debian.org and subject line Bug#761484: fixed in git-annex 5.20140915 has caused the Debian Bug report #761484, regarding git-annex: FTBFS on several architectures 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.) -- 761484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: git-annex version: 5.20140831 severity: serious Hi, The binNMU's of git-annex failed on armel and mipsel. The build failure on ppc64el looks similar. https://buildd.debian.org/status/package.php?p=git-annex Cheers, Ivo ---End Message--- ---BeginMessage--- Source: git-annex Source-Version: 5.20140915 We believe that the bug you reported is fixed in the latest version of git-annex, 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joey Hess jo...@debian.org (supplier of updated git-annex 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, 15 Sep 2014 10:45:00 -0400 Source: git-annex Binary: git-annex Architecture: source amd64 Version: 5.20140915 Distribution: unstable Urgency: medium Maintainer: Joey Hess jo...@debian.org Changed-By: Joey Hess jo...@debian.org Description: git-annex - manage files with git, without checking their contents into git Closes: 758593 761484 Changes: git-annex (5.20140915) unstable; urgency=medium . * New annex.hardlink setting. Closes: #758593 * init: Automatically detect when a repository was cloned with --shared, and set annex.hardlink=true, as well as marking the repository as untrusted. * Fix parsing of ipv6 address in git remote address when it was not formatted as an url. * The annex-rsync-transport configuration is now also used when checking if a key is present on a rsync remote, and when dropping a key from the remote. * Promote file not found warning message to an error. * Fix transfer lock file FD leak that could occur when two separate git-annex processes were both working to perform the same set of transfers. * sync: Ensure that pending changes to git-annex branch are committed before push when in direct mode. (Fixing a very minor reversion.) * WORM backend: Switched to include the relative path to the file inside the repository, rather than just the file's base name. Note that if you're relying on such things to keep files separate with WORM, you should really be using a better backend. * Rather than crashing when there's a problem with the requested bloomfilter capacity/accuracy, fall back to a reasonable default bloom filter size. * Fix build with optparse-applicative 0.10. Closes: #761484 * webapp: Fixed visual glitch in xmpp pairing that was reported live by a user who tracked me down in front of a coffee cart in Portland. (New bug reporting method of choice?) Checksums-Sha1: ddd2a630343f6399a4d1050245832259f912230c 3840 git-annex_5.20140915.dsc 26641c95d2c663189d0065ce78bee00a480545ee 5799985 git-annex_5.20140915.tar.gz 35123b091c4412b1d27c4baa2aaab7d8067f371f 8473732 git-annex_5.20140915_amd64.deb Checksums-Sha256: c2fe8b5540919ca43733e8e249536faae0edbabb111c8400b4960a5cf7979efe 3840 git-annex_5.20140915.dsc bd60730ee6033858ad01870a0384eaf09fad88e827914a99b9e368bb317afb86 5799985 git-annex_5.20140915.tar.gz 888f0158b6943bb05ba6b98a6dc581244070d73e023a8c03f98920264c5ae2e3 8473732 git-annex_5.20140915_amd64.deb Files: d380699c8ce18aa4e2d1e923864bd6f6 8473732 utils optional git-annex_5.20140915_amd64.deb 9e8750057203e2a6b5a2a7babf6cc1bd 3840 utils optional git-annex_5.20140915.dsc 8506a38f93ed908963bd74c4fe6f6108 5799985 utils optional git-annex_5.20140915.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVBcBE8kQ2SIlEuPHAQIBCA//a62g3ObnDNhEViUaSgAVY1FxKIg8dUO2 RYn4p2oHLpn8UeW0rB08tu7t1wC8fGx9vrHVJ7WvBU5pCCTa8E16+ZHWIEYZx2ve Um7CJ1ZlIl48nt2uW+C+YPU+Y4OFjFPtIKQqVA1NSVrywN+yjFX6o2K73GwtHdUR
Processed: missing dep
Processing commands for cont...@bugs.debian.org: severity 760638 serious Bug #760638 [flashplugin-nonfree] flashplugin-nonfree: Missing Depends: ca-certificates Severity set to 'serious' from 'grave' End of message, stopping processing here. Please contact me if you need assistance. -- 760638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760638 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#759952: [debian-freedict] Bug#759952: Build failure is caused by parallel build
Hello Jan, Jan Niehusmann schrieb am 15.09.2014, 0:11 +0200: it seems like #759952 is caused by the parallel build. The Double definition lines are not related. They are just warnings and wouldn't cause the build to fail. Yes, those are just produced by dbview. So I think there are two ways to fix this FTBFS: a) forbid parallel builds b) set proper dependencies so all-dz doesn't run before build-prep is Sorry, yesterday evening a patch was introduced upstream to address this. Thank you very much for your investigative work, I'll try to push the upstream fix as soon as possible. Sebastian signature.asc Description: Digital signature
Bug#761564: cimg: FTBFS: fatal error: Magick++.h: No such file or directory
Hi David, I can confirm this problem. However, I have no idea why this happens. The critical point is a makefile containing # Flags to enable native support of most classical image file formats, using the Magick++ library. # ( http://www.imagemagick.org/Magick++/ ) CIMG_MAGICK_CFLAGS = -Dcimg_use_magick `Magick++-config --cppflags` `Magick++-config --cxxflags` CIMG_MAGICK_LDFLAGS = `Magick++-config --ldflags` `Magick++-config --libs` and the build log says: cd examples /usr/bin/make Mlinux LDFLAGS=-lm -lpthread -lHalf make[2]: Entering directory '/tmp/buildd/cimg-1.5.9+dfsg/examples' /bin/sh: 1: Magick++-config: not found /bin/sh: 1: Magick++-config: not found /bin/sh: 1: Magick++-config: not found /bin/sh: 1: Magick++-config: not found make[3]: Entering directory '/tmp/buildd/cimg-1.5.9+dfsg/examples' ** Compiling 'CImg_demo (1.5.9)' with 'gcc version 4.9.1 (Debian 4.9.1-14) ' g++ -o CImg_demo CImg_demo.cpp -I.. -Wall -W -O3 -fno-tree-pre -Dcimg_use_vt100 -I/usr/X11R6/include -Dcimg_use_xrandr -Dcimg_use_tiff -Dcimg_use_openexr -I/usr/include/OpenEXR -Dcimg_use_png -Dcimg_use_jpeg - In file included from CImg_demo.cpp:48:0: ../CImg.h:347:22: fatal error: Magick++.h: No such file or directory #include Magick++.h ^ compilation terminated. Since libmagick++-dev provides the command in question and is in the Build-Depends (and according to the build log installed) I'm a bit clueless why this does not work. Any hint is welcome Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752277: waiting for SRM
Registered 761667, waiting for feedback from SRM. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761564: cimg: FTBFS: fatal error: Magick++.h: No such file or directory
Le 15 sept. 2014 17:55, Andreas Tille andr...@an3as.eu a écrit : Hi David, I can confirm this problem. However, I have no idea why this happens. The critical point is a makefile containing Newer imagemagick version does not supply this command. Please use pkg-config Bastien # Flags to enable native support of most classical image file formats, using the Magick++ library. # ( http://www.imagemagick.org/Magick++/ ) CIMG_MAGICK_CFLAGS = -Dcimg_use_magick `Magick++-config --cppflags` `Magick++-config --cxxflags` CIMG_MAGICK_LDFLAGS = `Magick++-config --ldflags` `Magick++-config --libs` and the build log says: cd examples /usr/bin/make Mlinux LDFLAGS=-lm -lpthread -lHalf make[2]: Entering directory '/tmp/buildd/cimg-1.5.9+dfsg/examples' /bin/sh: 1: Magick++-config: not found /bin/sh: 1: Magick++-config: not found /bin/sh: 1: Magick++-config: not found /bin/sh: 1: Magick++-config: not found make[3]: Entering directory '/tmp/buildd/cimg-1.5.9+dfsg/examples' ** Compiling 'CImg_demo (1.5.9)' with 'gcc version 4.9.1 (Debian 4.9.1-14) ' g++ -o CImg_demo CImg_demo.cpp -I.. -Wall -W -O3 -fno-tree-pre -Dcimg_use_vt100 -I/usr/X11R6/include -Dcimg_use_xrandr -Dcimg_use_tiff -Dcimg_use_openexr -I/usr/include/OpenEXR -Dcimg_use_png -Dcimg_use_jpeg - In file included from CImg_demo.cpp:48:0: ../CImg.h:347:22: fatal error: Magick++.h: No such file or directory #include Magick++.h ^ compilation terminated. Since libmagick++-dev provides the command in question and is in the Build-Depends (and according to the build log installed) I'm a bit clueless why this does not work. Any hint is welcome Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140915155510.gb14...@an3as.eu
Bug#756796: marked as done (espresso: FTBFS on s390x)
Your message dated Mon, 15 Sep 2014 16:04:16 + with message-id e1xtyle-0007d8...@franck.debian.org and subject line Bug#756796: fixed in espresso 5.1+dfsg-2 has caused the Debian Bug report #756796, regarding espresso: FTBFS on s390x 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.) -- 756796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: espresso Version: 5.1+dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) espresso failed to build on s390x with: | mpif90 -g -pthread -o pw.x \ |pwscf.o libpw.a ../../Modules/libqemod.a ../../flib/ptools.a ../../flib/flib.a ../../clib/clib.a ../../iotk/src/libiotk.a -lscalapack-mpich2 -lblacs-mpich2 -lblacsF77init-mpich2 -llapack -lblas -lfftw3 -lblas | /usr/bin/ld: cannot find -lscalapack-mpich2 | /usr/bin/ld: cannot find -lblacs-mpich2 | /usr/bin/ld: cannot find -lblacsF77init-mpich2 | collect2: error: ld returned 1 exit status | make[4]: *** [pw.x] Error 1 Full build logs are available from https://buildd.debian.org/status/fetch.php?pkg=espressoarch=s390xver=5.1+dfsg-1stamp=1406242584. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: espresso Source-Version: 5.1+dfsg-2 We believe that the bug you reported is fixed in the latest version of espresso, 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 756...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck mba...@debian.org (supplier of updated espresso package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 14 Sep 2014 23:57:55 +0200 Source: espresso Binary: quantum-espresso quantum-espresso-data Architecture: source amd64 all Version: 5.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debichem Team debichem-de...@lists.alioth.debian.org Changed-By: Michael Banck mba...@debian.org Description: quantum-espresso - Electronic-Structure and Ab-Initio Molecular Dynamics Suite quantum-espresso-data - Electronic-Structure and Ab-Initio Molecular Dynamics Suite (Docu Closes: 756796 Changes: espresso (5.1+dfsg-2) unstable; urgency=medium . * debian/rules (SCALAPACK_LIBS): Remove mpich work-around, which now leads to FTBFS errors (Closes: #756796). Checksums-Sha1: 8a811f1723a711028601a8873271b925da935998 4938 espresso_5.1+dfsg-2.dsc 4994b97e3404d53dd2c49fc0f06048bb50adbbd0 5726300 espresso_5.1+dfsg-2.debian.tar.xz 8e2a11be2cbfc0bf369e59282329a7341133afc5 10071398 quantum-espresso_5.1+dfsg-2_amd64.deb 01624f9b9b559ee33bf9d920fff4fad68d70de75 11061382 quantum-espresso-data_5.1+dfsg-2_all.deb Checksums-Sha256: dae9b237bcdb7461d0c8464c77c99ae645d17645a3147fa50184821855d06533 4938 espresso_5.1+dfsg-2.dsc 1752b23f53f7b750304bd2c8233b9da2cbb4ab479c726cba7c8d0620410cf65f 5726300 espresso_5.1+dfsg-2.debian.tar.xz 141511e6730691b715fb36b6f033b1b2c4a58de401c654d5f1655630fc456ed3 10071398 quantum-espresso_5.1+dfsg-2_amd64.deb d6e480c2cebf7a166bda28f3629e3eabcfe5b46ee4d15aa0098ece1de366cbd8 11061382 quantum-espresso-data_5.1+dfsg-2_all.deb Files: 47959244dc4a4eb303550d0ecac49b25 10071398 science optional quantum-espresso_5.1+dfsg-2_amd64.deb e29d6c76485168bd986cfb94295170af 11061382 science optional quantum-espresso-data_5.1+dfsg-2_all.deb c2082a3affba4b3cb6342d693680257d 4938 science optional espresso_5.1+dfsg-2.dsc 210580a625c4d42fb135ca38b388806a 5726300 science optional espresso_5.1+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUFwirAAoJENxoaie0NIGwpmoP/1pK/uhHBemHbqnPl8L+OhrQ LzOiszxEbVRqher4qEhx6rWspvziMWHbxOpJ6HfhZxx3vTNqsOdylanNStEaRqgJ kebmH+jurli5lXSELw38IySTIDe82bphGGWlpKRj9g2zd/UId9VwX2M/Uypsa+pu MPYsPnjROxXTPnoi5swwK3CBmTpDLWUWRclD7QFQPdWuwSD6zj/4eXx1rD1KwqGF mopYnFPrihCHJZEM5Ycth+B84879ac9O87rVbnuKzE/CU6AK/frejrMG0Wiss5+1 4EHJvfquqloWYckZleVRvoQYlM7NRHZAMSnJzWoAsiaeiQj0q2p1xFrn6ycZnyWr bt7y0AtVtbaBGrvCMN5UrLBB3vqODwV0uPnn+ppawD87DRacyySXH9+u0H4uZu+Z
Bug#761670: impossible to bootstrap build of node-jake and node-utilities: (build-)dependency loop
Package: node-jake Version: 0.7.9-1 Severity: serious Hi, Trying to do a bunch of backports, I came across this issue. node-utilities build-depends: node-jake node-jake depends: node-utilities So, it's impossible to build node-utilities, because it needs node-jake, which cannot be installed, because it depends on node-utilities, which isn't build. This cycle has to be broken, otherwise it makes it very hard for porters to bootstrap the rebuild of node-utilities node-jake. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761672: node-utilities build-depends on itself
Package: node-utilities Version: 0.0.31-1 Severity: serious The test-suite of node-utilities uses node-jake, which itself uses node-utilities. So, effectively, node-utilities is build-depending on itself, which should never happen, and which by the way isn't even declared in the debian/control file in an explicit way. To effectively rebuild node-utilities on a system where node-jake isn't available (yet), one has to manually disable the unit test or do some kind of hacks. Please fix the dependency loop. Also, please respect the DEB_BUILD_OPTIONS. You should add something like this: override_dh_auto_test: ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS))) some-tests endif Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759958: marked as done (dirspec: FTBFS: tests failed)
Your message dated Mon, 15 Sep 2014 17:18:43 + with message-id e1xtzvh-0008g9...@franck.debian.org and subject line Bug#759958: fixed in dirspec 4.2.0-2 has caused the Debian Bug report #759958, regarding dirspec: FTBFS: tests failed 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.) -- 759958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: dirspec Version: 4.2.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' ./run-tests + python ./setup.py build test clean running build running build_py running test running egg_info creating dirspec.egg-info writing dirspec.egg-info/PKG-INFO writing top-level names to dirspec.egg-info/top_level.txt writing dependency_links to dirspec.egg-info/dependency_links.txt writing manifest file 'dirspec.egg-info/SOURCES.txt' reading manifest file 'dirspec.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'dirspec.egg-info/SOURCES.txt' running build_ext test_darwin_pkgd (dirspec.tests.test_utils.DarwinPkgdTestCase) dirspec.tests.test_utils.DarwinPkgdTestCase.test_darwin_pkgd ... ok test_darwin_pkgd_raises_nopath (dirspec.tests.test_utils.DarwinPkgdTestCase) dirspec.tests.test_utils.DarwinPkgdTestCase.test_darwin_pkgd_raises_nopath ... ok test_darwin_pkgd_raises_on_no_appnames (dirspec.tests.test_utils.DarwinPkgdTestCase) dirspec.tests.test_utils.DarwinPkgdTestCase.test_darwin_pkgd_raises_on_no_appnames ... ok test_linux_no_src_relative_path (dirspec.tests.test_utils.PosixTestCase) dirspec.tests.test_utils.PosixTestCase.test_linux_no_src_relative_path ... ok test_linux_src_relative_path_exists (dirspec.tests.test_utils.PosixTestCase) dirspec.tests.test_utils.PosixTestCase.test_linux_src_relative_path_exists ... ok test_get_config_dirs (dirspec.tests.test_utils.TestBaseDirectoryWindows) dirspec.tests.test_utils.TestBaseDirectoryWindows.test_get_config_dirs ... ok test_get_data_dirs (dirspec.tests.test_utils.TestBaseDirectoryWindows) dirspec.tests.test_utils.TestBaseDirectoryWindows.test_get_data_dirs ... ok test_get_env_path_no_var (dirspec.tests.test_utils.TestBaseDirectoryWindows) dirspec.tests.test_utils.TestBaseDirectoryWindows.test_get_env_path_no_var ... skipped u'UnicodeEncodeError: bug #907053' test_get_env_path_var (dirspec.tests.test_utils.TestBaseDirectoryWindows) dirspec.tests.test_utils.TestBaseDirectoryWindows.test_get_env_path_var ... skipped u'UnicodeEncodeError: bug #907053' test_get_special_folders (dirspec.tests.test_utils.TestBaseDirectoryWindows) dirspec.tests.test_utils.TestBaseDirectoryWindows.test_get_special_folders ... skipped u'Win32 is required for this test.' test_unfrozen_dev_toplevel (dirspec.tests.test_utils.UnfrozenSrcTestCase) dirspec.tests.test_utils.UnfrozenSrcTestCase.test_unfrozen_dev_toplevel ... ok test_unfrozen_dev_toplevel_raises_nopath (dirspec.tests.test_utils.UnfrozenSrcTestCase) dirspec.tests.test_utils.UnfrozenSrcTestCase.test_unfrozen_dev_toplevel_raises_nopath ... ok test_user_home_is_utf8_bytes (dirspec.tests.test_utils.UtilsTestCase) dirspec.tests.test_utils.UtilsTestCase.test_user_home_is_utf8_bytes ... ok test_windows_pkgd (dirspec.tests.test_utils.Win32PkgdTestCase) dirspec.tests.test_utils.Win32PkgdTestCase.test_windows_pkgd ... ok test_windows_pkgd_raises_nopath (dirspec.tests.test_utils.Win32PkgdTestCase) dirspec.tests.test_utils.Win32PkgdTestCase.test_windows_pkgd_raises_nopath ... ok test_cache_home (dirspec.tests.test_basedir.BasedirTestCase) dirspec.tests.test_basedir.BasedirTestCase.test_cache_home ... ok test_config_dirs (dirspec.tests.test_basedir.BasedirTestCase) dirspec.tests.test_basedir.BasedirTestCase.test_config_dirs ... ok test_config_home (dirspec.tests.test_basedir.BasedirTestCase) dirspec.tests.test_basedir.BasedirTestCase.test_config_home ... ok test_data_dirs (dirspec.tests.test_basedir.BasedirTestCase) dirspec.tests.test_basedir.BasedirTestCase.test_data_dirs ... ok test_data_home (dirspec.tests.test_basedir.BasedirTestCase) dirspec.tests.test_basedir.BasedirTestCase.test_data_home ... ok test_default_cache_home (dirspec.tests.test_basedir.BasedirTestCase) dirspec.tests.test_basedir.BasedirTestCase.test_default_cache_home ... ok test_default_config_dirs
Bug#760638: marked as done (flashplugin-nonfree: Missing Depends: ca-certificates)
Your message dated Mon, 15 Sep 2014 17:19:25 + with message-id e1xtzvx-dq...@franck.debian.org and subject line Bug#760638: fixed in flashplugin-nonfree 1:3.6 has caused the Debian Bug report #760638, regarding flashplugin-nonfree: Missing Depends: ca-certificates 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.) -- 760638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flashplugin-nonfree Version: 1:3.2 Severity: grave Installing flashplugin-nonfree in wheezy does not work: # apt-get install flashplugin-nonfree Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: konqueror-nsplugins ttf-mscorefonts-installer ttf-dejavu ttf-xfree86-nonfree hal The following NEW packages will be installed: flashplugin-nonfree 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 20.1 kB of archives. After this operation, 181 kB of additional disk space will be used. Get:1 http://http.debian.net/debian/ wheezy/contrib flashplugin-nonfree amd64 1:3.2 [20.1 kB] Fetched 20.1 kB in 0s (69.4 kB/s) Selecting previously unselected package flashplugin-nonfree. (Reading database ... 68881 files and directories currently installed.) Unpacking flashplugin-nonfree (from .../flashplugin-nonfree_1%3a3.2_amd64.deb) ... Processing triggers for man-db ... Processing triggers for hicolor-icon-theme ... Processing triggers for desktop-file-utils ... Setting up flashplugin-nonfree (1:3.2) ... ERROR: wget failed to download http://people.debian.org/~bartm/flashplugin-nonfree/get-upstream-version.pl.gz.pgp More information might be available at: http://wiki.debian.org/FlashPlayer In fact, a direct wget does not work either: # wget http://people.debian.org/~bartm/flashplugin-nonfree/get-upstream-version.pl.gz.pgp --2014-09-06 13:25:59-- http://people.debian.org/~bartm/flashplugin-nonfree/get-upstream-version.pl.gz.pgp Resolving people.debian.org (people.debian.org)... 5.153.231.30, 2001:41c8:1000:21::21:30 Connecting to people.debian.org (people.debian.org)|5.153.231.30|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://people.debian.org/~bartm/flashplugin-nonfree/get-upstream-version.pl.gz.pgp [following] --2014-09-06 13:25:59-- https://people.debian.org/~bartm/flashplugin-nonfree/get-upstream-version.pl.gz.pgp Connecting to people.debian.org (people.debian.org)|5.153.231.30|:443... connected. ERROR: The certificate of `people.debian.org' is not trusted. ERROR: The certificate of `people.debian.org' hasn't got a known issuer. I guess this could be related to: * Recent move of people.debian.org from one machine to another one. * Recent move of things from http to https. but in either case I wonder, if get-upstream-version.pl does not change several times a week, why this little perl script is not included in the flashplugin-nonfree package itself. Would you please consider doing that? Thanks. ---End Message--- ---BeginMessage--- Source: flashplugin-nonfree Source-Version: 1:3.6 We believe that the bug you reported is fixed in the latest version of flashplugin-nonfree, 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 760...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bart Martens ba...@debian.org (supplier of updated flashplugin-nonfree 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, 15 Sep 2014 17:30:37 +0200 Source: flashplugin-nonfree Binary: flashplugin-nonfree Architecture: source amd64 Version: 1:3.6 Distribution: unstable Urgency: medium Maintainer: Bart Martens ba...@debian.org Changed-By: Bart Martens ba...@debian.org Description: flashplugin-nonfree - Adobe Flash Player - browser plugin Closes: 732577 760638 Changes: flashplugin-nonfree (1:3.6) unstable; urgency=medium . * debian/control: Depends: ca-certificates. Closes: #760638. * update-flashplugin-nonfree: Add use of wget option -nv. Closes: #732577. * Updated the tools to the newest versions: debian/rules
Processed: Re: Bug#761390: libdvb: should not be released with jessie
Processing control commands: reassign -1 ftp.debian.org Bug #761390 [src:libdvb] libdvb: should not be released with jessie Bug reassigned from package 'src:libdvb' to 'ftp.debian.org'. No longer marked as found in versions libdvb/0.5.5.1-5.1. Ignoring request to alter fixed versions of bug #761390 to the same values previously set retitle -1 RM: libdvb -- ROM; obsolete, dead upstream, no rev-deps Bug #761390 [ftp.debian.org] libdvb: should not be released with jessie Changed Bug title to 'RM: libdvb -- ROM; obsolete, dead upstream, no rev-deps' from 'libdvb: should not be released with jessie' severity -1 normal Bug #761390 [ftp.debian.org] RM: libdvb -- ROM; obsolete, dead upstream, no rev-deps Severity set to 'normal' from 'serious' -- 761390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761390 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#761390: libdvb: should not be released with jessie
Control: reassign -1 ftp.debian.org Control: retitle -1 RM: libdvb -- ROM; obsolete, dead upstream, no rev-deps Control: severity -1 normal On 2014-09-13 16:03:57, Sebastian Ramacher wrote: Source: libdvb Version: 0.5.5.1-5.1 Severity: serious Tags: sid jessie I think keeping libdvb around for another release is not useful. Since at least squeeze, libdvb does not have any reverse dependencies. The last upstream release happened in 2005 and the last upload in 2008. So it's time to let it go. Please remove libdvb from unstable for the reasons listed above. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#761681: should.js build-depends on node-mocha which isn't in Debian
Package: node-should Version: 4.0.4+dfsg-1 Severity: serious Hi, As per the title of this bug, node-mocha should be packaged, or should.js should not build-depend on it. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745844: libimobiledevice: Re: libimobiledevice-utils: Segfault with iphone 3GS on many utilities
Hi, I am encountering the same poblem. The system has usbmuxd 1.0.8-5 and libusbmuxd2:am 1.0.9-1. @Chow Loong Jin I read your coment abuout the usbmuxd package bu I am not sure I understood it, sorry for bothering again. Am I correct that we are aiting until pstream releases usbmuxd 1.0.9 to package it and that it is this release which is supposed tosolve the problem? Thanks! Shérab. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761602: missing source for config/ag_macros.m4
On 2014-09-14 Helmut Grohne hel...@subdivi.de wrote: Package: src:autogen Version: 1:5.18.3-6 Severity: serious Justification: missing source [...] I failed to find the source for config/ag_macros.m4. That file starts out with: | dnl -*- buffer-read-only: t -*- vi: set ro: | dnl | dnl DO NOT EDIT THIS FILE (ag_macros.m4) | dnl | dnl It has been AutoGen-ed May 17, 2014 at 07:49:41 AM by AutoGen 5.18.3 | dnl From the definitionsmisc.def | dnl and the template file conftest.tpl | dnl | dnl do always before generated macros: | dnl However, a file named misc.def is nowhere to be found. It contains an invocation of guile-config link. The only other file that also contains this invocation is configure, which is derived from the former. I conclude that the source for config/ag_macros.m4 is missing. Thanks for spotting this. The file is at least available in upstream GIT http://git.savannah.gnu.org/cgit/autogen.git/log/config/misc.def. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761682: pepperflashplugin-nonfree: After last update, it's not loaded by chromium
Package: pepperflashplugin-nonfree Version: 1.7 Severity: grave Justification: renders package unusable Dear Maintainer, after the last update, flash player seems gone from chromium. It's not listed in the plugin page. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.1d (SMP w/4 CPU cores; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pepperflashplugin-nonfree depends on: ii binutils 2.24.51.20140903-1 ii ca-certificates20140325 ii debconf [debconf-2.0] 1.5.53 ii gnupg 1.4.18-4 ii libatk1.0-02.12.0-1 ii libcairo2 1.12.16-5 ii libcurl3-gnutls7.38.0-1 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-1.1 ii libgcc11:4.9.1-14 ii libglib2.0-0 2.40.0-5 ii libgtk2.0-02.24.24-1 ii libnspr4 2:4.10.7-1 ii libnss32:3.17-1 ii libpango-1.0-0 1.36.7-1 ii libpango1.0-0 1.36.7-1 ii libstdc++6 4.9.1-14 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.2-1 ii libxt6 1:1.1.4-1 ii wget 1.15-1+b1 pepperflashplugin-nonfree recommends no packages. Versions of packages pepperflashplugin-nonfree suggests: ii chromium 35.0.1916.153-2 pn halnone pn ttf-dejavu none ii ttf-mscorefonts-installer 3.5 pn ttf-xfree86-nonfreenone -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Debian bug #760804, #761565
Processing commands for cont...@bugs.debian.org: owner 761565 ! Bug #761565 [scons] serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected Bug #760804 [scons] serf: FTBFS: Directory /usr/include/mit-krb5 found where file expected. Owner recorded as Jörg Frings-Fürst deb...@jff-webhosting.net. Owner recorded as Jörg Frings-Fürst deb...@jff-webhosting.net. owner 760804 ! Bug #760804 [scons] serf: FTBFS: Directory /usr/include/mit-krb5 found where file expected. Bug #761565 [scons] serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected Ignoring request to set the owner of bug #760804 to the same value Ignoring request to set the owner of bug #761565 to the same value -- Stopping processing here. Please contact me if you need assistance. -- 760804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760804 761565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761565 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#742048: systemd-remount-fs.service fails for split-usr
Processing control commands: found -1 215-3 Bug #742048 [systemd] systemd-remount-fs.service fails for split-usr Marked as found in versions systemd/215-3. severity -1 serious Bug #742048 [systemd] systemd-remount-fs.service fails for split-usr Severity set to 'serious' from 'normal' -- 742048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742048 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#761681: [Pkg-javascript-devel] Bug#761681: should.js build-depends on node-mocha which isn't in Debian
On 15 September 2014 19:42, Thomas Goirand z...@debian.org wrote: Hi, As per the title of this bug, node-mocha should be packaged, or should.js should not build-depend on it. Hi Thomas, node-mocha is provided by mocha package: Package: mocha Source: node-mocha ... Provides: node-mocha -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: pepperflashplugin-nonfree: support request
Processing commands for cont...@bugs.debian.org: severity 761682 wishlist Bug #761682 [pepperflashplugin-nonfree] pepperflashplugin-nonfree: After last update, it's not loaded by chromium Severity set to 'wishlist' from 'grave' retitle 761682 pepperflashplugin-nonfree: support request not listed in the plugin page Bug #761682 [pepperflashplugin-nonfree] pepperflashplugin-nonfree: After last update, it's not loaded by chromium Changed Bug title to 'pepperflashplugin-nonfree: support request not listed in the plugin page' from 'pepperflashplugin-nonfree: After last update, it's not loaded by chromium' stop Stopping processing here. Please contact me if you need assistance. -- 761682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761682 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#761682: pepperflashplugin-nonfree: support request
severity 761682 wishlist retitle 761682 pepperflashplugin-nonfree: support request not listed in the plugin page stop Hi Salvo, I don't have that problem (seems gone, not listed in the plugin page). I'm lowering the severity to a support request. Are you sure you have this problem with version 1.7 ? Regards, Bart Martens -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761681: [Pkg-javascript-devel] Bug#761681: should.js build-depends on node-mocha which isn't in Debian
On 15 September 2014 19:42, Thomas Goirand z...@debian.org wrote: Hi, As per the title of this bug, node-mocha should be packaged, or should.js should not build-depend on it. Hi Thomas, node-mocha is provided by mocha, see: $ apt-cache show mocha | grep ^Provides -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761684: prodigal: FTBFS: help2man: not found
Source: prodigal Version: 2.60-1 Severity: serious Justification: fails to build from source Builds of prodigal in minimal environments (notably the autobuilders) have been failing: help2man --no-discard-stderr ./prodigal prodigal.1 /bin/sh: 1: help2man: not found make[1]: *** [override_dh_install] Error 127 debian/rules:15: recipe for target 'override_dh_install' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [binary-arch] Error 2 debian/rules:12: recipe for target 'binary-arch' failed Please declare a build dependency on help2man and confirm with pbuilder or the like that you haven't missed any others. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759054: marked as done (python-fs: Please update to use wxpython3.0)
Your message dated Mon, 15 Sep 2014 18:49:57 + with message-id e1xtblz-00046d...@franck.debian.org and subject line Bug#759054: fixed in python-fs 0.4.0-2 has caused the Debian Bug report #759054, regarding python-fs: Please update to use wxpython3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 759054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-fs Version: 0.4.0-1 Severity: important Tags: sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wxpy3.0 Control: block 755757 by -1 We're aiming to migrate the archive to using wxpython3.0 instead of wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released. This transition is already underway, and is being tracked by the release team here: https://release.debian.org/transitions/html/wxpython3.0.html The wxPython 3.0 API mostly adds to the wxPython2.8 API. Many packages work with wxPython 3.0 without any changes, but there are a few incompatibilities. For example, wx.Color is no longer supported as an alias for wx.Colour, and some constants which were deprecated in 2.8 have been removed. All the removed constants I'm aware of were set to 0 in wxPython 2.8, so removing them is still compatible with 2.8. To assist updating to wxPython 3.0, I've put together a script which will help make the mechanical changes required. This is in a git repo on collab-maint along with a README about using it and updating packages for wxPython 3.0 in general: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git The script has some options to control the sorts of changes it makes - see the README and --help output for more information - you can view the latest version of the README online here: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I've developed this script by trying to convert 20+ packages. Please try it out on your package - in many cases, it should be enough to get your package working (if it doesn't already) - if it does, please upload (and close this bug). If the script doesn't do the job, please let me know (or improve the script if you can figure out what it needs to do to get your package working). Another issue you may hit is that wxWidgets 3.0 now defaults to enabling its WXDEBUG checks for incorrect API usage, so some applications will emit scary sounding assertion failures. These are unlikely to actually be new, just in a default build of 2.8, such incorrect uses were handled quietly behind the scenes. Sometimes these are easy to fix, but if not you can easily patch the application to tell wx 3.0 to handle them in the same way wx 2.8 does - details of how to do so are in the README: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I'm happy to sponsor uploads for this transition, though if you have an active sponsor already check with them first - I don't want to tread on anyone's toes. Cheers, Olly ---End Message--- ---BeginMessage--- Source: python-fs Source-Version: 0.4.0-2 We believe that the bug you reported is fixed in the latest version of python-fs, 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 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Janos Guljas ja...@debian.org (supplier of updated python-fs 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, 15 Sep 2014 20:29:58 +0200 Source: python-fs Binary: python-fs python-fs-browser python-fs-plugin-sftp python-fs-plugin-django python-fs-plugin-s3 python-fs-plugin-webdav python-fs-plugin-tahoe-lafs Architecture: source all Version: 0.4.0-2 Distribution: unstable Urgency: medium Maintainer: Janos Guljas ja...@debian.org Changed-By: Janos Guljas ja...@debian.org Description: python-fs - Python filesystem abstraction python-fs-browser - Python filesystem abstraction - Gtk browser python-fs-plugin-django - Python filesystem abstraction - Django File Storage python-fs-plugin-s3 - Python filesystem abstraction - Amazon S3 python-fs-plugin-sftp - Python filesystem abstraction -
Bug#759391: marked as done (tintii: please switch to default boost version)
Your message dated Mon, 15 Sep 2014 19:04:07 + with message-id e1xtbzh-00068v...@franck.debian.org and subject line Bug#759391: fixed in tintii 2.9.0-2 has caused the Debian Bug report #759391, regarding tintii: please switch to default boost version 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.) -- 759391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: tintii version: 2.9.0-1 Hi, Your package build-depends on libboost-graph1.54-dev and libboost1.54-dev, which are no longer the default version. Please switch to unversioned build-dependencies (libboost-graph-dev and libboost-dev). Cheers, Ivo ---End Message--- ---BeginMessage--- Source: tintii Source-Version: 2.9.0-2 We believe that the bug you reported is fixed in the latest version of tintii, 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 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Echeverry epsilo...@gmail.com (supplier of updated tintii package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 14 Sep 2014 13:56:41 -0500 Source: tintii Binary: tintii Architecture: source amd64 Version: 2.9.0-2 Distribution: unstable Urgency: low Maintainer: Daniel Echeverry epsilo...@gmail.com Changed-By: Daniel Echeverry epsilo...@gmail.com Description: tintii - photo filter for easy color effects Closes: 759391 Changes: tintii (2.9.0-2) unstable; urgency=low . * debian/control + switch to unversioned build-dependencies. Closes: #759391 Checksums-Sha1: 6bcfebf1acaa711193548023930c021107401826 1741 tintii_2.9.0-2.dsc 357169b5f7c1ebf66fe3b94d251334f39d416b1d 3156 tintii_2.9.0-2.debian.tar.xz f9dbcad5f4ee7d357089e3328369934bffac2099 495450 tintii_2.9.0-2_amd64.deb Checksums-Sha256: eaddc7cf2badd61701c992023dd013aa5d3f929e8a809dc4bf3f04b063d6258a 1741 tintii_2.9.0-2.dsc 27ebe0577e001095eaa8aee243fdbabac65a7db8e79f2a807f82d6a8864d9958 3156 tintii_2.9.0-2.debian.tar.xz ded11794faa9227e780340280e77830397152a48dd99a51a9f2f8751c5401d29 495450 tintii_2.9.0-2_amd64.deb Files: 98efb5052825daa8a3d5572a0728f9f5 495450 graphics optional tintii_2.9.0-2_amd64.deb 142dfcf63685a41cdd299c39284391a3 1741 graphics optional tintii_2.9.0-2.dsc bb72d95c1cc81ef318bd99073ce8abf6 3156 graphics optional tintii_2.9.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUFzZhAAoJENX9/BVhaL9gkGMQAMmIT40qz4WWE3JRgpSw5hWv BggZPpFTZBycqHaLC5JblMlb2YaxM0K4pxm+sMNcm5edxslb0xOH6/NlTC+jFDRd BhOms1B7IyBdYxoSxXfo2uoMtwoIcz56XjBL2UxWHLKyRmIGTYW/1J2w0/0gUUhW hAa0UenMTVbM5m4/RAzESvRn6g2jeGaGyiG7nQn3Nb37gFyYh5to8kgSNtVclKxa Htmmg38Gpzw7gB84yoPs8uvyAnKr3d0Ol/8+nMu6TS8f4Mriy9co9+Lz8+3yewFp BUUpNIWWUxR6wTyBArY27QqaAq/V1tt7EnfyAcAZe/tHtm4K4CWwwBN2Zk/Ja6SN OKYjLi/RdQ6r6rAJneF7QtyFuHB4iQJT91cLvxIxduWEIX8Ulz0a5Mw8bpnTRxyb XWZdxGsfh27woGRfzSP9MHZtRDs1qtm6ubzmfE6baNw4pF/vIrfqIZdxNxwvDJV3 pjHhbbs25El2ZPHEnqGKwqYyO10OHp/SZB3UZWfovfSO7A7yWGJ4SEW0ls0cxUD+ YRD84i4vbwGtOT+gwJaAlBD5bsovkYNx7omZQhI4vXYCbCmClc4JVRxJ30q87m1y zJ1rWNqRyGN6ATGfTU8rrMzy3N4RD6NjHYMxBF8JelZYQ4YbRYJqV8xq3J54mjsW S/GBIFhcc41Zje/4AWSe =daBC -END PGP SIGNATUREEnd Message---
Bug#761686: cowbuilder: Unable to unmount dev/pts filesystem
Package: cowbuilder Version: 0.73 Severity: grave Dear Maintainer, Cowbuilder fails at the moment when it tries to unmount the filesystem from dev/pts here is the output: dpkg-buildpackage: full upload (original source is included) I: Copying back the cached apt archive contents I: unmounting dev/pts filesystem W: Could not unmount dev/pts: umount: /var/cache/pbuilder/build/cow.6709/dev/pts: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) W: Retrying to unmount dev/pts in 5s After waiting for several retries I decided to kill the process. Also I've found that the result directory does not contain the resulting files from the build Hope this information is useful. Cheers -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_GT.UTF-8, LC_CTYPE=es_GT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cowbuilder depends on: ii cowdancer 0.73 ii libc6 2.19-11 ii pbuilder 0.215+nmu3 cowbuilder recommends no packages. cowbuilder suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reopening 761356
Processing commands for cont...@bugs.debian.org:
reopen 761356
Bug #761356 {Done: Mathieu Malaterre ma...@debian.org}
[libopenjp2-tools,openjpeg-tools] openjpeg-tools and libopenjp2-tools: error
when trying to install together
Bug reopened
Ignoring request to alter fixed versions of bug #761356 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
761356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761356
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: reopening 761355
Processing commands for cont...@bugs.debian.org:
reopen 761355
Bug #761355 {Done: Mathieu Malaterre ma...@debian.org}
[libopenjp2-7-dev,libopenjpeg6-dev] libopenjpeg6-dev and libopenjp2-7-dev:
error when trying to install together
Bug reopened
Ignoring request to alter fixed versions of bug #761355 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
761355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761355
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: reopening 761357
Processing commands for cont...@bugs.debian.org:
reopen 761357
Bug #761357 {Done: Mathieu Malaterre ma...@debian.org}
[libopenjp3d-tools,openjp3d-tools] openjp3d-tools and libopenjp3d-tools: error
when trying to install together
Bug reopened
Ignoring request to alter fixed versions of bug #761357 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
761357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761357
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#761355: closed by Mathieu Malaterre ma...@debian.org ()
On Mon, Sep 15, 2014 at 07:18:12AM +, Debian Bug Tracking System wrote: Date: Mon, 15 Sep 2014 09:15:46 +0200 From: Mathieu Malaterre ma...@debian.org To: 761355-d...@bugs.debian.org Subject: Control: tags -1 wontfix libopenjpeg6-dev never reached testing. closing as wontfix. That is not a reason to close a bug while it remains unfixed. Policy applies to sid as well as to testing or stable. The same holds of course for #761356 and #761357. -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760804: serf: FTBFS: Directory /usr/include/mit-krb5 found where file expected.
Hallo, I have refreshed the patch from James McCoy for scons v 2.3.3 and uploaded the package to mentors[1]. I hope that my sponsor review and upload the package as soon as possible. CU Jörg [1] http://mentors.debian.net/debian/pool/main/s/scons/scons_2.3.3-1.dsc -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#761533: marked as done (qutecom: FTBFS: error: incomplete type 'QTimer' used in nested name specifier)
Your message dated Mon, 15 Sep 2014 21:08:30 +0200 with message-id 5417392e.8030...@debian.org and subject line Re: qutecom: FTBFS: error: incomplete type 'QTimer' used in nested name specifier has caused the Debian Bug report #761533, regarding qutecom: FTBFS: error: incomplete type 'QTimer' used in nested name specifier 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.) -- 761533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: qutecom Version: 2.2.1+dfsg1-5 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140913 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/bin/cmake -E cmake_progress_report /«BUILDDIR»/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/CMakeFiles [ 96%] Building CXX object qutecom/src/presentation/qt/CMakeFiles/qutecom.dir/chat/QtChatEditWidget.o cd /«BUILDDIR»/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/qutecom/src/presentation/qt /usr/bin/g++ -DDEBUG -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/owutil -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/imwrapper/include -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/imwrapper/src/null -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/pixertool/include -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/libs/pixertool -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/sipwrapper/include -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/sound/include -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/imwrapper/src/purple -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/wifo/phapi -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/phapi -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/wifo/phapi-util/include -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/wifo/wifo-plugins/sfp-plugin/include -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/sipwrapper/src/phapi -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/imwrapper/src/multiim/../multiim -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/qutecom/src -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/qutecom/src/model/coipmanager/include -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/qutecom/src/model/coipmanager/filesessionmanager/include -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/qutecom/src/buildid -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/qtutil/include -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/webcam/include -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/3rdparty/psiidle/psiidle/.. -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/softupdater/include -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/qutecom/src/presentation/qt -I/«BUILDDIR»/qutecom-2.2.1+dfsg1/qutecom/src/presentation/qt -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0/glib -I/usr/include/glib-2.0/gobject -I/usr/include/libpurple -I/usr/include/qt4 -I/usr/include/qt4/Qt -I/usr/include/qt4/QtCore-fPIC -Wall -Wstrict-aliasing -Wextra -Wno-unused-parameter -fmessage-length=0 -DBOOST_ALL_DYN_LINK -pthread -DOWUTIL_DLL -D__STDC_CONSTANT_MACROS -DPHAPI_DLL -DPHAPIUTIL_DLL -DSFP_PLUGIN_DLL -DWEBCAM_DLL -DOWBASE_DLL -DOWSL_DLL -DQT_DLL -DQT_NO_KEYWORDS -DOW_RESOURCEDIR='/usr/share/qutecom' -DBOOST_ALL_DYN_LINK -pthread -DOWUTIL_DLL -D__STDC_CONSTANT_MACROS -DPHAPI_DLL -DPHAPIUTIL_DLL -DSFP_PLUGIN_DLL -DQT_DLL -DQT_NO_KEYWORDS -DWEBCAM_DLL -DPSIIDLE_DLL -DMULTIIMWRAPPER -DDISABLE_CALL_FORWARD -DDISABLE_SMS -DDISABLE_VOICE_MAIL -DDISABLE_FILETRANSFER -DQT_TRANSLATION_DIR='/usr/translations' -o CMakeFiles/qutecom.dir/chat/QtChatEditWidget.o -c /«BUILDDIR»/qutecom-2.2.1+dfsg1/qutecom/src/presentation/qt/chat/QtChatEditWidget.cpp In file included from /«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/owutil/util/Event.h:25:0, from /«BUILDDIR»/qutecom-2.2.1+dfsg1/libs/owutil/util/Logger.h:26, from /«BUILDDIR»/qutecom-2.2.1+dfsg1/qutecom/src/presentation/qt/chat/QtChatEditWidget.cpp:32: /usr/include/boost/signal.hpp:17:4: warning: #warning Boost.Signals is no longer being maintained and is now deprecated. Please switch to Boost.Signals2. To disable this warning message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING. [-Wcpp] # warning Boost.Signals is no longer being maintained and is now deprecated. Please switch to Boost.Signals2. To disable this warning message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING. ^ /usr/bin/cmake -E cmake_progress_report
Processed: forcibly merging 754114 753135 750557 760350
Processing commands for cont...@bugs.debian.org: forcemerge 754114 753135 750557 760350 Bug #754114 [pgadmin3] pgadmin3 crashes: Unrecognised instruction __lll_unlock_elision Bug #760350 [pgadmin3] [pgadmin3] pgadmin crashes every time, 100% reproducible Set Bug forwarded-to-address to 'http://www.postgresql.org/message-id/20140806155112.gd2...@msg.df7cb.de'. Severity set to 'grave' from 'important' There is no source info for the package 'pgadmin3' at version '1.18.1-3.pgdg70+1' with architecture '' Unable to make a source version for version '1.18.1-3.pgdg70+1' Marked as found in versions pgadmin3/1.18.1-3. Added tag(s) upstream, confirmed, and moreinfo. Bug #750557 [pgadmin3] pgadmin: have random crashes ( memory corruption or double free ) Set Bug forwarded-to-address to 'http://www.postgresql.org/message-id/20140806155112.gd2...@msg.df7cb.de'. Severity set to 'grave' from 'important' There is no source info for the package 'pgadmin3' at version '1.18.1-3.pgdg70+1' with architecture '' Unable to make a source version for version '1.18.1-3.pgdg70+1' Marked as found in versions 1.18.1-3.pgdg70+1. Added tag(s) confirmed. Bug #753135 [pgadmin3] pgadmin3: pgadmin crahes quite often with assertion failure in ../src/common/wincmn.cpp(478) Set Bug forwarded-to-address to 'http://www.postgresql.org/message-id/20140806155112.gd2...@msg.df7cb.de'. Severity set to 'grave' from 'normal' There is no source info for the package 'pgadmin3' at version '1.18.1-3.pgdg70+1' with architecture '' Unable to make a source version for version '1.18.1-3.pgdg70+1' Marked as found in versions 1.18.1-3.pgdg70+1. Added tag(s) upstream, confirmed, and moreinfo. Bug #754114 [pgadmin3] pgadmin3 crashes: Unrecognised instruction __lll_unlock_elision There is no source info for the package 'pgadmin3' at version '1.18.1-3.pgdg70+1' with architecture '' Unable to make a source version for version '1.18.1-3.pgdg70+1' Marked as found in versions 1.18.1-3.pgdg70+1. Added tag(s) upstream and moreinfo. Merged 750557 753135 754114 760350 thanks Stopping processing here. Please contact me if you need assistance. -- 750557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750557 753135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753135 754114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754114 760350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760350 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: Debian bug#760804, #761565
Processing commands for cont...@bugs.debian.org: fixed 760804 scons/2.3.3-1 Bug #760804 [scons] serf: FTBFS: Directory /usr/include/mit-krb5 found where file expected. Bug #761565 [scons] serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected The source scons and version 2.3.3-1 do not appear to match any binary packages Marked as fixed in versions scons/2.3.3-1. Marked as fixed in versions scons/2.3.3-1. fixed 761565 scons/2.3.3-1 Bug #761565 [scons] serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected Bug #760804 [scons] serf: FTBFS: Directory /usr/include/mit-krb5 found where file expected. The source scons and version 2.3.3-1 do not appear to match any binary packages Marked as fixed in versions scons/2.3.3-1; no longer marked as fixed in versions scons/2.3.3-1. Marked as fixed in versions scons/2.3.3-1; no longer marked as fixed in versions scons/2.3.3-1. -- Stopping processing here. Please contact me if you need assistance. -- 760804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760804 761565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 750557
Processing commands for cont...@bugs.debian.org: tags 750557 - moreinfo Bug #750557 [pgadmin3] pgadmin: have random crashes ( memory corruption or double free ) Bug #753135 [pgadmin3] pgadmin3: pgadmin crahes quite often with assertion failure in ../src/common/wincmn.cpp(478) Bug #754114 [pgadmin3] pgadmin3 crashes: Unrecognised instruction __lll_unlock_elision Bug #760350 [pgadmin3] [pgadmin3] pgadmin crashes every time, 100% reproducible Removed tag(s) moreinfo. Removed tag(s) moreinfo. Removed tag(s) moreinfo. Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 750557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750557 753135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753135 754114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754114 760350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760350 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#761550: Imagemagick transition
control: reassign -1 sunflow Hi, This bug lie in sunflow. Imagemagick is doing a transition. Please fix your package. Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Imagemagick transition
Processing control commands: reassign -1 sunflow Bug #761550 [src:imagemagick] sunflow: FTBFS: convert: unable to open file `/tmp/magick-25279uk8HYnu9HiFf': No such file or directory @ error/constitute.c/ReadImage/540. Bug reassigned from package 'src:imagemagick' to 'sunflow'. Ignoring request to alter found versions of bug #761550 to the same values previously set Ignoring request to alter fixed versions of bug #761550 to the same values previously set -- 761550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761550 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#760804: serf: FTBFS: Directory /usr/include/mit-krb5 found where file expected.
On Mon, Sep 15, 2014 at 09:08:46PM +0200, Jörg Frings-Fürst wrote: Hallo, I have refreshed the patch from James McCoy for scons v 2.3.3 and uploaded the package to mentors[1]. Note that I submitted a different patch upstream, as can be seen in the forwarded link. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy james...@debian.org signature.asc Description: Digital signature
Bug#751694: marked as done (morfologik-stemming: FTBFS - build-dep on non-existent package libcarrotsearch-hppc-java)
Your message dated Mon, 15 Sep 2014 21:31:01 +0200 with message-id 874mw8wuiy@msgid.hilluzination.de and subject line carrotsearch-hppc entered unstable has caused the Debian Bug report #751694, regarding morfologik-stemming: FTBFS - build-dep on non-existent package libcarrotsearch-hppc-java 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.) -- 751694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: morfologik-stemming Version: 1.9.0+dfsg-0.1 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] - Attempting to parse the build-deps - Considering build-dep debhelper (= 9) - Trying debhelper - Considering build-dep cdbs - Trying cdbs - Considering build-dep default-jdk - Trying default-jdk - Considering build-dep maven-debian-helper (= 1.5) - Trying maven-debian-helper - Considering build-dep libcommons-cli-java - Trying libcommons-cli-java - Considering build-dep libcarrotsearch-hppc-java - Trying libcarrotsearch-hppc-java - Cannot install libcarrotsearch-hppc-java; apt errors follow: Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package libcarrotsearch-hppc-java E: Could not satisfy build-dependency. Best, Michael pgplpM42rrwPC.pgp Description: PGP signature ---End Message--- ---BeginMessage--- #736647 was closed on Fri, 29 Aug 2014 04:00:13 +... so this bug can be closed as well. Cheers, -Hilko---End Message---
Bug#756783: marked as done (jemalloc: FTBFS on powerpc)
Your message dated Mon, 15 Sep 2014 19:33:44 + with message-id e1xtc1w-0001sw...@franck.debian.org and subject line Bug#756783: fixed in jemalloc 3.6.0-3 has caused the Debian Bug report #756783, regarding jemalloc: FTBFS on powerpc 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.) -- 756783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jemalloc Version: 3.6.0-2 Severity: serious Justification: fails to build from source jemalloc failed to build on powerpc with: | === test/unit/rb === | test_rb_empty: pass | Illegal instruction | Test harness error | make[2]: *** [check] Error 1 The full build log is available at https://buildd.debian.org/status/fetch.php?pkg=jemallocarch=powerpcver=3.6.0-2stamp=1406109194. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: jemalloc Source-Version: 3.6.0-3 We believe that the bug you reported is fixed in the latest version of jemalloc, 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 756...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stig Sandbeck Mathisen s...@debian.org (supplier of updated jemalloc 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, 15 Sep 2014 20:58:29 +0200 Source: jemalloc Binary: libjemalloc-dev libjemalloc1 libjemalloc1-dbg Architecture: source amd64 Version: 3.6.0-3 Distribution: unstable Urgency: medium Maintainer: Stig Sandbeck Mathisen s...@debian.org Changed-By: Stig Sandbeck Mathisen s...@debian.org Description: libjemalloc-dev - development files and documentation for jemalloc libjemalloc1 - general-purpose scalable concurrent malloc(3) implementation libjemalloc1-dbg - debug symbols for jemalloc Closes: 756783 Changes: jemalloc (3.6.0-3) unstable; urgency=medium . * debian/control: update Vcs-Browser, Testsuite * rebuild (Closes: #756783) Checksums-Sha1: 17090f4e9b0bcdb0cd1aaf1f9c297f1c75d0075d 1379 jemalloc_3.6.0-3.dsc 75147d65dc84af2be4e8aa91d81f0bf01272864e 10328 jemalloc_3.6.0-3.debian.tar.xz 2bd6d98d3c9360225691cd4e071cdb9d8d686cfc 182602 libjemalloc-dev_3.6.0-3_amd64.deb a38a67f8ef02f4bd501311561474bd3aadd402aa 89144 libjemalloc1_3.6.0-3_amd64.deb 4f0a380bfee275f37cda2450a9da4c1d21e32f84 327400 libjemalloc1-dbg_3.6.0-3_amd64.deb Checksums-Sha256: e23bcf280dab72eb0ff605363401d909fb8617fe3dd1211e89cb7062fe85523c 1379 jemalloc_3.6.0-3.dsc a5203e66f100894c95498519dd4720211235cacf0d9a5479da8d05f1639ee676 10328 jemalloc_3.6.0-3.debian.tar.xz b2712319c185cf64f667be55f8bcc10f13fc3236bef3c07c013b09248bedc764 182602 libjemalloc-dev_3.6.0-3_amd64.deb caeeb8b60bee0b732de25b6091dae30d58f1cebcf7467900525d5d266d4360ba 89144 libjemalloc1_3.6.0-3_amd64.deb 4a827e92a9f0b71bc6f6193b1334947a13dd97f7a1c87d0731d5109b32579dcf 327400 libjemalloc1-dbg_3.6.0-3_amd64.deb Files: b30234f6a3b19496dade823f17d40868 182602 libdevel extra libjemalloc-dev_3.6.0-3_amd64.deb a320272e6e651c382c7dcae3d56eb2bf 89144 libs extra libjemalloc1_3.6.0-3_amd64.deb c3150cbc90e2b6daf96bf4034262c4d6 327400 debug extra libjemalloc1-dbg_3.6.0-3_amd64.deb 7005ebd819a314c75be394c1ba1a8939 1379 libs extra jemalloc_3.6.0-3.dsc add9aed72889ed1862853cdc71d58628 10328 libs extra jemalloc_3.6.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlQXO+gACgkQQONU2fom4u6aOwCfReB+lr2j0PLeDXZ+3X2Bkjte /34AoINfxnsSL3wnIax7yiG7ULwcf/mL =d2v8 -END PGP SIGNATUREEnd Message---
Processed: Please retry with current version
Processing control commands: tag -1 moreinfo Bug #746456 [google-perftools] FTBFS as test does not terminate Added tag(s) moreinfo. -- 746456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746456 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#746456: Please retry with current version
Control: tag -1 moreinfo Michael, could you please retry your build attempt with the current version of google-perftools (2.2.1-0.1)? Before I made my NMU, I built in sbuild on amd64 -- and I am pretty sure that the testsuite was run successfully. 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: Please retry with current version
Processing control commands: tag -1 moreinfo Bug #746456 [google-perftools] FTBFS as test does not terminate Ignoring request to alter tags of bug #746456 to the same tags previously set -- 746456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746456 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#761371: marked as done (virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds)
Your message dated Mon, 15 Sep 2014 19:49:48 + with message-id e1xtchu-0003dg...@franck.debian.org and subject line Bug#761371: fixed in virtuoso-opensource 6.1.6+dfsg2-2 has caused the Debian Bug report #761371, regarding virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds 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.) -- 761371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: virtuoso-opensource Version: 6.1.6+dfsg2-1 Severity: serious Your package failed to build on kbsd: https://buildd.debian.org/status/fetch.php?pkg=virtuoso-opensourcearch=kfreebsd-amd64ver=6.1.6%2Bdfsg2-1stamp=1410539349 https://buildd.debian.org/status/fetch.php?pkg=virtuoso-opensourcearch=kfreebsd-i386ver=6.1.6%2Bdfsg2-1stamp=1410543249 Excerpt from the log: Virtuoso.ini creation... Waiting Virtuoso Server start on port ... netstat: kvm not available: /dev/mem: Permission denied Waiting Virtuoso Server start on port ... netstat: kvm not available: /dev/mem: Permission denied [...] Waiting Virtuoso Server start on port ... netstat: kvm not available: /dev/mem: Permission denied ***FAILED: Could not start Virtuoso Server within 600 seconds make[4]: *** [dbpedia_dav.vad] Error 1 Note how there were errors about /dev/mem in previous successful builds, so that may be a red herring, see: https://buildd.debian.org/status/fetch.php?pkg=virtuoso-opensourcearch=kfreebsd-amd64ver=6.1.6%2Bdfsg-4stamp=1385294128 Emilio ---End Message--- ---BeginMessage--- Source: virtuoso-opensource Source-Version: 6.1.6+dfsg2-2 We believe that the bug you reported is fixed in the latest version of virtuoso-opensource, 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lisandro Damián Nicanor Pérez Meyer lisan...@debian.org (supplier of updated virtuoso-opensource 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, 15 Sep 2014 14:48:35 -0300 Source: virtuoso-opensource Binary: virtuoso-opensource virtuoso-server virtuoso-minimal virtuoso-opensource-6.1 virtuoso-opensource-6.1-common virtuoso-opensource-6.1-bin virtuoso-vsp-startpage virtuoso-vad-conductor virtuoso-vad-doc virtuoso-vad-demo virtuoso-vad-tutorial virtuoso-vad-rdfmappers virtuoso-vad-sparqldemo virtuoso-vad-syncml virtuoso-vad-bpel virtuoso-vad-isparql virtuoso-vad-ods libvirtodbc0 libvirtuoso5.5-cil Architecture: source all amd64 Version: 6.1.6+dfsg2-2 Distribution: unstable Urgency: medium Maintainer: Debian Krap Maintainers debian-qt-...@lists.debian.org Changed-By: Lisandro Damián Nicanor Pérez Meyer lisan...@debian.org Description: libvirtodbc0 - high-performance database - ODBC libraries libvirtuoso5.5-cil - high-performance database - Mono assemblies virtuoso-minimal - high-performance database - core dependency package virtuoso-opensource - high-performance database virtuoso-opensource-6.1 - high-performance database - support files virtuoso-opensource-6.1-bin - high-performance database - binaries virtuoso-opensource-6.1-common - high-performance database - common files virtuoso-server - high-performance database - server dependency package virtuoso-vad-bpel - high-performance database - BPEL module virtuoso-vad-conductor - high-performance database - conductor module virtuoso-vad-demo - high-performance database - demo module virtuoso-vad-doc - high-performance database - documentation module virtuoso-vad-isparql - high-performance database - iSPARQL module virtuoso-vad-ods - high-performance database - Open Data Spaces module virtuoso-vad-rdfmappers - high-performance database - RDF mappers module virtuoso-vad-sparqldemo - high-performance database - SPARQL demo module virtuoso-vad-syncml - high-performance database - SyncML module virtuoso-vad-tutorial - high-performance database - tutorial module virtuoso-vsp-startpage - high-performance database - web interface files Closes: 761371 Changes: virtuoso-opensource (6.1.6+dfsg2-2) unstable; urgency=medium . * Update
Bug#756783: jemalloc: FTBFS on powerpc
Hi, thanks for the bug report. I'm unable to reproduce this on the powerpc porterbox partch.debian.org. There are no significant changes in the packaging between jemalloc 3.6.0-1 (did build) and 3.6.0-2 (did not build) I'm uploading again, in the hope that the powerpc buildd box will treat it as well as the porterbox does. Buildd logs: * https://buildd.debian.org/status/logs.php?pkg=jemallocver=3.6.0-2arch=powerpcsuite=sid * https://buildd.debian.org/status/logs.php?pkg=jemallocver=3.6.0-1arch=powerpcsuite=sid Packaging changes between debian/3.6.0-1...debian/3.6.0-2: * http://anonscm.debian.org/cgit/collab-maint/jemalloc.git/log/?qt=rangeq=debian/3.6.0-1...debian/3.6.0-2showmsg=1 -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761550: Imagemagick transition
the debdiff debdiff Description: Binary data
Processed: Depend on libmagickcore-6.q16-2-extra instead of libmagickcore-extra
Processing control commands: block #740495 by -1 Bug #740495 [release.debian.org] transition: imagemagick 740495 was blocked by: 758001 758459 746228 701655 758443 747857 758435 747907 747908 761104 740495 was blocking: 758492 Added blocking bug(s) of 740495: 761725 -- 740495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740495 761725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761725 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#761725: Depend on libmagickcore-6.q16-2-extra instead of libmagickcore-extra
package: ktikz version: 0.10-3 severity: serious control: block #740495 by -1 Hi due to imagemagick transition could depend on libmagickcore-extra | libmagickcore-6.q16-2-extra instead of only libmagickcore-extra. I plan do to a NMU soon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761517: Confirming...
This bug is also present when using calibre 2.2.0+dfsg-2 and python-sip 4.16.3+dfsg in a amd64 installation. Regards, -- tiago -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Depend on libmagickcore-6.q16-2-extra instead of libmagickcore-extra
Processing control commands: block #740495 by -1 Bug #740495 [release.debian.org] transition: imagemagick 740495 was blocked by: 758001 701655 746228 758459 758443 747857 758435 747907 761725 747908 761104 740495 was blocking: 758492 Added blocking bug(s) of 740495: 761726 -- 740495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740495 761726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761726 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#761726: Depend on libmagickcore-6.q16-2-extra instead of libmagickcore-extra
package: pyxplot version: 0.9.2-4 severity: serious control: block #740495 by -1 Hi due to imagemagick transition could depend on libmagickcore-extra | libmagickcore-6.q16-2-extra instead of only libmagickcore-extra. I plan do to a NMU soon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
