Bug#691307: libpetsc3.2-dbg: PETSC_CHECKS m4 macro fails with PETSC_ARCH=linux-gnu-c-debug
Package: libpetsc3.2-dbg Version: 3.2.dfsg-5 Severity: grave Justification: renders package unusable Dear Maintainer, Recently, I tried to link PETSC in debugging mode, but unfortunately it failed. I run my configure script that makes use of the PETSC_CHECKS macro and set the PETSC_DIR and PETSC_ARCH environment variables: ./configure PETSC_DIR=/usr/lib/petscdir/3.2 PETSC_ARCH=linux-gnu-c-debug Unfortunately, after some time configure told me that it could not compile the test that checks for PetscPrintf. After taking a look at the log files, I noticed that this was due to not linking to hdf5 libraries. I added -lhdf5 to the PETSC_EXTERNAL_LIBS variable within the /usr/share/aclocal/petsc.m4 macro (which links to /usr/lib/petscdir/3.2/aclocal/petsc.m4) and now everything is working. I didn't test the static library from the non-debug package. Best regards, Markus Mayr -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpetsc3.2-dbg depends on: ii libpetsc3.2-dev 3.2.dfsg-5 libpetsc3.2-dbg recommends no packages. Versions of packages libpetsc3.2-dbg suggests: pn petsc-dbg none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689951: Package appears to be non-free
Dear Andreas, I personally would be happy if you would decide for the later because in addition you get a lot of other information and how people might deal together with other problems. After my answer yesterday I subscribed to the CamiTK package only, but reading your answer, I just reconsidered and subscribed to debian-med mailing-list as it seems the best option to improve my learning curve. In this case would CamITK remain in *main*! Considering the fact that you know all these facts - would you volunteer to do the needed steps? I am on a tight schedule this week. Do you think it could be ok if: - I remove the licence offending part of the CamiTK source for the moment (the tetgen plugin) today - I do a better work at the beginning of next week where I could reintroduce the tetgen plugin but using the tetgen debian package instead and correct the two other bugs properly (#689021 and 690830) For #690830 there is a patch proposal and there is also a another way that I would like to try first (that will probably have better compiler specific/multi-arch support). Thanks again, all your help is really appreciated. -- Emmanuel Promayon UJF-Grenoble 1, CNRS, TIMC-IMAG UMR 5525 (équipe GMCAO) Institut de l'Ingénierie de l'Information de Santé Faculté de Médecine - 38706 La Tronche cedex - France Tel. +33/0 456 52 00 03 - Fax. +33/0 456 52 00 55 - B7 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682616: marked as done (chromium: Chromium keeps crashing with segfaults)
Your message dated Wed, 24 Oct 2012 08:23:06 +0200 with message-id 5087894a.2030...@iuculano.it and subject line Fixed has caused the Debian Bug report #682616, regarding chromium: Chromium keeps crashing with segfaults 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.) -- 682616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: chromium Version: 20.0.1132.57~r145807-1 Severity: important Dear Maintainer, * What led up to the situation? I was browsing with Chromium as normal. * What exactly did you do (or not do) that was effective (or ineffective)? All crashes happened randomly. * What was the outcome of this action? Chromium crashes with segfaults. * What outcome did you expect instead? Not crash. Here are the segfaults I gathered from dmesg: [ 2419.690487] chromium[4043]: segfault at 100 ip 0100 sp 7fff9805d758 error 14 in icon-theme.cache[7f0a5f99d000+41bb000] [10199.843439] chromium[6900]: segfault at 64 ip 0064 sp 7fff2d271298 error 14 in libspeexdsp.so.1.5.0[7fa88a878000+12000] [10208.614005] chromium[10473]: segfault at 44 ip 0044 sp 7fff17c798f8 error 14 [12644.372979] chromium[11300]: segfault at 0 ip (null) sp 7fffe4a5d418 error 14 in SYSV (deleted)[7f40aabba000+4a8000] [28646.980941] chromium[13056]: segfault at 55 ip 0055 sp 7fffb82272d8 error 14 in ipag.ttf[7f4126af5000+5f3000] [29006.979059] chromium[20435]: segfault at 45 ip 0045 sp 7fff07b899e8 error 14 in SYSV (deleted)[7f80eb532000+4a8000] The update came in this morning, then the floodgate opened. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii chromium-inspector 20.0.1132.57~r145807-1 ii gconf-service 3.2.5-1 ii libasound2 1.0.25-3 ii libatk1.0-0 2.4.0-2 ii libbz2-1.0 1.0.6-3 ii libc6 2.13-33 ii libcairo2 1.12.2-2 ii libcups21.5.3-1 ii libdbus-1-3 1.6.0-1 ii libevent-2.0-5 2.0.19-stable-3 ii libexpat1 2.1.0-1 ii libflac81.2.1-6 ii libfontconfig1 2.9.0-6 ii libfreetype62.4.9-1 ii libgcc1 1:4.7.1-2 ii libgconf-2-43.2.5-1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgnome-keyring0 3.4.1-1 ii libgtk2.0-0 2.24.10-1 ii libjpeg88d-1 ii libnspr42:4.9.1-1 ii libnss3 2:3.13.5-1 ii libnss3-1d 2:3.13.5-1 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-1 ii libpulse0 2.0-3 ii libspeex1 1.2~rc1-6 ii libstdc++6 4.7.1-2 ii libudev0175-3.1 ii libwebp20.1.3-3 ii libx11-62:1.5.0-1 ii libxcomposite1 1:0.4.3-2 ii libxext62:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxml2 2.8.0+dfsg1-4 ii libxrender1 1:0.9.7-1 ii libxslt1.1 1.1.26-13 ii libxss1 1:1.2.2-1 ii xdg-utils 1.1.0~rc1+git20111210-6 ii zlib1g 1:1.2.7.dfsg-13 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n none -- no debconf information ---End Message--- ---BeginMessage--- Source: chromium-browser Source-Version: 22.0.1229.94~r161065-1 Hi, I think this bug is fixed, feel free to reopen it if necessary. Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature ---End Message---
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Wednesday 24 October 07:03:07 UTC 2012 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: a href=http://packages.qa.debian.org/libav;libav/a tags 691088 + pending Bug #691088 [libavutil51] libavcodec-extra-53: symbol ff_sqrt_tab, version LIBAVUTIL_51 not defined in file libavutil.so.51 with link time reference Added tag(s) pending. # Source package in NEW: libnetfilter-acct tags 666026 + pending Bug #666026 [wnpp] ITP: libnetfilter-acct -- nfacct library files Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 666026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666026 691088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691088 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#689951: Package appears to be non-free
Hi Emmanuel, On Wed, Oct 24, 2012 at 08:47:33AM +0200, Emmanuel Promayon wrote: I personally would be happy if you would decide for the later because in addition you get a lot of other information and how people might deal together with other problems. After my answer yesterday I subscribed to the CamiTK package only, but reading your answer, I just reconsidered and subscribed to debian-med mailing-list as it seems the best option to improve my learning curve. Fine. So in future mails I will spare the To: to your address - you should receive the messages via Bug tracking system and mailing list. :-) In this case would CamITK remain in *main*! Considering the fact that you know all these facts - would you volunteer to do the needed steps? I am on a tight schedule this week. Do you think it could be ok if: - I remove the licence offending part of the CamiTK source for the moment (the tetgen plugin) today If you can remove it upstream this would probably the bes solution. Please note the following: The Debian Release team does not accept new upstream versions for Wheezy in general. So if the change should be successfull for propagation to Wheezy please make prfectly sure that this change is the only one compared to the tarball currently in testing. So you culd do something like camitk-3.0.2.1.tar.gz and mention in the upstream changelog something like - Just removed parts of code which are not DFSG free (no other code changes In the debian/changelog we could refer to the fact mentioned in your upstream changelog to convince the release team that we do not attempt to sneak in new upstream code. Otherwise we would need to backport the changes to the version inside Debian. (In case my advise was not clear enough feel free to ask for further clarification.) - I do a better work at the beginning of next week where I could reintroduce the tetgen plugin but using the tetgen debian package instead and correct the two other bugs properly (#689021 and 690830) May be I was not fully clear. If we drop the tetgen dependency completely (and if I understood correctly the plugin in queston needs to be dropped / deactivated as well) then and only than camitk can remain in Debian main. If there is some dependency from any non-free component (be it tetgen or whatever) the package needs to be moved from main to contrib which is something I would like to avoid. So the action to let camitk remain in main is the following: 1. Remove tetgen fom the upstream tarball (may be also cut the plugin in question as well if it does not make any sense without tetgen). 2. Build a camitk package targeting at main from this source tarball. To gain full functionality we could gain (for Wheezy+1) optionally with 3. Create another source tarball camitk-plugins (or camitk-plugins-non-dfsg or whatever name). 4. Build an according Debian package from this plugins tarball linking with Debian packaged tetgen targeting at contrib and recommending camitk from main 5. You can Suggests camitk-plugins in the camitk package (but not Recommends, which is only allowed inside main) For #690830 there is a patch proposal and there is also a another way that I would like to try first (that will probably have better compiler specific/multi-arch support). This could be done if you are pretty sure about this and the change is obviosely simple and straight to get accepted by the release team. While it is a really good thing to fix this bug we need to make pretty sure it will not introduce new problems (which is the sense of the freeze process). For the time line: I think doing step 1.+2. from above until end of October is fine. Everything else has time because it does not affect the current release. Is this doable for you? Thanks again, all your help is really appreciated. Also thanks to you because without your cooperation we would not have competence and manpower to maintain camitk inside Debian. Kind regards 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#688197: Where is the upload
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, from your last post, I conclude that the fix is ready to be released. Could you please upload the fixed version to unstable or, if you are not sure of it, provide the source package here for others to test? - -- Cheers, Nik PGP-Fingerprint: 8BC7 ABAB C2F2 4D5E 24FC FC1C DB0E A4BC E210 7412 Please contact me for a face-to-face meeting if you wish to exchange signatures with me. Signature Policy: https://www.dominik-george.de/gpg-policy.txt.asc Public key: https://www.dominik-george.de/gpg.asc X.509 certificate fingerprint for key download: 51:D8:36:36:7E:20:3F:E7:AB:EF:B8:83:25:A6:BB:74:48:03:3D:F0 Please do NOT send HTML mail! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQJOBAEBAgA4BQJQh6SPMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQx86z/xVBKI6hWw//Z+HQshgDYWuDDMwGzX4g pbb6sZ/wSBdgRWt0zXZ+64Ezq2nFzc190bmZkJCFcXqlGhBXhErw4ijRohviQsq7 Sjxm4tqiG6bGmDoEFIr4RyOoxlt4b6wAARvwbxYd7yU5idWIx/Tr+CtRCf9haZx5 qh+Ud/74run2/nscj+mzLycMyB06jf6ufK+raD47JXqQtfDJqk93+VytFW9Tmdg7 yGFvq9bXYDNBSqvE+HK22PNbuKwAWxsh4rYl3jJGesLxLMLAroR9tGwFFg4dIkZv Ms/Vaz9+Q5AU/AcA1/rGCVdJ/OSWvx2IWlPFYK35/RyDEz11omG+7pprth9vfI8B CF5WuU/vVurd4McqwNUmOGTvrhz//EYrUX17kDcWPZjJW+t4aNLKcZO2ctpmbmjQ EK6mRiD9L4jjqlU1iTwyUbtIOfkoVuo6+utrIKrgLA3xbNsu8PugAgk9NgRTv8u8 1WoyYK0jBQ3+CBW9rJkYSn1qf5WyhxN04q65LMuZ8GM3u01xkpZrdKcW+0rH0pGS ifP/FnAJiA975+QmwnjRozqNxYVqXg3THTONZ+Nu7Kkuau8g9GryT4sjgO2UFS3V CIjVYHZ6+rg1sklQpw8cAAINlIJ9TldmUZPnxvv1rLdFwstSPfa+5fEj2/utm0++ QrfsXjZl+clmThGdOJ/w3ZA= =kbVW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Pkg-octave-devel] Bug#691311: error: feval: function `unimplemented' not found
Processing control commands: severity -1 serious Bug #691311 [octave] error: feval: function `unimplemented' not found Severity set to 'serious' from 'normal' tags -1 + confirmed Bug #691311 [octave] error: feval: function `unimplemented' not found Added tag(s) confirmed. -- 691311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691311 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#689951: Package appears to be non-free
Hi Andreas, If you can remove it upstream this would probably the bes solution. Please note the following: The Debian Release team does not accept new upstream versions for Wheezy in general. So if the change should be successfull for propagation to Wheezy please make prfectly sure that this change is the only one compared to the tarball currently in testing. So you culd do something like camitk-3.0.2.1.tar.gz and mention in the upstream changelog something like - Just removed parts of code which are not DFSG free (no other code changes In the debian/changelog we could refer to the fact mentioned in your upstream changelog to convince the release team that we do not attempt to sneak in new upstream code. Otherwise we would need to backport the changes to the version inside Debian. (In case my advise was not clear enough feel free to ask for further clarification.) May be I was not fully clear. If we drop the tetgen dependency completely (and if I understood correctly the plugin in queston needs to be dropped / deactivated as well) then and only than camitk can remain in Debian main. If there is some dependency from any non-free component (be it tetgen or whatever) the package needs to be moved from main to contrib which is something I would like to avoid. So the action to let camitk remain in main is the following: 1. Remove tetgen fom the upstream tarball (may be also cut the plugin in question as well if it does not make any sense without tetgen). 2. Build a camitk package targeting at main from this source tarball. Would it not be possible/preferable/easier to convince the release team to remove the non-free code as a debian package patch? If not, as at the moment the upstream changelog is not very visible, should I add a specific news on the web page to explain what happened between camitk-3.0.2.1.tar.gz and camitk-3.0.2.tar.gz? To gain full functionality we could gain (for Wheezy+1) optionally with 3. Create another source tarball camitk-plugins (or camitk-plugins-non-dfsg or whatever name). 4. Build an according Debian package from this plugins tarball linking with Debian packaged tetgen targeting at contrib and recommending camitk from main 5. You can Suggests camitk-plugins in the camitk package (but not Recommends, which is only allowed inside main) That sounds like the perfect idea. For #690830 there is a patch proposal and there is also a another way that I would like to try first (that will probably have better compiler specific/multi-arch support). This could be done if you are pretty sure about this and the change is obviosely simple and straight to get accepted by the release team. While it is a really good thing to fix this bug we need to make pretty sure it will not introduce new problems (which is the sense of the freeze process). For the time line: I think doing step 1.+2. from above until end of October is fine. Everything else has time because it does not affect the current release. Is this doable for you? Yes, I think there is no problem to do that between now and the end of the month. -- Emmanuel Promayon UJF-Grenoble 1, CNRS, TIMC-IMAG UMR 5525 (équipe GMCAO) Institut de l'Ingénierie de l'Information de Santé Faculté de Médecine - 38706 La Tronche cedex - France Tel. +33/0 456 52 00 03 - Fax. +33/0 456 52 00 55 - B7 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689951: Package appears to be non-free
Hi, On Wed, Oct 24, 2012 at 10:46:51AM +0200, Emmanuel Promayon wrote: 1. Remove tetgen fom the upstream tarball (may be also cut the plugin in question as well if it does not make any sense without tetgen). 2. Build a camitk package targeting at main from this source tarball. Would it not be possible/preferable/easier to convince the release team to remove the non-free code as a debian package patch? Definitely not. The release team has the only task to accept or remove packges created by somebody else (read: maintainer or creator of a non-maintainer upload). The release team will not change anything inside a package. Moreover: The problem is in the source of the package and thus you can not fix it by a patch. If you prefer it is also possile to create a source tarball camitk_3.0.2+dfsg1.orig.tar.gz which can be created by removing those non-free bits from upstream camitk-3.0.2.tar.gz. We would usually do this if no upstream author is involved and it is perfectly OK as well. In this case you should document the removal in debian/README.source and write a target get-orig-source for debian/rules. I'd regard it less effort to simply do it inside the upstream source that's why my suggestion. If not, as at the moment the upstream changelog is not very visible, should I add a specific news on the web page to explain what happened between camitk-3.0.2.1.tar.gz and camitk-3.0.2.tar.gz? That's OK as well. Just some documentation that no new code is in this new version is sufficient (I havn't checked the surce when writing my advise). To gain full functionality we could gain (for Wheezy+1) optionally with 3. Create another source tarball camitk-plugins (or camitk-plugins-non-dfsg or whatever name). 4. Build an according Debian package from this plugins tarball linking with Debian packaged tetgen targeting at contrib and recommending camitk from main 5. You can Suggests camitk-plugins in the camitk package (but not Recommends, which is only allowed inside main) That sounds like the perfect idea. Nice that you like it. For the time line: I think doing step 1.+2. from above until end of October is fine. Everything else has time because it does not affect the current release. Is this doable for you? Yes, I think there is no problem to do that between now and the end of the month. Fine. Just keep on asking if something remains unclear or you might need any other help. Kind regards 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#687320: marked as done (grub-efi-amd64: Stuck at grub recovery prompt when USB media reader attached)
Your message dated Wed, 24 Oct 2012 09:47:55 +
with message-id e1tqxz5-0007gc...@franck.debian.org
and subject line Bug#687320: fixed in grub2 1.99-23.1
has caused the Debian Bug report #687320,
regarding grub-efi-amd64: Stuck at grub recovery prompt when USB media reader
attached
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.)
--
687320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: grub-efi-amd64
Version: 1.99-22.1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
With the recent hubbub about UEFI I thought I'd try getting my new system, an
Asus P8H61-M LE/CSM with Core i53450, booting using EFI instead of bios
compatibility mode.
At first I tried to convert my system to uefi boot without reinstalling by
following some guides online, but I was left with a system that wouldn't boot
past just GRUB showing the upper left.
With no clue what I did wrong I decided to try Steve's efi test install cd 1
which installed elilo by default. This gave me a booting system for a while,
but I was unhappy with elilo so I tried switching over to grub by adding
/boot/efi to fstab and installing grub-efi-amd64. On rebooting I got invalid
sector size 65535
Figuring that I'd fubared my system again I reinstalled using Steve's 3rd CD.
This left my system booting to the same grub recovery prompt and the invalid
sector size 65535. At this point I searched for the error and found:
http://savannah.gnu.org/bugs/?35382
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/975061
So now I can boot my system, either by opening the case and disconnecting my
card reader before power up OR manually setting the prefix and loading/running
the normal module.
I've tried several variations of running grub-install with and without the card
reader attached, rebooting between tries, and I have also tried manually
setting things in devices.map. So far the only way I can get my system to boot
without intervention is to disconnect the card reader.
This is my first time submitting a bug... please me gentle
Thanks :)
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/disk/by-uuid/aa3909a2-fcc8-4b69-9b32-f6716fdd2e7e / ext4
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda1 /boot/efi vfat
rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors
=remount-ro 0 0
/dev/sdb1 /home xfs rw,relatime,attr2,noquota 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-ST340016A_3HS4JDEX
(hd1) /dev/disk/by-id/ata-ST3320613AS_9SZ6H6P4
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod efi_gop
insmod efi_uga
insmod video_bochs
insmod video_cirrus
}
insmod part_gpt
insmod ext2
set root='(hd5,gpt2)'
search --no-floppy --fs-uuid --set=root aa3909a2-fcc8-4b69-9b32-f6716fdd2e7e
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=1440x900x32
load_video
insmod gfxterm
insmod part_gpt
insmod ext2
set root='(hd5,gpt2)'
search --no-floppy --fs-uuid --set=root aa3909a2-fcc8-4b69-9b32-f6716fdd2e7e
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='(hd5,gpt2)'
search --no-floppy --fs-uuid --set=root aa3909a2-fcc8-4b69-9b32-f6716fdd2e7e
insmod png
if background_image /usr/share/images/desktop-base/joy-grub.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 3.5-trunk-amd64' --class debian --class
gnu-linux --class gnu --class os {
load_video
set gfxpayload=keep
insmod gzio
Processed: Fwd: Processed: Re: Bug#691140: graphicsmagick: libmagickcore-dev uses out of date libtiff4-dev
Processing commands for cont...@bugs.debian.org: reassign 691140 libgeotiff-dev Bug #691140 [libmagickcore-dev] graphicsmagick: libmagickcore-dev uses out of date libtiff4-dev Bug reassigned from package 'libmagickcore-dev' to 'libgeotiff-dev'. Ignoring request to alter found versions of bug #691140 to the same values previously set Ignoring request to alter fixed versions of bug #691140 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 691140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691140 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#682735: questions regarding debian bug #682735
I have a new package version containing your patch ready. I filed #689588 [1] to ask the Release team whether the change could get a freeze exception. I got no response so far. Best Regards Jan [1] http://bugs.debian.org/689588 -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://ddportfolio.debian.net/ - http://people.debian.org/~jandd/ signature.asc Description: Digital signature
Bug#631968: marked as done (gnome-terminal: fails to start on kFreeBSD)
Your message dated Wed, 24 Oct 2012 12:02:41 + with message-id e1tqzfv-0003od...@franck.debian.org and subject line Bug#631968: fixed in glib2.0 2.33.12+really2.32.4-3 has caused the Debian Bug report #631968, regarding gnome-terminal: fails to start on kFreeBSD 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.) -- 631968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-terminal Version: 3.0.1-1 Severity: grave User: debian-...@lists.debian.org Usertags: kfreebsd (this bug most likely needs reassigning, but I don't know where, so filing it on the application that exhibits the symptom) gnome-terminal aborts on start, with unknown signal: rmh@dimoni:~$ LD_LIBRARY_PATH=/usr/lib/debug/lib/x86_64-kfreebsd-gnu gdb gnome-terminal GNU gdb (GDB) 7.2-debian Copyright (C) 2010 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-kfreebsd-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/gnome-terminal...(no debugging symbols found)...done. (gdb) r Starting program: /usr/bin/gnome-terminal Program received signal ?, Unknown signal. __pthread_sigsuspend () at ../ports/sysdeps/unix/bsd/bsd4.4/kfreebsd/linuxthreads/pt-sigsuspend.S:24 24 ../ports/sysdeps/unix/bsd/bsd4.4/kfreebsd/linuxthreads/pt-sigsuspend.S: El fitxer o directori no existeix. in ../ports/sysdeps/unix/bsd/bsd4.4/kfreebsd/linuxthreads/pt-sigsuspend.S (gdb) bt #0 __pthread_sigsuspend () at ../ports/sysdeps/unix/bsd/bsd4.4/kfreebsd/linuxthreads/pt-sigsuspend.S:24 #1 0x000802e433b8 in __pthread_wait_for_restart_signal (self=value optimized out) at pthread.c:1274 #2 0x000802e43f8c in suspend (thread=0x688ae0, attr=value optimized out, start_routine=value optimized out, arg=value optimized out) at restart.h:34 #3 __pthread_create_2_1 (thread=0x688ae0, attr=value optimized out, start_routine=value optimized out, arg=value optimized out) at pthread.c:877 #4 0x000801fa8212 in g_thread_create_posix_impl (thread_func=0x802455c00 g_thread_create_proxy, arg=0x688ab0, stack_size=value optimized out, joinable=value optimized out, bound=0, priority=G_THREAD_PRIORITY_NORMAL, thread=0x688ae0, error=0x7fffda68) at /build/buildd-glib2.0_2.28.6-1-kfreebsd-amd64-yDxNka/glib2.0-2.28.6/./gthread/gthread-posix.c:355 #5 0x00080245688d in g_thread_create_full (func=value optimized out, data=value optimized out, stack_size=0, joinable=0, bound=0, priority=value optimized out, error=0x7fffdac8) at /build/buildd-glib2.0_2.28.6-1-kfreebsd-amd64-yDxNka/glib2.0-2.28.6/./glib/gthread.c:1967 #6 0x000802458126 in g_thread_pool_start_thread (pool=0x688c00, error=0x0) at /build/buildd-glib2.0_2.28.6-1-kfreebsd-amd64-yDxNka/glib2.0-2.28.6/./glib/gthreadpool.c:420 #7 0x000802458822 in g_thread_pool_push (pool=value optimized out, data=0x655b30, error=0x0) at /build/buildd-glib2.0_2.28.6-1-kfreebsd-amd64-yDxNka/glib2.0-2.28.6/./glib/gthreadpool.c:558 #8 0x0008015ea5ad in g_async_initable_real_init_async (initable=value optimized out, io_priority=0, cancellable=0x0, callback=0x801660050 bus_get_async_initable_cb, user_data=0x675760) at /build/buildd-glib2.0_2.28.6-1-kfreebsd-amd64-yDxNka/glib2.0-2.28.6/./gio/gasyncinitable.c:285 #9 0x000801661c53 in g_bus_get (bus_type=G_BUS_TYPE_SESSION, cancellable=0x0, callback=value optimized out, user_data=value optimized out) at /build/buildd-glib2.0_2.28.6-1-kfreebsd-amd64-yDxNka/glib2.0-2.28.6/./gio/gdbusconnection.c:6383 #10 0x00080166e94b in g_bus_own_name (bus_type=G_BUS_TYPE_SESSION, name=0x6540a0 org.gnome.Terminal.Display_0_0, flags=G_BUS_NAME_OWNER_FLAGS_NONE, bus_acquired_handler=0x417d60, name_acquired_handler=0x417cc0, name_lost_handler=0x418120, user_data=0x654b00, user_data_free_func=0) at /build/buildd-glib2.0_2.28.6-1-kfreebsd-amd64-yDxNka/glib2.0-2.28.6/./gio/gdbusnameowning.c:622 #11 0x00414fb9 in ?? () #12 0x0008030771e9 in __libc_start_main (main=0x414d00, argc=1, ubp_av=0x7fffdcf0, init=value optimized out, fini=0x94016030, rtld_fini=0, stack_end=0x7fffdcd8) at libc-start.c:257 #13 0x0041512c in ?? () #14 0x7fffdcd8 in ?? () #15 0x001c
Bug#691311: [Pkg-octave-devel] Bug#691311: Bug#691311: error: feval: function `unimplemented' not found
On Wed, Oct 24, 2012 at 4:32 AM, Sébastien Villemot wrote: It appears that octave 3.6.2 does not work with liboctave1 3.6.3, and conversely octave 3.6.3 does not work with liboctave1 3.6.2. I took a look at this and the problem is simply that the load path contains Octave's version number. No soname incompatibility. And unless something is changed, this will continue to be the case between different upstream versions of octave and liboctaveX. The octave package provides the directories, and liboctinterp.so.1 has a compiled-in set of paths with its version number that it attempts to load. You can see these paths with: $ strings /usr/lib/x86_64-linux-gnu/liboctinterp.so.1 | grep /3.6../ If I print the default path from a working 3.6.3: $ octave -qf --eval disp(path) then downgrade liboctave1/sid and set that full string to be the path in the interpreter: $ octave -qf octave:1 ls error: feval: function `unimplemented' not found octave:1 path (full_path_here); octave:2 ls no more error. -- mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Broken su/sudo/whatever - breaks systems - up goes the severity
Processing commands for cont...@bugs.debian.org: severity 658739 grave Bug #658739 [gnutls26] gnutls26: LDAP+SSL account cannot use setuid binaries until gnutls26 is rebuilt with nettle not libgcrypt11 Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 658739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658739 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#625020: [chan-capi-users] Bug#625020: version HEAD no FTBFS
On 19.10.2012 23:13, Geert Stappers wrote: For the people at chan-capi-users(a)lists.melware.net, you find context at http://bugs.debian.org/625020 On Thu, Oct 18, 2012 at 01:11:13PM +0200, Geert Stappers wrote: On Thu, Oct 18, 2012 at 07:24:16AM +0200, Joerg Dorchain wrote: I would not mind a packages from ftp://ftp.chan-capi.org/chan-capi/chan_capi-HEAD.tgz , which works with the current asterisk in testing. Based upon that information, I did remove the won't fix tag The FTBFS is indeed gone in upstream's HEAD version. I got a clean debianbuild with the october 19th version of chan-capi. The most clean solution to fix this Fails To Build From Source Bug would be getting an version number greater as 1.1.5 from upstream. (They are now in the loop) Another solution would be create version something like 1.1.5+VCS20121019 chan-capi 1.1.6 is now available. regards Armin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691340: chrony: Chrony Version 1.24 from wheezy does not work on kernel 3.x
Package: chrony Version: 1.24-3.1 Severity: critical Justification: breaks unrelated software Hello, there are quite a few packages (kerberos in my case) which are dependant on a relatively exact time. I actually could not log in to my freshly installed kerberized wheezy system due to a mayor clock skew produced by a malfunctioning chrony daemon. The Version of chrony currently supplied with wheezy does have a runable daemon, but this daemon is unable to set the system clock at all. The reason for this are actually two bugs in debian BTS which have already been fixed in unstable, but only partially in the the Version which wheezy ended up with after the feature freeze. I'm talking about the following bugs: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628919 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642209 The state of the wheezy Version is that bug #628919 has been fixed incompletely. This led to bugreport #642209 which has then been fixed in unstable only by means of using a newer upstream version. There are two possible ways to fix the version supplied with wheezy: 1. Migrate to Version 1.26-2 from sid (no unsatisfiable dependancies in wheezy) 2. Apply the simple patch supplied in bug report #642209 Regards Sven -- System Information: Debian Release: wheezy APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.6.3-00694-g9017061 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chrony depends on: ii dpkg 1.16.8 ii install-info 4.13a.dfsg.1-10 ii libc6 2.13-35 ii libncurses5 5.9-10 ii libreadline5 5.2-12 ii timelimit 1.8-1 ii ucf 3.0025+nmu3 Versions of packages chrony recommends: ii udev 175-7 chrony 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: Unfuck my syntax
Processing commands for cont...@bugs.debian.org: # Meh reassign 667995 python-cups 1.9.48-1 Bug #667995 [cups] cupsd configuration: cupsdAuthorize: Empty Basic password! Bug reassigned from package 'cups' to 'python-cups'. No longer marked as found in versions cups/1.5.2-9. Ignoring request to alter fixed versions of bug #667995 to the same values previously set Bug #667995 [python-cups] cupsd configuration: cupsdAuthorize: Empty Basic password! Marked as found in versions python-cups/1.9.48-1. severity 667995 serious Bug #667995 [python-cups] cupsd configuration: cupsdAuthorize: Empty Basic password! Severity set to 'serious' from 'normal' affects 667995 cups Bug #667995 [python-cups] cupsd configuration: cupsdAuthorize: Empty Basic password! Added indication that 667995 affects cups affects 667995 system-config-printer Bug #667995 [python-cups] cupsd configuration: cupsdAuthorize: Empty Basic password! Added indication that 667995 affects system-config-printer thanks Stopping processing here. Please contact me if you need assistance. -- 667995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667995 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#691346: kfreebsd-amd64 fails to install on LSI MegaRAID SAS 2208
Package: installation-reports Severity: critical Tags: d-i -- Package-specific info: Boot method: CD Image version: debian-wheezy-DI-b3-kfreebsd-amd64-netinst.iso Date: 201210241200 Machine: IBM System x3650 M4 Partitions: no partitions Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: On this server the LSI RAID controller LSI MegaRAID SAS 2208/ServeRAID M5110e is installed. I tried installing kfreebsd-amd64 on it from CD. The installer GRUB menu works (see attachment boot.png), but right after that the FreeBSD kernel hangs during boot with an error (see attachment error.png). After 10/20 seconds another error line gets printed -- something about hard resetting something -- but it was too fast for me to take a screenshot, and the system reboots. On the very same machine I was able to install the standard debian-wheezy-DI-b3-amd64-netinst.iso without any problem. On LSI website I found this: http://kb.lsi.com/KnowledgebaseArticle16687.aspx which seems to indicate that FreeBSD 9.0 ships an obsolete kernel module for this controller, and they suggest a procedure how to create a FreeBSD 9.0 installer with an updated module. My knowledge of FreeBSD are a bit too limited for me to seriously think about recompile the kernel and injecting some additional modules, but maybe someone in the kfreebsd debian team knows how to do it? I now have the machine up and running with linux debian amd64, so I can make any needed additional hardware info -- as linux sees it -- available. I can also make the remote control console accessible to more knowledgeable people for debugging. Thanks, Tiziano PS: I did not know what severity to set, I thought that complete install failures qualifies for critical, but please downgrade it if needed. attachment: boot.pngattachment: error.png
Processed: fixed 684245 fcitx/1:4.2.6.1-1
Processing commands for cont...@bugs.debian.org:
fixed 684245 fcitx/1:4.2.6.1-1
Bug #684245 {Done: YunQiang Su wzss...@gmail.com} [fcitx] fcitx: makes
gnumeric cursor keys edit (and delete) instead of navigate
Marked as fixed in versions fcitx/1:4.2.6.1-1.
--
Stopping processing here.
Please contact me if you need assistance.
--
684245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684245
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#682320: marked as done (scite: (background?) save fail, resulting in file content loss)
Your message dated Wed, 24 Oct 2012 15:20:31 + with message-id e1tr2kx-0001bk...@franck.debian.org and subject line Bug#682320: fixed in scite 3.0.2-3 has caused the Debian Bug report #682320, regarding scite: (background?) save fail, resulting in file content loss 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.) -- 682320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: scite Version: 3.0.2-2 Severity: critical Tags: patch Justification: causes serious data loss Hi, It seems that there is a bug in SciTE 3.0.2 that appears when you're trying to save a file. The * doesn't disappear, and subsequent saving commands report already saved. Unfortunately, that's not the case, and the file after this is completely empty and has a zero byte size. Many features of SciTE are not working anymore when this happens (including closing), and if you try to save another file, the result will be the same (file content loss). It can happen several times a day, and have quite bad consequences for users... It seems that it may be because of threading, and linked to background saving of files. The package developpers seem to have a workaround for this: putting___ if PLAT_GTK background.save.size=1000 ___ in the global properties file, disabling background saving for files under 10MB This should have been also included in 3.0.4, 3.1 and 3.2 versions, I guess. Details at: http://sourceforge.net/tracker/?func=detailaid=3466525group_id=2439atid=102439 Is it possible to at least update the global properties file to avoid that too many people lose their work because of this bug? Thanks in advance -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages scite depends on: ii libc6 2.13-34 ii libcairo2 1.12.2-2 ii libgcc1 1:4.7.1-5 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgtk2.0-0 2.24.10-1 ii libpango1.0-0 1.30.0-1 ii libstdc++6 4.7.1-5 scite recommends no packages. scite suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: scite Source-Version: 3.0.2-3 We believe that the bug you reported is fixed in the latest version of scite, 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 682...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Vogt m...@debian.org (supplier of updated scite 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 24 Oct 2012 17:02:07 +0200 Source: scite Binary: scite Architecture: source amd64 Version: 3.0.2-3 Distribution: unstable Urgency: low Maintainer: Michael Vogt m...@debian.org Changed-By: Michael Vogt m...@debian.org Description: scite - Lightweight GTK-based Programming Editor Closes: 119604 682320 690429 Changes: scite (3.0.2-3) unstable; urgency=low . [ Michael Vogt ] * add missing man-page (closes: #690429) . [ Antonio Valentino ] * install global configuration files under /etc (closes: #119604) * disable background save in order to avoid save failures and data loss (closes: #682320) * Antonio Valentino added to uploaders Checksums-Sha1: 79367a94ece679e74aa1297cf042950f6614b65c 1146 scite_3.0.2-3.dsc 98bb1b85b2f9a25245991086a160857abded7b41 15764 scite_3.0.2-3.debian.tar.gz 0063573c2a19f564cbe0dab9933ab81ac3300bfa 1210616 scite_3.0.2-3_amd64.deb Checksums-Sha256: a6542ece45ee986c90341b4b2c5169a8c5c5655683bb07374f9ed80be10e1e4c 1146 scite_3.0.2-3.dsc f144d002d6cea19171c10e71f621c4195e15a73947007325fcfac6fb054c 15764 scite_3.0.2-3.debian.tar.gz c0923e6356f03ee4d3d481d3d58100c0472defa5a6ccc2a496d1cfdcd84f290b 1210616 scite_3.0.2-3_amd64.deb Files: 8a69f857b66b880d7b4b9df3dd686453 1146 editors optional scite_3.0.2-3.dsc 0433407fcfd1d33ea2080c8c280c24df 15764 editors
Processed: tagging 690150
Processing commands for cont...@bugs.debian.org: tags 690150 - patch Bug #690150 [libphone-ui-dev] libphone-ui-dev: missing copyright file after upgrade from squeeze Removed tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 690150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690150 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#691071: marked as done (gir1.2-ibus-1.0: Missing call to dh_girepository, Depends field empty)
Your message dated Wed, 24 Oct 2012 15:32:38 + with message-id e1tr2wg-0004b9...@franck.debian.org and subject line Bug#691071: fixed in ibus 1.4.99.20120917-3 has caused the Debian Bug report #691071, regarding gir1.2-ibus-1.0: Missing call to dh_girepository, Depends field empty 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.) -- 691071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gir1.2-ibus-1.0 Version: 1.4.1-7 Severity: serious Tags: patch Hi, The depends field of gir1.2-ibus-1.0 is empty because dh_girepository has not been called during build. The gir sequence must be called (--with gir) during build. See the attached patch. Cheers Laurent Bigonville -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru ibus-1.4.99.20120917/debian/rules ibus-1.4.99.20120917/debian/rules --- ibus-1.4.99.20120917/debian/rules 2012-10-17 07:09:24.0 +0200 +++ ibus-1.4.99.20120917/debian/rules 2012-10-21 00:41:52.0 +0200 @@ -4,7 +4,7 @@ LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS) -Wl,--as-needed %: - dh $@ --with python2 --with autoreconf + dh $@ --with python2 --with autoreconf --with gir override_dh_auto_configure: dh_auto_configure -- \ ---End Message--- ---BeginMessage--- Source: ibus Source-Version: 1.4.99.20120917-3 We believe that the bug you reported is fixed in the latest version of ibus, 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 691...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aron Xu a...@debian.org (supplier of updated ibus 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 24 Oct 2012 22:55:06 +0800 Source: ibus Binary: ibus libibus-1.0-5 libibus-1.0-dev ibus-gtk ibus-gtk3 python-ibus ibus-doc gir1.2-ibus-1.0 Architecture: source amd64 all Version: 1.4.99.20120917-3 Distribution: experimental Urgency: low Maintainer: IME Packaging Team pkg-ime-de...@lists.alioth.debian.org Changed-By: Aron Xu a...@debian.org Description: gir1.2-ibus-1.0 - Intelligent Input Bus - introspection data ibus - Intelligent Input Bus - core ibus-doc - Intelligent Input Bus - development documentation ibus-gtk - Intelligent Input Bus - GTK+2 support ibus-gtk3 - Intelligent Input Bus - GTK+3 support libibus-1.0-5 - Intelligent Input Bus - shared library libibus-1.0-dev - Intelligent Input Bus - development file python-ibus - Intelligent Input Bus - Python support Closes: 691071 Changes: ibus (1.4.99.20120917-3) experimental; urgency=low . * Team upload * Call gir with dh sequences (Closes: #691071). Checksums-Sha1: b155af92e9e7675ade347c969f86db4c0a40e7ee 2397 ibus_1.4.99.20120917-3.dsc 84fe196d7ce17b148d77e25215209401651f4bb8 15647 ibus_1.4.99.20120917-3.debian.tar.gz 3b93e8d32976b2c0b17823941be0566b3f7a86d8 472886 ibus_1.4.99.20120917-3_amd64.deb a3fd50f639fc664ca9e02bb080d61fe633c2b687 297726 libibus-1.0-5_1.4.99.20120917-3_amd64.deb b9e21529ec6f34813d8547a2b3e32a12b6047b6d 350036 libibus-1.0-dev_1.4.99.20120917-3_amd64.deb bda104d5b6ed00385057695d27c4a4ffe0f6220a 178200 ibus-gtk_1.4.99.20120917-3_amd64.deb d7c08961137aa0cf350de63d2fa4093db2903e29 178164 ibus-gtk3_1.4.99.20120917-3_amd64.deb 6f99bf700ad5ee60b71b3a132cf3c0b37edec2bd 200038 python-ibus_1.4.99.20120917-3_all.deb ae63cdd1ca847f8dbcf6951eff62c33b257ed502 350290 ibus-doc_1.4.99.20120917-3_all.deb 34b0f3da516f9c6a665c90acb6c75ea467bc6e5d 255660 gir1.2-ibus-1.0_1.4.99.20120917-3_amd64.deb Checksums-Sha256: 924dd5c46dfceb7d272ecdcb88240fa781c5bdcde37ad50a75c9a5d9a209b21b 2397 ibus_1.4.99.20120917-3.dsc 12874e9ecf3e0e4a39b3609b7daf98eb53080996a02798361a3917e16761d932 15647 ibus_1.4.99.20120917-3.debian.tar.gz 593fbef2b5d0e4416584fca000b9fd20d184f08dd68e07b51bbd3be72b92f976 472886 ibus_1.4.99.20120917-3_amd64.deb
Bug#690150: libphone-ui-dev: missing copyright file after upgrade from squeeze
Control: tag -1 + patch On Sat, 20 Oct 2012 10:56:06 +0200, Andreas Beckmann wrote: that NMU makes /usr/share/doc/libphone-ui-dev a dangling symlink. The correct target would probably be libphone-ui-20110825. Or libphone-ui-common: debian/rules: override_dh_installdocs: dh_installdocs --link-doc=libphone-ui-common The packages in debian/control depend either on libphone-ui-common, or on libphone-ui-20110825 which also has a symlink to libphone-ui-common and depends on libphone-ui-common. Not sure if the indirect symlink or the indirect dependency is less ugly; but from the perceived end result according to d/rules, I'd go for libphone-ui-common. (Untested) patch attached for review. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Various Artists: Katie diff -Nru libphone-ui-0.0.1+git20110825/debian/changelog libphone-ui-0.0.1+git20110825/debian/changelog --- libphone-ui-0.0.1+git20110825/debian/changelog 2012-10-14 14:26:07.0 +0200 +++ libphone-ui-0.0.1+git20110825/debian/changelog 2012-10-24 17:38:53.0 +0200 @@ -1,3 +1,14 @@ +libphone-ui (1:0.0.1+git20110825-2.2) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Fix missing copyright file after upgrade from squeeze: +change docdir in libphone-ui-dev.postinst from non-existant +libphone-ui to libphone-ui-common (same as in debian/rules for new +installs). +(Closes: #690150) + + -- gregor herrmann gre...@debian.org Wed, 24 Oct 2012 17:32:51 +0200 + libphone-ui (1:0.0.1+git20110825-2.1) unstable; urgency=low * Non-maintainer upload. diff -Nru libphone-ui-0.0.1+git20110825/debian/libphone-ui-dev.postinst libphone-ui-0.0.1+git20110825/debian/libphone-ui-dev.postinst --- libphone-ui-0.0.1+git20110825/debian/libphone-ui-dev.postinst 2012-10-14 14:24:05.0 +0200 +++ libphone-ui-0.0.1+git20110825/debian/libphone-ui-dev.postinst 2012-10-24 17:37:39.0 +0200 @@ -5,7 +5,7 @@ docdir=/usr/share/doc/libphone-ui-dev if [ -d $docdir ] [ ! -L $docdir ]; then if rmdir $docdir 2/dev/null; then -ln -sf libphone-ui $docdir +ln -sf libphone-ui-common $docdir fi fi signature.asc Description: Digital signature
Processed: Re: Bug#690150: libphone-ui-dev: missing copyright file after upgrade from squeeze
Processing control commands: tag -1 + patch Bug #690150 [libphone-ui-dev] libphone-ui-dev: missing copyright file after upgrade from squeeze Added tag(s) patch. -- 690150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690150 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#687398: More information on how to reproduce the `dlopen' issue
On Sun, 30 Sep 2012 18:10:16 -0400, Asheesh Laroia wrote: So what I'm going to do is: * Adjust debian/rules to *not* specify SHARED_TRG * Right after rhash_shared is built, use 'mv' to rename it to 'rhash' That's all it should take to fix this, I believe. I'll prepare a 1-day delayed NMU for that. Maintainer, please feel free to remove it; I don't mean to step on your toes, just to move this bug along. I'll attach the debdiff here before doing the upload. The debdiff arrived some minutes later, but I don't see an upload. What's the status? Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Various Artists: Katie signature.asc Description: Digital signature
Bug#684852: python-greenlet: diff for NMU version 0.3.1-2.1
On Sat, 13 Oct 2012 12:25:50 +0200, Jelmer Vernooij wrote: I've uploaded Laszlo's NMU for python-greenlet (versioned as 0.3.1-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. That's the last entry in the bug log, but I don't see a -2.1 package in the PTS -- just curious what happened :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Various Artists: Katie signature.asc Description: Digital signature
Processed: severity of 642136 is serious
Processing commands for cont...@bugs.debian.org: severity 642136 serious Bug #642136 [network-manager] network-manager: Connecting to a wifi network requires org.freedesktop.NM.settings.modify.system privileges Bug #645815 [network-manager] network-manager-gnome: Should not create system-wide connections by default Bug #646407 [network-manager] Annoying password asking Bug #654874 [network-manager] network manager won't reconnnect, various errors Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 642136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642136 645815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645815 646407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646407 654874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654874 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#678890: scim: fail to start scim after latest upgrade
On Wed, 24 Oct 2012 13:40:57 +0900, Nobuhiro Iwamatsu wrote: Please fix. I attached patch which removed unnecessary patch. Looks like the patch hasn't made it into the BTS :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Various Artists: Katie signature.asc Description: Digital signature
Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed
On Thu, 11 Oct 2012 22:21:04 -0700, tony mancill wrote: During a rebuild of all packages in *wheezy*, your package failed to build on amd64. I couldn't reproduce this in wheezy or sid, but I was only using pbuilder to test. I was able to get the build to fail by setting DISPLAY to something not accessible to the build machine, but it failed in the first unit test (different than the failure in the bug report). After unsetting DISPLAY, the build is successful. So I don't think it's the same issue. My builds were in a cowbuilder chroot. It fails for me in cowbuilder (without doing anything) in the first unit test with a clear error message: compile-test: [javac] /tmp/buildd/bsaf-1.9/build.xml:49: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 26 source files to /tmp/buildd/bsaf-1.9/test [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [copy] Copying 28 files to /tmp/buildd/bsaf-1.9/test check-display: test: [junit] Running org.jdesktop.application.AbstractBeanTest [junit] Testsuite: org.jdesktop.application.AbstractBeanTest [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.046 sec [junit] No protocol specified [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.046 sec [junit] [junit] Testcase: fireOnEdtTest(org.jdesktop.application.AbstractBeanTest): Caused an ERROR [junit] Can't connect to X11 window server using ':0' as the value of the DISPLAY variable. [junit] java.lang.InternalError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable. [junit] at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method) [junit] at sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:62) [junit] at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:178) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at sun.awt.X11GraphicsEnvironment.clinit(X11GraphicsEnvironment.java:142) [junit] at java.lang.Class.forName0(Native Method) [junit] at java.lang.Class.forName(Class.java:186) [junit] at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:82) [junit] at sun.awt.X11.XToolkit.clinit(XToolkit.java:112) [junit] at java.lang.Class.forName0(Native Method) [junit] at java.lang.Class.forName(Class.java:186) [junit] at java.awt.Toolkit$2.run(Toolkit.java:849) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:841) [junit] at java.awt.Toolkit.getEventQueue(Toolkit.java:1698) [junit] at java.awt.EventQueue.isDispatchThread(EventQueue.java:878) [junit] at javax.swing.SwingUtilities.isEventDispatchThread(SwingUtilities.java:1360) [junit] at javax.swing.event.SwingPropertyChangeSupport.firePropertyChange(SwingPropertyChangeSupport.java:90) [junit] at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:229) [junit] at org.jdesktop.application.AbstractBean.firePropertyChange(Unknown Source) [junit] at org.jdesktop.application.AbstractBeanTest$TestBean.fire(Unknown Source) [junit] at org.jdesktop.application.AbstractBeanTest.fireOnEdtTest(Unknown Source) [junit] [junit] BUILD FAILED /tmp/buildd/bsaf-1.9/build.xml:68: Test org.jdesktop.application.AbstractBeanTest failed Running the tests under xvfb I get a different failure: (Side question: why are the tests run at dh_auto_build time and not under dh_auto_test?) [junit] Running org.jdesktop.application.ApplicationTest [junit] Testsuite: org.jdesktop.application.ApplicationTest [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.453 sec [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.453 sec [junit] [junit] This test generates logger warnings. Ignore them. [junit] Running org.jdesktop.application.BadSessionStateTest [junit] Testsuite: org.jdesktop.application.BadSessionStateTest [junit] Oct 24, 2012 4:03:59 PM org.jdesktop.application.LocalStorage getId [junit] WARNING: unspecified resource Application.id using BadSessionStateApplication [junit] Oct 24, 2012 4:03:59 PM org.jdesktop.application.SingleFrameApplication initRootPaneContainer [junit] WARNING: couldn't restore session [mainFrame.session.xml] [junit] java.lang.ArrayIndexOutOfBoundsException: 0 [junit] at com.sun.beans.ObjectHandler.dequeueResult(ObjectHandler.java:189) [junit] at
Bug#691311: [Pkg-octave-devel] Bug#691311: Bug#691311: Bug#691311: error: feval: function `unimplemented' not found
On 24 October 2012 08:17, Mike Miller mtmil...@ieee.org wrote: The octave package provides the directories, and liboctinterp.so.1 has a compiled-in set of paths with its version number that it attempts to load. Ah, this is probably not the greatest idea ever. I'm not sure how to fix it. Provide a build-time option for setting this path? Setting the path by default to a versionless path? - Jordi G. H. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690148: Please give back gcc-mingw-w64 (so it rebuilds using gcc-4.6 4.6.3-12)
Control: tag -1 + patch On Mon, 15 Oct 2012 20:41:27 +0200, Stephen Kitt wrote: On Mon, 15 Oct 2012 14:49:31 +0100, Jonathan Wiltshire j...@debian.org wrote: I started looking at this bug yesterday, the fix is easy but I did not have time to check all binary packages. Patch to follow if you want it. If you've got the patch to hand I'd appreciate it. As you say the fix is easy, but I won't have time to work on it this evening... Something like the attached debdiff maybe? (Note that I haven't built the binary packages, but I've run the postinst manually in a chroot after a squeeze → wheezy update of gcc-mingw32.) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Various Artists: Katie diff -Nru gcc-mingw-w64-7/debian/changelog gcc-mingw-w64-7+nmu1/debian/changelog --- gcc-mingw-w64-7/debian/changelog 2012-08-08 08:21:59.0 +0200 +++ gcc-mingw-w64-7+nmu1/debian/changelog 2012-10-24 18:31:58.0 +0200 @@ -1,3 +1,13 @@ +gcc-mingw-w64 (7+nmu1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Fix missing copyright file after upgrade from squeeze: +add debian/gcc-mingw32.postinst to handle dir → symlink transition for +gcc-ming32's docdir. +(Closes: #690148) + + -- gregor herrmann gre...@debian.org Wed, 24 Oct 2012 18:15:13 +0200 + gcc-mingw-w64 (7) unstable; urgency=low * When upgrading from versions where /usr/share/doc/gcc-mingw-w64 is a diff -Nru gcc-mingw-w64-7/debian/gcc-mingw32.postinst gcc-mingw-w64-7+nmu1/debian/gcc-mingw32.postinst --- gcc-mingw-w64-7/debian/gcc-mingw32.postinst 1970-01-01 01:00:00.0 +0100 +++ gcc-mingw-w64-7+nmu1/debian/gcc-mingw32.postinst 2012-10-24 18:30:52.0 +0200 @@ -0,0 +1,13 @@ +#!/bin/sh +set -e + +# Replace documentation directory with symlink +if [ -d /usr/share/doc/gcc-mingw32 ] [ ! -L /usr/share/doc/gcc-mingw32 ]; then +if rmdir /usr/share/doc/gcc-mingw32 2/dev/null; then +ln -sf gcc-mingw-w64-base /usr/share/doc/gcc-mingw32 +fi +fi + +#DEBHELPER# + +exit 0 signature.asc Description: Digital signature
Processed: Re: Bug#690148: Please give back gcc-mingw-w64 (so it rebuilds using gcc-4.6 4.6.3-12)
Processing control commands: tag -1 + patch Bug #690148 [gcc-mingw32] gcc-mingw32: missing copyright file after upgrade from squeeze Added tag(s) patch. -- 690148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690148 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#688197: Where is the upload
On Wed, 24 Oct 2012, Dominik George wrote: from your last post, I conclude that the fix is ready to be released. Yes I am confident this issue is resolved but We still have one huge problem, bug #665407. Upstream provided a fix but it does not seem to work. I have delayed the upload because I am still hoping we can come up with some solution though time is running short. Could you please upload the fixed version to unstable or, if you are not sure of it, provide the source package here for others to test? The dovecot package git repository can be found at git.debian.org/collab-maint/dovecot -- Jaldhar H. Vyas jald...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623578: marked as done (gadfly: build wrong version of the packaging during a binNMU)
Your message dated Wed, 24 Oct 2012 17:32:28 +
with message-id e1tr4oe-0003us...@franck.debian.org
and subject line Bug#623578: fixed in gadfly 1.0.0-15.1
has caused the Debian Bug report #623578,
regarding gadfly: build wrong version of the packaging during a binNMU
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.)
--
623578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: gadfly
Version: 1.0.0-14
Severity: serious
gadfly has been binNMU for the python transition, so that the version
should contain +b1. This doesn't work, as the .deb that is built
corresponds to the source version, for example
python-kjbuckets_1.0.0-14_mips.deb. As a consequence, this package is
rejected by dak.
For example, see the build logs of the binNMU:
https://buildd.debian.org/status/fetch.php?pkg=gadflyarch=mipsver=1.0.0-14%2Bb1stamp=1303380314
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
---End Message---
---BeginMessage---
Source: gadfly
Source-Version: 1.0.0-15.1
We believe that the bug you reported is fixed in the latest version of
gadfly, 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 623...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated gadfly 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...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 22 Oct 2012 19:10:00 +0200
Source: gadfly
Binary: gadfly python-gadfly python-kjbuckets
Architecture: source all amd64
Version: 1.0.0-15.1
Distribution: unstable
Urgency: low
Maintainer: Matthias Klose d...@debian.org
Changed-By: gregor herrmann gre...@debian.org
Description:
gadfly - Server and interactive shell for Gadfly SQL database
python-gadfly - SQL database and parser generator for Python
python-kjbuckets - Set and graph data types for Python
Closes: 623578
Changes:
gadfly (1.0.0-15.1) unstable; urgency=low
.
* Non-maintainer upload.
* Fix build wrong version of the packaging during a binNMU:
- debian/rules: get binary package version from dpkg-parsechangelog
instead of using ${source:Version}; thanks to Guillem Jover for the
patch, and to Jakub Wilk for the improvement
- debian/control: build-depend on dpkg-dev (= 1.16.9)
(cf. #690823)
(Closes: #623578)
Checksums-Sha1:
0d63016244585db7d5884f22c041c0a812658016 1816 gadfly_1.0.0-15.1.dsc
cdbc93ea27bee6d20a6656339eed9cafac183e5f 6679 gadfly_1.0.0-15.1.diff.gz
dee005005832b91f93466c5af95d58878fd7a9c1 178252
python-gadfly_1.0.0-15.1_all.deb
5c264eaf3099d5ff21e3c97d1aaeea3a2fa2a2e0 27184 gadfly_1.0.0-15.1_all.deb
bb39ada8dff9aacf7dc2b1bab0a1611ed5c0d6b0 66170
python-kjbuckets_1.0.0-15.1_amd64.deb
Checksums-Sha256:
33343b88fd6d5178b0b1f74833db442dfeef8a71ead857db24bf63df5d272b8b 1816
gadfly_1.0.0-15.1.dsc
64e9ac7c5fb0b68430840dade736f3fa9551b62844cac3093ee95bf22c601530 6679
gadfly_1.0.0-15.1.diff.gz
bec1ab8a0c83ab22f9db16a3cbd0820b1b9b2fb5b46312c0a8261e303f6172a3 178252
python-gadfly_1.0.0-15.1_all.deb
23d903e1842921b5ee6ad383919aa2181e24f8f4ee3bd5a5dc511f6ada38c78d 27184
gadfly_1.0.0-15.1_all.deb
277b1ce27073c7b2b31d6ac33c8d0dc5622d690b5afc664083e761a6250705ac 66170
python-kjbuckets_1.0.0-15.1_amd64.deb
Files:
cbd5318e23b5f279eea63973baef09e7 1816 python optional gadfly_1.0.0-15.1.dsc
f591630ce1204b85e634b899f0206bcf 6679 python optional gadfly_1.0.0-15.1.diff.gz
ac33a74d39704c05c8fffe739e198cfd 178252 python optional
python-gadfly_1.0.0-15.1_all.deb
8c06161c8b81fb22ee7f73535bc7 27184 interpreters optional
gadfly_1.0.0-15.1_all.deb
9c7c39eeaf8175352283b06a6b3fefe9 66170 python optional
python-kjbuckets_1.0.0-15.1_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQhX4sAAoJELs6aAGGSaoGz0cP/3kKceMEF6D8rS+PG9v7m6D9
JdFLh+hhp6/OBdFzRI9bKkpzoktEM2V6dmnDZF5kPnvroxh036TaYgDEp27CKpMz
Bug#675971: marked as done (Cannot communicate with the vast majority of Mumble servers due to lack of required baseline codec)
Your message dated Wed, 24 Oct 2012 17:32:42 + with message-id e1tr4os-0003d5...@franck.debian.org and subject line Bug#675971: fixed in mumble 1.2.3-349-g315b5f5-2.1 has caused the Debian Bug report #675971, regarding Cannot communicate with the vast majority of Mumble servers due to lack of required baseline codec 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.) -- 675971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mumble Version: 1.2.3-349-g315b5f5-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? The maintainer patch which disables CELT * What exactly did you do (or not do) that was effective (or ineffective)? Update the package to the most recent version * What was the outcome of this action? Audio is completely broken since the maintainer-patched client uses an incomplete integration of a widely unsupported audio codec (OPUS) and completely disables codecs required to communicate with any other released version of the software. * What outcome did you expect instead? A usable VoIP tool. With disabled CELT, mumble produces horrible audio glitches which are a known issue with the current OPUS integration. Furthermore, it means Debian mumble clients can no longer sanely communicate with any officially released version. In the worst case, it will even break things for other users on a server since it shows very incomplete codec support. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (700, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.4 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mumble depends on: ii gconf2 3.2.5-1 ii libasound2 1.0.25-3 ii libavahi-client3 0.6.31-1 ii libavahi-common3 0.6.31-1 ii libavahi-compat-libdnssd1 0.6.31-1 ii libc6 2.13-33 ii libg15daemon-client1 1.9.5.3-8.2 ii libgcc11:4.7.0-11 ii libopus0 0.9.14+20120521-2 ii libprotobuf7 2.4.1-2 ii libpulse0 2.0-3 ii libqt4-dbus4:4.8.1-2 ii libqt4-network 4:4.8.1-2 ii libqt4-sql 4:4.8.1-2 ii libqt4-sql-sqlite 4:4.8.1-2 ii libqt4-svg 4:4.8.1-2 ii libqt4-xml 4:4.8.1-2 ii libqtcore4 4:4.8.1-2 ii libqtgui4 4:4.8.1-2 ii libsndfile11.0.25-4 ii libspeechd20.7.1-6.1 ii libspeex1 1.2~rc1-6 ii libspeexdsp1 1.2~rc1-6 ii libssl1.0.01.0.1c-1 ii libstdc++6 4.7.0-11 ii libx11-6 2:1.4.99.901-2 ii libxi6 2:1.6.1-1 ii lsb-release4.1+Debian6 Versions of packages mumble recommends: ii speech-dispatcher 0.7.1-6.1 Versions of packages mumble suggests: ii mumble-server 1.2.3-349-g315b5f5-1 -- no debconf information ---End Message--- ---BeginMessage--- Source: mumble Source-Version: 1.2.3-349-g315b5f5-2.1 We believe that the bug you reported is fixed in the latest version of mumble, 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 675...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christopher Knadle chris.kna...@coredump.us (supplier of updated mumble 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 04 Oct 2012 11:45:05 -0400 Source: mumble Binary: mumble mumble-server mumble-dbg Architecture: source amd64 Version: 1.2.3-349-g315b5f5-2.1 Distribution: unstable Urgency: low Maintainer: Ron Lee r...@debian.org Changed-By: Christopher Knadle chris.kna...@coredump.us Description: mumble - Low latency VoIP client mumble-dbg - Low latency VoIP client (debugging symbols) mumble-server - Low latency VoIP server Closes: 675971 Changes: mumble (1.2.3-349-g315b5f5-2.1)
Processed: Re: Bug#690148: Please give back gcc-mingw-w64 (so it rebuilds using gcc-4.6 4.6.3-12)
Processing control commands: tag -1 + pending Bug #690148 [gcc-mingw32] gcc-mingw32: missing copyright file after upgrade from squeeze Added tag(s) pending. -- 690148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690148 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#690148: Please give back gcc-mingw-w64 (so it rebuilds using gcc-4.6 4.6.3-12)
Control: tag -1 + pending Hi Gregor, On Wed, Oct 24, 2012 at 06:49:12PM +0200, gregor herrmann wrote: Something like the attached debdiff maybe? (Note that I haven't built the binary packages, but I've run the postinst manually in a chroot after a squeeze → wheezy update of gcc-mingw32.) Sorry, I should have tagged the bug pending! Your patch is exactly what I submitted for Wheezy approval in http://bugs.debian.org/690810 (tested with binary packages, upgrading from Squeeze and current Wheezy). Regards, Stephen signature.asc Description: Digital signature
Bug#690148: Please give back gcc-mingw-w64 (so it rebuilds using gcc-4.6 4.6.3-12)
On Wed, 24 Oct 2012 19:40:17 +0200, Stephen Kitt wrote: Something like the attached debdiff maybe? Sorry, I should have tagged the bug pending! Your patch is exactly what I submitted for Wheezy approval in http://bugs.debian.org/690810 (tested with binary packages, upgrading from Squeeze and current Wheezy). Ah, cool, good to see that a fix for this issue is already on its way. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Various Artists: Katie signature.asc Description: Digital signature
Bug#687398: More information on how to reproduce the `dlopen' issue
On Wed, 24 Oct 2012, gregor herrmann wrote: The debdiff arrived some minutes later, but I don't see an upload. What's the status? Oh, snap, I neglected to upload the actual NMU. I will do that tonight, unless someone (gregoa?) beats me to it. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687398: More information on how to reproduce the `dlopen' issue
On Wed, 24 Oct 2012 14:08:11 -0400, Asheesh Laroia wrote: The debdiff arrived some minutes later, but I don't see an upload. What's the status? Oh, snap, I neglected to upload the actual NMU. I will do that tonight, unless someone (gregoa?) beats me to it. I'm happy to leave the honour^Wwork to you as I'm looking at another RC bug right now :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Various Artists: Katie signature.asc Description: Digital signature
Processed: Re: Bug#690147: cyrus-common-2.2: missing copyright file after upgrade from squeeze
Processing control commands: tag -1 + patch Bug #690147 [cyrus-common-2.2] cyrus-common-2.2: missing copyright file after upgrade from squeeze Added tag(s) patch. -- 690147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690147 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#690147: cyrus-common-2.2: missing copyright file after upgrade from squeeze
Control: tag -1 + patch On Wed, 10 Oct 2012 16:00:23 +0200, Andreas Beckmann wrote: Package: cyrus-common-2.2 Version: 2.4.16-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts After the upgrade /usr/share/doc/$package/ is just an empty directory. From the attached logfile (scroll to the bottom): MISSING COPYRIGHT FILE: /usr/share/doc/cyrus-common-2.2/copyright drwxr-xr-x 2 root root 40 Oct 10 09:54 /usr/share/doc/cyrus-common-2.2 total 0 drwxr-xr-x 2 root root 40 Oct 10 09:54 . drwxr-xr-x 120 root root 2560 Oct 10 09:54 .. I assume that this affects all transitional packages built from this source package and not only cyrus-common-2.2? I've prepared a patch now that adds .postinst files for all of them (replacing the old directory with the new symlink on upgrades). Reviews welcome! Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Various Artists: Katie diff -Nru cyrus-imapd-2.4-2.4.16/debian/changelog cyrus-imapd-2.4-2.4.16/debian/changelog --- cyrus-imapd-2.4-2.4.16/debian/changelog 2012-04-19 14:31:27.0 +0200 +++ cyrus-imapd-2.4-2.4.16/debian/changelog 2012-10-24 20:23:35.0 +0200 @@ -1,3 +1,13 @@ +cyrus-imapd-2.4 (2.4.16-1.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Fix missing copyright file after upgrade from squeeze: +add postinst scripts for all transitional packages to handle the +directory → symlink transition of their docdirs. +(Closes: #690147) + + -- gregor herrmann gre...@debian.org Wed, 24 Oct 2012 18:50:42 +0200 + cyrus-imapd-2.4 (2.4.16-1) unstable; urgency=low * Imported Upstream version 2.4.16 diff -Nru cyrus-imapd-2.4-2.4.16/debian/cyrus-admin-2.2.postinst cyrus-imapd-2.4-2.4.16/debian/cyrus-admin-2.2.postinst --- cyrus-imapd-2.4-2.4.16/debian/cyrus-admin-2.2.postinst 1970-01-01 01:00:00.0 +0100 +++ cyrus-imapd-2.4-2.4.16/debian/cyrus-admin-2.2.postinst 2012-10-24 20:20:57.0 +0200 @@ -0,0 +1,17 @@ +#!/bin/sh + +set -e + +# Replace documentation directory with symlink +docdir=/usr/share/doc/cyrus-admin-2.2 +target=cyrus-common + +if [ -d $docdir ] [ ! -L $docdir ]; then + if rmdir $docdir 2/dev/null; then + ln -sf $target $docdir + fi +fi + +#DEBHELPER# + +exit 0 diff -Nru cyrus-imapd-2.4-2.4.16/debian/cyrus-clients-2.2.postinst cyrus-imapd-2.4-2.4.16/debian/cyrus-clients-2.2.postinst --- cyrus-imapd-2.4-2.4.16/debian/cyrus-clients-2.2.postinst 1970-01-01 01:00:00.0 +0100 +++ cyrus-imapd-2.4-2.4.16/debian/cyrus-clients-2.2.postinst 2012-10-24 20:20:57.0 +0200 @@ -0,0 +1,17 @@ +#!/bin/sh + +set -e + +# Replace documentation directory with symlink +docdir=/usr/share/doc/cyrus-clients-2.2 +target=cyrus-common + +if [ -d $docdir ] [ ! -L $docdir ]; then + if rmdir $docdir 2/dev/null; then + ln -sf $target $docdir + fi +fi + +#DEBHELPER# + +exit 0 diff -Nru cyrus-imapd-2.4-2.4.16/debian/cyrus-common-2.2.postinst cyrus-imapd-2.4-2.4.16/debian/cyrus-common-2.2.postinst --- cyrus-imapd-2.4-2.4.16/debian/cyrus-common-2.2.postinst 1970-01-01 01:00:00.0 +0100 +++ cyrus-imapd-2.4-2.4.16/debian/cyrus-common-2.2.postinst 2012-10-24 20:20:57.0 +0200 @@ -0,0 +1,17 @@ +#!/bin/sh + +set -e + +# Replace documentation directory with symlink +docdir=/usr/share/doc/cyrus-common-2.2 +target=cyrus-common + +if [ -d $docdir ] [ ! -L $docdir ]; then + if rmdir $docdir 2/dev/null; then + ln -sf $target $docdir + fi +fi + +#DEBHELPER# + +exit 0 diff -Nru cyrus-imapd-2.4-2.4.16/debian/cyrus-dev-2.2.postinst cyrus-imapd-2.4-2.4.16/debian/cyrus-dev-2.2.postinst --- cyrus-imapd-2.4-2.4.16/debian/cyrus-dev-2.2.postinst 1970-01-01 01:00:00.0 +0100 +++ cyrus-imapd-2.4-2.4.16/debian/cyrus-dev-2.2.postinst 2012-10-24 20:20:57.0 +0200 @@ -0,0 +1,17 @@ +#!/bin/sh + +set -e + +# Replace documentation directory with symlink +docdir=/usr/share/doc/cyrus-dev-2.2 +target=cyrus-common + +if [ -d $docdir ] [ ! -L $docdir ]; then + if rmdir $docdir 2/dev/null; then + ln -sf $target $docdir + fi +fi + +#DEBHELPER# + +exit 0 diff -Nru cyrus-imapd-2.4-2.4.16/debian/cyrus-doc-2.2.postinst cyrus-imapd-2.4-2.4.16/debian/cyrus-doc-2.2.postinst --- cyrus-imapd-2.4-2.4.16/debian/cyrus-doc-2.2.postinst 1970-01-01 01:00:00.0 +0100 +++ cyrus-imapd-2.4-2.4.16/debian/cyrus-doc-2.2.postinst 2012-10-24 20:20:57.0 +0200 @@ -0,0 +1,17 @@ +#!/bin/sh + +set -e + +# Replace documentation directory with symlink +docdir=/usr/share/doc/cyrus-doc-2.2 +target=cyrus-common + +if [ -d $docdir ] [ ! -L $docdir ]; then + if rmdir $docdir 2/dev/null; then + ln -sf $target $docdir + fi +fi + +#DEBHELPER# + +exit 0 diff -Nru cyrus-imapd-2.4-2.4.16/debian/cyrus-imapd-2.2.postinst cyrus-imapd-2.4-2.4.16/debian/cyrus-imapd-2.2.postinst ---
Bug#688069: liblocale-subcountry-perl: Version checks fail (our $VERSION moved before package Locale::SubCountry)
On Tue, 18 Sep 2012 13:54:35 -0700, Ivan Kohler wrote: $ perl -e 'use Locale::SubCountry 54' Locale::SubCountry does not define $Locale::SubCountry::VERSION--version check failed at -e line 1. Sometime after version 1.50, our $VERSION = 1.xx was moved to the top of the code, above any package declaration. It is therefore not declaring $Locale::SubCountry::VERSION, and previously-working version checks like use Locale::SubCountry 1.42 now throw a fatal error. The patch below adds a package Locale::SubCountry to the beginning of the code. This seems like typical / best practice for modules, to avoid any symbol exports from the intial use statements from polluting the main:: namespace. Are you going to upload the fixed package? Or should someone else go ahead? Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Ben Weaver: Boxcars signature.asc Description: Digital signature
Bug#690199: Patch
Hi Anton, 2012/10/22 Anton Gladky gladky.an...@gmail.com: Hello, please, consider the following git-patch for package VCS [1], which fixes the issue. Thanks for the patches, I will review and incorporate them soon. I think that this patch is only part of the story, and that I failed to document more things in Tools. I put the stress on the main library's directories, and forgot about tools, specially because we only use a couple. Is this Scintilla code (name of the patch) shared with other packages in Debian? Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690147: cyrus-common-2.2: missing copyright file after upgrade from squeeze
On 2012-10-24 20:29, gregor herrmann wrote: I assume that this affects all transitional packages built from this source package and not only cyrus-common-2.2? There may be more packages buggy, but are not tested by piuparts if they (indirectly) depend on other failing packages. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690147: cyrus-common-2.2: missing copyright file after upgrade from squeeze
On Wed, 24 Oct 2012 22:14:26 +0200, Andreas Beckmann wrote: On 2012-10-24 20:29, gregor herrmann wrote: I assume that this affects all transitional packages built from this source package and not only cyrus-common-2.2? There may be more packages buggy, but are not tested by piuparts if they (indirectly) depend on other failing packages. Thanks, I assumed something like this. Let's see if one of the 5 uploaders can add some info before we double-check this for each of the packages :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Goldfinger: Don't Say Goodbye signature.asc Description: Digital signature
Bug#690199: Patch
Hi Manuel, 2012/10/24 Manuel A. Fernandez Montecelo manuel.montez...@gmail.com: I think that this patch is only part of the story, and that I failed to document more things in Tools. I put the stress on the main library's directories, and forgot about tools, specially because we only use a couple. I usually use the following command to roughly create a copyright-file: licensecheck --copyright -r . | /usr/lib/cdbs/licensecheck2dep5 debian/copyright Is this Scintilla code (name of the patch) shared with other packages in Debian? Sorry, I have no idea. Cheers, Anton -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 689831 is forwarded to http://code.google.com/p/gconf-cleaner/issues/detail?id=18
Processing commands for cont...@bugs.debian.org: forwarded 689831 http://code.google.com/p/gconf-cleaner/issues/detail?id=18 Bug #689831 [gconf-cleaner] gconf-cleaner: Impossible to backup configuration Set Bug forwarded-to-address to 'http://code.google.com/p/gconf-cleaner/issues/detail?id=18'. thanks Stopping processing here. Please contact me if you need assistance. -- 689831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689831 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#689831: gconf-cleaner: Impossible to backup configuration
This was reported upstream at: http://code.google.com/p/gconf-cleaner/issues/detail?id=18 It was also reported in Ubuntu at: https://bugs.launchpad.net/debian/+source/gconf-cleaner/+bug/764041 The issue seems to be that gconf-cleaner does not support the Schema value: http://developer.gnome.org/gconf/2.32/gconf-gconf-schema.html#GConfSchema -- Andrew Starr-Bochicchio Ubuntu Developer https://launchpad.net/~andrewsomething Debian Maintainer http://qa.debian.org/developer.php?login=a.starr.b%40gmail.com PGP/GPG Key ID: D53FDCB1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690370: Upload rejected
Luca, could you, please, reupload the package with attached nmu-patch? It should fix the issue. 2 other git-diffs should, probably, be interesting for maintainers to integrate them into the fife-VCS. Thanks, Anton nmu.debdiff Description: Binary data 0001-Add-engine-core-util-utf8-utf8-to-copyright-file-Clo.patch Description: Binary data 0002-Use-packaged-version-of-Glee.patch Description: Binary data
Bug#633799: getmail causes irrecoverable mail corruption when using mbox
Hi. The getmail developer has released[0] a new upstream version (4.35.0). It's apparently expected to fix the corruption issue, I haven't been able to check this, yet. Could you please package this and get an exception for wheezy? However, I still think we need to add a warning about the corruption in the: - NEWS file - release notes but we don't need to add it to the package description/debconf,... if the fix proves working. Cheers, Chris. [0] http://article.gmane.org/gmane.mail.getmail.announce/140 smime.p7s Description: S/MIME cryptographic signature
Bug#666334: gnustep-back: FTBFS: build-arch doesn't apply patches
Control: reopen 666334
Control: found 666334 0.22.0-1
Control: retitle 666334 FTBFS: build-arch problems with patch applying and
instalation of files genrated only in build-indep target
Hi
(only going to RC bugs for wheezy):
On Mon, Jul 30, 2012 at 02:37:17PM +0200, Ralf Treinen wrote:
Control: tags + patch
Hello,
this bug still has to be dealt with in wheezy, since the release team
most probably won't accept the new upstream version into wheezy. Here
is a trivial patch:
% debdiff *.dsc
diff -u gnustep-back-0.20.1/debian/changelog
gnustep-back-0.20.1/debian/changelog
--- gnustep-back-0.20.1/debian/changelog
+++ gnustep-back-0.20.1/debian/changelog
@@ -1,3 +1,11 @@
+gnustep-back (0.20.1-3) unstable; urgency=low
+
+ * NMU
+ * debian/rules: targets build-arch and build-indep, not build, must depend
+on patch (closes: #666334)
+
+ -- Ralf Treinen trei...@debian.org Mon, 30 Jul 2012 14:25:59 +0200
+
gnustep-back (0.20.1-2) unstable; urgency=low
* Upload to unstable.
diff -u gnustep-back-0.20.1/debian/rules gnustep-back-0.20.1/debian/rules
--- gnustep-back-0.20.1/debian/rules
+++ gnustep-back-0.20.1/debian/rules
@@ -112,16 +112,16 @@
touch $@
-build: patch build-indep build-arch
+build: build-indep build-arch
-build-indep: debian/build-indep-stamp
+build-indep: patch debian/build-indep-stamp
clean_files += debian/build-indep-stamp
debian/build-indep-stamp: config
$(MAKE) -C Documentation messages=yes
touch $@
-build-arch: debian/build-art-stamp debian/build-cairo-stamp
+build-arch: patch debian/build-art-stamp debian/build-cairo-stamp
clean_files += debian/build-art-stamp debian/build-cairo-stamp
debian/build-art-stamp: debian/configure-art-stamp
dh_testdir
This unfortunately seems not enough to fix the issue: When building
not package FTBFS with:
cut-cut-cut-cut-cut-cut-
Making install for bundle libgnustep-cairo-020...
Creating
/build/build-gnustep-back_0.20.1-2.1-amd64-xpAXlq/gnustep-back-0.20.1/debian/gnustep-back0.20-cairo//usr/lib/GNUstep/Bundles...
Installing bundle directory...
make[1]: Leaving directory
`/build/build-gnustep-back_0.20.1-2.1-amd64-xpAXlq/gnustep-back-0.20.1/build-cairo/Source'
: # Allow it to be used as a default backend
dh_link -pgnustep-back0.20-cairo \
/usr/lib/GNUstep/Bundles/libgnustep-cairo-020.bundle/libgnustep-cairo-020 \
/usr/lib/GNUstep/Bundles/libgnustep-cairo-020.bundle/libgnustep-back-020
dh_testdir -a
dh_testroot -a
dh_installchangelogs -a ChangeLog
dh_installdocs -a Documentation/{ANNOUNCE,NEWS,README}
cp: cannot stat `Documentation/ANNOUNCE': No such file or directory
dh_installdocs: cp -a Documentation/ANNOUNCE
debian/gnustep-back0.20-art/usr/share/doc/gnustep-back0.20-art returned exit
code 1
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary-arch gave error
exit status 2
cut-cut-cut-cut-cut-cut-
This happens also in the experimental version.
@Yavor, so this still affects wheezy. I can try to help and provide a
patch and/or do an NMU (time permitting), in case Ralf cannot do right
now. Please let me know.
Due the above I have, reopened the bug, retitled to reflect that there
seems a more general problem using build-arch/build-indep targets in
debian/rules.
Regards,
Salvatore
signature.asc
Description: Digital signature
Processed: Re: Bug#666334: gnustep-back: FTBFS: build-arch doesn't apply patches
Processing control commands:
reopen 666334
Bug #666334 {Done: Yavor Doganov ya...@gnu.org} [src:gnustep-back]
gnustep-back: FTBFS: build-arch doesn't apply patches
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gnustep-back/0.22.0-1.
found 666334 0.22.0-1
Bug #666334 [src:gnustep-back] gnustep-back: FTBFS: build-arch doesn't apply
patches
Marked as found in versions gnustep-back/0.22.0-1.
retitle 666334 FTBFS: build-arch problems with patch applying and instalation
of files genrated only in build-indep target
Bug #666334 [src:gnustep-back] gnustep-back: FTBFS: build-arch doesn't apply
patches
Changed Bug title to 'FTBFS: build-arch problems with patch applying and
instalation of files genrated only in build-indep target' from 'gnustep-back:
FTBFS: build-arch doesn't apply patches'
--
666334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666334
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#691376: schroot: session recovery mounts $device, not $mount-device, for LVM snapshots
Package: schroot Version: 1.6.3-1 Severity: serious Tags: security Justification: Security violation and potential for dataloss Originally reported here: https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1070008 Calling --recover-session on a session using an LVM snapshot, it remounts using the original LV rather than the snapshot LV. This is due to this check failing: sbuild::chroot_block_device_base::set_device(): /// @todo: This may not be appropriate for derived classes such as /// lvm_snapshot, since re-setting the device could overwrite the /// mount device. chroot_facet_mountable::ptr pmnt (get_facetchroot_facet_mountable()); #ifdef SBUILD_FEATURE_LVMSNAP if (!dynamic_castchroot_lvm_snapshot *(this)) #endif pmnt-set_mount_device(this-device); This is due to the use of dynamic_cast in this method. This is not in itself wrong, but because this method is called from the constructor, the dynamic_cast returns null due to the vptr not yet having any knowledge of the derived class--it will work fine once the base class is constructed. This was already commented in several places to refactor to clean this up, but the presence of this issue will require this to be done immediately. I've tagged this security due to the potential for a user to access the original source chroot. However, the scope is relatively limited since the filesystem permissions will prevent them from doing anything they should not (unless you granted them root access, in which case they already had the ability to do this). Regards, Roger -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32.33-kvm-i386-2028-dirty (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages schroot depends on: ii libboost-filesystem1.49.0 1.49.0-3.1 ii libboost-iostreams1.49.01.49.0-3.1 ii libboost-program-options1.49.0 1.49.0-3.1 ii libboost-regex1.49.01.49.0-3.1 ii libboost-system1.49.0 1.49.0-3.1 ii libc6 2.13-35 ii libgcc1 1:4.7.1-7 ii liblockdev1 1.0.3-1.5 ii libpam0g1.1.3-7.1 ii libstdc++6 4.7.1-7 ii libuuid12.20.1-5.2 ii schroot-common 1.6.3-1 schroot recommends no packages. Versions of packages schroot suggests: pn aufs-modules | unionfs-modules none pn btrfs-tools none ii debootstrap 1.0.42 pn lvm2none pn qemu-user-staticnone -- Configuration Files: /etc/schroot/schroot.conf changed [not included] -- 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#687403: libio-async-loop-epoll-perl: FTBFS: test failed
Control: reassign -1 libio-async-perl Control: found -1 0.51-1 # we could also merge it with #680790 but meh. On Thu, 18 Oct 2012 10:48:37 +0200, gregor herrmann wrote: Should this be _CAN_SUBSECOND_ACCURATELY = 0 to turn it off unless some loop test explicitly sets it? Ok, some investigation: The tests can either be skipped by - either setting _CAN_SUBSECOND_ACCURATELY to 0 in libio-async-perl - or in libio-async-loop-epoll-perl Both patches attached. Paul, did you have a change to look into this issue? (FWIW: My intuition is that setting _CAN_SUBSECOND_ACCURATELY to 0 as the default would make sense.) In a quick chat on IRC Paul confirmed this -- thanks. Cheers, gregor, preparing an upload -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Paul Mc Cartney: However Absurd signature.asc Description: Digital signature
Processed: Re: Bug#687403: libio-async-loop-epoll-perl: FTBFS: test failed
Processing control commands: reassign -1 libio-async-perl Bug #687403 [src:libio-async-loop-epoll-perl] libio-async-loop-epoll-perl: FTBFS: test failed Bug reassigned from package 'src:libio-async-loop-epoll-perl' to 'libio-async-perl'. No longer marked as found in versions libio-async-loop-epoll-perl/0.12-1. Ignoring request to alter fixed versions of bug #687403 to the same values previously set found -1 0.51-1 Bug #687403 [libio-async-perl] libio-async-loop-epoll-perl: FTBFS: test failed Marked as found in versions libio-async-perl/0.51-1. -- 687403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687403 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: your mail
Processing commands for cont...@bugs.debian.org: tags 690142 + patch Bug #690142 [bind9] remote named DoS on recursor (CVE-2012-5166) Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 690142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690142 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#687403: Pending fixes for bugs in the libio-async-perl package
tag 687403 + pending thanks Some bugs in the libio-async-perl package are closed in revision 191f3e206e424a8f810fd1b6124f48b620404b8f in branch 'master' by gregor herrmann The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libio-async-perl.git;a=commitdiff;h=191f3e2 Commit message: Update subscond.patch: set _CAN_SUBSECOND_ACCURATELY to 0. Turn of the subsecond tests by default, individual loops can than enable them. -- Change confirmed by upstream on IRC. Closes: #687403 Thanks: Paul LeoNerd Evans for confirming this fix. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Pending fixes for bugs in the libio-async-perl package
Processing commands for cont...@bugs.debian.org: tag 687403 + pending Bug #687403 [libio-async-perl] libio-async-loop-epoll-perl: FTBFS: test failed Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 687403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687403 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: affects 687403
Processing commands for cont...@bugs.debian.org: affects 687403 libio-async-loop-epoll-perl Bug #687403 [libio-async-perl] libio-async-loop-epoll-perl: FTBFS: test failed Added indication that 687403 affects libio-async-loop-epoll-perl thanks Stopping processing here. Please contact me if you need assistance. -- 687403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687403 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#581113: marked as done (infiniband-diags: bashism in /bin/sh script)
Your message dated Wed, 24 Oct 2012 22:02:26 +
with message-id e1tr91u-0008au...@franck.debian.org
and subject line Bug#581113: fixed in infiniband-diags 1.4.4-20090314-1.2
has caused the Debian Bug report #581113,
regarding infiniband-diags: bashism in /bin/sh script
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.)
--
581113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: infiniband-diags
Severity: important
Version: 1.4.4-20090314-1
User: debian-rele...@lists.debian.org
Usertags: goal-dash
Hello maintainer,
While performing an archive wide checkbashisms (from the 'devscripts' package)
check I've found your package containing a /bin/sh script making use
of a bashism.
checkbashisms' output:
possible bashism in ./usr/sbin/set_nodedesc line 8 ($HOST(TYPE|NAME)):
newname=$HOSTNAME
possible bashism in ./usr/sbin/set_nodedesc line 11 ('function' is
useless):
function usage
possible bashism in ./usr/sbin/set_nodedesc line 18 ($HOST(TYPE|NAME)):
echo Default is to use the hostname: \$HOSTNAME\
possible bashism in ./usr/sbin/set_nodedesc line 22 ('function' is
useless):
function viewall
Not using bash (or a Debian Policy compliant shell interpreter that doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours. Please be aware that dash is now the default /bin/sh.
Hints about how to fix bashisms can be found at:
https://wiki.ubuntu.com/DashAsBinSh
If you still don't know how to fix the bashisms don't hesitate to reply to
this email, or tag the bug as 'help'.
Thank you,
Raphael Geissert
---End Message---
---BeginMessage---
Source: infiniband-diags
Source-Version: 1.4.4-20090314-1.2
We believe that the bug you reported is fixed in the latest version of
infiniband-diags, 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 581...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Gilbert mgilb...@debian.org (supplier of updated infiniband-diags
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...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 22 Oct 2012 17:47:02 -0400
Source: infiniband-diags
Binary: infiniband-diags
Architecture: source amd64
Version: 1.4.4-20090314-1.2
Distribution: unstable
Urgency: medium
Maintainer: OFED and Debian Developement and Discussion
pkg-ofed-de...@lists.alioth.debian.org
Changed-By: Michael Gilbert mgilb...@debian.org
Description:
infiniband-diags - InfiniBand diagnostic programs
Closes: 581113
Changes:
infiniband-diags (1.4.4-20090314-1.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix bashisms in scripts/set_nodedesc.sh (closes: #581113).
Checksums-Sha1:
62ccce6b30441506483595d96363b2d6e688e48b 2828
infiniband-diags_1.4.4-20090314-1.2.dsc
73de12f8f4401caa717e2b60f5d14bda4d44967f 6847
infiniband-diags_1.4.4-20090314-1.2.debian.tar.gz
ef628e1127d65a22925f69a5987114a1bffabbf2 180566
infiniband-diags_1.4.4-20090314-1.2_amd64.deb
Checksums-Sha256:
54faece8be0f5342c053a6506235aff0a05bc4b41bcbe24129b8fe9acdf871e8 2828
infiniband-diags_1.4.4-20090314-1.2.dsc
d7013fb0f3936b10a772f1d9de30363a551eb07ad911356b93bd9fc3306e8b11 6847
infiniband-diags_1.4.4-20090314-1.2.debian.tar.gz
11aaab2c93d95753f8bb19355899a5d489dea185a518472c731596822bcda2b6 180566
infiniband-diags_1.4.4-20090314-1.2_amd64.deb
Files:
cac88f530c20fd668ff0227a50d0da46 2828 net extra
infiniband-diags_1.4.4-20090314-1.2.dsc
83d370cf6e19fbc611c09eb98551e03d 6847 net extra
infiniband-diags_1.4.4-20090314-1.2.debian.tar.gz
7fe76acf2824b3001a3ed48f1b02f890 180566 net extra
infiniband-diags_1.4.4-20090314-1.2_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQQcBAEBCAAGBQJQhb89AAoJELjWss0C1vRzzo4f/0i3wxSG2IszYk2yrPi4Wt5d
gzzhqWW/mmgs/Ltahl9GxCNuvg1CnY933bn70XHSItf4QHS5O92dctMcHATapy7T
iBo8bewzncPjuG9ODYErfzSVzgtjEAmQZV17gUAcuHc/jYRDS5qrsgDoWR5MHsTc
v7x1Q+3c7xuA6RqaBvQMgTHOlT1QPbHIKahl1traQnu71pgWFP+kI97thXIPX1KG
zKnzwTdoK1taBpjMXTaEFriWqRnDVyB+HvnsvDE1Q59polAj0Rqp0WUpFTTIGdQ2
V1p7D0bQJ/ohQTLmwE4UEJYLB0eFXTQM+mBAFSbnDdR8B4aJKX1oyjrQn26EzVXE
Bug#687403: marked as done (libio-async-loop-epoll-perl: FTBFS: test failed)
Your message dated Wed, 24 Oct 2012 22:02:31 + with message-id e1tr91z-0008dl...@franck.debian.org and subject line Bug#687403: fixed in libio-async-perl 0.51-4 has caused the Debian Bug report #687403, regarding libio-async-loop-epoll-perl: FTBFS: test 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.) -- 687403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libio-async-loop-epoll-perl Version: 0.12-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120912 qa-ftbfs Justification: FTBFS in wheezy on amd64 Hi, [ It seems that the fix for #680790 was not applied to libio-async-loop-epoll-perl ? Or is it only because the fixed libio-async-perl did not reach testing? ] During a rebuild of all packages in *wheezy*, your package failed to build on amd64. Relevant part: debian/rules build dh build dh_testdir dh_auto_configure Created MYMETA.yml and MYMETA.json Creating new 'Build' script for 'IO-Async-Loop-Epoll' version '0.12' dh_auto_build Building IO-Async-Loop-Epoll dh_auto_test t/00use.t ... ok t/01loop-io.t ... ok # Failed test 'One -loop_once(1) sufficient for a single 0.1 second timer' # at /usr/share/perl5/IO/Async/LoopTests.pm line 484. # got: '2' # expected: '1' # Looks like you failed 1 test of 26. t/02loop-timer.t Dubious, test returned 1 (wstat 256, 0x100) Failed 1/26 subtests t/03loop-signal.t ... ok t/04loop-idle.t . ok t/05loop-child.t ok t/06loop-control.t .. ok t/99pod.t ... ok Test Summary Report --- t/02loop-timer.t (Wstat: 256 Tests: 26 Failed: 1) Failed test: 20 Non-zero exit status: 1 Files=8, Tests=105, 16 wallclock secs ( 0.06 usr 0.04 sys + 0.51 cusr 0.15 csys = 0.76 CPU) Result: FAIL Failed 1/8 test programs. 1/105 subtests failed. dh_auto_test: perl Build test returned exit code 255 make: *** [build] Error 255 The full build log is available from: http://people.debian.org/~lucas/logs/2012/09/12/libio-async-loop-epoll-perl_0.12-1_wheezy.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: libio-async-perl Source-Version: 0.51-4 We believe that the bug you reported is fixed in the latest version of libio-async-perl, 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 687...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated libio-async-perl 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 24 Oct 2012 23:43:00 +0200 Source: libio-async-perl Binary: libio-async-perl Architecture: source all Version: 0.51-4 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: gregor herrmann gre...@debian.org Description: libio-async-perl - module providing asynchronous filehandle I/O Closes: 687403 Changes: libio-async-perl (0.51-4) unstable; urgency=low . * Update subscond.patch: set _CAN_SUBSECOND_ACCURATELY to 0. Turn of the subsecond tests by default, individual loops can than enable them. -- Change confirmed by upstream on IRC. Thanks to Paul LeoNerd Evans for confirming this fix. (Closes: #687403) Checksums-Sha1: 4a7b856d8e1ee46687a56b14bc09dfc7a11ed768 2352 libio-async-perl_0.51-4.dsc 8d6f1017a78cc8b1746a375851210fa640300d0e 5289 libio-async-perl_0.51-4.debian.tar.gz 5f3fd24e9339a831531ac4f0514a76e1d3137e3f 262772 libio-async-perl_0.51-4_all.deb Checksums-Sha256: 242c9e4fbc469d5160c7905c621c161aab8c54af8bedbe14f79d6d3326b5cd2c 2352 libio-async-perl_0.51-4.dsc bbc11645f35bce996d871d323132174c862981a942a003a2cd0078d94e65ab12 5289
Bug#691306: iptables add 4 rules instead just one in kernel INPUT chain
Hint: If you comment out ::1 localhost in /etc/hosts, the problem disappears. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: found 691306 iptables/1.4.14-3 Bug #691306 [iptables] [iptables] iptables add 4 rules instead just one in kernel INPUT chain Marked as found in versions iptables/1.4.14-3. End of message, stopping processing here. Please contact me if you need assistance. -- 691306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691306 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#691215: X request failed: BadDrawable
Antoine Beaupré escreveu: On 2012-10-23, Antonio Terceiro wrote: git clone git://wiki.reseaulibre.ca/ I killed the git clone after a couple minutes, it's taking too long. Can you please provide a tarball with only the presentation files intead (.pin + background images)? Understood. Should I attach it straight to the bug report or host it somewhere else? If it's not too big (a few hundred kb), I guess the bug report is OK. Otherwise you can upload it somewhere and give me an URL (and a sha1sum?). -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#691376: [buildd-tools-devel] Bug#691376: schroot: session recovery mounts $device, not $mount-device, for LVM snapshots
tags 1.6.3-1 + patch pending
thanks
On Wed, Oct 24, 2012 at 10:23:27PM +0100, Roger Leigh wrote:
Patch to address this issue. Note that this is not yet completely
tested for all the other block-device-using chroot types. **Do
not apply until tested.**
commit 19293f7a7b0943997397ef30465cd11686990a9b
Author: Roger Leigh rle...@debian.org
Date: Wed Oct 24 23:25:10 2012 +0100
sbuild: Don't call set_mount_device indirectly from ctor
See #691376.
sbuild::chroot_block_device_base::set_device was called from
the chroot_block_device_base ctor, and called
sbuild::chroot_facet_mountable::set_mount_device for all chroot
types except lvm-snapshot. However, dynamic_cast fails during
construction, leading to the mount device being overwritten, and
--recover-session mounting the source LV rather than the snapshot
LV. This patch moves the call to set_mount_device to the session
clone operation in sbuild::chroot_facet_session_clonable, which
is where the equivalent operation is done for lvm-snapshot. This
is done prior to lvm-snapshot to ensure that the snapshot is not
overwritten here either.
diff --git a/sbuild/sbuild-chroot-block-device-base.cc
b/sbuild/sbuild-chroot-block-device-base.cc
index 2f2f958..86f3af6 100644
--- a/sbuild/sbuild-chroot-block-device-base.cc
+++ b/sbuild/sbuild-chroot-block-device-base.cc
@@ -46,12 +46,8 @@ chroot_block_device_base::chroot_block_device_base ():
chroot_block_device_base::chroot_block_device_base
(const chroot_block_device_base rhs):
chroot(rhs),
- device()
+ device(rhs.device)
{
- /// @todo Required to set mount_device. Remove once no longer
- /// needed.
- if (!rhs.device.empty())
-set_device(rhs.device);
}
chroot_block_device_base::~chroot_block_device_base ()
@@ -71,16 +67,6 @@ chroot_block_device_base::set_device (std::string const
device)
throw error(device, DEVICE_ABS);
this-device = device;
-
- /// @todo: This may not be appropriate for derived classes such as
- /// lvm_snapshot, since re-setting the device could overwrite the
- /// mount device.
- chroot_facet_mountable::ptr pmnt
-(get_facetchroot_facet_mountable());
-#ifdef SBUILD_FEATURE_LVMSNAP
- if (!dynamic_castchroot_lvm_snapshot *(this))
-#endif
-pmnt-set_mount_device(this-device);
}
std::string
diff --git a/sbuild/sbuild-chroot-facet-session-clonable.cc
b/sbuild/sbuild-chroot-facet-session-clonable.cc
index 408e9ab..1d924ad 100644
--- a/sbuild/sbuild-chroot-facet-session-clonable.cc
+++ b/sbuild/sbuild-chroot-facet-session-clonable.cc
@@ -19,6 +19,7 @@
#include config.h
#include sbuild-chroot.h
+#include sbuild-chroot-facet-mountable.h
#include sbuild-chroot-facet-session.h
#include sbuild-chroot-facet-session-clonable.h
#include sbuild-chroot-facet-source-clonable.h
@@ -138,6 +139,19 @@ chroot_facet_session_clonable::clone_session_setup
(chroot::ptr clone,
format(Mount Location: %1%) % clone-get_mount_location()
endl;
+ /* Block devices need the mount device name specifying. */
+ /* Note that this will be overridden by LVM snapshot, below, so the
+ order here is important. */
+ std::shared_ptrchroot_block_device_base
blockdevbase(std::dynamic_pointer_castchroot_block_device_base(clone));
+ if (blockdevbase)
+{
+ chroot_facet_mountable::ptr pmnt
+ (clone-get_facetchroot_facet_mountable());
+ if (pmnt)
+ pmnt-set_mount_device(blockdevbase-get_device());
+}
+
+
#ifdef SBUILD_FEATURE_LVMSNAP
/* LVM devices need the snapshot device name specifying. */
std::shared_ptrchroot_lvm_snapshot
snapshot(std::dynamic_pointer_castchroot_lvm_snapshot(clone));
--
.''`. Roger Leigh
: :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686845: sympa: install fails when using sympa with sqlite3
Hi,
About these two bugs, there is actually 2 issues. Here is the status:
1) A new installation with the sqlite backend didn't work and leads
to the bug described in #686846
2) The upgrade from squeeze? to wheezy of sympa using sqlite backend
fails: sympa is unable to upgrade sqlite schema
About 1) I've already fixed it in my local devel branch.
About 2) I'm currently working on it but it could affect 1)
I'll try upload sympa with these 2 bugs fixed within the following days.
M.
--
Emmanuel Bouthenot
mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
xmpp: kol...@im.openics.org irc: kolter@{freenode,oftc}
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Pending
Processing commands for cont...@bugs.debian.org: tags 691376 + patch pending Bug #691376 [schroot] schroot: session recovery mounts $device, not $mount-device, for LVM snapshots Added tag(s) pending and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 691376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691376 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#691306: iptables add 4 rules instead just one in kernel INPUT chain
I traced that behavior to host_to_ipaddr function in libxtables/xtables.c --source hostname will match all the IP addresses of hostname. Same thing for --destination The problem is that gethostbyname(localhost) returns two results: 127.0.0.1 and 127.0.0.1 (yes, the same thing). So this might be a bug in libc --source localhost --destination localhost wrongly yields 2x2 = 4 combination of addresses signature.asc Description: This is a digitally signed message part.
Bug#691306: Bug #691306: iptables add 4 rules instead just one in kernel INPUT chain
Hi libc folks,
iptables --insert --source localhost ...
is currently creating duplicate entries.
I believe this is because of a problem in gethostbyname(localhost) that
returns duplicate answers.
Attached is a tiny test case.
./main
127.0.0.1
120.0.0.1
If I comment out ::1 localhost in my /etc/hosts file, I only get one answer:
./main
127.0.0.1
Has anything like that bent repported/fixed recently?
#include stdio.h
#include netdb.h
#include arpa/inet.h
int main() {
struct hostent *host;
struct in_addr **addr;
host = gethostbyname(localhost);
if (!host
|| host-h_addrtype != AF_INET
|| host-h_length != sizeof(struct in_addr))
return -1;
for(addr=host-h_addr_list; *addr; ++addr)
puts(inet_ntoa(**addr));
return 0;
}
signature.asc
Description: This is a digitally signed message part.
Bug#451137: aptitude update succeeds despite hash sum mismatch, etc.
Hi. Questions: a) Did this just affect the command line aptitude update or also the interactive u (well I guess so)? b) Is the problem just, that I don't get a proper exit/status, error message? Or were really (possibly forged) repo files added to the system and subsequently possibly compromised packages installed? I mean would have aptitude recognised is later that something is fishy,... and stopped installation of packages or not? Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#672030: Fwd: Re: Cannot build beast with gcc 4.7
On 20.10.2012 12:42, Reinhard Tartler wrote: Hi Tim, I wonder if there is any news on this bug on your side? Beast 0.7.6 with full support for g++-4.7 has been released now, see our website: http://beast.testbit.eu/ The full announcement is here: https://mail.gnome.org/archives/beast/2012-October/msg0.html Let me know if you have any further problems and thanks for your efforts. -- Yours sincerely, Tim Janik --- http://timj.testbit.eu/ - Free software Author -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683555: subversion: not working at all SASL context error
reassign 683555 libsasl2-2 forcemerge 636534 683555 forwarded 636534 https://bugzilla.cyrusimap.org/show_bug.cgi?id=3589 tags 636534 + fixed-upstream severity 636534 important thanks On Thu, Aug 02, 2012 at 01:59:36AM +0900, Norbert Preining wrote: due to a broken laptop I had to switch to an old one. After upgrading from a about 2 year old system, suddenly my svn is completely broken wrt to svn:// URLs. ALl trials (co, up, ...) terminate with the same error: $ svn up Updating '.': svn: E170001: Unable to connect to a repository at URL 'svn://u...@server.org/some/path' svn: E170001: Could not create SASL context: generic failure: No such file or directory $ The same happens with svn+ssh://... on svn.debian.org So, I was bitten by this as well. It seems that this bug is breaking Subversion on upgrades on systems that don't have a correct hostname. Having a broken hostname is of course bad, but this shouldn't stop Subversion from working, esp. since it's a regression from squeeze. It appears that it's not that uncommon: we had two separate bug reports with multiple reporters in Debian, there's a similar openSUSE¹ bug, a similar MacPorts bug² etc. It also affects more than Subversion; KMail Kontact have been explictly mentioned. So, I'm bumping the severity to important -- I also considered serious/RC, but I'll leave that up to the maintainer. The issue seems to have been fixed upstream with commit 8fc14fd702897e652a38384af2f55e51752e8c15, as mentioned in the upstream bug report³, so I think it'd be great if this ended up backported into wheezy. Thanks, Faidon ¹: https://bugzilla.novell.com/show_bug.cgi?id=771983 ²: https://trac.macports.org/ticket/34861 ³: https://bugzilla.cyrusimap.org/show_bug.cgi?id=3589 -- 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#683555: subversion: not working at all SASL context error
Processing commands for cont...@bugs.debian.org: reassign 683555 libsasl2-2 Bug #683555 [subversion] subversion: not working at all SASL context error Bug reassigned from package 'subversion' to 'libsasl2-2'. No longer marked as found in versions subversion/1.7.5-1. Ignoring request to alter fixed versions of bug #683555 to the same values previously set forcemerge 636534 683555 Bug #636534 [libsasl2-2] libsasl2-2: Hostname lookup has to succeed in 2.1.24 (didn't matter in 2.1.23) Bug #645435 [libsasl2-2] svn: generic failure with latest libsasl2-2 Bug #683555 [libsasl2-2] subversion: not working at all SASL context error Severity set to 'normal' from 'serious' Marked as found in versions cyrus-sasl2/2.1.24~rc1.dfsg1+cvs2011-05-23-4. Bug #645435 [libsasl2-2] svn: generic failure with latest libsasl2-2 Merged 636534 645435 683555 forwarded 636534 https://bugzilla.cyrusimap.org/show_bug.cgi?id=3589 Bug #636534 [libsasl2-2] libsasl2-2: Hostname lookup has to succeed in 2.1.24 (didn't matter in 2.1.23) Bug #645435 [libsasl2-2] svn: generic failure with latest libsasl2-2 Bug #683555 [libsasl2-2] subversion: not working at all SASL context error Set Bug forwarded-to-address to 'https://bugzilla.cyrusimap.org/show_bug.cgi?id=3589'. Set Bug forwarded-to-address to 'https://bugzilla.cyrusimap.org/show_bug.cgi?id=3589'. Set Bug forwarded-to-address to 'https://bugzilla.cyrusimap.org/show_bug.cgi?id=3589'. tags 636534 + fixed-upstream Bug #636534 [libsasl2-2] libsasl2-2: Hostname lookup has to succeed in 2.1.24 (didn't matter in 2.1.23) Bug #645435 [libsasl2-2] svn: generic failure with latest libsasl2-2 Bug #683555 [libsasl2-2] subversion: not working at all SASL context error Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. severity 636534 important Bug #636534 [libsasl2-2] libsasl2-2: Hostname lookup has to succeed in 2.1.24 (didn't matter in 2.1.23) Bug #645435 [libsasl2-2] svn: generic failure with latest libsasl2-2 Bug #683555 [libsasl2-2] subversion: not working at all SASL context error Severity set to 'important' from 'normal' Severity set to 'important' from 'normal' Severity set to 'important' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 636534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636534 645435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645435 683555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683555 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#691394: opendkim: DomainKeys Identified Mail (DKIM) Verifiers may inappropriately convey message trust
Package: opendkim Version: 2.0.1+dfsg-1 Severity: grave Tags: security upstream Justification: user security hole See http://www.kb.cert.org/vuls/id/268267, VU#268267 opendkim in squeeze, wheezy, sid offers no method to prevent use of keys less than 1024 bits. This is added in the new upstream release, 2.6.8, that was released just for this issue. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691394: marked as done (opendkim: DomainKeys Identified Mail (DKIM) Verifiers may inappropriately convey message trust)
Your message dated Thu, 25 Oct 2012 05:47:31 + with message-id e1trghz-0006ih...@franck.debian.org and subject line Bug#691394: fixed in opendkim 2.6.8-1 has caused the Debian Bug report #691394, regarding opendkim: DomainKeys Identified Mail (DKIM) Verifiers may inappropriately convey message trust 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.) -- 691394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: opendkim Version: 2.0.1+dfsg-1 Severity: grave Tags: security upstream Justification: user security hole See http://www.kb.cert.org/vuls/id/268267, VU#268267 opendkim in squeeze, wheezy, sid offers no method to prevent use of keys less than 1024 bits. This is added in the new upstream release, 2.6.8, that was released just for this issue. ---End Message--- ---BeginMessage--- Source: opendkim Source-Version: 2.6.8-1 We believe that the bug you reported is fixed in the latest version of opendkim, 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 691...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman sc...@kitterman.com (supplier of updated opendkim 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 25 Oct 2012 01:04:27 -0400 Source: opendkim Binary: opendkim opendkim-tools libopendkim7 libopendkim-dev libvbr2 libvbr-dev Architecture: source i386 Version: 2.6.8-1 Distribution: experimental Urgency: low Maintainer: Mike Markley m...@markley.org Changed-By: Scott Kitterman sc...@kitterman.com Description: libopendkim-dev - Headers and development libraries for the OpenDKIM library libopendkim7 - Library for signing and verifying DomainKeys Identified Mail sign libvbr-dev - Headers and development libraries for the OpenDKIM VBR library libvbr2- Library for RFC 5518 Vouch By Reference (VBR) opendkim - Milter implementation of DomainKeys Identified Mail opendkim-tools - Set of command line tools for OpenDKIM Closes: 691394 Changes: opendkim (2.6.8-1) experimental; urgency=low . * New upstream security release to add capability to exclude use of insecure keys (Closes: #691394, LP: #1071139) Checksums-Sha1: 794583903556c78846607cefc641ab9189a48d49 1397 opendkim_2.6.8-1.dsc c15cce7f254190567c4b96508a9d94f68ea806e8 1141247 opendkim_2.6.8.orig.tar.gz 00efa7109a185afee0845c8b11e51ab9eda5c87c 13100 opendkim_2.6.8-1.diff.gz f2ae7f1802b9f887133e55410d7778ef8ac6f35c 177920 opendkim_2.6.8-1_i386.deb d78e46bf01b05dcd6dce1a0932f8f74f74b2e5b7 167024 opendkim-tools_2.6.8-1_i386.deb 92efaabf58081b9629879f625e38a414a2de9fd9 86862 libopendkim7_2.6.8-1_i386.deb f91a70d0fcd56afedae063043f363a11a94e7ecd 175036 libopendkim-dev_2.6.8-1_i386.deb 355ba5a9ab2ad00740bef1ead0cbc10ee9387184 35256 libvbr2_2.6.8-1_i386.deb 35ad6c0097cfcf7cb76cfb37dcc9dbbe3050e31d 39022 libvbr-dev_2.6.8-1_i386.deb Checksums-Sha256: ab24aea2e141cdfbc17f7b3682c414f68d2a099a927268ffa2de328d25190bc8 1397 opendkim_2.6.8-1.dsc 1b2e9033842634a1dc891afa10a94ba58c0e7663670e2faf117b27bead541edc 1141247 opendkim_2.6.8.orig.tar.gz caeac4b57869a6b26fd81508994661b44f3cd2e66802ab9c8ac7012ed3f5d72a 13100 opendkim_2.6.8-1.diff.gz 7ad14c0191fa3674547d770c2c884ab761bddea633ecdf0e8e3d8e67bf5dfb2d 177920 opendkim_2.6.8-1_i386.deb 2181d2405333e534536525dac6cff5a6dfdfd5a8048a3ec362c07548ceeaf604 167024 opendkim-tools_2.6.8-1_i386.deb 56da135e9ae6441d079dfd05137290a5e8f163ed3c075422679e3241fa9c257d 86862 libopendkim7_2.6.8-1_i386.deb 569dc7061fbf433e5d856ed46bef593181a522912b35a54dea8f8a734e4f76f1 175036 libopendkim-dev_2.6.8-1_i386.deb 74f5766975d40c8e0283deda1f8636cc933102ddb3482b5efb4830cf5aee6b72 35256 libvbr2_2.6.8-1_i386.deb ebb4d8dc0db8a3f7748591d6c750affa299115cb0f90f3e01072d12dbbf58d8f 39022 libvbr-dev_2.6.8-1_i386.deb Files: dc7640424dd17f41e19ec0969fda169c 1397 mail extra opendkim_2.6.8-1.dsc b9f57c0635612f42c5f5173b3a23f097 1141247 mail extra opendkim_2.6.8.orig.tar.gz b91c138b7ba9569041d1a95b959f42e9 13100 mail extra opendkim_2.6.8-1.diff.gz b2c5e1afada71e51a6339ed5211d79fc 177920 mail extra opendkim_2.6.8-1_i386.deb
