Bug#675621: system freeze after safely unmounting usb drive
Hi, On 06/07/2012 11:22 PM, Ben Hutchings wrote: On Tue, Jun 05, 2012 at 09:05:42AM +0200, Rik Theys wrote: I have seen similar crashes with the 6.0.x kernel on some of our systems. Unfortunately the systems are in a remote location and I was unable to capture any crash screens. [...] This sounds somewhat the bug fixed by: commit 8354a9e00afb022f6b508bd7d6bd74daebb8b751 or possibly: commit 5e4c1dbf52bc1ff33782266332a62151d5b5f0be But we've had those since linux-2.6 version 2.6.32-36 (Debian release 6.0.3). So unless Sebastien has somehow failed to upgrade then this must be something different. I've checked the dpkg.log file on one of the systems on which I'm certain I switched to a 3.1 kernel because of this bug, and the last 2.6.32 kernel on it before I switched is 2.6.32-39. The 3.1.5 kernel I installed at that time did not have the bug. We're really going to need a kernel log in order to make any progress on this. I'll try to reproduce this on a test system, but I leave on holiday in a few hours so it could take a while. Rik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675183: sitplus: diff for NMU version 1.0.3-2.1
Hi Tim, On Thu, Jun 07, 2012 at 11:06:25PM +0100, Tim Retout wrote: > > many thanks for your fix. Â Would you be so kind to commit your change to > > the Git repository? Â Every DD has commit permissions to Debian Med Vcs. > > Just tell me if you do not feel able to do so and I will inject your > > changes. > > Hey Andreas! I've committed my changes... That's perfect, thanks. > I've left the upload in the > delayed queue for now, though. Fine for me - your work is perfectly welcome. 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#674006:
Please find attached a draft patch refreshed in the Debian style. This patch has passed build testing only on a Debian system. It has passed testing on Fedora. Run-time testing this patch on Debian will have to await either till I get access to the hardware effected or another person affected by this bug test compiles on their hardware, it works and they notify me so I can hustle for a NMU. best regards, Peter 07_magic_number.diff Description: Binary data
Bug#671711: Assumptions when processing triggers (was [pkg-mono-group] Bug#671711: monodoc-browser: fails to upgrade) from 'testing'
Hi! On Wed, 2012-05-09 at 16:12:14 +0100, Iain Lane wrote: > On Sun, May 06, 2012 at 10:37:53AM +0200, Andreas Beckmann wrote: > > […] > > > > during a test with piuparts I noticed your package fails to upgrade from > > 'testing'. > > It installed fine in 'testing', then the upgrade to 'sid' fails. > > > > >From the attached log (scroll to the bottom...): > > > > Preparing to replace monodoc-clutter-manual > > 1.0.0~alpha3~git20090817.r1.349dba6-7 (using > > .../monodoc-clutter-manual_1.0.0~alpha3~git20090817.r1.349dba6-8_all.deb) > > ... > > Unpacking replacement monodoc-clutter-manual ... > > Processing triggers for monodoc-browser ... > > generating monodoc search index... > > grep: /etc/gre.d/*.conf: No such file or directory > > > > Unhandled Exception: System.IO.FileNotFoundException: Could not load file > > or assembly 'gtk-sharp, Version=2.12.0.0, Culture=neutral, > > PublicKeyToken=35e10195dab3c99f' or one of its dependencies. > > File name: 'gtk-sharp, Version=2.12.0.0, Culture=neutral, > > PublicKeyToken=35e10195dab3c99f' > > [ERROR] FATAL UNHANDLED EXCEPTION: System.IO.FileNotFoundException: Could > > not load file or assembly 'gtk-sharp, Version=2.12.0.0, Culture=neutral, > > PublicKeyToken=35e10195dab3c99f' or one of its dependencies. > > File name: 'gtk-sharp, Version=2.12.0.0, Culture=neutral, > > PublicKeyToken=35e10195dab3c99f' > > dpkg: error processing monodoc-browser (--unpack): > >subprocess installed post-installation script returned error exit status > > 1 > > configured to not write apport reports > > Errors were encountered while processing: > >monodoc-browser > > It's because libgtk2.0-cil (on which monodoc-browser depends) has been > unpacked but not configured at this point. I thought (from reading > /usr/share/doc/dpkg-dev/triggers.txt.gz): > > , > | Packages in t-awaited and t-pending demand satisfaction of their > | dependencies just like packages in installed. > ` > > that I could assume this would be the case when running the trigger, but > apparently not. What am I guaranteed here? I spoke to Colin Watson about > this yesterday and he suggested that perhaps the postinst trigger could > register gtk-sharp into the GAC itself, which would be somewhat > unfortunate but would probably work if it is guaranteed that > libgtk2.0-cil will be unpacked or better when the trigger is activated. Hmmm, so I had prepared a patch which basically checks if the package has its dependencies fulfilled before calling the postinst script with "triggered", and otherwise defers the trigger processing for later (but only as long as it is not running from inside the deferred trigproc run). This fixes this specific case just fine (t-triggers-depends test case in dpkg/pkg-tests.git), but this in turn creates problems with packages with pending triggers depending on packages awaiting them, as it forces breaking trigger cycles, which is not really a nice upgrade path. An immediate example of this is man-db and dpkg itself. While this specific case could be fixed by removing the old versioned dpkg dependency from man-db, I'm assuming other such cases might exist on the archive, and I'm not prepared to add any such fix to dpkg w/o further analysis. In any case, this and most other similar cases would just disappear by switching those triggers to the noawait variants, but that's not supported by dpkg in stable so that would need to wait until after wheezy. OTOH I'm quite tired right now, and it's probable I'm missing something obvious... but in view of the above possibly producing mass breakage I've pulled out that patch from the dpkg 1.16.4 release which I wanted to push yesterday already. thanks, guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676598: libwine-bin: trying to overwrite '/usr/share/man/man1/regedit.1.gz', which is also in package wine-bin 1.4-3
Package: libwine-bin Version: 1.4-4 Severity: serious Justification: does not upgrade Hi Wine Maintainers, during the upgrade from 1.4-3 to 1.4-4 the following happens: Preparing to replace libwine-bin:i386 1.4-3 (using .../libwine-bin_1.4-4_i386.deb) ... Unpacking replacement libwine-bin:i386 ... dpkg: error processing /var/cache/apt/archives/libwine-bin_1.4-4_i386.deb (--unpack): trying to overwrite '/usr/share/man/man1/regedit.1.gz', which is also in package wine-bin 1.4-3 Grüße, Sven. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'experimental'), (400, 'testing'), (300, 'stable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.3.0-trunk-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libwine-bin depends on: ii libc62.13-33 ii libncurses5 5.9-8 ii libtinfo55.9-8 ii libwine 1.4-4 libwine-bin recommends no packages. libwine-bin suggests no packages. -- no debconf information -- debsums errors found: debsums: package libwine-bin is not installed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 675621 is serious
Processing commands for cont...@bugs.debian.org: > severity 675621 serious Bug #675621 [src:linux-2.6] base: system freeze after safely unmounting usb drive Severity set to 'serious' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 675621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675621 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#672204: csladspa causes several audio programs to segfault
Same here.. LMMS and jack-rack also sigfaults with cladspa.. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671979: (no subject)
On Thursday, June 07, 2012 08:15:41 PM Lisandro Damián Nicanor Pérez Meyer wrote: > Most Qt applications do not need to use pkg-config. If an app needs an > external library which ships a .pc file (libusb, for example), then the > programmer needs to call pkg-config from within the .pro. So, it's the app > that requires pkg-config and not qmake. > > For what I understand of the bug report, this is the case. > > Although part of Debian's Qt-KDE team, I don't usually hack in Qt itself > (at least in it's packaging), but I think the team will agree that > pkg-config should not be even a Suggest. If they don't... well, someone > may change that ;-) Looking at qtads.pro, it contains: CONFIG += link_pkgconfig PKGCONFIG += sdl So it looks like there's an optional qmake feature to ease using pkg-config. -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671979: (no subject)
On Jue 07 Jun 2012 23:26:55 Daniel Schepler escribió: > On Thu, Jun 7, 2012 at 3:42 PM, Nikos Chantziaras wrote: > > If qmake in Debian doesn't depend on pkg-config, then that's to be > > expected. qmake is a build system that uses pkg-config. Most Qt > > applications don't make use of that functionality though. > > > > I'm not the Debian maintainer. I'm qtads upstream, chipping-in to point > > out that qmake should most probably depend on pkg-config :-) > > If qmake can function without pkg-config, that makes the dependency at > most a Recommends. And if most Qt applications don't use the > pkg-config functionality, then a Suggests seems most appropriate. (Cc > to qt4-qmake package maintainers to get input on this point.) In > either case, the original bug report would be correct that qtads > should be Build-Depending on pkg-config. Most Qt applications do not need to use pkg-config. If an app needs an external library which ships a .pc file (libusb, for example), then the programmer needs to call pkg-config from within the .pro. So, it's the app that requires pkg-config and not qmake. For what I understand of the bug report, this is the case. Although part of Debian's Qt-KDE team, I don't usually hack in Qt itself (at least in it's packaging), but I think the team will agree that pkg-config should not be even a Suggest. If they don't... well, someone may change that ;-) Kinds regards, Lisandro. -- Theory and practice sometimes clash. And when that happens, theory loses. Every single time. Linus Benedict Torvalds. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: r4902 - in packages/grcompiler/tags: . 4.2~pre6-1 4.2~pre6-1/debian 4.2~pre6-1/test/GrcRegressionTest/fonts
Processing commands for cont...@bugs.debian.org:
> tags 673723 pending
Bug #673723 {Done: Daniel Glassey } [grcompiler] FTBFS: test
failures on arm, powerpc, s390
Ignoring request to alter tags of bug #673723 to the same tags previously set
> tags 614754 pending
Bug #614754 {Done: Daniel Glassey } [wnpp] ITP: grcompiler --
SIL Graphite compiler
Ignoring request to alter tags of bug #614754 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
614754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614754
673723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673723
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#671979: (no subject)
On Thu, Jun 7, 2012 at 3:42 PM, Nikos Chantziaras wrote: > If qmake in Debian doesn't depend on pkg-config, then that's to be expected. > qmake is a build system that uses pkg-config. Most Qt applications don't > make use of that functionality though. > > I'm not the Debian maintainer. I'm qtads upstream, chipping-in to point out > that qmake should most probably depend on pkg-config :-) If qmake can function without pkg-config, that makes the dependency at most a Recommends. And if most Qt applications don't use the pkg-config functionality, then a Suggests seems most appropriate. (Cc to qt4-qmake package maintainers to get input on this point.) In either case, the original bug report would be correct that qtads should be Build-Depending on pkg-config. -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Raising severity
Processing commands for cont...@bugs.debian.org: > severity 674006 critical Bug #674006 [libwvstreams4.6-base] wvdial stop working: Assertion `magic_number == -0x123678' failed Severity set to 'critical' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 674006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674006 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#674899: Bug disappeared after upgrading accountsservice to 0.6.21-3
Hi, This bug disappeared after upgrading accountsservice to 0.6.21-3. There are also bugs related to gnome-shell in package accountsservice. This bug might be the same to bug #675863. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675863 Hope that helps. zevan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676591: parted: FTBFS in sid: ABI has changed. Please, update you ABI package version.
Package: parted Version: 2.3-9.1 Severity: serious Justification: FTBFS Tags: patch Hello, The parted build fails due to new symbols appearing from the gnulib code: --- ../scripts/data/abi/baseline_symbols.txt2012-06-08 00:30:25.219504001 + +++ ./current_symbols.txt 2012-06-08 00:30:49.346954684 + @@ -501,11 +501,15 @@ FUNC:version_etc_ar FUNC:version_etc_arn FUNC:version_etc_va +FUNC:x2nrealloc FUNC:x2realloc FUNC:xalloc_die FUNC:xcalloc +FUNC:xcharalloc FUNC:xmalloc FUNC:xmemdup +FUNC:xnmalloc +FUNC:xnrealloc FUNC:xrealloc FUNC:xstrdup FUNC:xstrndup ABI has changed. Please, update you ABI package version. The attached patch will fix it, I plan to NMU it along other fixes. Samuel -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.4 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages parted depends on: ii libblkid1 2.20.1-4 ii libc6 2.13-32 ii libdevmapper1.02.1 2:1.02.67-2 ii libparted0debian1 2.3-9.1 ii libreadline66.2-8 ii libtinfo5 5.9-7 ii libuuid12.20.1-4 parted recommends no packages. Versions of packages parted suggests: ii parted-doc 2.3-9.1 -- no debconf information -- Samuel Thibault sl - display animations aimed to correct users who accidentally enter sl instead of ls. --- debian/patches/update-abi-symbols.patch.orig2012-06-08 02:33:07.779805212 +0200 +++ debian/patches/update-abi-symbols.patch 2012-06-08 02:33:52.394790988 +0200 @@ -200,7 +200,7 @@ FUNC:ped_round_down_to FUNC:ped_round_to_nearest FUNC:ped_round_up_to -@@ -406,45 +449,112 @@ +@@ -406,45 +449,116 @@ FUNC:ped_unit_parse FUNC:ped_unit_parse_custom FUNC:ped_unit_set_default @@ -258,11 +258,15 @@ +FUNC:version_etc_ar +FUNC:version_etc_arn +FUNC:version_etc_va ++FUNC:x2nrealloc +FUNC:x2realloc +FUNC:xalloc_die +FUNC:xcalloc ++FUNC:xcharalloc +FUNC:xmalloc +FUNC:xmemdup ++FUNC:xnmalloc ++FUNC:xnrealloc +FUNC:xrealloc +FUNC:xstrdup +FUNC:xstrndup
Bug#676590: parted: FTBFS in sid: variable 'buf' set but not used
Package: parted
Version: 2.3-9.1
Severity: serious
Justification: FTBFS
Tags: patch
Hello,
parted currently FTBFS in sid:
../../lib/regex_internal.c:738:20: error: variable 'buf' set but not used
[-Werror=unused-but-set-variable]
This is indeed a bug, which was fixed in upstream gnulib, here is the
corresponding patch, why I intend to NMU along the hurd patch.
Samuel
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages parted depends on:
ii libblkid1 2.20.1-4
ii libc6 2.13-32
ii libdevmapper1.02.1 2:1.02.67-2
ii libparted0debian1 2.3-9.1
ii libreadline66.2-8
ii libtinfo5 5.9-7
ii libuuid12.20.1-4
parted recommends no packages.
Versions of packages parted suggests:
ii parted-doc 2.3-9.1
-- no debconf information
--
Samuel Thibault
* B kicks DW (non mais franchement)
* DW was kicked
-+- #ens-mim - comment ça hopeless ? -+-
--- regex_internal.c.orig 2012-06-08 02:15:54.083227641 +0200
+++ regex_internal.c2012-06-08 02:20:44.364702306 +0200
@@ -738,16 +738,18 @@
unsigned char buf[6];
size_t mbclen;
+ const unsigned char *pp = p;
if (BE (pstr->trans != NULL, 0))
{
int i = mlen < 6 ? mlen : 6;
while (--i >= 0)
buf[i] = pstr->trans[p[i]];
+ pp = buf;
}
/* XXX Don't use mbrtowc, we know which conversion
to use (UTF-8 -> UCS4). */
memset (&cur_state, 0, sizeof (cur_state));
- mbclen = __mbrtowc (&wc2, (const char *) p, mlen,
+ mbclen = __mbrtowc (&wc2, (const char *) pp, mlen,
&cur_state);
if (raw + offset - p <= mbclen
&& mbclen < (size_t) -2)
Bug#676510: marked as done (CVE-2012-1820: DoS in BGP)
Your message dated Fri, 08 Jun 2012 00:03:53 + with message-id and subject line Bug#676510: fixed in quagga 0.99.21-3 has caused the Debian Bug report #676510, regarding CVE-2012-1820: DoS in BGP 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.) -- 676510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: quagga Severity: grave Tags: security Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-1820 for details and a patch. Cheers, Moritz --- End Message --- --- Begin Message --- Source: quagga Source-Version: 0.99.21-3 We believe that the bug you reported is fixed in the latest version of quagga, which is due to be installed in the Debian FTP archive: quagga-dbg_0.99.21-3_amd64.deb to main/q/quagga/quagga-dbg_0.99.21-3_amd64.deb quagga-doc_0.99.21-3_all.deb to main/q/quagga/quagga-doc_0.99.21-3_all.deb quagga_0.99.21-3.debian.tar.gz to main/q/quagga/quagga_0.99.21-3.debian.tar.gz quagga_0.99.21-3.dsc to main/q/quagga/quagga_0.99.21-3.dsc quagga_0.99.21-3_amd64.deb to main/q/quagga/quagga_0.99.21-3_amd64.deb 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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Hammers (supplier of updated quagga 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: Fri, 08 Jun 2012 01:15:32 +0200 Source: quagga Binary: quagga quagga-dbg quagga-doc Architecture: source amd64 all Version: 0.99.21-3 Distribution: unstable Urgency: high Maintainer: Christian Hammers Changed-By: Christian Hammers Description: quagga - BGP/OSPF/RIP routing daemon quagga-dbg - BGP/OSPF/RIP routing daemon (debug symbols) quagga-doc - documentation files for quagga Closes: 676510 Changes: quagga (0.99.21-3) unstable; urgency=high . * SECURITY: CVE-2012-1820 - Quagga contained a bug in BGP OPEN message handling. A denial-of-service condition could be caused by an attacker controlling one of the pre-configured BGP peers. In most cases this means, that the attack must be originated from an adjacent network. Closes: #676510 Checksums-Sha1: 10365fa085747bfd8d269429388f9ed206736861 1434 quagga_0.99.21-3.dsc 56387fc02f2d9d304e50575b47073be746595229 39087 quagga_0.99.21-3.debian.tar.gz 2744e5c0155b82c3d748fe30ae5dddc3da834f20 1707946 quagga_0.99.21-3_amd64.deb be5cff3e6a304ff2a511dd80c1beec8f3bd14d31 2500786 quagga-dbg_0.99.21-3_amd64.deb 6914053ac48b0ad476a7ccb3ee778ddfaaf2a360 645080 quagga-doc_0.99.21-3_all.deb Checksums-Sha256: 43452d259b6864e30cf56aba1cc0e0d979a3c383551dc6140680b6ca99df6543 1434 quagga_0.99.21-3.dsc e412312efa9635d65bdcd62140600b9326f4d35b23fd199a3dc124542f98a644 39087 quagga_0.99.21-3.debian.tar.gz 3bba73189f0f081592771cdddf3ba1accdeaf09711467272c8e5e5581fa94bb6 1707946 quagga_0.99.21-3_amd64.deb 9d1621d839648205e6280a3b00013c5e34d8089738580915d2168e28965bc843 2500786 quagga-dbg_0.99.21-3_amd64.deb d462367883849add437629084047efca6428923b45ec9a1b2d13f24c75ed1396 645080 quagga-doc_0.99.21-3_all.deb Files: bf0a87b64d83a71c2edfe65d52da2f9c 1434 net optional quagga_0.99.21-3.dsc fda2e4b4ceed964aa270b92685e9de43 39087 net optional quagga_0.99.21-3.debian.tar.gz da85822a4300b91986cb677ee1127feb 1707946 net optional quagga_0.99.21-3_amd64.deb e623d24b662c3560aff7a46b9d7aacc9 2500786 debug extra quagga-dbg_0.99.21-3_amd64.deb 3ffda7f77eb335724ac00bb03c42f435 645080 net optional quagga-doc_0.99.21-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/RPDwACgkQkR9K5oahGObkfgCfXt0FCzInncou+oe7lkYwxjKQ n/0An0lylESWuFTBr1TEHAAeXGECMME4 =rMqf -END PGP SIGNATURE- --- End Message ---
Bug#676584: marked as done (libx86 1.1+ds1-8 FTFS on amd64)
Your message dated Thu, 07 Jun 2012 23:47:50 + with message-id and subject line Bug#676584: fixed in libx86 1.1+ds1-9 has caused the Debian Bug report #676584, regarding libx86 1.1+ds1-8 FTFS on amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 676584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libx86 Severity: Serious Version: 1.1+ds1-8 https://buildd.debian.org/status/fetch.php?pkg=libx86&arch=amd64&ver=1.1%2Bds1-8&stamp=1338893113 cc -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -O2 -Wall -DDEBUG -g -fPIC -fPIE -pie -Wl,-z,relro -Wl,-z,now -o libx86.so.1 -shared -Wl,-soname,libx86.so.1 x86-common.o thunk.o x86emu/decode.o x86emu/debug.o x86emu/fpu.o x86emu/ops.o x86emu/ops2.o x86emu/prim_ops.o x86emu/sys.o /usr/bin/ld: thunk.o: relocation R_X86_64_PC32 against symbol `mmap_addr' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status --- End Message --- --- Begin Message --- Source: libx86 Source-Version: 1.1+ds1-9 We believe that the bug you reported is fixed in the latest version of libx86, which is due to be installed in the Debian FTP archive: libx86-1_1.1+ds1-9_amd64.deb to main/libx/libx86/libx86-1_1.1+ds1-9_amd64.deb libx86-dbg_1.1+ds1-9_amd64.deb to main/libx/libx86/libx86-dbg_1.1+ds1-9_amd64.deb libx86-dev_1.1+ds1-9_amd64.deb to main/libx/libx86/libx86-dev_1.1+ds1-9_amd64.deb libx86_1.1+ds1-9.debian.tar.bz2 to main/libx/libx86/libx86_1.1+ds1-9.debian.tar.bz2 libx86_1.1+ds1-9.dsc to main/libx/libx86/libx86_1.1+ds1-9.dsc 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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anibal Monsalve Salazar (supplier of updated libx86 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: Fri, 08 Jun 2012 08:39:13 +1000 Source: libx86 Binary: libx86-dev libx86-1 libx86-dbg Architecture: source amd64 Version: 1.1+ds1-9 Distribution: unstable Urgency: low Maintainer: Anibal Monsalve Salazar Changed-By: Anibal Monsalve Salazar Description: libx86-1 - x86 real-mode library libx86-dbg - x86 real-mode library - debugging symbols libx86-dev - x86 real-mode library - development files Closes: 398249 570676 654399 676584 Changes: libx86 (1.1+ds1-9) unstable; urgency=low . * Build architectures are any-i386 and any-amd64 only Closes: #654399, #570676, #398249 * Comment out "export DEB_BUILD_MAINT_OPTIONS = hardening=+all" Closes: #676584 Checksums-Sha1: e936279956aee4f1c53d84f754e86a926c5a7fa0 1965 libx86_1.1+ds1-9.dsc 06c5aaa9fbed6f2fd947e3fe9839ec9fc3e3fff1 5718 libx86_1.1+ds1-9.debian.tar.bz2 ae4b433e5b54cad46def4f255e65c7ee3b1a9f87 96954 libx86-dev_1.1+ds1-9_amd64.deb 87b2daed50d327dbd47ddac12824db385a0b5a97 85782 libx86-1_1.1+ds1-9_amd64.deb 7829cf679db43f6a152a867ff212af3025f992c2 123824 libx86-dbg_1.1+ds1-9_amd64.deb Checksums-Sha256: 80b771c59669665c0bf6503aab3e2ae4900a9b677157a2ea955de4c5e949c431 1965 libx86_1.1+ds1-9.dsc 9f30db8d0339543001409e8b1ea03ed6996524f2435c36d6d6f42fa8380fead9 5718 libx86_1.1+ds1-9.debian.tar.bz2 834677e2e782de0be6a037f1d611419dec4f5439619bd7f89f3e7fbee3c77d30 96954 libx86-dev_1.1+ds1-9_amd64.deb 39b7c90cfa5c8f8e6fb50a01d213d12734d96acdd9920914af301431ef6e2e98 85782 libx86-1_1.1+ds1-9_amd64.deb 2620645f8200d2b96c3081cbb5e25a54b843321b87c5c64471d8d0b6544fbbc1 123824 libx86-dbg_1.1+ds1-9_amd64.deb Files: 23d6fea0f0be13ca15d219cd94dba5b0 1965 libs optional libx86_1.1+ds1-9.dsc e7129acc52b15debad17e5f0d1040ea2 5718 libs optional libx86_1.1+ds1-9.debian.tar.bz2 c7ab45e02a756f38735401c6d4e70209 96954 libdevel optional libx86-dev_1.1+ds1-9_amd64.deb d61f27b57a6ddf767c1f4316240fe6df 85782 libs optional libx86-1_1.1+ds1-9_amd64.deb 4a9274bd6ef5fdd88c4ca91bbb3d6755 123824 debug extra libx86-dbg_1.1+ds1-9_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP0TqNAAoJEHxWrP6UeJfYa8MP/1jfY2IKWig2XiN6Di9D3nbh xAh3WOKc+mr9viH49mYddhRd25MRwpwi8G1H1LSZd0w8xpSEJjXOkVqAhyckcN
Bug#676584: libx86 1.1+ds1-8 FTFS on amd64
Package: libx86 Severity: Serious Version: 1.1+ds1-8 https://buildd.debian.org/status/fetch.php?pkg=libx86&arch=amd64&ver=1.1%2Bds1-8&stamp=1338893113 cc -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -O2 -Wall -DDEBUG -g -fPIC -fPIE -pie -Wl,-z,relro -Wl,-z,now -o libx86.so.1 -shared -Wl,-soname,libx86.so.1 x86-common.o thunk.o x86emu/decode.o x86emu/debug.o x86emu/fpu.o x86emu/ops.o x86emu/ops2.o x86emu/prim_ops.o x86emu/sys.o /usr/bin/ld: thunk.o: relocation R_X86_64_PC32 against symbol `mmap_addr' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667109: marked as done (barry: ftbfs with GCC-4.7)
Your message dated Thu, 7 Jun 2012 17:16:20 -0400 with message-id <20120607211620.ga3...@foursquare.net> and subject line Barry 0.18.3-3 contains patch already has caused the Debian Bug report #667109, regarding barry: ftbfs with GCC-4.7 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.) -- 667109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: barry Version: 0.15-1.2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. packet.h:219:17: error: 'off_t' has not been declared The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/barry_0.15-1.2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.. -D_FORTIFY_SOURCE=2 -ansi -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -c -o r_message_base.lo r_message_base.cc g++ -DHAVE_CONFIG_H -I.. -D_FORTIFY_SOURCE=2 -ansi -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -c r_message_base.cc -fPIC -DPIC -o .libs/r_message_base.o r_message_base.cc: In member function 'const unsigned char* Barry::MessageBase::ParseField(const unsigned char*, const unsigned char*, const Barry::IConverter*)': r_message_base.cc:161:7: warning: variable 'swallow' set but not used [-Wunused-but-set-variable] g++ -DHAVE_CONFIG_H -I.. -D_FORTIFY_SOURCE=2 -ansi -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -c r_message_base.cc -o r_message_base.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.. -D_FORTIFY_SOURCE=2 -ansi -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -c -o r_servicebook.lo r_servicebook.cc g++ -DHAVE_CONFIG_H -I.. -D_FORTIFY_SOURCE=2 -ansi -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -c r_servicebook.cc -fPIC -DPIC -o .libs/r_servicebook.o g++ -DHAVE_CONFIG_H -I.. -D_FORTIFY_SOURCE=2 -ansi -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -c r_servicebook.cc -o r_servicebook.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.. -D_FORTIFY_SOURCE=2 -ansi -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -c -o r_sms.lo r_sms.cc g++ -DHAVE_CONFIG_H -I.. -D_FORTIFY_SOURCE=2 -ansi -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -c r_sms.cc -fPIC -DPIC -o .libs/r_sms.o g++ -DHAVE_CONFIG_H -I.. -D_FORTIFY_SOURCE=2 -ansi -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -c r_sms.cc -o r_sms.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.. -D_FORTIFY
Bug#671979: (no subject)
On 08/06/12 00:04, Artur Rona wrote: W dniu 2012-06-07 22:02, Nikos Chantziaras pisze: qtads.pro uses qmake's support for pkg-config and never calls it directly. pkg-config support is shipped with Qt in "mkspecs/features/link_pkgconfig.prf". It assumes pkg-config is present on the system. Maybe in theory. In practise, pbuilder gives FTBFS in result. If qmake in Debian doesn't depend on pkg-config, then that's to be expected. qmake is a build system that uses pkg-config. Most Qt applications don't make use of that functionality though. BTW, can you please upgrade qtads to 2.1.3? I'm not the Debian maintainer. I'm qtads upstream, chipping-in to point out that qmake should most probably depend on pkg-config :-) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674186: [Bug 301075] [digikam] external mysql db empty after database migration
https://bugs.kde.org/show_bug.cgi?id=301075 Francesco Riosa changed: What|Removed |Added CC||francesco+...@pnpitalia.it --- Comment #2 from Francesco Riosa --- Hi, could you please help us providing some more info? To see more debug output launch `kdebugdialog --fullmode` search for 'digikam', activate the debug output, expecially for area 50007 output to information to a file. Launch digikam possibly from a shell, then try to redo the conversion and attach to this bug the result. Also, previous version of digikam? -- You are receiving this mail because: You reported the bug. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676539: [debian-mysql] Bug#676539: mysql-server-5.5: migration from /var/run/mysqld to /run/mysqld incomplete
Greg, As it happens someone else raised the same bug at about the same time. I happened to come across yours first. The issue is fairly obvious if one thinks about it and it should not really have been missed. On 07/06/12 23:22, Greg Alexander wrote: Hi - Thanks for looking into this. The mysql script caused the creation of a new /run from scratch without consideration for the old /var/run, which does not honor the contract specified in: http://wiki.debian.org/ReleaseGoals/RunDirectory There it is specified that /var/run is an alias for /run, but the mysql upgrade process did not cause that result. Sorry, I'm a little snippy. Upgrade compatibility is a minor obsession of mine, and the reason that I use Debian (and look down on most other OSes). I'll delete the sarcastic paragraph and jump straight to the punchline. I am running initscripts-2.87dsf-6 (2009 - quite modern, in fact). The modern mysql packages appear to have an undeclared dependency upon initscripts-2.88dsf-13.3. Or in other words, quoting from that ReleaseGoals/RunDirectory document: Before wheezy, a versioned depends upon initscripts (>= 2.88dsf-13.3) will be required to ensure the presence of a functional /run. Since wheezy is not even released yet, and since 17 other packages do still have declared dependencies on initscripts>= 2.88dsf-13.3, I assume that is still in effect... Probably you guys just weren't aware that the /run transition is newer than any LSB document, so the lsb-base dependency doesn't do anything for us here. Cheers, - Greg evidence that this is causing a problem. On a standard recent Debian system /var/run will be a symlink to /run. In fact I could not even see Debian On Thu, Jun 07, 2012 at 10:25:10PM +0100, Nicholas Bamber wrote: severity 676539 minor tag 676539 +moreinfo thanks Greg, Thanks for pointing out the incompletenesses in our migration. They will be acted on if substantiated. I am downgrading the severity because I could not see any actual evidence that this is causing a problem. On a standard recent Debian system /var/run will be a symlink to /run. In fact I could not even see any evidence that this is true. What I think happened is that since /etc/mysql/debian.cnf already existed, the mysql-server-5.5 postinst script had no reason to create it afresh. As for the change it may well (or not) be a pointless change but it is recommended by section 9.1.4 of the latest version of the Debian policy. The lintian tool attempts to find and report on violations. As for libdbd-mysql-perl that is a separate package. If it was an issue it would require a separate bug report. I had a look through both the upstream and packaging code and I could not see anywhere where the MySQL socket file location is defaulted or hardcoded. I think it should be picked up from the libmysqlclient18 package (which is part the mysql-5.5 package). However libdbd-mysql-perl has not yet been binNMU'ed so that would be why that is picking up the old location. If you have any more information please let me know. Otherwise can I close the ticket? On 07/06/12 18:10, Greg Alexander wrote: Package: mysql-server-5.5 Version: 5.5.24+dfsg-2 Severity: important Dear Maintainer, Upon upgrading to mysql-server-5.5, I find that /var/run/mysqld has been needlessly renamed to /run/mysqld. Pointless renaming is considered harmful! You forgot to update a few things when you performed this pointless operation. /etc/mysql/debian.cnf continues to reference /var/run/mysqld. The perl DBI package continues to reference /var/run/mysqld. The need to enumerate the innumerable potential dependencies on the mysqld socket location can be ameliorated through the use of symlinks. Add this to the postrm file: ln -s /run/mysqld /var/run/mysqld But in fact, you could have avoided this whole problem in the first place by not pointlessly renaming /var/run to /run. In the future, try not to break things for no reason. We have symlinks for a reason. Any unix admin who needs /var/run to live in a special location can achieve this effect using mount or ln already. There is no need to render every mysql-dependent configuration file suspect to achieve this end. If the person who decided to rename /var/run/mysqld to /run/mysqld should happen to read this thread, I beg you to please consider swearing off future contribution to open source projects. You are simply not cool enough for my club. - Greg -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32.22 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages mysql-server-5.5 depends on: ii adduser3.102 ii debconf [debconf-2.0] 1.5.40 ii libc6 2.13-10 ii libdbi-perl1.621-1 ii libgcc1
Bug#676539: [debian-mysql] Bug#676539: mysql-server-5.5: migration from /var/run/mysqld to /run/mysqld incomplete
Hi - Thanks for looking into this. The mysql script caused the creation of a new /run from scratch without consideration for the old /var/run, which does not honor the contract specified in: http://wiki.debian.org/ReleaseGoals/RunDirectory There it is specified that /var/run is an alias for /run, but the mysql upgrade process did not cause that result. Sorry, I'm a little snippy. Upgrade compatibility is a minor obsession of mine, and the reason that I use Debian (and look down on most other OSes). I'll delete the sarcastic paragraph and jump straight to the punchline. I am running initscripts-2.87dsf-6 (2009 - quite modern, in fact). The modern mysql packages appear to have an undeclared dependency upon initscripts-2.88dsf-13.3. Or in other words, quoting from that ReleaseGoals/RunDirectory document: Before wheezy, a versioned depends upon initscripts (>= 2.88dsf-13.3) will be required to ensure the presence of a functional /run. Since wheezy is not even released yet, and since 17 other packages do still have declared dependencies on initscripts >= 2.88dsf-13.3, I assume that is still in effect... Probably you guys just weren't aware that the /run transition is newer than any LSB document, so the lsb-base dependency doesn't do anything for us here. Cheers, - Greg > evidence that this is causing a problem. On a standard recent Debian > system /var/run will be a symlink to /run. In fact I could not even see Debian On Thu, Jun 07, 2012 at 10:25:10PM +0100, Nicholas Bamber wrote: > severity 676539 minor > tag 676539 +moreinfo > thanks > > Greg, > > Thanks for pointing out the incompletenesses in our migration. They > will be acted on if substantiated. > > I am downgrading the severity because I could not see any actual > evidence that this is causing a problem. On a standard recent Debian > system /var/run will be a symlink to /run. In fact I could not even see > any evidence that this is true. What I think happened is that since > /etc/mysql/debian.cnf already existed, the mysql-server-5.5 postinst > script had no reason to create it afresh. > > As for the change it may well (or not) be a pointless change but it is > recommended by section 9.1.4 of the latest version of the Debian policy. > The lintian tool attempts to find and report on violations. > > As for libdbd-mysql-perl that is a separate package. If it was an issue > > it would require a separate bug report. I had a look through both the > upstream and packaging code and I could not see anywhere where the MySQL > socket file location is defaulted or hardcoded. I think it should be > picked up from the libmysqlclient18 package (which is part the mysql-5.5 > package). However libdbd-mysql-perl has not yet been binNMU'ed so that > would be why that is picking up the old location. > > If you have any more information please let me know. Otherwise can I > close the ticket? > > On 07/06/12 18:10, Greg Alexander wrote: >> Package: mysql-server-5.5 >> Version: 5.5.24+dfsg-2 >> Severity: important >> >> Dear Maintainer, >> >> Upon upgrading to mysql-server-5.5, I find that /var/run/mysqld has been >> needlessly renamed to /run/mysqld. >> >> Pointless renaming is considered harmful! >> >> You forgot to update a few things when you performed this pointless >> operation. /etc/mysql/debian.cnf continues to reference /var/run/mysqld. >> The perl DBI package continues to reference /var/run/mysqld. >> >> The need to enumerate the innumerable potential dependencies on the >> mysqld socket location can be ameliorated through the use of symlinks. >> Add this to the postrm file: >> ln -s /run/mysqld /var/run/mysqld >> >> But in fact, you could have avoided this whole problem in the first >> place by not pointlessly renaming /var/run to /run. >> >> In the future, try not to break things for no reason. We have symlinks >> for a reason. Any unix admin who needs /var/run to live in a special >> location can achieve this effect using mount or ln already. There is >> no need to render every mysql-dependent configuration file suspect to >> achieve this end. >> >> If the person who decided to rename /var/run/mysqld to /run/mysqld >> should happen to read this thread, I beg you to please consider swearing >> off future contribution to open source projects. You are simply not cool >> enough for my club. >> >> - Greg >> >> >> -- System Information: >> Debian Release: squeeze/sid >>APT prefers unstable >>APT policy: (500, 'unstable') >> Architecture: i386 (i686) >> >> Kernel: Linux 2.6.32.22 (SMP w/2 CPU cores; PREEMPT) >> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) >> Shell: /bin/sh linked to /bin/bash >> >> Versions of packages mysql-server-5.5 depends on: >> ii adduser3.102 >> ii debconf [debconf-2.0] 1.5.40 >> ii libc6 2.13-10 >> ii libdbi-perl1.621-1 >> ii libgcc11:4.6.1-4 >> ii libstdc++6
Bug#666959: marked as done (pfstools: Adjust for the new octave package version 3.6.1)
Your message dated Thu, 07 Jun 2012 22:25:09 +
with message-id
and subject line Bug#666959: fixed in pfstools 1.8.5-0.1
has caused the Debian Bug report #666959,
regarding pfstools: Adjust for the new octave package version 3.6.1
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.)
--
666959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pfstools
Version: 1.8.1-2
Severity: important
Tags: patch
The current version of pfstools in sid build-depends on
octave3.2-headers. This later package will be removed from unstable once
the transition to the new version of octave (currently 3.6.1)q will be
completed (see the wiki page of the DOG [1]).
The pfstools package needs octave3.2-headers for including the makefile
fragment defs.make and for calling the octave-depends script that makes
the substitution of ${octave:Depends}. These files have been dropped in
the Debian packaging of Octave 3.6.1.
I am attaching below a patch for fixing the issues in this bug report.
The patch was obtained through debdiff. I added the corresponding entries
to debian/changelog. The octave-pfstools package should now simply
depend on octave. Note that the octave-pfstools package will, in fine,
depend on liboctave1, which will pull the appropriate version of octave
(3.6.1-4, currently).
I also changed the file debian/octave-pfstools.install to reflect the
fact that the path for the *.oct files is now multiarch and contains the
architecture triplet.
Rafael
[1] http://wiki.debian.org/Teams/DebianOctaveGroup
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (700, 'testing'), (650, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u pfstools-1.8.1/debian/octave-pfstools.install
pfstools-1.8.1/debian/octave-pfstools.install
--- pfstools-1.8.1/debian/octave-pfstools.install
+++ pfstools-1.8.1/debian/octave-pfstools.install
@@ -1,3 +1,3 @@
-usr/lib/octave/*
+usr/lib/*/octave/*
usr/share/octave/*
diff -u pfstools-1.8.1/debian/control pfstools-1.8.1/debian/control
--- pfstools-1.8.1/debian/control
+++ pfstools-1.8.1/debian/control
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Debian PhotoTools Maintainers
Uploaders: Sebastian Harl
-Build-Depends: debhelper (>= 5), dpkg-dev (>= 1.14.6), dpatch, gfortran,
autotools-dev, libqt3-mt-dev, libmagick++-dev | libmagick++9-dev, libtiff4-dev,
libopenexr-dev, libnetpbm10-dev, octave3.2-headers, texlive-latex-base,
freeglut3-dev
+Build-Depends: debhelper (>= 5), dpkg-dev (>= 1.14.6), dpatch, gfortran,
autotools-dev, libqt3-mt-dev, libmagick++-dev | libmagick++9-dev, libtiff4-dev,
libopenexr-dev, libnetpbm10-dev, liboctave-dev, texlive-latex-base,
freeglut3-dev
Standards-Version: 3.8.4
Homepage: http://pfstools.sourceforge.net/
Vcs-Git: git://git.debian.org/git/pkg-phototools/pfstools.git
@@ -12,7 +12,7 @@
Package: pfstools
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
-Recommends: pfsglview | pfsview, pfstmo, octave3.2, octave-signal,
octave-pfstools
+Recommends: pfsglview | pfsview, pfstmo, octave, octave-signal, octave-pfstools
Suggests: dcraw, exrtools, imagemagick
Description: command line HDR manipulation programs
pfstools is a set of command line (and two GUI) programs for reading,
@@ -90,7 +90,7 @@
Package: octave-pfstools
Section: math
Architecture: any
-Depends: ${octave:Depends}, ${shlibs:Depends}, ${misc:Depends}
+Depends: octave, ${shlibs:Depends}, ${misc:Depends}
Description: octave bindings for pfstools
PFS is a high-dynamic range (HDR) image format. It is an attempt to integrate
existing file formats by providing a simple data format that can be used to
diff -u pfstools-1.8.1/debian/rules pfstools-1.8.1/debian/rules
--- pfstools-1.8.1/debian/rules
+++ pfstools-1.8.1/debian/rules
@@ -19,7 +19,9 @@
CXXFLAGS += -O2
endif
-include /usr/share/octave/debian/defs.make
+MDIR = $(shell octave-config --print LOCALFCNFILEDIR)
+OCTDIR = $(shell octave-config --print LOCALOCTFILEDIR)
+
include /usr/share/dpatch/dpatch.make
confflags = --host=$(DEB_HOST_GNU_TYPE) \
@@ -114,7 +116,6 @@
dh_makeshlibs
dh_installdeb
dh_shlibdeps -Llibpfs-1.2-0 -ldebian/libpfs-1.2-0/usr/lib/
- octave3.2-depends -poctave-pfstools
dh_gencontrol
dh_md5sums
dh_builddeb
diff -u pfstools-1.8.1/debian/changelog pfstools-1.8.1/debian/chang
Processed: Re: [debian-mysql] Bug#676539: Bug#676539: mysql-server-5.5: migration from /var/run/mysqld to /run/mysqld incomplete
Processing commands for cont...@bugs.debian.org: > tag 676560 -moreinfo Bug #676560 [mysql-server-5.5] mysql-5.5: Serious system breakage as a result of using /run Bug #676539 [mysql-server-5.5] mysql-server-5.5: migration from /var/run/mysqld to /run/mysqld incomplete Removed tag(s) moreinfo. Removed tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 676539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676539 676560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676560 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#667814: marked as done (sudo: Fails to start process with signal 143)
Your message dated Fri, 08 Jun 2012 00:15:27 +0200 with message-id <4fd127ff.4040...@debian.org> and subject line systemd: breaks sudo has caused the Debian Bug report #667470, regarding sudo: Fails to start process with signal 143 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.) -- 667470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sudo Version: 1.8.3p2-1 Severity: grave Justification: renders package unusable Dear Maintainer, since some days, I can not tell exactly when, sudo fails with error status: sudo -D 9 /bin/bash ; echo $? sudo: settings: debug_level=9 sudo: settings: progname=sudo sudo: settings: network_addrs=192.168.178.2/255.255.255.0 192.168.100.1/255.255.255.0 192.168.10.1/255.255.255.0 :::::/::::: :::::/::::: sudo: sudo_mode 1 sudo: policy plugin returns 1 sudo: command info: umask=022 sudo: command info: command=/bin/bash sudo: command info: runas_uid=0 sudo: command info: runas_gid=0 sudo: command info: runas_groups=0 sudo: command info: closefrom=3 sudo: command info: set_utmp=true sudo: received signal 17 sudo: calling policy close with wait status 143 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sudo depends on: ii libc6 2.13-27 ii libpam-modules 1.1.3-7 ii libpam0g1.1.3-7 ii libselinux1 2.1.9-4 sudo recommends no packages. sudo suggests no packages. -- Configuration Files: /etc/sudoers [Errno 13] Permission denied: u'/etc/sudoers' /etc/sudoers.d/README [Errno 13] Permission denied: u'/etc/sudoers.d/README' -- no debconf information --- End Message --- --- Begin Message --- Version: 44-2 Re-add workaround for non-interactive PAM sessions sudo is still broken if pam_loginuid.so is not enabled (which is the default). So re-add the workaround to disable pam_systemd.so for non-interactive sessions. Closes: #667470 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#667495: marked as done (libpam-systemd: sudo does not work anymore after upgrading to 44-1)
Your message dated Fri, 08 Jun 2012 00:15:27 +0200 with message-id <4fd127ff.4040...@debian.org> and subject line systemd: breaks sudo has caused the Debian Bug report #667470, regarding libpam-systemd: sudo does not work anymore after upgrading to 44-1 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.) -- 667470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-systemd Version: 44-1 Severity: important After upgrading from 43-1 (experimental) to 44-1 sudo does not work anymore. It exits immediately with RC=143. There is nothing usable in the logs. berni@schleppi:~$ sudo -s berni@schleppi:~$ sudo su - berni@schleppi:~$ echo $? 143 Removing pam_systemd.so from /etc/pam.d/common-session-noninteractive fixes the issue. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam-systemd depends on: ii libc6 2.13-27 ii libcap2 1:2.22-1 ii libdbus-1-3 1.4.18-1 ii libpam0g1.1.3-7 ii libselinux1 2.1.9-2 ii libsystemd-daemon0 37-1.1 ii systemd 44-1 libpam-systemd recommends no packages. libpam-systemd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 44-2 Re-add workaround for non-interactive PAM sessions sudo is still broken if pam_loginuid.so is not enabled (which is the default). So re-add the workaround to disable pam_systemd.so for non-interactive sessions. Closes: #667470 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#667515: marked as done (libpam-systemd: version 44-1 breaks sudo)
Your message dated Fri, 08 Jun 2012 00:15:27 +0200 with message-id <4fd127ff.4040...@debian.org> and subject line systemd: breaks sudo has caused the Debian Bug report #667470, regarding libpam-systemd: version 44-1 breaks sudo 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.) -- 667470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-systemd Version: 44-1 Severity: normal Hi, since systemd was upgraded to version 44-1, sudo doesn't work on my system any longer. When trying to run a command with sudo, it prints nothing and terminates with an exit status of 143. It works when booting with sysvinit rather than systemd, and it also worked with the older systemd 37-1.1 package. Cheers Matthias -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libpam-systemd depends on: ii libc6 2.13-27 ii libcap2 1:2.22-1 ii libdbus-1-3 1.5.12-1 ii libpam0g1.1.3-7 ii libselinux1 2.1.9-4 ii libsystemd-daemon0 44-1 ii systemd 44-1 libpam-systemd recommends no packages. libpam-systemd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 44-2 Re-add workaround for non-interactive PAM sessions sudo is still broken if pam_loginuid.so is not enabled (which is the default). So re-add the workaround to disable pam_systemd.so for non-interactive sessions. Closes: #667470 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#667470: marked as done (systemd: breaks sudo)
Your message dated Fri, 08 Jun 2012 00:15:27 +0200 with message-id <4fd127ff.4040...@debian.org> and subject line systemd: breaks sudo has caused the Debian Bug report #667470, regarding systemd: breaks sudo 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.) -- 667470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 44-1 Severity: grave After upgrading from 37-1.1, many commands fail with error codes 143 or 129 under sudo, including "sudo bash" or "sudo passwd root", meaning that the problem cannot easily be rectified or circumvented if root logins are disabled. Hence, I'm filing this at RC severity, feel free to downgrade if you cannot reproduce the problem. Attached is the output of "strace -f sudo env" run under root. It shows that sudo was SIGHUP'ed, but I have no idea why that happened. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.3.1-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii dpkg 1.16.2 ii initscripts 2.88dsf-22.1 ii libacl1 2.2.51-5 ii libaudit01:1.7.18-1.1 ii libc62.13-27 ii libcap2 1:2.22-1 ii libcryptsetup4 2:1.4.1-2 ii libdbus-1-3 1.5.12-1 ii libkmod2 6-2 ii liblzma5 5.1.1alpha+20110809-3 ii libpam0g 1.1.3-7 ii libselinux1 2.1.9-4 ii libsystemd-daemon0 44-1 ii libsystemd-id128-0 44-1 ii libsystemd-journal0 44-1 ii libsystemd-login044-1 ii libudev0 175-3.1 ii libwrap0 7.6.q-23 ii udev 175-3.1 ii util-linux 2.20.1-4 Versions of packages systemd recommends: ii libpam-systemd 44-1 Versions of packages systemd suggests: pn python 2.7.2-10 pn systemd-gui -- no debconf information sudo_env.gz Description: strace of "sudo env" --- End Message --- --- Begin Message --- Version: 44-2 Re-add workaround for non-interactive PAM sessions sudo is still broken if pam_loginuid.so is not enabled (which is the default). So re-add the workaround to disable pam_systemd.so for non-interactive sessions. Closes: #667470 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: Re: [debian-mysql] Bug#676539: Bug#676539: mysql-server-5.5: migration from /var/run/mysqld to /run/mysqld incomplete
Processing commands for cont...@bugs.debian.org: > reassign 676560 mysql-server-5.5 Bug #676560 [mysql-5.5] mysql-5.5: Serious system breakage as a result of using /run Bug reassigned from package 'mysql-5.5' to 'mysql-server-5.5'. No longer marked as found in versions 5.5.23-2. Ignoring request to alter fixed versions of bug #676560 to the same values previously set > forcemerge 676560 676539 Bug #676560 [mysql-server-5.5] mysql-5.5: Serious system breakage as a result of using /run Bug #676539 [mysql-server-5.5] mysql-server-5.5: migration from /var/run/mysqld to /run/mysqld incomplete Severity set to 'serious' from 'minor' Bug #676560 [mysql-server-5.5] mysql-5.5: Serious system breakage as a result of using /run Marked as found in versions mysql-5.5/5.5.24+dfsg-2. Added tag(s) moreinfo. Merged 676539 676560 > End of message, stopping processing here. Please contact me if you need assistance. -- 676539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676539 676560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676560 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#666570: marked as done (vala: FTBFS: test failed)
Your message dated Thu, 07 Jun 2012 22:11:02 + with message-id and subject line Bug#665418: Removed package(s) from unstable has caused the Debian Bug report #666570, regarding vala: 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.) -- 666570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vala Version: 0.10.4-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120331 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[5]: Entering directory `/«PKGBUILDDIR»/tests' > TEST: Building...[72G[0;32mOK[m > /basic-types/integers: [72G[0;32mOK[m > /basic-types/floats: [72G[0;32mOK[m > /basic-types/strings: [72G[0;32mOK[m > /basic-types/arrays: [72G[0;32mOK[m > /basic-types/pointers: [72G[0;32mOK[m > /basic-types/bug595751: [72G[0;32mOK[m > /basic-types/bug596637: [72G[0;32mOK[m > /basic-types/bug596785: [72G[0;32mOK[m > /namespaces: [72G[0;32mOK[m > /methods/lambda: [72G[0;32mOK[m > /methods/closures: [72G[0;32mOK[m > /methods/bug595538: [72G[0;32mOK[m > /methods/bug596726: [72G[0;32mOK[m > /methods/bug597426: [72G[0;32mOK[m > /methods/bug598738: [72G[0;32mOK[m > /methods/bug599892: [72G[0;32mOK[m > /methods/bug613483: [72G[0;32mOK[m > /methods/bug620673: [72G[0;32mOK[m > /control-flow/break: [72G[0;32mOK[m > /control-flow/expressions-conditional: [72G[0;32mOK[m > /control-flow/for: [72G[0;32mOK[m > /control-flow/foreach: [72G[0;32mOK[m > /control-flow/switch: [72G[0;32mOK[m > /control-flow/sideeffects: [72G[0;32mOK[m > /enums/enums: [72G[0;32mOK[m > /structs/structs: [72G[0;32mOK[m > /structs/gvalue: [72G[0;32mOK[m > /structs/bug530605: [72G[0;32mOK[m > /structs/bug583603: [72G[0;32mOK[m > /structs/bug595587: [72G[0;32mOK[m > /structs/bug606202: [72G[0;32mOK[m > /structs/bug613513: [72G[0;32mOK[m > /structs/bug613825: [72G[0;32mOK[m > /structs/bug622422: [72G[0;32mOK[m > /delegates/delegates: [72G[0;32mOK[m > /delegates/bug595610: [72G[0;32mOK[m > /delegates/bug595639: [72G[0;32mOK[m > /objects/classes: [72G[0;32mOK[m > /objects/fields: [72G[0;32mOK[m > /objects/interfaces: [72G[0;32mOK[m > /objects/methods: [72G[0;32mOK[m > /objects/properties: [72G[0;32mOK[m > /objects/regex: [72G[0;32mOK[m > /objects/signals: [72G[0;32mOK[m > /objects/test-025: [72G[0;32mOK[m > /objects/test-026: [72G[0;32mOK[m > /objects/test-029: [72G[0;32mOK[m > /objects/test-034: [72G[0;32mOK[m > /objects/bug566909: [72G[0;32mOK[m > /objects/bug593260: [72G[0;32mOK[m > /objects/bug596621: [72G[0;32mOK[m > /objects/bug597155: [72G[0;32mOK[m > /objects/bug597161: [72G[0;32mOK[m > /objects/bug613486: [72G[0;32mOK[m > /objects/bug620706: [72G[0;32mOK[m > /errors/errors: [72G[0;32mOK[m > /errors/bug567181: [72G[0;32mOK[m > /errors/bug579101: [72G[0;32mOK[m > /errors/bug596228: [72G[0;32mOK[m > /errors/bug623049: [72G[0;32mOK[m > /asynchronous/bug595735: [72G[0;32mOK[m > /asynchronous/bug595755: [72G[0;32mOK[m > /asynchronous/bug596177: [72G[0;32mOK[m > /asynchronous/bug597294: [72G[0;32mOK[m > /asynchronous/bug598677: [72G[0;32mOK[m > /asynchronous/bug598697: [72G[0;32mOK[m > /asynchronous/bug598698: [72G[0;32mOK[m > /asynchronous/bug599568: [72G[0;32mOK[m > /asynchronous/bug600827: [72G[0;32mOK[m > /asynchronous/bug601558: [72G[0;32mOK[m > /asynchronous/bug613484: [72G[0;32mOK[m > /asynchronous/bug620740: [72G[0;32mOK[m > /dbus/basic-types/server: [72G[0;32mOK[m > /dbus/arrays/server: [72G[0;32mOK[m > /dbus/structs/server: [72G[0;32mOK[m > /dbus/async/server: [72G[0;31mFAIL[m > > (process:10181): GLib-CRITICAL **: g_variant_unref: assertion > `value->ref_count > 0' failed > dbus.async.server.check: line 4: 10181 Trace/breakpoint trap ./test > /dbus/async/server > > ** (process:10183): CRITICAL **: file /«PKGBUILDDIR»/tests/_test/main.c: line > 19742: uncaught error: The connection is closed (g-io-error-quark, 18) > /dbus/signals/server: [72G[0;32mOK[m > /dbus/bug596862: [72G[0;32mOK[m > /dbus/bug602003/server: [72G[0;32mOK[m > 1 of 79 tests failed > make[5]: *** [check-TESTS] Error 1 The full build log is avail
Bug#675183: sitplus: diff for NMU version 1.0.3-2.1
On 7 June 2012 18:44, Andreas Tille wrote: > Hi Tim, > > many thanks for your fix. Would you be so kind to commit your change to > the Git repository? Every DD has commit permissions to Debian Med Vcs. > Just tell me if you do not feel able to do so and I will inject your > changes. Hey Andreas! I've committed my changes... I've left the upload in the delayed queue for now, though. Kind regards, -- Tim Retout -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: [debian-mysql] Bug#676539: Bug#676539: mysql-server-5.5: migration from /var/run/mysqld to /run/mysqld incomplete
Processing commands for cont...@bugs.debian.org:
> forcemerge 676560 676539
Bug #676560 [mysql-5.5] mysql-5.5: Serious system breakage as a result of using
/run
Unable to merge bugs because:
package of #676539 is 'mysql-server-5.5' not 'mysql-5.5'
Failed to forcibly merge 676560: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x24306b8)',
'requester', 'Nicholas Bamber ', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid', '<4fd12452.2090...@periapt.co.uk>',
'request_subject', ...) called at /usr/lib/debbugs/service line 887
eval {...} called at /usr/lib/debbugs/service line 886
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
676539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676539
676560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676560
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#666307: (no subject)
On Thu, Jun 7, 2012 at 4:21 PM, Artur Rona wrote: > > I'm not sure whether do I want to adopt this one. Since 1.17 upstream > tarball is not clear, e.g. there are no pic directory (including all .png > files) which makes htp a bit ugly. I've sent a question to upstream, though. > > Could you please then orphan a package? Here it is: http://bugs.debian.org/676574 Thanks for the heads up. Diego -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676090: marked as done (liblockfile-ruby: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- ftools (LoadError))
Your message dated Thu, 07 Jun 2012 21:41:17 + with message-id and subject line Bug#675721: Removed package(s) from unstable has caused the Debian Bug report #676090, regarding liblockfile-ruby: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- ftools (LoadError) 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.) -- 676090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: liblockfile-ruby Version: 1.4.3-2.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120604 qa-ftbfs User: debian-r...@lists.debian.org Usertags: default19 Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > fakeroot debian/rules binary > dh install >dh_testroot >dh_prep >dh_installdirs >dh_auto_install >dh_install >dh_installdocs >dh_installchangelogs >dh_installexamples >dh_installman >dh_installcatalogs >dh_installcron >dh_installdebconf >dh_installemacsen >dh_installifupdown >dh_installinfo >dh_installinit >dh_installmenu >dh_installmime >dh_installmodules >dh_installlogcheck >dh_installlogrotate >dh_installpam >dh_installppp >dh_installudev >dh_installwm >dh_installxfonts >dh_installgsettings >dh_bugfiles >dh_ucf >dh_lintian >dh_gconf >dh_icons >dh_perl >dh_usrlocal >dh_link >dh_compress >dh_fixperms > ruby install.rb \ > --libdir `pwd`/debian/`dh_listpackages`/usr/lib/ruby/1.8 \ > --bindir `pwd`/debian/`dh_listpackages`/usr/bin > /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load > such file -- ftools (LoadError) > from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' > from install.rb:4:in `' > make: *** [install-stamp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/04/liblockfile-ruby_1.4.3-2.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Version: 1.4.3-2.1+rm Dear submitter, as the package liblockfile-ruby has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/675721 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain) --- End Message ---
Processed: tagging 675621
Processing commands for cont...@bugs.debian.org: > tags 675621 + moreinfo Bug #675621 [src:linux-2.6] base: system freeze after safely unmounting usb drive Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 675621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675621 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#675621: system freeze after safely unmounting usb drive
On Tue, Jun 05, 2012 at 09:05:42AM +0200, Rik Theys wrote: > reassign 675621 linux-2.6 > thanks > > Hi, > > I have seen similar crashes with the 6.0.x kernel on some of our > systems. Unfortunately the systems are in a remote location and I > was unable to capture any crash screens. [...] This sounds somewhat the bug fixed by: commit 8354a9e00afb022f6b508bd7d6bd74daebb8b751 Author: James Bottomley Date: Wed May 25 15:52:14 2011 -0500 Fix oops caused by queue refcounting failure commit e73e079bf128d68284efedeba1fbbc18d78610f9 upstream. or possibly: commit 5e4c1dbf52bc1ff33782266332a62151d5b5f0be Author: James Bottomley Date: Wed May 18 16:20:10 2011 +0200 block: add proper state guards to __elv_next_request commit 0a58e077eb600d1efd7e54ad9926a75a39d7f8ae upstream. But we've had those since linux-2.6 version 2.6.32-36 (Debian release 6.0.3). So unless Sebastien has somehow failed to upgrade then this must be something different. We're really going to need a kernel log in order to make any progress on this. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: retitle 663293 to Please port to more recent vala versions, severity of 663293 is serious
Processing commands for cont...@bugs.debian.org: > retitle 663293 Please port to more recent vala versions Bug #663293 [src:avant-window-navigator] avant-window-navigator: upcoming vala 0.10 removal Changed Bug title to 'Please port to more recent vala versions' from 'avant-window-navigator: upcoming vala 0.10 removal' > severity 663293 serious Bug #663293 [src:avant-window-navigator] Please port to more recent vala versions Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 663293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663293 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#666307: (no subject)
W dniu 2012-06-07 23:11, Diego Escalante Urrelo pisze: Hi Artur, Since a long time now htp was in the to-be-removed list and just a few days ago I got an email that it had been officially removed from testing. Considering that I don't use it anymore and that popcon always says there are -1 users... I don't know if it is worth further maintaining. That said, feel free to take over the package if you use htp or have an interest in maintaining it. Thanks for the email :-) Diego I'm not sure whether do I want to adopt this one. Since 1.17 upstream tarball is not clear, e.g. there are no pic directory (including all .png files) which makes htp a bit ugly. I've sent a question to upstream, though. Could you please then orphan a package? -- Pozdrawiam / Kind regards, Artur Rona -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676353: marked as done (jnr-netdb: missing --java-lib in POM file)
Your message dated Thu, 07 Jun 2012 21:22:54 + with message-id and subject line Bug#676353: fixed in jnr-netdb 1.0.3-2 has caused the Debian Bug report #676353, regarding jnr-netdb: missing --java-lib in POM file 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.) -- 676353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jnr-netdb Version: 1.0.3-1 Severity: serious Tags: patch Hello, Your package causes other packages as jruby to fail to build from source as newer maven-debian-helper changes, prevent your package to install symlinks in /usr/share/java directory. Adding --java-lib option in your POM files should fix the issue. Regards -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Source: jnr-netdb Source-Version: 1.0.3-2 We believe that the bug you reported is fixed in the latest version of jnr-netdb, which is due to be installed in the Debian FTP archive: jnr-netdb_1.0.3-2.debian.tar.gz to main/j/jnr-netdb/jnr-netdb_1.0.3-2.debian.tar.gz jnr-netdb_1.0.3-2.dsc to main/j/jnr-netdb/jnr-netdb_1.0.3-2.dsc libjnr-netdb-java-doc_1.0.3-2_all.deb to main/j/jnr-netdb/libjnr-netdb-java-doc_1.0.3-2_all.deb libjnr-netdb-java_1.0.3-2_all.deb to main/j/jnr-netdb/libjnr-netdb-java_1.0.3-2_all.deb 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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Miguel Landaeta (supplier of updated jnr-netdb 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, 07 Jun 2012 19:55:24 -0430 Source: jnr-netdb Binary: libjnr-netdb-java libjnr-netdb-java-doc Architecture: source all Version: 1.0.3-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers Changed-By: Miguel Landaeta Description: libjnr-netdb-java - Lookup TCP and UDP services from java libjnr-netdb-java-doc - Documentation for jnr-netdb Closes: 676353 Changes: jnr-netdb (1.0.3-2) unstable; urgency=low . * Team upload. * Add --java-lib flag to install jars in /usr/share/java directory. (Closes: #676353). * Bump Standards-Version to 3.9.3. No changes were required. * Fix lintian warning with copyright file. Checksums-Sha1: da2ce2c48af3f689ceaabe0bd4d718694df7d763 2179 jnr-netdb_1.0.3-2.dsc 8c60c01e7792b393481d8cffb893d2f6cc303525 3847 jnr-netdb_1.0.3-2.debian.tar.gz 41c7dbd8e39fc59da6e349073f8d0186d349d58a 52736 libjnr-netdb-java_1.0.3-2_all.deb e8174d054ac8204ca8efcf23c7d02c62cf56651f 36608 libjnr-netdb-java-doc_1.0.3-2_all.deb Checksums-Sha256: d80a347e812a8f06f643e0a860abb949f0518a0461890f3b7287602156970108 2179 jnr-netdb_1.0.3-2.dsc 86455d5b87cafafef5ef86d75b3935e7b1d54ddf4b3ef7c6a34bcf07c73574fd 3847 jnr-netdb_1.0.3-2.debian.tar.gz 1e98a8e4dda9a15700de9041331db275a21732ecfda73cbe65347b4181614e6a 52736 libjnr-netdb-java_1.0.3-2_all.deb aa64b27c3c83126d81802a22409148fbd74a0feadb4b02bec9b55acc4cb0de20 36608 libjnr-netdb-java-doc_1.0.3-2_all.deb Files: 173df60da49ab7e0c5340dc982032bea 2179 java optional jnr-netdb_1.0.3-2.dsc f5bb59061d887616f64d6fd53349f7ac 3847 java optional jnr-netdb_1.0.3-2.debian.tar.gz 29726cbf94bf878d509d08ccd0956689 52736 java optional libjnr-netdb-java_1.0.3-2_all.deb ddceb50cca6ddeebdfe9095302b15e84 36608 doc optional libjnr-netdb-java-doc_1.0.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJP0RlbAAoJECHSBYmXSz6W8S8P+QFuU4dxfTL/gF0i11/YZ+HF Axh60u5UCHGWjX+OueuLginMQ3lxT03yIHhMD/jlcznWhFsmaD7S9F3nkaa3uaRC 2wAuORHkrP4HDzdcO6cvxFbfyH4vPiz8BKz3Cy7k0GnR2kpSHvLSzZCrYnJ8Zxxp lBpOvjlu0V/Vo57YFnns/UaZJBBUF7An848Q0cYmN3rNmepHbC46gr30SO6RmVCx 2tdIVIXx2zavxj+rAoIy/UNISs7umZOZguOz1n8Jop6ZsnS/6IvPjATODZSeMRNo HmxehVzSyEyLUBE1TBwgqbgdop9q5Kod/YNLqm5auxog+kuE89Z5it+3Db8X8o+6 ZnYxqDvbuMrPUVvVaGZgOgAyp7jRQP0nkC0//0DPmJKOpwLJ+BCo1MKXr/bfRswK VWyabLa4jj1YdCS9n2f7OB5A7yExmrZ
Bug#669949: sysvinit: Break X11: no more mouse and keyboard
On Thu, Jun 07, 2012 at 10:45:44PM +0200, Jakub Moc wrote: > Definitely caused by /run -> /var/run symlink here. After getting rid > of that and creating /run dir in /, I have my keyboard, mouse and > sound back. Extremely weird bug, also only got this recently, been > running unstable for quite a while on LMDE. Thanks all for investigating. It looks like we need to cater for the directory and symlink being the wrong way around, and to rectify that if possible. Other than for chroots, where we don't have a choice, and no means to effectively upgrade to the correct configuration, this has never been an officially supported configuration. Regards, Roger -- .''`. 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#674844: marked as done (figlet: non-distributable files)
Your message dated Thu, 07 Jun 2012 21:17:36 +
with message-id
and subject line Bug#674844: fixed in figlet 2.2.5-1
has caused the Debian Bug report #674844,
regarding figlet: non-distributable files
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.)
--
674844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: figlet
Version: 2.2.2-1
Severity: serious
Bart Martens writes:
> The package contains material that must not be distributed. One example is
> that the file fonts/8859-3.flc contains a license contains a license which
> "specifically excludes the right to re-distribute".
Filing a bug to keep track of this. Note that this also affect Squeeze
and archives for Lenny.
Ansgar
--- End Message ---
--- Begin Message ---
Source: figlet
Source-Version: 2.2.5-1
We believe that the bug you reported is fixed in the latest version of
figlet, which is due to be installed in the Debian FTP archive:
figlet_2.2.5-1.debian.tar.gz
to main/f/figlet/figlet_2.2.5-1.debian.tar.gz
figlet_2.2.5-1.dsc
to main/f/figlet/figlet_2.2.5-1.dsc
figlet_2.2.5-1_amd64.deb
to main/f/figlet/figlet_2.2.5-1_amd64.deb
figlet_2.2.5.orig.tar.gz
to main/f/figlet/figlet_2.2.5.orig.tar.gz
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 674...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonathan McCrohan (supplier of updated figlet 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: Sat, 02 Jun 2012 00:35:22 +0100
Source: figlet
Binary: figlet
Architecture: source amd64
Version: 2.2.5-1
Distribution: unstable
Urgency: low
Maintainer: Carlos Laviola
Changed-By: Jonathan McCrohan
Description:
figlet - Make large character ASCII banners out of ordinary text
Closes: 150174 403665 436302 530082 557254 617422 672320 674844
Changes:
figlet (2.2.5-1) unstable; urgency=low
.
* New upstream release. (closes: #674844) (closes: #617422) (closes: #150174)
- figlet has been relicensed as BSD. All undistributable files have either
been relicenced, or replaced with properly licenced alternatives; figlet
can re-enter the archive, and can move back to main from non-free. \o/
- Drop 2.2.2-1 patches, applied upstream
- New upstream makefile does not support setting variables from
debian/rules; Added makefile_set_debian_{buildflags,paths}.patch
accordingly.
* Improve packaging
- Update S-V to 3.9.3
- Bump Debhelper to v9
- Switch to dpkg-source 3.0 (quilt) format
- Switch to dh-style debian/rules (closes: #672320)
- Various lintian fixes
- Update package description (closes: #557254)
- Update debian/copyright (closes: #436302)
- Fix moolets bashism (closes: #530082)
- Move figlet manpage to alternatives system (closes: #403665)
- Add watchfile
- Add Homepage to debian/control
- Remove references to deprecated figfonts(-cjk) packages
- Remove local copies of man pages (merged upstream)
* Add myself as co-maintainer
Checksums-Sha1:
03ebcab5f952f6a6f6b2a7bb172581f13c8d2bfb 1080 figlet_2.2.5-1.dsc
dda696958c161bd71d6590152c94c4f705415727 233201 figlet_2.2.5.orig.tar.gz
3ca70303091bf5d865d3c6502e7a96f12dd32a76 7595 figlet_2.2.5-1.debian.tar.gz
4f00128b7075d1c219dd632469a4024873329145 187356 figlet_2.2.5-1_amd64.deb
Checksums-Sha256:
6e9e7823f8621b7d551d497e36a74284ad39d560ba5e893b787ca7d373a8d2fc 1080
figlet_2.2.5-1.dsc
bf88c40fd0f077dab2712f54f8d39ac952e4e9f2e1882f1195be9e5e4257417d 233201
figlet_2.2.5.orig.tar.gz
4890a49eba647abb63e121a0f8b655214ff1eab9326b244933fec0abdfe49c04 7595
figlet_2.2.5-1.debian.tar.gz
f669555a577de268fbf46fca74cdd74ba7ac7fbd6e2e29414308a2350154fbc7 187356
figlet_2.2.5-1_amd64.deb
Files:
0602ec456d05e2fbc6c8c47dadd3ef39 1080 text optional figlet_2.2.5-1.dsc
d88cb33a14f1469fff975d021ae2858e 233201 text optional figlet_2.2.5.orig.tar.gz
16e1d8d9c0d4e3003e1f6abe18263e82 7595 text optional
figlet_2.2.5-1.debian.tar.gz
08a7b038e33e53c37b84e4a2bd914c1e 187356 text optional figlet_2.2.5-1_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iD8DBQFPz7Y8ZAYCJz
Bug#666307: (no subject)
Hi Artur, On Thu, Jun 7, 2012 at 10:35 AM, Artur Rona wrote: > Hello maintainers, > > I've working a bit on this bug and I concluded upgrade to 1.17 fixes FTBFS > (including refreshed patches etc.). If you want to fix it, let's upgrade it. > If you don't have time, I'm going to go on with NMU. Since a long time now htp was in the to-be-removed list and just a few days ago I got an email that it had been officially removed from testing. Considering that I don't use it anymore and that popcon always says there are -1 users... I don't know if it is worth further maintaining. That said, feel free to take over the package if you use htp or have an interest in maintaining it. Thanks for the email :-) Diego -- 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#676430: kmymoney: Please update build-deps to libaqbanking34-dev
Processing commands for cont...@bugs.debian.org: > severity 676430 serious Bug #676430 [src:kmymoney] kmymoney: Please update build-deps to libaqbanking34-dev Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 676430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676430 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#671979: (no subject)
W dniu 2012-06-07 22:02, Nikos Chantziaras pisze: qtads.pro uses qmake's support for pkg-config and never calls it directly. pkg-config support is shipped with Qt in "mkspecs/features/link_pkgconfig.prf". It assumes pkg-config is present on the system. Maybe in theory. In practise, pbuilder gives FTBFS in result. BTW, can you please upgrade qtads to 2.1.3? -- Pozdrawiam / Kind regards, Artur Rona -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676432: marked as done (wine-bin: fails to upgrade: update-alternatives: error: alternative link /usr/share/man/de.UTF-8/man1/wine.1.gz is already managed by wine.1.de.UTF-8.gz (slave of wine).)
Your message dated Thu, 07 Jun 2012 20:59:10 + with message-id and subject line Bug#676320: fixed in wine 1.4-4 has caused the Debian Bug report #676320, regarding wine-bin: fails to upgrade: update-alternatives: error: alternative link /usr/share/man/de.UTF-8/man1/wine.1.gz is already managed by wine.1.de.UTF-8.gz (slave of wine). 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.) -- 676320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wine-bin Version: 1.4-3 Severity: serious Justification: fails to upgrade Hi Wine Maintainers, during upgrade to 1.4-3 on Sid the following happens: Setting up wine-bin (1.4-3) ... update-alternatives: error: alternative link /usr/share/man/de.UTF-8/man1/wine.1.gz is already managed by wine.1.de.UTF-8.gz (slave of wine). dpkg: error processing wine-bin (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of wine: wine depends on wine-bin (= 1.4-3); however: Package wine-bin is not configured yet. dpkg: error processing wine (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: wine-bin wine -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'experimental'), (400, 'testing'), (300, 'stable') Architecture: i386 (x86_64) Kernel: Linux 3.3.0-trunk-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wine-bin depends on: ii libc6 2.13-33 ii libwine-bin1.4-3 ii libwine-gecko-1.4 1.4+dfsg-1 ii x11-utils 7.7~1 ii xbase-clients 1:7.6+13 wine-bin recommends no packages. Versions of packages wine-bin suggests: ii libwine-gl 1.4-3 ii libwine-print 1.4-3 Versions of packages libwine depends on: ii debconf [debconf-2.0] 1.5.43 ii libc6 2.13-33 ii libfreetype6 2.4.9-1 ii libhal10.5.14-8 ii libice62:1.0.8-2 ii libjpeg8 8d-1 ii libmpg123-01.14.2-1 ii libpng12-0 1.2.49-1 ii libsm6 2:1.2.1-2 ii libssl1.0.01.0.1c-1 ii libx11-6 2:1.4.99.901-2 ii libxcursor11:1.1.13-1 ii libxext6 2:1.3.1-2 ii libxi6 2:1.6.1-1 ii libxinerama1 2:1.1.2-1 ii libxml22.8.0+dfsg1-3 ii libxrandr2 2:1.3.2-2 ii libxrender11:0.9.7-1 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages libwine recommends: ii fonts-liberation [ttf-liberation] 1.07.2-2 ii libgsm11.0.13-4 ii libwine-alsa 1.4-3 ii libwine-gl 1.4-3 ii ttf-liberation 1.07.2-2 Versions of packages libwine suggests: ii libwine-cms 1.4-3 ii libwine-gphoto2 1.4-3 ii libwine-ldap 1.4-3 ii libwine-openal 1.4-3 ii libwine-print1.4-3 ii libwine-sane 1.4-3 ii wine-doc 1.0.0-1 -- no debconf information --- End Message --- --- Begin Message --- Source: wine Source-Version: 1.4-4 We believe that the bug you reported is fixed in the latest version of wine, which is due to be installed in the Debian FTP archive: wine_1.4-4.diff.gz to main/w/wine/wine_1.4-4.diff.gz wine_1.4-4.dsc to main/w/wine/wine_1.4-4.dsc wine_1.4-4_amd64.deb to main/w/wine/wine_1.4-4_amd64.deb 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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated wine 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, 07 Jun 2012 15:53:06 -0400 Source: wine Binary: wine wine-bin libwine-dbg libwine-dev libwine libwine-alsa libwine-bin libwine-capi libwine-cms libwine-gl libwine-gphoto2 libwine-ldap libwine-openal libwine-oss libwine-print libwine-sane Architecture: source amd64 Version: 1.4-4 Distribution: unstable Urgency: low Maintainer: Debian Wine Party Changed-By:
Bug#676457: marked as done (wine: uninstallable on amd64, missing wine-bin)
Your message dated Thu, 07 Jun 2012 20:59:10 + with message-id and subject line Bug#676457: fixed in wine 1.4-4 has caused the Debian Bug report #676457, regarding wine: uninstallable on amd64, missing wine-bin 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.) -- 676457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wine Version: 1.4-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, wine-bin is missing on amd64, making wine uninstallable. Package: wine Version: 1.4-3 Architecture: amd64 Depends: wine-bin (= 1.4-3) $ rmadison wine wine | 1.0.1-1 | lenny| source, amd64, i386 wine | 1.0.1-3.1 | squeeze | source, amd64, i386 wine | 1.2.3-0.3 | wheezy | source, amd64, i386, kfreebsd-i386 wine | 1.2.3-0.3 | sid | source wine | 1.4-0.3 | experimental | source, kfreebsd-i386 wine | 1.4-0.4 | experimental | source, amd64, i386, powerpc wine | 1.4-3 | sid | source, amd64, i386, kfreebsd-amd64, kfreebsd-i386, powerpc $ rmadison wine-bin wine-bin | 1.0.1-1 | lenny| amd64, i386 wine-bin | 1.0.1-3.1 | squeeze | amd64, i386 wine-bin | 1.2.3-0.3 | wheezy | amd64, i386, kfreebsd-i386 wine-bin | 1.2.3-0.3 | sid | amd64 wine-bin | 1.4-0.3 | experimental | amd64, kfreebsd-i386 wine-bin | 1.4-0.4 | experimental | i386, powerpc wine-bin | 1.4-3 | sid | i386, kfreebsd-i386, powerpc Without being installable, I don't think this package may migrate to testing. Andreas --- End Message --- --- Begin Message --- Source: wine Source-Version: 1.4-4 We believe that the bug you reported is fixed in the latest version of wine, which is due to be installed in the Debian FTP archive: wine_1.4-4.diff.gz to main/w/wine/wine_1.4-4.diff.gz wine_1.4-4.dsc to main/w/wine/wine_1.4-4.dsc wine_1.4-4_amd64.deb to main/w/wine/wine_1.4-4_amd64.deb 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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated wine 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, 07 Jun 2012 15:53:06 -0400 Source: wine Binary: wine wine-bin libwine-dbg libwine-dev libwine libwine-alsa libwine-bin libwine-capi libwine-cms libwine-gl libwine-gphoto2 libwine-ldap libwine-openal libwine-oss libwine-print libwine-sane Architecture: source amd64 Version: 1.4-4 Distribution: unstable Urgency: low Maintainer: Debian Wine Party Changed-By: Michael Gilbert Description: libwine- Windows API implementation - library libwine-alsa - Windows API implementation - ALSA sound module libwine-bin - Windows API implementation - system services libwine-capi - Windows API implementation - ISDN module libwine-cms - Windows API implementation - color management module libwine-dbg - Windows API implementation - debugging symbols libwine-dev - Windows API implementation - development files libwine-gl - Windows API implementation - OpenGL module libwine-gphoto2 - Windows API implementation - camera module libwine-ldap - Windows API implementation - LDAP module libwine-openal - Windows API implementation - OpenAL module libwine-oss - Windows API implementation - OSS sound module libwine-print - Windows API implementation - printing module libwine-sane - Windows API implementation - scanner module wine - Windows API implementation - standard suite wine-bin - Windows API implementation - binary loader Closes: 676320 676457 Changes: wine (1.4-4) unstable; urgency=low . * Fix manpage alternatives (closes: #676320) * Make multiarch wine binnmu safe (closes: #676457) * Install additional wine exe files * Install upstream manpages where available Checksums-Sha1: e38aaa17e94e2af11af10a22060a1e115e7cec3b 4630 wine_1.4-4.dsc 081b177999c902442ac9174c3a963efbd584b432 69670 wine_1.4-4.diff.gz 7f54c53d8eeaf6d3e2806b068dcde14bf88e7007 938 wine_1.4-4_amd64.deb Checksums-Sha256: a03ae39917b3bb803471c907c457f66438ae8839acc2f8d7ef38d18e0e1688bb 4630 wine_1.4-4.dsc 206c639f434bff90492e198f8c7e495653b2c618d0512c228915f3
Bug#676320: marked as done (wine-bin: update-alternatives: error: unknown argument `/usr/share/man/*/man1/wine32.1.gz')
Your message dated Thu, 07 Jun 2012 20:59:10 + with message-id and subject line Bug#676320: fixed in wine 1.4-4 has caused the Debian Bug report #676320, regarding wine-bin: update-alternatives: error: unknown argument `/usr/share/man/*/man1/wine32.1.gz' 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.) -- 676320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wine-bin Version: 1.4-3 Severity: serious Your package fails to configure: , | Setting up wine-bin (1.4-3) ... | update-alternatives: error: unknown argument `/usr/share/man/*/man1/wine32.1.gz' | dpkg: error processing wine-bin (--configure): | subprocess installed post-installation script returned error exit status 2 | Errors were encountered while processing: | wine-bin ` -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.4.1-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wine-bin depends on: ii libc6 2.13-33 ii libwine-bin1.4-3 ii libwine-gecko-1.4 1.4+dfsg-1 ii x11-utils 7.7~1 wine-bin recommends no packages. Versions of packages wine-bin suggests: pn libwine-gl 1.4-3 pn libwine-print Versions of packages libwine depends on: ii debconf [debconf-2.0] 1.5.43 ii libc6 2.13-33 ii libfreetype6 2.4.2-2.1+squeeze4 ii libhal10.5.14-8 ii libice62:1.0.8-2 ii libjpeg8 8d-1 ii libmpg123-01.14.2-1 ii libpng12-0 1.2.49-1 ii libsm6 2:1.2.1-2 ii libssl1.0.01.0.1c-1 ii libx11-6 2:1.4.99.901-2 ii libxcursor11:1.1.13-1 ii libxext6 2:1.3.1-2 ii libxi6 2:1.6.1-1 ii libxinerama1 2:1.1.2-1 ii libxml22.8.0+dfsg1-3 ii libxrandr2 2:1.3.2-2 ii libxrender11:0.9.7-1 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages libwine recommends: ii fonts-liberation [ttf-liberation] 1.07.2-2 ii libgsm11.0.13-4 ii libwine-alsa 1.4-3 ii libwine-gl 1.4-3 Versions of packages libwine suggests: ii libwine-cms ii libwine-gphoto2 ii libwine-ldap ii libwine-openal ii libwine-print ii libwine-sane ii wine-doc 1.0.0-1 -- no debconf information --- End Message --- --- Begin Message --- Source: wine Source-Version: 1.4-4 We believe that the bug you reported is fixed in the latest version of wine, which is due to be installed in the Debian FTP archive: wine_1.4-4.diff.gz to main/w/wine/wine_1.4-4.diff.gz wine_1.4-4.dsc to main/w/wine/wine_1.4-4.dsc wine_1.4-4_amd64.deb to main/w/wine/wine_1.4-4_amd64.deb 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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated wine 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, 07 Jun 2012 15:53:06 -0400 Source: wine Binary: wine wine-bin libwine-dbg libwine-dev libwine libwine-alsa libwine-bin libwine-capi libwine-cms libwine-gl libwine-gphoto2 libwine-ldap libwine-openal libwine-oss libwine-print libwine-sane Architecture: source amd64 Version: 1.4-4 Distribution: unstable Urgency: low Maintainer: Debian Wine Party Changed-By: Michael Gilbert Description: libwine- Windows API implementation - library libwine-alsa - Windows API implementation - ALSA sound module libwine-bin - Windows API implementation - system services libwine-capi - Windows API implementation - ISDN module libwine-cms - Windows API implementation - color management module libwine-dbg - Windows API implementation - debugging symbols libwine-dev - Windows API implementation - development files libwine-gl - Windows API implementation - OpenGL module libwine-gphoto2 - Windows API implementation - camer
Bug#674000: marked as done (python-pyopencl-headers: fails to upgrade from 'testing' - trying to overwrite /usr/include/pyopencl/pyopencl-ranluxcl.cl)
Your message dated Thu, 07 Jun 2012 20:56:47 + with message-id and subject line Bug#674000: fixed in pyopencl 2011.2+git20120517-1 has caused the Debian Bug report #674000, regarding python-pyopencl-headers: fails to upgrade from 'testing' - trying to overwrite /usr/include/pyopencl/pyopencl-ranluxcl.cl 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.) -- 674000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-pyopencl-headers Version: 2011.2+git20120508-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'unstable' fails because it tries to overwrite files that are owned by other packages without declaring a Breaks/Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package python-pyopencl-headers. Unpacking python-pyopencl-headers (from .../python-pyopencl-headers_2011.2+git20120508-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/python-pyopencl-headers_2011.2+git20120508-1_all.deb (--unpack): trying to overwrite '/usr/include/pyopencl/pyopencl-ranluxcl.cl', which is also in package python-pyopencl 2011.2-1 cheers, Andreas python-pyopencl_2011.2+git20120508-1.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: pyopencl Source-Version: 2011.2+git20120517-1 We believe that the bug you reported is fixed in the latest version of pyopencl, which is due to be installed in the Debian FTP archive: pyopencl_2011.2+git20120517-1.debian.tar.gz to contrib/p/pyopencl/pyopencl_2011.2+git20120517-1.debian.tar.gz pyopencl_2011.2+git20120517-1.dsc to contrib/p/pyopencl/pyopencl_2011.2+git20120517-1.dsc pyopencl_2011.2+git20120517.orig.tar.gz to contrib/p/pyopencl/pyopencl_2011.2+git20120517.orig.tar.gz python-pyopencl-doc_2011.2+git20120517-1_all.deb to contrib/p/pyopencl/python-pyopencl-doc_2011.2+git20120517-1_all.deb python-pyopencl-headers_2011.2+git20120517-1_all.deb to contrib/p/pyopencl/python-pyopencl-headers_2011.2+git20120517-1_all.deb python-pyopencl_2011.2+git20120517-1_amd64.deb to contrib/p/pyopencl/python-pyopencl_2011.2+git20120517-1_amd64.deb python-pyopencl_2011.2+git20120517-1_i386.deb to contrib/p/pyopencl/python-pyopencl_2011.2+git20120517-1_i386.deb python3-pyopencl_2011.2+git20120517-1_amd64.deb to contrib/p/pyopencl/python3-pyopencl_2011.2+git20120517-1_amd64.deb python3-pyopencl_2011.2+git20120517-1_i386.deb to contrib/p/pyopencl/python3-pyopencl_2011.2+git20120517-1_i386.deb 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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tomasz Rybak (supplier of updated pyopencl 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: SHA512 Format: 1.8 Date: Tue, 29 May 2012 19:52:40 +0200 Source: pyopencl Binary: python-pyopencl-headers python-pyopencl python3-pyopencl python-pyopencl-doc Architecture: all amd64 i386 source Version: 2011.2+git20120517-1 Distribution: unstable Urgency: low Maintainer: Tomasz Rybak Changed-By: Tomasz Rybak Closes: 673992 674000 Description: python3-pyopencl - Python 3 module to access OpenCL parallel computation API python-pyopencl-doc - module to access OpenCL parallel computation API (documentation) python-pyopencl-headers - headers for Python module to access OpenCL parallel computation A python-pyopencl - Python module to access OpenCL parallel computation API Changes: pyopencl (2011.2+git20120517-1) unstable; urgency=low . * New upstream release. * Call dh_numpy3 in debian/rules for NumPy ABI and ABI dependencies in Python3 module. * Fix copyright for files in src/cl/* * Update debian/compat to 9, update dependencies. * Add Replaces: python-pyopencl to python-pyopencl-headers to avoid problem with updating, and ensure that python-pyopencl and python3-pyopencl always use correct version of python
Bug#669161: gle-graphics: FTBFS on sparc (*** glibc detected *** ../../build/bin/gle: double free or corruption (!prev): 0x70468660 ***)
On Thu, Jun 07, 2012 at 10:26:43PM +0200, Pino Toscano wrote: > reopen 669161 > thanks > > Hi Christian, > > Alle domenica 13 maggio 2012, Christian T. Steigies ha scritto: > > On Tue, Apr 17, 2012 at 10:36:30PM +0200, Julien Cristau wrote: > > > Source: gle-graphics > > > Version: 4.2.4-1 > > > Severity: serious > > > Tags: wheezy sid > > > Justification: fails to build from source (but built successfully > > > in the past) > > > > > > gle-graphics no longer builds on sparc, see e.g. the log at > > > https://buildd.debian.org/status/fetch.php?pkg=gle-graphics&arch=sp > > > arc&ver=4.2.4-1&stamp=1333804744 > > > > I have uploaded a new version of gle-graphics and it fails to build > > with the same problem on sparc: > > > > https://buildd.debian.org/status/fetch.php?pkg=gle-graphics&arch=spar > > c&ver=4.2.4c-1&stamp=1336781297 > > Sorry to reopen this bug, but the problem still persist, and it it's on > the way of the poppler 0.18 transition; see [1] > > [1] > https://buildd.debian.org/status/fetch.php?pkg=gle-graphics&arch=sparc&ver=4.2.4c-2%2Bb1&stamp=1338767008 > > It seems gle-graphics is a leaf package, so in case it could be > temporarly hinted out of testing to make the transition complete soon > (it will reenter once it has been fixed, of course). I think the problem is not gle-graphics but the sparc buildd, I can not reproduce the build failure on the sparc porter box. Can you explain to me why it fails on the buildd, but not on the porter box? Or can you tell me what should be changed in the package? Please try to build it on a different sparc machine, I can successfully build it on smetana.debian.org, and I do not have access to any other sparc machine. My explanation is that the sparc buildd is broken, I have seen that before when I was running m68k buildds. The only other explanation, in case the sparc buildd is not broken, would be that the porter box is broken so that it produces working packages. I think this is less likely. Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676463: sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others
Am Donnerstag, den 07.06.2012, 18:57 +0100 schrieb Roger Leigh: > severity 676463 serious > severity 676520 serious > forcemerge 676463 676520 > thanks > > On Thu, Jun 07, 2012 at 09:09:55AM +0200, Paul Menzel wrote: > > in contrast to earlier versions, with this version installation of > > `sysv-rc` fails when migration to dependency based boot fails. > > Additionally it complains about obsolete init.d scripts of packages > > which were never a problem before and whose init.d scripts do not seem > > to be obsolete. > > Previously, sysv-rc gave you two options: legacy bootordering or > dependency based bootordering. You could keep the broken scripts > and remain with legacy, or you could clean up the scripts and > enable dependency bootordering. > > The change here is that we now require you to migrate to > dependency based bootordering, because we will no longer support > legacy static ordering. Please have a read through the details > in NEWS.Debian: > > +sysv-rc (2.88dsf-23) experimental; urgency=low > + > + Dependency based boot ordering is now required. > + > + Most systems will already be using dependency based boot ordering. > + This includes all squeeze and later releases, unless you have taken > + deliberate action to disable it. Installations upgraded from etch, > + lenny or earlier releases will have enabled dependency based booting > + when upgrading to squeeze and later releases. However, it was > + previously possible to opt out of migrating to dependency based > + booting and retain static boot ordering. This is no longer the case. > + > + If your system is still using static boot ordering, migrating to > + dependency based boot ordering will be performed when sysv-rc is > + configured. If this is not possible for any reason, you will have to > + correct the problem before upgrading can continue. It will not be > + possible to complete the upgrade until insserv is configured. > + > + The most commonly encountered problem preventing migration is the > + presence of obsolete init scripts from removed (but unpurged) > + packages. If this is the case, you will be prompted with > + instructions detailing how to purge these old packages. > + > + If you have custom init scripts, please ensure that these have the > + correct dependency information in an LSB header so that they will be > + run at the correct point in the boot sequence. > + > + -- Roger Leigh Wed, 18 Apr 2012 23:30:37 +0100 > > > sysv-rc (2.88dsf-26) wird eingerichtet ... > > info: Checking if it is safe to convert to dependency based boot. > > > > error: Unable to migrate to dependency based boot sequencing. > > error: Problems detected: package fuse left obsolete init.d script > > behind, package initscripts left obsolete init.d script behind, package > > initscripts left obsolete init.d script behind, package initscripts left > > obsolete init.d script behind, package libchipcard-tools left obsolete > > init.d script behind, package smartmontools left obsolete init.d script > > behind, , package gdm removed but not purged > > > > If this is due to the presence of unpurged obsolete initscripts, > > it is suggested that the following is run to remove them: > > dpkg --purge fuse initscripts initscripts initscripts > > libchipcard-tools smartmontools > > This is wrong; we shouldn't be purging initscripts. Could you possibly > let me know which specific files were left behind which were causing > problems? We should be able to correct this during the upgrade. > > > Also the other init.d scripts are packaged properly. > > Yes. The ones causing problems aren't current ones, they are > obsolete ones left by removed (but not purged) packages. Purging > the packages will remove them, allowing you to continue. As David pointed out in this replies too, the assumptions that the listed packages were removed is incorrect. $ LANG=C aptitude show fuse Package: fuse New: yes State: installed Automatically installed: yes Version: 2.9.0-1 Priority: optional Section: utils Maintainer: Daniel Baumann Architecture: i386 Uncompressed Size: 177 k Depends: libc6 (>= 2.4), libfuse2 (= 2.9.0-1), adduser, mount (>= 2.19.1), sed (>= 4), udev | makedev Conflicts: fuse-utils (< 2.8.5-2~) Breaks: loop-aes-utils (< 2.16.2-3~) Replaces: fuse-utils Description: Filesystem in Userspace Filesystem in Userspace (FUSE) is a simple interface for userspace programs to export a virtual filesystem to the Linux kernel. It also aims to provide a secure method for non privileged users to create and mount their own filesystem implementations. Homepage: http://fuse.sourceforge.net/ This is also true for `initscripts`, `libchipcard-tools` and `smartmontools`. > Ideally, we could do this automatically. I intend to
Bug#669949: sysvinit: Break X11: no more mouse and keyboard
Definitely caused by /run -> /var/run symlink here. After getting rid of that and creating /run dir in /, I have my keyboard, mouse and sound back. Extremely weird bug, also only got this recently, been running unstable for quite a while on LMDE. -- 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#669161: gle-graphics: FTBFS on sparc (*** glibc detected *** ../../build/bin/gle: double free or corruption (!prev): 0x70468660 ***)
Processing commands for cont...@bugs.debian.org:
> reopen 669161
Bug #669161 {Done: c...@debian.org (Christian T. Steigies)} [src:gle-graphics]
gle-graphics: FTBFS on sparc (*** glibc detected *** ../../build/bin/gle:
double free or corruption (!prev): 0x70468660 ***)
'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 gle-graphics/4.2.4c-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
669161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669161
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#669161: gle-graphics: FTBFS on sparc (*** glibc detected *** ../../build/bin/gle: double free or corruption (!prev): 0x70468660 ***)
reopen 669161 thanks Hi Christian, Alle domenica 13 maggio 2012, Christian T. Steigies ha scritto: > On Tue, Apr 17, 2012 at 10:36:30PM +0200, Julien Cristau wrote: > > Source: gle-graphics > > Version: 4.2.4-1 > > Severity: serious > > Tags: wheezy sid > > Justification: fails to build from source (but built successfully > > in the past) > > > > gle-graphics no longer builds on sparc, see e.g. the log at > > https://buildd.debian.org/status/fetch.php?pkg=gle-graphics&arch=sp > > arc&ver=4.2.4-1&stamp=1333804744 > > I have uploaded a new version of gle-graphics and it fails to build > with the same problem on sparc: > > https://buildd.debian.org/status/fetch.php?pkg=gle-graphics&arch=spar > c&ver=4.2.4c-1&stamp=1336781297 Sorry to reopen this bug, but the problem still persist, and it it's on the way of the poppler 0.18 transition; see [1] [1] https://buildd.debian.org/status/fetch.php?pkg=gle-graphics&arch=sparc&ver=4.2.4c-2%2Bb1&stamp=1338767008 It seems gle-graphics is a leaf package, so in case it could be temporarly hinted out of testing to make the transition complete soon (it will reenter once it has been fixed, of course). Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#676553: libreoffice: X11 was crashed some times writer, calc, is running
[ Marcelo, I guess you wanted to tell that Janaina. n...@bugs.debian.org does NOT go to the submitter of bugs. You always need to Cc the right email or nnn-submit...@bugs.debian.org ] Hi, On Thu, Jun 07, 2012 at 05:01:19PM -0300, Marcelo Luiz de Laia wrote: > I got the same in 1:3.5.3-5 [1]. I downgrade to 3.4.6-2 to solve (!) > this problem, but didin't got success. Eh, no? Your cause was crash and takes X with it and it's way, this is - if I understand Janainas intial post right - more like hangs until killed. That's something different. Might have the same cause, but... Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676569: gcc-4.7: -nostdlib broken, multiarch library path always added
Package: gcc-4.7
Version: 4.7.0-12
Severity: serious
Justification: breaks unrelated software
The following scenario is broken: I would expect the link to fail.
This is a carefully nailed-down testcase to figure out that the
fault is with gcc not binutils.
tg@zigo:~ $ echo 'int login_tty(int); void _exit(int); void _start() {
_exit(login_tty(0)); }' >test.c
tg@zigo:~ $ rm -f test.out; gcc -nostdlib -lutil -o test.out test.c; ls -l
test.out
-rwxr-xr-x 1 tg tg 3712 Jun 7 20:09 test.out
Reason behind this is that GNU autoconf generated configure scripts
(and other things like that) use such tests to check whether to add
libraries providing certain functionality to the build. Now if klibc
or dietlibc are used, you don't want to have libraries linked against
eglibc added to the build, as that will eventually fail. Figured this
out while trying to see whether jupp can be built with those libcs.
tg@zigo:~ $ gcc -nostdlib -lutil -o test.out test.c -v 2>&1 | tail -1
/usr/lib/gcc/x86_64-linux-gnu/4.7/collect2 --sysroot=/ --build-id
--no-add-needed --eh-frame-hdr -m elf_x86_64 --hash-style=both -dynamic-linker
/lib64/ld-linux-x86-64.so.2 -o test.out -L/usr/lib/gcc/x86_64-linux-gnu/4.7
-L/usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu
-L/usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib -L/lib/x86_64-linux-gnu
-L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib
-L/usr/lib/gcc/x86_64-linux-gnu/4.7/../../.. -lutil /tmp/ccjpTrCm.o
tg@zigo:~ $ $(gcc -nostdlib -lutil -o test.out test.c -v -save-temps 2>&1 |
tail -1) -t
/usr/bin/ld.bfd.real: mode elf_x86_64
-lutil (/usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/libutil.so)
test.o
Here ^ we see "nicely" how gcc is the culprit adding -L directives,
and that ld uses them at library resolution time.
tg@zigo:~ $ gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc-4.7.real
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.0-12'
--with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs
--enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.7 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object
--enable-plugin --enable-objc-gc --with-arch-32=i586 --with-tune=generic
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.7.0 (Debian 4.7.0-12)
-- System Information:
Debian Release: wheezy/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable'), (500, 'testing'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
m68k
Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh
Versions of packages gcc-4.7 depends on:
ii binutils 2.22-6.1
ii cpp-4.7 4.7.0-12
ii gcc-4.7-base 4.7.0-12
ii libc6 2.13-33
ii libgcc1 1:4.7.0-12
ii libgmp10 2:5.0.5+dfsg-2
ii libgomp1 4.7.0-12
ii libitm1 4.7.0-12
ii libmpc2 0.9-4
ii libmpfr4 3.1.0-5
ii libquadmath0 4.7.0-12
ii zlib1g1:1.2.7.dfsg-11
Versions of packages gcc-4.7 recommends:
ii libc6-dev 2.13-33
Versions of packages gcc-4.7 suggests:
pn binutils-gold
pn gcc-4.7-doc
pn gcc-4.7-locales
pn gcc-4.7-multilib
pn libgcc1-dbg
pn libgomp1-dbg
pn libitm1-dbg
pn libmudflap0-4.7-dev
pn libmudflap0-dbg
pn libquadmath0-dbg
-- 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#676553: libreoffice: X11 was crashed some times writer, calc, is running
I got the same in 1:3.5.3-5 [1]. I downgrade to 3.4.6-2 to solve (!) this problem, but didin't got success. 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675882 -- Marcelo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671979: (no subject)
On 07/06/12 17:27, Daniel Schepler wrote: On Thu, Jun 7, 2012 at 4:49 AM, Artur Rona wrote: tags 671979 + patch thanks Hello, I've prepared small patch to fix this one. Just add pkg-config to Build-Depends. If you (maintainer) don't have a time to upload this one, I'm going to go on with NMU. Sorry I haven't gotten around to looking into it in more detail -- but from the build log I saw, it looks like it's qt4-qmake that should have a Depends on pkg-config. Unless qmake can run on some .pro files without pkg-config present, and qtads.pro calls pkg-config itself... qtads.pro uses qmake's support for pkg-config and never calls it directly. pkg-config support is shipped with Qt in "mkspecs/features/link_pkgconfig.prf". It assumes pkg-config is present on the system. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676566: alacarte broken
Package: alacarte Version: 0.13.4-2 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrade to v. 0.13.4-2, alacarte crashes with the following error Traceback (most recent call last): File "/usr/bin/alacarte", line 37, in main() File "/usr/bin/alacarte", line 34, in main app.run() File "/usr/share/alacarte/Alacarte/MainWindow.py", line 65, in run self.loadMenus() File "/usr/share/alacarte/Alacarte/MainWindow.py", line 204, in loadMenus self.on_menu_tree_cursor_changed(menu_tree) File "/usr/share/alacarte/Alacarte/MainWindow.py", line 355, in on_menu_tree_cursor_changed self.loadItems(self.menu_store[menu_path][2], menu_path) File "/usr/share/alacarte/Alacarte/MainWindow.py", line 218, in loadItems for item, show in self.editor.getItems(menu): File "/usr/share/alacarte/Alacarte/MenuEditor.py", line 147, in getItems item = item_iter.get_separator() AttributeError: 'TreeIter' object has no attribute 'get_separator' Thanks for all, Domenico -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages alacarte depends on: ii gir1.2-gdkpixbuf-2.0 2.26.1-1 ii gir1.2-glib-2.0 1.32.1-1 ii gir1.2-gmenu-3.0 3.4.2-1 ii gir1.2-gtk-3.03.4.2-1 ii python2.7.3~rc2-1 Versions of packages alacarte recommends: ii gnome-panel 3.4.2.1-2 alacarte 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: severity of 672749 is important
Processing commands for cont...@bugs.debian.org: > # out of date binaries removed > severity 672749 important Bug #672749 [src:rquantlib] rquantlib: ftbfs on armel/armhf Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 672749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672749 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: severity of 672750 is important
Processing commands for cont...@bugs.debian.org: > # out of date binary removed > severity 672750 important Bug #672750 [src:quantlib-swig] quantlib-swig: ftbfs on s390 (virtual memory exhausted) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 672750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672750 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#668669: marked as done (brltty: FTBFS[kfreebsd]:)
Your message dated Thu, 07 Jun 2012 19:47:22 + with message-id and subject line Bug#668669: fixed in brltty 4.4-1 has caused the Debian Bug report #668669, regarding brltty: FTBFS[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.) -- 668669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:brltty Version: 4.3-3 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: gcc -g -O2 -Wall -I. -I../../Programs -I./../Programs -I../../Programs -I./.. -I../.. -D_POSIX_C_SOURCE=2 -D_BSD_SOURCE -D_XOPEN_SOURCE=500 -D_XOPEN_SOURCE_EXTENDED -D_GNU_SOURCE -DHAVE_CONFIG_H -c ../../Programs/usb_kfreebsd.c In file included from ../../Programs/usb_kfreebsd.c:39:0: ../../Programs/usb_bsd.h: In function 'usbSetTimeout': ../../Programs/usb_bsd.h:38:21: error: 'USB_SET_TIMEOUT' undeclared (first use in this function) ../../Programs/usb_bsd.h:38:21: note: each undeclared identifier is reported only once for each function it appears in ../../Programs/usb_bsd.h: In function 'usbSetShortTransfers': ../../Programs/usb_bsd.h:49:19: error: 'USB_SET_SHORT_XFER' undeclared (first use in this function) ../../Programs/usb_bsd.h: In function 'usbSetConfiguration': ../../Programs/usb_bsd.h:75:25: error: 'USB_SET_CONFIG' undeclared (first use in this function) ../../Programs/usb_bsd.h: In function 'usbSetAlternative': ../../Programs/usb_bsd.h:113:28: error: storage size of 'arg' isn't known ../../Programs/usb_bsd.h:117:25: error: 'USB_SET_ALTINTERFACE' undeclared (first use in this function) ../../Programs/usb_bsd.h:113:28: warning: unused variable 'arg' [-Wunused-variable] ../../Programs/usb_bsd.h: In function 'usbControlTransfer': ../../Programs/usb_bsd.h:146:26: error: storage size of 'arg' isn't known ../../Programs/usb_bsd.h:154:19: error: 'USBD_SHORT_XFER_OK' undeclared (first use in this function) ../../Programs/usb_bsd.h:156:27: error: 'USB_DO_REQUEST' undeclared (first use in this function) ../../Programs/usb_bsd.h:146:26: warning: unused variable 'arg' [-Wunused-variable] ../../Programs/usb_bsd.h: In function 'usbReadDeviceDescriptor': ../../Programs/usb_bsd.h:246:25: error: 'USB_GET_DEVICE_DESC' undeclared (first use in this function) ../../Programs/usb_bsd.h: In function 'usbFindDevice': ../../Programs/usb_bsd.h:327:32: error: storage size of 'info' isn't known ../../Programs/usb_bsd.h:330:24: error: 'USB_DEVICEINFO' undeclared (first use in this function) ../../Programs/usb_bsd.h:338:43: error: 'USB_MAX_DEVNAMES' undeclared (first use in this function) ../../Programs/usb_bsd.h:327:32: warning: unused variable 'info' [-Wunused-variable] make[2]: *** [usb_kfreebsd.o] Error 1 Full build log at https://buildd.debian.org/status/fetch.php?pkg=brltty&arch=kfreebsd-amd64&ver=4.3-3&stamp=1334117762 Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer --- End Message --- --- Begin Message --- Source: brltty Source-Version: 4.4-1 We believe that the bug you reported is fixed in the latest version of brltty, which is due to be installed in the Debian FTP archive: brltty-espeak_4.4-1_amd64.deb to main/b/brltty/brltty-espeak_4.4-1_amd64.deb brltty-flite_4.4-1_amd64.deb to main/b/brltty/brltty-flite_4.4-1_amd64.deb brltty-speechd_4.4-1_amd64.deb to main/b/brltty/brltty-speechd_4.4-1_amd64.deb brltty-udeb_4.4-1_amd64.udeb to main/b/brltty/brltty-udeb_4.4-1_amd64.udeb brltty-x11_4.4-1_amd64.deb to main/b/brltty/brltty-x11_4.4-1_amd64.deb brltty_4.4-1.debian.tar.gz to main/b/brltty/brltty_4.4-1.debian.tar.gz brltty_4.4-1.dsc to main/b/brltty/brltty_4.4-1.dsc brltty_4.4-1_amd64.deb to main/b/brltty/brltty_4.4-1_amd64.deb brltty_4.4.orig.tar.gz to main/b/brltty/brltty_4.4.orig.tar.gz cl-brlapi_4.4-1_all.deb to main/b/brltty/cl-brlapi_4.4-1_all.deb libbrlapi-dev_4.4-1_amd64.deb to main/b/brltty/libbrlapi-dev_4.4-1_amd64.deb libbrlapi-java_4.4-1_all.deb to main/b/brltty/libbrlapi-java_4.4-1_all.deb libbrlapi-jni_4.4-1_amd64.deb to main/b/brltty/libbrlapi-jni_4.4-1_amd64.deb libbrlapi0.5_4.4-1_amd64.deb to main/b/brltty/libbrlapi0.5_4.4-1_amd64.deb python-brlapi_4.4-1_amd64.deb to main/b/brltty/python-brlapi_4.4-1_amd64.deb xbrlapi_4.4-1_amd64.deb
Bug#657870: marked as done (Multiple issues in Struts)
Your message dated Thu, 7 Jun 2012 21:48:34 +0200 with message-id <643e801dea7974933b7d68da7b16317d.squir...@wm.kinkhorst.nl> and subject line Re: Bug#657870: some more struts issues has caused the Debian Bug report #657870, regarding Multiple issues in Struts 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.) -- 657870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libstruts1.2-java Severity: grave Tags: security Hi, several vulnerabilities have been reported against Struts: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0391 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0392 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0393 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0394 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-5057 The version is Debian seems ancient and unmaintained, can you please check, whether an update is needed? Cheers, Moritz --- End Message --- --- Begin Message --- On Thu, June 7, 2012 07:21, tony mancill wrote: > On 06/02/2012 09:53 AM, Thijs Kinkhorst wrote: >> Hi, >> >> I'm sorry, but we've got yet another set of struts vulnerabilities: >> >> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2087 >> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2088 >> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0838 >> >> It would be really helpful if you could check how these affect Debian >> aswell. > > I reviewed these CVEs and they are associated with Struts 2.x. Debian > currently only contains Struts 1.2, and so I don't believe these are > applicable. (However, I have not attempted to replicate the > vulnerabilities against sites based on the Debian libstruts1.2-java > package.) Thanks, closing this bug then. Thijs --- End Message ---
Processed: Re: Bug#676553: libreoffice: X11 was crashed some times writer, calc, is running
Processing commands for cont...@bugs.debian.org: > tag 676553 + moreinfo Bug #676553 [libreoffice] libreoffice: X11 was crashed some times writer, calc, is running Added tag(s) moreinfo. > tag 676553 + unreproducible Bug #676553 [libreoffice] libreoffice: X11 was crashed some times writer, calc, is running Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 676553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676553 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#676553: libreoffice: X11 was crashed some times writer, calc, is running
tag 676553 + moreinfo tag 676553 + unreproducible thanks On Thu, Jun 07, 2012 at 03:47:03PM -0300, Janaína F Gonçalves wrote: > Package: libreoffice > Version: 1:3.4.6-2 Unsupported version. Only 3.5.x is supported. (Yes, I know 3.4.6 is in testing, that doesn't matter. It won't be for long anymore. But 3.5.x is constantly held back in sid due to transitions etc.) Anyway, I won't try it. And not on a clean i386 wheezy anyway as I don't have such. > Severity: grave > Justification: renders package unusable No, it doesn't. > When the writer or calc is running in a file, sometimes X11 crash and will be *sometimes*. So it doesn't make the package unusable. > needed to restart the system by press power button, because any other kbd key > isn't respond. This looks like the already reported #673942 (which got reassigned to X). #674818 (which that one is merged with) says that it's fixed in xorg 1:7.6+13 which is in testing already, though. Do you use that? What if you upgrade xorg and/or upgrade to 3.5.4 as from sid? Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676520: [sysv-rc] System unsuitable for dep-based boot cannot configure
On Thursday 07 June 2012 21:07:39 Roger Leigh wrote: > On Thu, Jun 07, 2012 at 05:34:33PM +0300, David Baron wrote: > > I have an older init scripted system which will not configure for > > dep-based boot due to man missing lsb tags and overrides (what can I do > > about this?). > > > >From NEWS.Debian: > +sysv-rc (2.88dsf-23) experimental; urgency=low > + > + Dependency based boot ordering is now required. > + > + Most systems will already be using dependency based boot ordering. > + This includes all squeeze and later releases, unless you have taken > + deliberate action to disable it. Installations upgraded from etch, > + lenny or earlier releases will have enabled dependency based booting > + when upgrading to squeeze and later releases. However, it was > + previously possible to opt out of migrating to dependency based > + booting and retain static boot ordering. This is no longer the case. > + > + If your system is still using static boot ordering, migrating to > + dependency based boot ordering will be performed when sysv-rc is > + configured. If this is not possible for any reason, you will have to > + correct the problem before upgrading can continue. It will not be > + possible to complete the upgrade until insserv is configured. > + > + The most commonly encountered problem preventing migration is the > + presence of obsolete init scripts from removed (but unpurged) > + packages. If this is the case, you will be prompted with > + instructions detailing how to purge these old packages. > + > + If you have custom init scripts, please ensure that these have the > + correct dependency information in an LSB header so that they will be > + run at the correct point in the boot sequence. > + > + -- Roger Leigh Wed, 18 Apr 2012 23:30:37 +0100 > > > Additonally, as per bug #676463, there are numerous complaints about init > > scripts for removed applications and some that are not removed! > > These are, as said above, obsolete init scripts from removed (but > not purged) conffiles. They lack LSB headers, and the packages > need purging to remove them. > > > In the past, sysv-rc would configure for the old boot correctly and > > upgrades went merrily on their way. Now, it gives an error return. > > > > Sysv-rc is left unconfigured and NO other apt operations are possible! > > This is intentional. Previously, you had the option to either enable > dynamic dependency-based ordering, or stick with static legacy > ordering. We now require dependency-based ordering, and static is > no longer supported. So we can't continue until you've fixed the > system by removing the broken scripts. We haven't really changed the > logic of the scripts here--we've just removed the choice of retaining > the legacy ordering. > > For the next upload, I need to see if we can just enable it > unconditionally, irrespective of whether the broken scripts are > present or not. If you can possibly mail me a copy of all the > broken scripts it identified, I'll test that possibility. It will > make the transition much smoother. > > Note that this only affects upgrades from older releases which lacked > LSB init scripts. The reason for doing this is because the static > ordering is bitrotting, and is no longer being actively tested since > we are all now using dynamic ordering. Rather than have systems start > to break as the ordering becomes progressively wrong, this will ensure > all systems will use a single correct ordering. Maybe this is desirable, but breaking (irretrievably!) older systems is not so nice. There are many many lsb-less init.d scripts on my box. I got rid of all the packages that need purging. I removed (not making much use of) all the fuse stuff which IS erroneously listed in this group--actual packages were uninstalled, not simply purging obselete init scripts! Short of making a deboostrap chroot and moving all the scripts from there (if this would even do the job), what can I do? I note that there are alternatives around to this sysv-rc system, i.e. file-rc (a flat, one level, no sym-link) and I recall seeing another alternative as well. Are these supported, deprecated, should be removed from the repo? I enclose the list, edited from the console output by inserting new lines are required. There are several item there that can be hand deleted. Knoppix stuff no longer used, kde3.5 no longer used, etc. My x_oddsandends should be in local.rc (which I did know about when I wrote it). The others seem to be normal inits from the packages. How would they get the need lsb info to correct the problem. I believe there are many more but that one big line ran out of space. BTW, attempts to downgrade to testing package simply reinstall the Sid package. The recommendation: dpkg --purge initscripts initscripts initscripts nut-server sysvinit (The fuse items have been uninstalled.) would be removing packages, not purging init.d files! error: Unable to migrate
Bug#676560: mysql-5.5: Serious system breakage as a result of using /run
Package: mysql-5.5 Version: 5.5.23-2 Severity: serious Justification: Breaks /run transition > ql-5.5 (5.5.23-2) unstable; urgency=low > > * Changed /var/run to /run as required by Debian Policy 3.9.3 (9.1.1) No, it's not required by policy. /var/run continues to exist, and you should continue to use it. The new directory is available, but that does not mean you should use it blindly. Please **carefully** read http://wiki.debian.org/ReleaseGoals/RunDirectory You've broken the /run transition. You **can not use /run without a versioned initscripts dependency**. Without it, /run does not exist, and you certainly shouldn't be creating it yourself. You have two options: 1) Revert to using /var/run 2) Add a versioned dependency as described in the above reference This does not include working out how to undo the damage you have caused, if this is safe or possible. Regards, Roger -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (550, 'unstable'), (500, 'testing'), (400, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676553: libreoffice: X11 was crashed some times writer, calc, is running
Package: libreoffice Version: 1:3.4.6-2 Severity: grave Justification: renders package unusable Dear Maintainer, When the writer or calc is running in a file, sometimes X11 crash and will be needed to restart the system by press power button, because any other kbd key isn't respond. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libreoffice depends on: ii fonts-sil-gentium-basic [ttf-sil-gentium-basic] 1.1-5 ii liblucene2-java 2.9.4+ds1-4 ii libreoffice-base 1:3.4.6-2 ii libreoffice-calc 1:3.4.6-2 ii libreoffice-core 1:3.4.6-2 ii libreoffice-draw 1:3.4.6-2 ii libreoffice-filter-mobiledev 1:3.4.6-2 ii libreoffice-impress 1:3.4.6-2 ii libreoffice-java-common 1:3.4.6-2 ii libreoffice-math 1:3.4.6-2 ii libreoffice-report-builder-bin 1:3.4.6-2 ii libreoffice-writer 1:3.4.6-2 ii ttf-dejavu 2.33-2 ii ttf-sil-gentium-basic1.1-5 Versions of packages libreoffice recommends: ii fonts-liberation [ttf-liberation] 1.07.2-2 ii libpaper-utils 1.1.24+nmu2 ii ttf-liberation 1.07.2-2 ii ttf-mscorefonts-installer 3.4+nmu1 Versions of packages libreoffice suggests: ii cups-bsd 1.5.2-5 ii gstreamer0.10-ffmpeg 1:0.10.13-0.2 ii gstreamer0.10-plugins-bad 0.10.23-1+b1 ii gstreamer0.10-plugins-base 0.10.36-1 ii gstreamer0.10-plugins-good 0.10.31-3 ii gstreamer0.10-plugins-ugly 0.10.19-2+b1 ii hunspell-dictionary ii hyphen-hyphenation-patterns ii iceweasel 10.0.4esr-3 ii imagemagick8:6.7.4.0-5 ii libgl1-mesa-glx [libgl1] 7.11.2-1 ii libldap-2.4-2 2.4.28-1.1 ii libreoffice-filter-binfilter 1:3.4.6-2 ii libreoffice-gnome 1:3.4.6-2 ii libreoffice-help-pt-br [libreoffice-help-3.4] 1:3.4.6-2 ii libreoffice-l10n-pt-br [libreoffice-l10n-3.4] 1:3.4.6-2 ii libreoffice-officebean ii libsane1.0.22-7.1 ii libxrender11:0.9.7-1 ii myspell-en-us [myspell-dictionary] 1:3.3.0-3 ii myspell-pt-br [myspell-dictionary] 20110527-2 ii mythes-en-us [mythes-thesaurus]1:3.3.0-3 ii openclipart-libreoffice ii pstoedit 3.60-2+b1 ii sun-java6-jre [java5-runtime] 6.26-3 ii unixodbc 2.2.14p2-5 Versions of packages libreoffice-core depends on: ii fontconfig 2.9.0-5 ii fonts-opensymbol [ttf-opensymbol] 2:2.4.3+LibO3.4.6-2 ii libatk1.0-02.4.0-2 ii libc6 2.13-32 ii libcairo2 1.12.2-1 ii libcurl3-gnutls7.25.0-1 ii libdb5.1 5.1.29-1 ii libexpat1 2.1.0-1 ii libfontconfig1 2.9.0-5 ii libfreetype6 2.4.9-1 ii libgcc11:4.7.0-8 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgraphite2-2.0.0 1.1.1-1 ii libgstreamer-plugins-base0.10-00.10.36-1 ii libgstreamer0.10-0 0.10.36-1 ii libgtk2.0-02.24.10-1 ii libhunspell-1.3-0 1.3.2-4 ii libhyphen0 2.8.3-2 ii libice62:1.0.8-2 ii libicu48 4.8.1.1-6 ii libjpeg8 8d-1 ii libmythes-1.2-02:1.2.2-1 ii libneon27-gnutls 0.29.6-3 ii libnspr4-0d2:4.9-3 ii libnss3-1d 2:3.13.4-3 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-1 ii librdf01.0.15-1 ii libreoffice-common 1:3.4.6-2 ii libsm6 2:1.2.1-2 ii libssl1.0.01.0.1c-1 ii libstdc++6 4.7.0-8 ii l
Processed: Close the bug
Processing commands for cont...@bugs.debian.org:
> fixed 673931 0.15.0~dfsg-2
Bug #673931 {Done: Anton Gladky } [sumo] sumo and
netgen: error when trying to install together
Marked as fixed in versions sumo/0.15.0~dfsg-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
673931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673931
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#673931: Close the bug
fixed 673931 0.15.0~dfsg-2 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Reassign
Processing commands for cont...@bugs.debian.org:
> reassign 673931 sumo 0.15.0~dfsg-1
Bug #673931 {Done: Anton Gladky } [netgen,sumo] sumo
and netgen: error when trying to install together
Bug reassigned from package 'netgen,sumo' to 'sumo'.
No longer marked as found in versions sumo/0.15.0~dfsg-1, netgen/4.9.13.dfsg-4,
and netgen/4.9.13.dfsg-3.1.
No longer marked as fixed in versions sumo/0.15.0~dfsg-2.
Bug #673931 {Done: Anton Gladky } [sumo] sumo and
netgen: error when trying to install together
Marked as found in versions sumo/0.15.0~dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
673931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673931
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#673931: Reassign
reassign 673931 sumo 0.15.0~dfsg-1 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: merging
Processing commands for cont...@bugs.debian.org: > forcemerge 676320 676432 Bug #676320 [wine-bin] wine-bin: update-alternatives: error: unknown argument `/usr/share/man/*/man1/wine32.1.gz' Bug #676432 [wine-bin] wine-bin: fails to upgrade: update-alternatives: error: alternative link /usr/share/man/de.UTF-8/man1/wine.1.gz is already managed by wine.1.de.UTF-8.gz (slave of wine). Merged 676320 676432 > thanks Stopping processing here. Please contact me if you need assistance. -- 676320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676320 676432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676432 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#675495: Should not be released with Wheezy
On Fri, Jun 1, 2012 at 20:12:07 +0200, Damien Raude-Morvan wrote: > - AFAIK, there is still 50+ FTBFS [3] :/ > Could somebody verify and file those in the debian bts as a first step? Cheers, Julien -- 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 674342 + fixed-upstream Bug #674342 [src:gnunet-fuse] fatal error: GNUnet/gnunet_ecrs_lib.h: No such file or directory Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 674342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674342 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#676543: oolite silently exit on debian wheezy
Georgiewskiy Yuriy wrote: > Package: oolite > Version: 1.76dfsg-1 > Severity: grave > Justification: renders package unusable > oolite silently exit on debian wheezy with the following message: Are you sure it actually exits? It doesn't for me -- I get the warning, but the game starts. I'm on i386 too. > 2012-06-07 20:33:01.071 oolite[15143] WARNING your program is > becoming multi- threaded, but you are using an ObjectiveC runtime > library which does not have a thread-safe implementation of the > +initialize method. This should be a harmless warning. All multi-threaded programs using gnustep-base and creating new threads via NSThread get this (there are quite a few). If it results in `abort' or even worse, `silent exit' (which assumes a successful exit code of the application), then it is a serious bug in gnustep-base. If oolite crashes because of improper initialization of some class while emitting this warning, then the bug belongs to libobjc4. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674342: gnunet-fuse FTBFS
GNUnet-fuse 0.9.3 is out, and it seems to build fine with gcc 4.7. So this bug is fixed upstream. I'll try to update the package as soon as possible, but it depends on GNUnet 0.9.3 which I need to package first. Cheers, Bertrand -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676520: [sysv-rc] System unsuitable for dep-based boot cannot configure
On Thu, Jun 07, 2012 at 05:34:33PM +0300, David Baron wrote: > I have an older init scripted system which will not configure for dep-based > boot due to man missing lsb tags and overrides (what can I do about this?). >From NEWS.Debian: +sysv-rc (2.88dsf-23) experimental; urgency=low + + Dependency based boot ordering is now required. + + Most systems will already be using dependency based boot ordering. + This includes all squeeze and later releases, unless you have taken + deliberate action to disable it. Installations upgraded from etch, + lenny or earlier releases will have enabled dependency based booting + when upgrading to squeeze and later releases. However, it was + previously possible to opt out of migrating to dependency based + booting and retain static boot ordering. This is no longer the case. + + If your system is still using static boot ordering, migrating to + dependency based boot ordering will be performed when sysv-rc is + configured. If this is not possible for any reason, you will have to + correct the problem before upgrading can continue. It will not be + possible to complete the upgrade until insserv is configured. + + The most commonly encountered problem preventing migration is the + presence of obsolete init scripts from removed (but unpurged) + packages. If this is the case, you will be prompted with + instructions detailing how to purge these old packages. + + If you have custom init scripts, please ensure that these have the + correct dependency information in an LSB header so that they will be + run at the correct point in the boot sequence. + + -- Roger Leigh Wed, 18 Apr 2012 23:30:37 +0100 > Additonally, as per bug #676463, there are numerous complaints about init > scripts for removed applications and some that are not removed! These are, as said above, obsolete init scripts from removed (but not purged) conffiles. They lack LSB headers, and the packages need purging to remove them. > In the past, sysv-rc would configure for the old boot correctly and upgrades > went merrily on their way. Now, it gives an error return. > > Sysv-rc is left unconfigured and NO other apt operations are possible! This is intentional. Previously, you had the option to either enable dynamic dependency-based ordering, or stick with static legacy ordering. We now require dependency-based ordering, and static is no longer supported. So we can't continue until you've fixed the system by removing the broken scripts. We haven't really changed the logic of the scripts here--we've just removed the choice of retaining the legacy ordering. For the next upload, I need to see if we can just enable it unconditionally, irrespective of whether the broken scripts are present or not. If you can possibly mail me a copy of all the broken scripts it identified, I'll test that possibility. It will make the transition much smoother. Note that this only affects upgrades from older releases which lacked LSB init scripts. The reason for doing this is because the static ordering is bitrotting, and is no longer being actively tested since we are all now using dynamic ordering. Rather than have systems start to break as the ordering becomes progressively wrong, this will ensure all systems will use a single correct ordering. Regards, Roger -- .''`. 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#634923: marked as done (python-django-authority: ships Python module "example")
Your message dated Thu, 07 Jun 2012 18:02:23 + with message-id and subject line Bug#634923: fixed in django-authority 0.4-2 has caused the Debian Bug report #634923, regarding python-django-authority: ships Python module "example" 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.) -- 634923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-camelot,python-django-authority Version: python-camelot/11.05.13-c1-1 Version: python-django-authority/0.4-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-05-19 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libcap2 libpcre3 libwrap0 libxml2 mime-support python2.6-minimal libdb4.8 libexpat1 python2.6 python-minimal python python-central python-support ucf libfreetype6 ttf-dejavu-core fontconfig-config libfontconfig1 fontconfig hicolor-icon-theme iso-codes libasound2 libasyncns0 libxau6 x11-common libice6 libsm6 libxdmcp6 libxcb1 libx11-data libx11-6 libxt6 libaudio2 libdbus-1-3 libdrm2 libogg0 libflac8 libxfixes3 libxdamage1 libxext6 libxxf86vm1 libgl1-mesa-glx libglib2.0-0 libglu1-mesa libgstreamer0.10-0 libgstreamer-plugins-base0.10-0 libjpeg62 libjs-jquery liblcms1 libmng1 libpng12-0 libvorbis0a libvorbisenc2 libsndfile1 libxi6 libxtst6 libpulse0 libpython2.6 libqtcore4 libqt4-xml libqt4-dbus libqt4-network libqt4-script libqt4-sql libqt4-xmlpatterns libtiff4 libxrender1 libqtgui4 libqt4-declarative libqt4-designer libqt4-help libqt4-opengl libqt4-scripttools libqt4-svg libqt4-test libqtassistantclient4 libqtlocation1 libxv1 libqtmultimediakit1 libqtwebkit4 python-antlr python-pkg-resources python-babel python-sqlalchemy python-elixir python-decorator python-tempita python-migrate python-markupsafe python-jinja2 python-chardet python-xlwt python-xlrd python-sip python-qt4 python-pybabel python-jinja python-excelerator tango-icon-theme python-camelot python-django-authority Extracting templates from packages: 29% Extracting templates from packages: 59% Extracting templates from packages: 89% Extracting templates from packages: 100% Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libcap2. (Reading database ... 9229 files and directories currently installed.) Unpacking libcap2 (from .../libcap2_1%3a2.20-1_amd64.deb) ... Selecting previously deselected package libpcre3. Unpacking libpcre3 (from .../libpcre3_8.12-3_amd64.deb) ... Selecting previously deselected package libwrap0. Unpacking libwrap0 (from .../libwrap0_7.6.q-19_amd64.deb) ... Selecting previously deselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.8.dfsg-2+b1_amd64.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.51-1_all.deb) ... Selecting previously deselected package python2.6-minimal. Unpacking python2.6-minimal (from .../python2.6-minimal_2.6.6-10_amd64.deb) ... Selecting previously deselected package libdb4.8. Unpacking libdb4.8 (from .../libdb4.8_4.8.30-8_amd64.deb) ... Selecting previously deselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-7_amd64.deb) ... Selecting previously deselected package python2.6. Unpacking python2.6 (from .../python2.6_2.6.6-10_amd64.deb) ... Selecting previously deselected package python-minimal. Unpacking python-minimal (from .../python-minimal_2.6.6-14_all.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.6.6-14_all.deb) ... Selecting previously deselected package python-central. Unpacking python-central (from .../python-central_0.6.17_all.deb) ... Selecting previously deselected package python-support. Unpacking python-support (from .../python-support_1.0.13_all.deb) ... Selecting previously deselected package ucf. Unpacking ucf (from .../ucf_3.0025+nmu2_all.deb) ... Moving old data out of the way Selecting previously deselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.4.4-1_amd64.deb) ... Selecting previously deselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.33-1_all.deb) ... Selecting previously deselected package fontconfig-config. Unpacking fontconfig-
Bug#676236: marked as done (Missing files when rebuilding from source)
Your message dated Thu, 07 Jun 2012 18:02:44 + with message-id and subject line Bug#676236: fixed in plexus-classworlds 1.5.0-4 has caused the Debian Bug report #676236, regarding Missing files when rebuilding from source 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.) -- 676236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plexus-classworlds Version: 1.5.0-3 Severity: serious Hello, I tried to rebuild the package from sources under a wheezy i386 chroot but the resulting package lacked the files in /usr/share/java/. Adding the --java-libs option to debian/libplexus-classworlds-java.poms seems to solve the issue. Thanks, Emanuele. --- End Message --- --- Begin Message --- Source: plexus-classworlds Source-Version: 1.5.0-4 We believe that the bug you reported is fixed in the latest version of plexus-classworlds, which is due to be installed in the Debian FTP archive: libplexus-classworlds-java-doc_1.5.0-4_all.deb to main/p/plexus-classworlds/libplexus-classworlds-java-doc_1.5.0-4_all.deb libplexus-classworlds-java_1.5.0-4_all.deb to main/p/plexus-classworlds/libplexus-classworlds-java_1.5.0-4_all.deb plexus-classworlds_1.5.0-4.debian.tar.gz to main/p/plexus-classworlds/plexus-classworlds_1.5.0-4.debian.tar.gz plexus-classworlds_1.5.0-4.dsc to main/p/plexus-classworlds/plexus-classworlds_1.5.0-4.dsc 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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Miguel Landaeta (supplier of updated plexus-classworlds 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: Tue, 05 Jun 2012 11:37:52 -0430 Source: plexus-classworlds Binary: libplexus-classworlds-java libplexus-classworlds-java-doc Architecture: source all Version: 1.5.0-4 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers Changed-By: Miguel Landaeta Description: libplexus-classworlds-java - Class loading utilities for the Plexus framework libplexus-classworlds-java-doc - API Documentation for plexus-classworlds Closes: 676236 Changes: plexus-classworlds (1.5.0-4) unstable; urgency=low . * Team upload. * Add --java-lib flag to install jars in /usr/share/java directory. (Closes: #676236). * Bump Standards-Version to 3.9.3. No changes were required. Checksums-Sha1: 72da2ffc4e4b33abb5b8a0150bf45e039ab7f608 2317 plexus-classworlds_1.5.0-4.dsc 732c1af1c6e64ae0667d4adb5ea696de4cf5cc74 6139 plexus-classworlds_1.5.0-4.debian.tar.gz c7fe93e0d823b55b0b428a35ce7b9339677fc0d1 49456 libplexus-classworlds-java_1.5.0-4_all.deb c12679d5c517c762a93d92188490a1a3e52aa696 320010 libplexus-classworlds-java-doc_1.5.0-4_all.deb Checksums-Sha256: 227e95de0e2327dffb42a2776a6d6984a76a7ebbeb267cb910e0e6e44216c484 2317 plexus-classworlds_1.5.0-4.dsc 4331d3f983ab1dbb1bd063e40339e928d5a325bfe5e32843c84779834fb4669a 6139 plexus-classworlds_1.5.0-4.debian.tar.gz 1bad83a69d3c4458bbe6a87d2d123b2f2915c77d69caaa8b46a301842cd2a2d8 49456 libplexus-classworlds-java_1.5.0-4_all.deb f51eba5bc6ba07ddccd7a68a822a1ae40984519f057bf55b013f87ad50c08240 320010 libplexus-classworlds-java-doc_1.5.0-4_all.deb Files: 4343aabf5b559585740668d4e3bd51fc 2317 java optional plexus-classworlds_1.5.0-4.dsc e56a747432d2eae6f59e3544a2a3695f 6139 java optional plexus-classworlds_1.5.0-4.debian.tar.gz 6856eceb6467fb8e828940e8d484dd0e 49456 java optional libplexus-classworlds-java_1.5.0-4_all.deb 7d1ec189ef144016a5d163458de3e5e1 320010 doc optional libplexus-classworlds-java-doc_1.5.0-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJP0OsgAAoJECHSBYmXSz6W0v8QAI1l/klt0JRs/C7csh4uppd+ EZgNUq01urG8TfoXc3JBP2WDJ9vj4w+jEo+ovCEYERDBUcO2D6SXaUM7Dh8rukcd P318YK26URzDoUJCU7YA+uNhkZhWEiCXVELrkk5vD1tgH/WvSetx6Butma5CSIea XYMsbaImIMLXMdK3xz0vuWTKXqE/zOAAJZ4fskFZg8RkfAg6DS/b3OSZaXw4HK2w DrWzSN9OGX7/RZPskCqbsNlcxDsRlHubOl03+vMcPifnaS5OXeI0A6qGN9VIdBMb tJbjgZISb6/fRiMDYdsLTvRLjScetVZAWDe/wqSwPtHZJfkbigIU8+O24xbkjva7 msilSU91f4O5XZSl+Qxhv6TqgXLL1xAcaqpz3tLR7TMKgbGUdRio3Lh4JRkHdRut xxI2sYwjgqfWI5YOj+nl9y3v5C7YAItoW95qiBHCoZHyUbI49LmoerkEZvj0F1bB G9Rs
Processed: Re: Bug#676463: sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others
Processing commands for cont...@bugs.debian.org: > severity 676463 serious Bug #676463 [sysv-rc] sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others Severity set to 'serious' from 'important' > severity 676520 serious Bug #676520 [sysv-rc] [sysv-rc] System unsuitable for dep-based boot cannot configure Severity set to 'serious' from 'grave' > forcemerge 676463 676520 Bug #676463 [sysv-rc] sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others Bug #676520 [sysv-rc] [sysv-rc] System unsuitable for dep-based boot cannot configure Merged 676463 676520 > thanks Stopping processing here. Please contact me if you need assistance. -- 676463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676463 676520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676520 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#555168: Unclear license situation for (e)glibc locales provided by you
Hello, you are listed as contact person/author of the following locale(s): en_BW en_ZW These locales come with a statement % Distribution and use is free, also % for commercial purposes. Thus they do not allow modification; it is unclear, however, if this statement was meant as a license. As discussed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555168 these locales could strictly speaking not be part of Debian which would be a great loss. (Currently they are allowed pending investigation). To properly resolve this, I would like to ask you the following question: Would you be willing to relicense these locale(s) to a proper license, e.g. (L)GPL v2 or higher or another free software license of your choice? If you have any questions regarding this issue, do not hesitate to contact me (via the reply-to address set). Thanks for helping to resolve this! Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
Bug#676245: marked as done (Missing files when rebuilding from source)
Your message dated Thu, 07 Jun 2012 17:48:38 + with message-id and subject line Bug#676245: fixed in libxbean-java 3.7-5 has caused the Debian Bug report #676245, regarding Missing files when rebuilding from source 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.) -- 676245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxbean-java Version: 1.5.0-3 Severity: serious Hello, I tried to rebuild the package from sources under a wheezy i386 chroot but, due to a change in maven-debian-helper 1.5, the resulting package lack the files in /usr/share/java/. Adding the --java-libs option to the following entries in debian/libxbean-java.poms solves the issue: maven-xbean-plugin/pom.xml --java-lib xbean-asm-shaded/pom.xml --java-lib xbean-bundleutils/pom.xml --java-lib xbean-classloader/pom.xml --java-lib xbean-classpath/pom.xml --java-lib xbean-finder/pom.xml --java-lib xbean-finder-shaded/pom.xml --java-lib xbean-naming/pom.xml --java-lib xbean-reflect/pom.xml --java-lib xbean-spring/pom.xml --java-lib xbean-telnet/pom.xml --java-lib Thanks, Emanuele. --- End Message --- --- Begin Message --- Source: libxbean-java Source-Version: 3.7-5 We believe that the bug you reported is fixed in the latest version of libxbean-java, which is due to be installed in the Debian FTP archive: libxbean-java-doc_3.7-5_all.deb to main/libx/libxbean-java/libxbean-java-doc_3.7-5_all.deb libxbean-java_3.7-5.debian.tar.gz to main/libx/libxbean-java/libxbean-java_3.7-5.debian.tar.gz libxbean-java_3.7-5.dsc to main/libx/libxbean-java/libxbean-java_3.7-5.dsc libxbean-java_3.7-5_all.deb to main/libx/libxbean-java/libxbean-java_3.7-5_all.deb 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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Miguel Landaeta (supplier of updated libxbean-java package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 05 Jun 2012 20:30:59 -0430 Source: libxbean-java Binary: libxbean-java libxbean-java-doc Architecture: source all Version: 3.7-5 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers Changed-By: Miguel Landaeta Description: libxbean-java - plugin based Java application server libxbean-java-doc - API documentation for XBean Closes: 676245 Changes: libxbean-java (3.7-5) unstable; urgency=low . * Team upload. * Add --java-lib flag to install jars in /usr/share/java directory. (Closes: #676245). * Bump Standards-Version to 3.9.3. No changes were required. Checksums-Sha1: 4683189b08864bb80ad422e218d2a02421cc04bd 2610 libxbean-java_3.7-5.dsc b61c94a643492df4b877a1dff365348ff3ed7995 8641 libxbean-java_3.7-5.debian.tar.gz e779a889a9c9a4ecce160d897ec8725b846709dc 638458 libxbean-java_3.7-5_all.deb ed0bf4508b170047f938430a292a24df7d3f8308 1089950 libxbean-java-doc_3.7-5_all.deb Checksums-Sha256: c2ed703415fbe137be11648c82cd2522e6bebcd2b3a2650b2debb0fdba50a734 2610 libxbean-java_3.7-5.dsc 29c1850a460273f1b7819da48630cc74fd1768dbdd3a7f42d0c651f580d0af69 8641 libxbean-java_3.7-5.debian.tar.gz 8fc4fd007d32791e2110db0b81564bfbdc2fc918533aebbc63dcdd40deccb2ff 638458 libxbean-java_3.7-5_all.deb b4884b5317283fdd402e8bf7919d048f12b9b16d87266063378d0310737e7b90 1089950 libxbean-java-doc_3.7-5_all.deb Files: 8ae43dfd212c7136a9b157ed688d49c0 2610 java optional libxbean-java_3.7-5.dsc dadb48813d9c2caaf6106b36e7cf4ee1 8641 java optional libxbean-java_3.7-5.debian.tar.gz 0a43dd0747442d8bd534735a74ad698b 638458 java optional libxbean-java_3.7-5_all.deb d65e11824521b956dcf8fe9fd955cfaf 1089950 doc optional libxbean-java-doc_3.7-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJP0OJEAAoJECHSBYmXSz6WRjIP/0YdMkKGyU3WE4X9yeSUozDt qPXEUfkXaLUoKM5MIuxRgVBKPSDlTbBRdATzY7C7Ym6QruPbcADLGJvdLl6/H4F0 VLq0PT7rmxkWi761tUZBQP/pQwIk7Qcp1k/6VWQK7aU9ZW5w+Moc/VS8YwQuq8nF bYy3cswUVzJXWi9gNF9EYnLCc02KPaRYyPSHhOzLxy6hOwdPPgUlmmlWGk3OeSdX K6B8FWqBu4PclnUMPvDyJ7jUvE0gVDsSuKihPyUyiDR6Rl5zO/ehAi0IFomH265S h1yPPn9e89OBNtsdXd8IHkplAwSsQ8qK0ndx/0XMoG94L2+0zimAly8jedaaF6Zk ZOmnjcwmEEAcHWAvvx9YG1yTFwLSOxCbpXnzZ9MaAPfg19VP
Bug#674344: marked as done (xmakemol: FTBFS: build-dependency not installable: libglw1-mesa-dev)
Your message dated Thu, 07 Jun 2012 19:47:55 +0200 with message-id <87obov2eus@turtle.gmx.de> and subject line caused by #673233 has caused the Debian Bug report #674344, regarding xmakemol: FTBFS: build-dependency not installable: libglw1-mesa-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 674344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xmakemol Version: 5.16-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > ┌──┐ > │ Install xmakemol build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-xmakemol-dummy : Depends: libglw1-mesa-dev but it is > not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/24/xmakemol_5.16-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- The build dependencies of xmakemol were uninstallable because of #673233, a problem that has been corrected in the meantime. --- End Message ---
Processed: get mesa into testing
Processing commands for cont...@bugs.debian.org:
> # looks like the RC bug keeps mesa out of testing, although
> # the new packages from the glw source already migrated
> severity 673233 normal
Bug #673233 {Done: Julien Cristau } [src:mesa] mesa: no
longer builds libglw1-mesa
Severity set to 'normal' from 'serious'
> reassign 673233 wnpp
Bug #673233 {Done: Julien Cristau } [src:mesa] mesa: no
longer builds libglw1-mesa
Bug reassigned from package 'src:mesa' to 'wnpp'.
No longer marked as found in versions mesa/8.0.2-2.
No longer marked as fixed in versions glw/8.0.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
673233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673233
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#675183: sitplus: diff for NMU version 1.0.3-2.1
Hi Tim, many thanks for your fix. Would you be so kind to commit your change to the Git repository? Every DD has commit permissions to Debian Med Vcs. Just tell me if you do not feel able to do so and I will inject your changes. Kind regards and thanks again for helping out Andreas. On Thu, Jun 07, 2012 at 05:54:43PM +0100, Tim Retout wrote: > tags 675183 + patch > tags 675183 + pending > thanks > > Dear maintainer, > > I've prepared an NMU for sitplus (versioned as 1.0.3-2.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. > > Regards. > diff -Nru sitplus-1.0.3/debian/changelog sitplus-1.0.3/debian/changelog > --- sitplus-1.0.3/debian/changelog2012-05-11 07:14:03.0 +0100 > +++ sitplus-1.0.3/debian/changelog2012-06-07 08:34:42.0 +0100 > @@ -1,3 +1,11 @@ > +sitplus (1.0.3-2.1) unstable; urgency=low > + > + * Non-maintainer upload. > + * debian/control: Replace Build-Depends on libcv-dev and > +libcvaux-dev with libopencv-dev. (Closes: #675183) > + > + -- Tim Retout Thu, 07 Jun 2012 08:33:27 +0100 > + > sitplus (1.0.3-2) unstable; urgency=low > >* Work around build failure with GCC 4.7. (Thanks for the patch to > diff -Nru sitplus-1.0.3/debian/control sitplus-1.0.3/debian/control > --- sitplus-1.0.3/debian/control 2012-05-11 07:14:03.0 +0100 > +++ sitplus-1.0.3/debian/control 2012-06-07 08:33:20.0 +0100 > @@ -8,7 +8,7 @@ > Build-Depends: debhelper (>= 9), cmake, libpoco-dev, libboost-dev, > libboost-program-options-dev, libboost-thread-dev, libboost-system-dev, > wx2.8-headers, libwxbase2.8-dev, libbluetooth-dev, libconfig-dev, > libsdl1.2-dev, > - libcv-dev (>= 2.3.1-7), libcvaux-dev, libhighgui-dev, libv4l-dev, > libportmidi-dev, > + libopencv-dev, libhighgui-dev, libv4l-dev, libportmidi-dev, > libboost-filesystem-dev, asciidoc, libsdl-gfx1.2-dev, libsdl-image1.2-dev, > libwxgtk2.8-dev, doxygen, libxtst-dev > Standards-Version: 3.9.3 > ___ > Debian-med-packaging mailing list > debian-med-packag...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#634923: python-django-authority: ships Python module "example"
Hi Clint, On Thu, Jun 7, 2012 at 7:31 PM, Clint Adams wrote: > On Thu, Jun 07, 2012 at 07:21:02PM +0200, Janos Guljas wrote: >> I had a similar issue with one of my packages, and I am sending a patch >> that is removing example from packaging it as a module, and putting that >> directory as example under documentation. > > Thanks.. I'll apply it shortly. You wouldn't want to adopt it, > would you? Thanks for the offering, but I am not using this module in my projects. Best, Janos -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676543: oolite silently exit on debian wheezy
Package: oolite Version: 1.76dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** oolite silently exit on debian wheezy with the following message: 2012-06-07 20:33:01.071 oolite[15143] WARNING your program is becoming multi- threaded, but you are using an ObjectiveC runtime library which does not have a thread-safe implementation of the +initialize method. This means that any classes not already used may be incorrectly initialised, potentially causing strange behaviors and crashes. To put this into context, the runtime bug has been knoown for several years and only rarely causes problems ... the easy workaround being to ensure that any classes used by a new thread have already been used in the main thread before the new thread starts. If you are worried, please build/run GNUstep with a runtime which supports the +initialize method. The GNUstep stable runtime (libobjc) and experimental runtime (libobjc2), available from the GNUstep website and subversion repository, should both work. To disable this warning (eg. for an application which does not suffer any problems caused by this runtime bug), please set the GSSilenceInitializeWarning user default to YES. i resently upgrades to wheezy, previously i use stable with same oolite version backported manualy, and it's works fine on debian stable. *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.19-rt29-r249 (PREEMPT) Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Shell: /bin/sh linked to /bin/dash Versions of packages oolite depends on: ii gnustep-base-runtime 1.22.1-2+b1 ii libc6 2.13-32 ii libgcc1 1:4.7.0-8 ii libgl1-mesa-glx [libgl1] 7.11.2-1 ii libglu1-mesa | libglu1 ii libgnustep-base1.22 1.22.1-2+b1 ii libmozjs10d 10.0.4esr-3 ii libobjc4 4.7.0-8 ii libpng12-01.2.49-1 ii libsdl-mixer1.2 1.2.12-2 ii libsdl1.2debian 1.2.15-3 ii oolite-data 1.76dfsg-1 Versions of packages oolite recommends: pn oolite-data-sounds 1.76dfsg-1 pn oolite-doc oolite 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
debian-bugs-rc@lists.debian.org
Processing commands for cont...@bugs.debian.org: > forwarded 675951 > http://developer.berlios.de/support/index.php?func=detailsupport&support_id=103364&group_id=273 Bug #675951 [src:ruby-ncurses] ruby-ncurses: FTBFS: -Werror=format-security Set Bug forwarded-to-address to 'http://developer.berlios.de/support/index.php?func=detailsupport&support_id=103364&group_id=273'. > thanks Stopping processing here. Please contact me if you need assistance. -- 675951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675951 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: limit source to ruby-ncurses, tagging 675951
Processing commands for cont...@bugs.debian.org: > #ruby-ncurses (1.3.1-2) unstable; urgency=low > # > # * Fix FTBFS. Closes: #675951 > #- Add patch for formatting error string. > # > limit source ruby-ncurses Limiting to bugs with field 'source' containing at least one of 'ruby-ncurses' Limit currently set to 'source':'ruby-ncurses' > tags 675951 + pending Bug #675951 [src:ruby-ncurses] ruby-ncurses: FTBFS: -Werror=format-security Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 675951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675951 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#634923: python-django-authority: ships Python module "example"
On Thu, Jun 07, 2012 at 07:21:02PM +0200, Janos Guljas wrote: > I had a similar issue with one of my packages, and I am sending a patch > that is removing example from packaging it as a module, and putting that > directory as example under documentation. Thanks.. I'll apply it shortly. You wouldn't want to adopt it, would you? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#634923: python-django-authority: ships Python module "example"
Package: python-django-authority
Followup-For: Bug #634923
Hi,
I had a similar issue with one of my packages, and I am sending a patch
that is removing example from packaging it as a module, and putting that
directory as example under documentation.
Best,
Janos
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.3.0-trunk-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
>From da45d000526bfb38dd2c034d628e379d9861cf6d Mon Sep 17 00:00:00 2001
From: Janos Guljas
Date: Thu, 7 Jun 2012 19:06:00 +0200
Subject: [PATCH] Exclude example directory from packaging in global python
namespace.
---
debian/examples |1 +
debian/patches/exclude-example-module.patch | 17 +
debian/patches/series |1 +
3 files changed, 19 insertions(+)
create mode 100644 debian/examples
create mode 100644 debian/patches/exclude-example-module.patch
create mode 100644 debian/patches/series
diff --git a/debian/examples b/debian/examples
new file mode 100644
index 000..33a9488
--- /dev/null
+++ b/debian/examples
@@ -0,0 +1 @@
+example
diff --git a/debian/patches/exclude-example-module.patch b/debian/patches/exclude-example-module.patch
new file mode 100644
index 000..0ebf1e7
--- /dev/null
+++ b/debian/patches/exclude-example-module.patch
@@ -0,0 +1,17 @@
+Description: Exclude example directory from packaging in global python namespace.
+Author: Janos Guljas
+Bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634923
+Last-Update: 2012-06-07
+
+
+--- a/setup.py
b/setup.py
+@@ -14,7 +14,7 @@
+ license='BSD',
+ url='http://bitbucket.org/jezdez/django-authority/',
+ download_url='http://bitbucket.org/jezdez/django-authority/downloads/',
+-packages=find_packages(),
++packages=find_packages(exclude=('example','example.exampleapp')),
+ classifiers=[
+ 'Development Status :: 3 - Alpha',
+ 'Environment :: Web Environment',
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..93e6129
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+exclude-example-module.patch
--
1.7.10
Bug#675538: marked as done (apper-data: fails to upgrade from 'testing' - trying to overwrite /usr/share/kde4/services/kcm_apper.desktop)
Your message dated Thu, 7 Jun 2012 19:01:09 +0200 with message-id and subject line Bug#675538: fixed in apper 0.7.2-3 has caused the Debian Bug report #675538, regarding apper-data: fails to upgrade from 'testing' - trying to overwrite /usr/share/kde4/services/kcm_apper.desktop 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.) -- 675538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apper-data Version: 0.7.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks/Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package apper-data. Unpacking apper-data (from .../apper-data_0.7.2-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/apper-data_0.7.2-1_all.deb (--unpack): trying to overwrite '/usr/share/kde4/services/kcm_apper.desktop', which is also in package apper 0.7.1-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) cheers, Andreas apper_0.7.2-1.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: apper Source-Version: 0.7.2-3 --- End Message ---
Processed: sitplus: diff for NMU version 1.0.3-2.1
Processing commands for cont...@bugs.debian.org: > tags 675183 + patch Bug #675183 [src:sitplus] src:sitplus: FTBFS on amd64 in clean pbuilder OpenCV required but some headers or libs not found Added tag(s) patch. > tags 675183 + pending Bug #675183 [src:sitplus] src:sitplus: FTBFS on amd64 in clean pbuilder OpenCV required but some headers or libs not found Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 675183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675183 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#675183: sitplus: diff for NMU version 1.0.3-2.1
tags 675183 + patch tags 675183 + pending thanks Dear maintainer, I've prepared an NMU for sitplus (versioned as 1.0.3-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru sitplus-1.0.3/debian/changelog sitplus-1.0.3/debian/changelog --- sitplus-1.0.3/debian/changelog 2012-05-11 07:14:03.0 +0100 +++ sitplus-1.0.3/debian/changelog 2012-06-07 08:34:42.0 +0100 @@ -1,3 +1,11 @@ +sitplus (1.0.3-2.1) unstable; urgency=low + + * Non-maintainer upload. + * debian/control: Replace Build-Depends on libcv-dev and +libcvaux-dev with libopencv-dev. (Closes: #675183) + + -- Tim Retout Thu, 07 Jun 2012 08:33:27 +0100 + sitplus (1.0.3-2) unstable; urgency=low * Work around build failure with GCC 4.7. (Thanks for the patch to diff -Nru sitplus-1.0.3/debian/control sitplus-1.0.3/debian/control --- sitplus-1.0.3/debian/control 2012-05-11 07:14:03.0 +0100 +++ sitplus-1.0.3/debian/control 2012-06-07 08:33:20.0 +0100 @@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 9), cmake, libpoco-dev, libboost-dev, libboost-program-options-dev, libboost-thread-dev, libboost-system-dev, wx2.8-headers, libwxbase2.8-dev, libbluetooth-dev, libconfig-dev, libsdl1.2-dev, - libcv-dev (>= 2.3.1-7), libcvaux-dev, libhighgui-dev, libv4l-dev, libportmidi-dev, + libopencv-dev, libhighgui-dev, libv4l-dev, libportmidi-dev, libboost-filesystem-dev, asciidoc, libsdl-gfx1.2-dev, libsdl-image1.2-dev, libwxgtk2.8-dev, doxygen, libxtst-dev Standards-Version: 3.9.3
Processed: [bts-link] source package tiff3
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package tiff3 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #668087 (http://bugs.debian.org/668087) > # Bug title: libtiff4: libtiff crashes with corrupted images > # * http://bugzilla.maptools.org/show_bug.cgi?id=2378 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> WORKSFORME > # * closed upstream > tags 668087 + fixed-upstream Bug #668087 [libtiff4] libtiff4: libtiff crashes with corrupted images Added tag(s) fixed-upstream. > usertags 668087 - status-NEW Bug#668087: libtiff4: libtiff crashes with corrupted images Usertags were: status-NEW. Usertags are now: . > usertags 668087 + status-RESOLVED resolution-WORKSFORME Bug#668087: libtiff4: libtiff crashes with corrupted images There were no usertags set. Usertags are now: status-RESOLVED resolution-WORKSFORME. > thanks Stopping processing here. Please contact me if you need assistance. -- 668087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668087 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#676496: dpkg: premature removal of "Multi-arch:" leads to all dpkg commands failing
Hi! On Thu, 2012-06-07 at 12:40:59 +0200, Adam Borowski wrote: > Package: dpkg > Version: 1.16.3 > Severity: grave > Justification: renders package unusable > After an interrupted dpkg run, any subsequent invocation fails with: > > dpkg: error: libc6-dev:armel (Multi-Arch: no) is not co-installable > with libc6-dev which has multiple installed instances > > This affects not only -i, --purge, --unpack but even -l or dpkg-query. > > The last two relevant entries of dpkg/updates (there's over a hundred > entries after that, none mentioning libc6-dev) are: > ,--[ /var/lib/dpkg/updates/0006 > Package: libc6-dev > Status: unknown ok not-installed > Priority: optional > Section: libdevel > Architecture: armel > ` > After manually appending "Multi-Arch: same" to the file in dpkg/updates (for > libc6-dev:armel and for another package from the same run), dpkg let me > proceed. > This suggests a fix: don't remove the field until possibly some time later. Hrm, I thought I had handled that case in the code correctly, but apparently not. :/ It's really a problem that the update log is only ever used on some interrupted runs, as that makes reliably testing it quite difficult, I should add a way to test it in the future. > (I have a btrfs snapshot of the system, in case more information is needed.) No need, and thanks for the report, will be fixed in 1.16.4, being finished right now. thanks, guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: jnr-netdb: missing --java-lib in POM file
Processing commands for cont...@bugs.debian.org: > tags 676353 + pending Bug #676353 [jnr-netdb] jnr-netdb: missing --java-lib in POM file Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 676353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676353 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#676353: jnr-netdb: missing --java-lib in POM file
tags 676353 + pending thanks On Wed, Jun 06, 2012 at 01:21:25PM +0200, Hector Oron wrote: > Package: jnr-netdb > Version: 1.0.3-1 > Severity: serious > Tags: patch > > Hello, > > Your package causes other packages as jruby to fail to build from source as > newer maven-debian-helper changes, prevent your package to install symlinks > in /usr/share/java directory. Adding --java-lib option in your POM files > should fix the issue. Hi, This is already fixed in the git repo. Cheers, -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/ "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#676222: marked as done (eclipse-platform-data: fails to upgrade from 'sid' - trying to overwrite /usr/lib/eclipse/configuration/config.ini)
Your message dated Thu, 07 Jun 2012 16:02:54 +
with message-id
and subject line Bug#676222: fixed in eclipse 3.8.0~rc3-2
has caused the Debian Bug report #676222,
regarding eclipse-platform-data: fails to upgrade from 'sid' - trying to
overwrite /usr/lib/eclipse/configuration/config.ini
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.)
--
676222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eclipse-platform-data
Version: 3.8.0~rc3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks/Replaces relation.
See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
>From the attached log (scroll to the bottom...):
Preparing to replace eclipse-platform-data 3.7.2-1 (using
.../eclipse-platform-data_3.8.0~rc3-1_all.deb) ...
Unpacking replacement eclipse-platform-data ...
dpkg: error processing
/var/cache/apt/archives/eclipse-platform-data_3.8.0~rc3-1_all.deb (--unpack):
trying to overwrite '/usr/lib/eclipse/configuration/config.ini', which is
also in package eclipse-platform 3.7.2-1
Preparing to replace eclipse-platform 3.7.2-1 (using
.../eclipse-platform_3.8.0~rc3-1_amd64.deb) ...
Unpacking replacement eclipse-platform ...
cheers,
Andreas
eclipse-platform_3.8.0~rc3-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: eclipse
Source-Version: 3.8.0~rc3-2
We believe that the bug you reported is fixed in the latest version of
eclipse, which is due to be installed in the Debian FTP archive:
eclipse-jdt_3.8.0~rc3-2_all.deb
to main/e/eclipse/eclipse-jdt_3.8.0~rc3-2_all.deb
eclipse-pde_3.8.0~rc3-2_all.deb
to main/e/eclipse/eclipse-pde_3.8.0~rc3-2_all.deb
eclipse-platform-data_3.8.0~rc3-2_all.deb
to main/e/eclipse/eclipse-platform-data_3.8.0~rc3-2_all.deb
eclipse-platform_3.8.0~rc3-2_amd64.deb
to main/e/eclipse/eclipse-platform_3.8.0~rc3-2_amd64.deb
eclipse-rcp_3.8.0~rc3-2_amd64.deb
to main/e/eclipse/eclipse-rcp_3.8.0~rc3-2_amd64.deb
eclipse_3.8.0~rc3-2.debian.tar.gz
to main/e/eclipse/eclipse_3.8.0~rc3-2.debian.tar.gz
eclipse_3.8.0~rc3-2.dsc
to main/e/eclipse/eclipse_3.8.0~rc3-2.dsc
eclipse_3.8.0~rc3-2_all.deb
to main/e/eclipse/eclipse_3.8.0~rc3-2_all.deb
libequinox-osgi-java_3.8.0~rc3-2_all.deb
to main/e/eclipse/libequinox-osgi-java_3.8.0~rc3-2_all.deb
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 676...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jakub Adam (supplier of updated eclipse 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, 07 Jun 2012 17:08:30 +0200
Source: eclipse
Binary: eclipse eclipse-jdt eclipse-pde eclipse-platform eclipse-platform-data
eclipse-rcp libequinox-osgi-java
Architecture: source all amd64
Version: 3.8.0~rc3-2
Distribution: experimental
Urgency: low
Maintainer: Debian Orbital Alignment Team
Changed-By: Jakub Adam
Description:
eclipse- Extensible Tool Platform and Java IDE
eclipse-jdt - Eclipse Java Development Tools (JDT)
eclipse-pde - Eclipse Plug-in Development Environment (PDE)
eclipse-platform - Eclipse platform without development plug-ins
eclipse-platform-data - Eclipse platform without development plug-ins (data)
eclipse-rcp - Eclipse Rich Client Platform (RCP)
libequinox-osgi-java - Equinox OSGi framework
Closes: 676222
Changes:
eclipse (3.8.0~rc3-2) experimental; urgency=low
.
[ Jakub Adam ]
* Fix FTBFS on most architectures.
* Install libgnomeproxy-1.0.0.so to system JNI directory.
- Prevents the library from being copied in to user's ~/.eclipse
* Fix JSP precompilation in org.eclipse.help.webapp.
* Make eclipse-platform-data Replace & Break eclipse-platform (<< 3.8.0~)
(Closes: #676222)
.
[ Niels Thykier ]
* Add missing ${misc:Pre-Depends} dependency in eclipse-platform.
* Drop unused ${shlibs:Recomends} dependency in ecl
