Bug#714861: Asterisk do not log source IP for Failed to authenticate device
Op 2013-07-04 om 01:48 schreef Tzafrir Cohen: On Wed, Jul 03, 2013 at 06:36:44PM +0400, Kozakman wrote: Thus usage of Fail2ban or other tools is limited. This is technically a simple issue to fix (I don't have the upstream issue handy, but it's nothing much more thn a fix of a format string and such). Upstream declined to do so for 1.8 as it was too late to do so by the time it froze. For the same reason I don't see this bug getting fixed in Wheezy (right?). On the other hand is this particular string format fix a security update. Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#569668: heart beat
Hi, Here a progress report. Meanwhile I have a succesfull build of davmail. The Alioth repository has my changes. Next steps are * install check * de-install check * install * test drive the programm in CLI deamon mode ( no GUI stuff ) * upload Help on Lintian warning W: davmail: executable-not-elf-or-script usr/share/java/davmail-4.3.0.2125.jar is welcome. Cheers Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#655614: FWIW wheezy is released
Hello, For what it's worth: Wheezy is released. Please close this bugreport so that package prepaid-manager-applet gets into Jessie. And more important: that is worthwhile to sent in patches about local operators not yet in the serviceproviders.xml Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589304: status Alioth git repository
Hi, This a reply on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589304#80 Quoting Willem van den Akker: I tried to create a git repository on git.debian.org pkg-jabberd2 in /git. But didnt had the permission for it. What is the status for a jabber2d packaging repository at Alioth? Things I'm asking for is What is allready in place? and What is needed? More steering on the wanted answer: * Allready in place: ** Alioth accountname for Willem van den Akker ** That account is member of the XMPP group * Still needed: ** Some one with the privilege to create the repository as describe at . An answer such as repo meanwhile created is also fine ;-) Groeten Geert Stappers Alioth accountname: stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#710262: extended description
The extend description is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710282 This bugreport and that bugreport are allready merged. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712565: syslinux: new upstream versions 4.06/5.00/5.01/5.10 available
Daniel Baumann [Mon Jun 17, 2013 at 12:40:57PM +0200]: On 06/17/2013 12:21 PM, Michael Prokop wrote: But 3:6.00~pre4+dfsg-11 is not a stable version AFAICT it's identical to 5.01 but has additional uefi support. And which upstream version number does that match? Or in another way: Which syslinux in Debian is close upstream Syslinux 5.10? Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707093: progress: git commits pushed
Op 2013-05-26 om 09:19 schreef Alexandre Rossi: Please allow me to commit it to the Alioth git repository. Go on, thanks! Done Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#710212: Regarding: Bug#710212: fails to install
Op 2013-05-29 om 23:30 schreef Alex Vanderpol: Attempting to narrow down the cause of this bug led me to an interesting discovery. There's a rather large difference between the /usr/sbin/extlinux-update files in 3:6.00~pre4+dfsg-7 and 3:6.00~pre4+dfsg-8 that appears (in part, at least) to be related to this issue. This difference also exists in 3:6.00~pre4+dfsg-9. For what it is worth: this from syslinux (3:6.00~pre4+dfsg-10) * Correcting typo in extlinux debhelper install file (Closes: #710306). Please try the new version and report back. Here's the diff output from 3:6.00~pre4+dfsg-7 to 3:6.00~pre4+dfsg-8 and 3:6.00~pre4+dfsg-9: 12,34d11 _EXTLINUX_DIRECTORY=/boot/extlinux Thanks. A request: Please get the habit to use the '-u' flag of `diff`. Example: `diff -u previous.file newer.file` This way we get the same output as `svn diff` and `git diff` give. Cheers Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707093: about to upload libhtmlcleaner-java, closing ITP 707093
Hello, After making white space changes in the upstream source, such as adding a terminating end-of-line, got I clean build. Another change of me is the version number: --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -libhtmlcleaner-java (2.2-1~pre+1) unstable; urgency=low +libhtmlcleaner-java (2.2-1) unstable; urgency=low * Initial release (Closes: #707093). A manual unpack of the generated .deb reveals that is has twice the jar. screenshot stappers@nero:~/src/unpack $ cat md5sums 6a7f04dce317e6b10c0a69c732b4fd8c usr/share/doc/libhtmlcleaner-java/changelog.Debian.gz cd2a52a615d8a9ae6b9667d1c506069f usr/share/doc/libhtmlcleaner-java/copyright 6d920a8d671a7617c0a68bc197a5d281 usr/share/java/htmlcleaner-2.2.jar stappers@nero:~/src/unpack $ md5sum usr/share/java/* 6d920a8d671a7617c0a68bc197a5d281 usr/share/java/htmlcleaner-2.2.jar 6d920a8d671a7617c0a68bc197a5d281 usr/share/java/htmlcleaner.jar stappers@nero:~/src/unpack $ /screenshot Despite the dual jars, I will be uploading libhtlmcleaner-java_2.2-1. My reason for doing so, is that in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707093#52 is stated the build system will be changed. ( switching to maven ) Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#707093: about to upload libhtmlcleaner-java, closing ITP 707093
Op 2013-05-26 om 20:34 schreef Geert Stappers: A manual unpack of the generated .deb reveals that is has twice the jar. screenshot stappers@nero:~/src/unpack $ cat md5sums 6a7f04dce317e6b10c0a69c732b4fd8c usr/share/doc/libhtmlcleaner-java/changelog.Debian.gz cd2a52a615d8a9ae6b9667d1c506069f usr/share/doc/libhtmlcleaner-java/copyright 6d920a8d671a7617c0a68bc197a5d281 usr/share/java/htmlcleaner-2.2.jar stappers@nero:~/src/unpack $ md5sum usr/share/java/* 6d920a8d671a7617c0a68bc197a5d281 usr/share/java/htmlcleaner-2.2.jar 6d920a8d671a7617c0a68bc197a5d281 usr/share/java/htmlcleaner.jar stappers@nero:~/src/unpack $ /screenshot Despite the dual jars, I will be uploading libhtlmcleaner-java_2.2-1. Despite the duplicate jars, I will be uploading libhtlmcleaner-java_2.2-1. And at http://ftp-master.debian.org/new/libhtmlcleaner-java_2.2-1.html#binary-libhtmlcleaner-java-contents it is cleanerly visible that is a symbolic link. screenshot contents of libhtmlcleaner-java_2.2-1_all.deb (click to toggle) drwxr-xr-x root/root 0 2013-05-25 21:16 ./ drwxr-xr-x root/root 0 2013-05-25 21:16 ./usr/ drwxr-xr-x root/root 0 2013-05-25 21:16 ./usr/share/ drwxr-xr-x root/root 0 2013-05-25 21:16 ./usr/share/java/ -rw-r--r-- root/root 76328 2013-05-25 21:16 ./usr/share/java/htmlcleaner-2.2.jar drwxr-xr-x root/root 0 2013-05-25 21:16 ./usr/share/doc/ drwxr-xr-x root/root 0 2013-05-25 21:16 ./usr/share/doc/libhtmlcleaner-java/ -rw-r--r-- root/root 2001 2013-05-25 21:14 ./usr/share/doc/libhtmlcleaner-java/copyright -rw-r--r-- root/root 168 2013-05-20 14:59 ./usr/share/doc/libhtmlcleaner-java/changelog.Debian.gz lrwxrwxrwx root/root 0 2013-05-25 21:16 ./usr/share/java/htmlcleaner.jar - htmlcleaner-2.2.jar /screenshot So the duplicate is fine. :-/ Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#707093: progress
Op 2013-05-24 om 15:43 schreef Alexandre Rossi: My next action will this Lintian message: E: libhtmlcleaner-java: helper-templates-in-copyright False positive. But anyway I switched the package to DEP-5 yesterday which should fix the issue. Yes, it should ... See http://anonscm.debian.org/gitweb/?p=pkg-java/libhtmlcleaner-java.git;a=commitdiff;h=63976bf5f660eef5371d63b117b2396e70e9e76d Then there is/was: $ lintian -I W: libhtmlcleaner-java source: missing-field-in-dep5-copyright license (paragraph at line 6) W: libhtmlcleaner-java source: missing-field-in-dep5-copyright license (paragraph at line 38) E: libhtmlcleaner-java: copyright-should-refer-to-common-license-file-for-gpl This patch does fix it: --- a/debian/copyright +++ b/debian/copyright @@ -5,7 +5,7 @@ Source: http://htmlcleaner.sourceforge.net Files: * Copyright: 2006-2010 Vladimir Nikic -Licence: BSD htmlcleaner +License: BSD-3-clause Redistribution and use of this software in source and binary forms, with or without modification, are permitted provided that the following conditions are met: @@ -37,4 +37,7 @@ Licence: BSD htmlcleaner Files: debian/* Copyright: 2011 Alexandre Rossi -Licence: GPL-2 +License: GPL-2 + On Debian systems, the full text of the GNU General Public + License version 2 can be found in the file + `/usr/share/common-licenses/GPL-2'. Please allow me to commit it to the Alioth git repository. Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#707093: progress
Op 2013-05-21 om 22:05 schreef Geert Stappers: Op 2013-05-19 om 20:34 schreef tony mancill: If you just want to see how it build, you can follow these steps: [ good instructions ] That information got me back on track. I'm now making white space changes to fix warnings as | dpkg-source: warning: file libhtmlcleaner-java/src/test/resources/Expected_1.html has no final newline (either original or modified version) to see what is causing | dpkg-source: error: unrepresentable changes to source | dpkg-buildpackage: error: dpkg-source -b libhtmlcleaner-java gave error exit status 2 That seems to be gone due to white space changes. My next action will this Lintian message: E: libhtmlcleaner-java: helper-templates-in-copyright Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707093: reproducing the build and the upload process of libhtmlcleaner-java
Op 2013-05-24 om 15:37 schreef Alexandre Rossi: I'll be working on this, but the version on mentors.debian.org seems pretty acceptable to me for review. Regarding the git repo issue, I can branch of the debian/2.2-1_pre+1 tag in order to take into account packaging review comments, while working on getting 2.5 in shape. Or I can start over for master to be exactly what has been uploaded at mentors.d.n and keep my work on 2.5 private. Please advice. My advice: Work on 2.5, push the commit to the Alioth repository. My plan: Reviewing 2.2 and uploading it with the warm feeling that 2.5 is waiting. Alex Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#707093: reproducing the build and the upload process of libhtmlcleaner-java
Op 2013-05-19 om 20:34 schreef tony mancill: If you just want to see how it build, you can follow these steps: # clone the pkg-java repo git clone git+ssh://git.debian.org/git/pkg-java/libhtmlcleaner-java.git cd libhtmlcleaner-java # (re)create the upstream tarball for the 2.2 version git archive upstream/2.2 --prefix=libhtmlcleaner-java-2.2/ -o ../libhtmlcleaner-java_2.2.orig.tar.gz # clean up the 2.4 sources that are currently there # (as an alternative, you could copy ./debian/ to a new folder) rm -rf .git __MACOSX src # restore the 2.2 sources tar --strip-components=1 -xvf ../libhtmlcleaner-java_2.2.orig.tar.gz # build! debuild -us -uc That information got me back on track. I'm now making white space changes to fix warnings as | dpkg-source: warning: file libhtmlcleaner-java/src/test/resources/Expected_1.html has no final newline (either original or modified version) to see what is causing | dpkg-source: error: unrepresentable changes to source | dpkg-buildpackage: error: dpkg-source -b libhtmlcleaner-java gave error exit status 2 Tony: Thank you! Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707093: reproducing the build and the upload process of libhtmlcleaner-java
Hello Alexandre,
Hello People reading ITP libhtmlcleaner-java,
and hello Debian Java People,
Summary:
Please document the maintainers workflow for libhtmlcleaner-java,
have a debian/README.soure in the git repository.
This is an e-mail about wanting to help, but being helpless.
About wanting to go beyond helpless and being helpfull.
There is Debian Bug report #707093
ITP: libhtmlcleaner-java -- Java HTML Parser library
( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707093 )
Alexandre Rossi did the packing work, but has no upload privilege.
Geert Stappers has upload privilege, but can't review the work of Alexandre.
It is part my ignorance and part missing documentation.
To solve my ignorance am I, stappers, willing to learn. To solve missing
documentation
is my proposal add a debian/README.source file. See
http://wiki.debian.org/Java/JavaVcs
for minimal content.
In the README.source having documented how to convert the .zip from upstream
into the git repository would also be a good thing.
The command `dpkg-buildpackage -uc -us` gives this
output
dpkg-source -b libhtmlcleaner-java
dpkg-source: error: can't build with source format '3.0 (quilt)': no upstream
tarball found at ../libhtmlcleaner-java_2.2.orig.tar.{bz2,gz,lzma,xz}
dpkg-buildpackage: error: dpkg-source -b libhtmlcleaner-java gave error exit
status 255
/output
If something else as `dpkg-buildpackage` should be used, please document it.
Groeten
Geert Stappers
--
And is there a policy on top-posting vs. bottom-posting?
Yes.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569668: FWIW: minor feedback on Davmail ITP sponsoring
Hello all, At http://mentors.debian.net/debian/pool/main/d/davmail/ there is a davmail_4.2.1.orig.tar.gz and a davmail_4.2.1-1~3.gbp244580.debian.tar.gz Upstream has davmail-srconly-4.2.1-2089.tgz and `uscan` makes davmail_4.2.1-2089.orig.tar.gz I will be spending time to see if I can convince gitbuildpackage to make something like davmail_4.2.1.2089-1_all.deb Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616689: more encounters ... gone :-)
Op 2013-05-15 om 22:14 schreef Geert Stappers: I'm gonna play with the error on the virtual machine. That was a nice exprience. Learned a lot. And the best thing is that I got it working. With a _completer apt archive_ is works fine. Yes, I could reproduce this bug due an incomplete apt archive. So not a initramfs-tools error, but an user error ... Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616689: more encounters ...
Hello, My first encounter with this bug was last weekend (yes, a week after the release of Wheezy) on real hardware. And tonight I got it reproduced twice on VirtualBox VM. The workaround on the real hardware was avoiding LVM. I'm gonna play with the error on the virtual machine. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#707093: sponsoring libhtmlcleaner-java for davmail
Hello Reader, Here I volunteer to sponsor libhtmlcleaner-java libhtmlcleaner-java is a dependency for davmail Status of davmail is at http://bugs.debian.org/569668 Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#569668: workflow for libhtmlcleaner-java and davmail
Previous message was only in http://bugs.debian.org/569668 Op 2013-05-07 om 14:12 schreef Alexandre Rossi: Thanks. Filled as #707093. http://bugs.debian.org/707093 I'm hoping to be able to prepare packages for sponsorship on Friday. Alex We need^W^WI feel the need to invest some time in workflow I will be reading the java packaging workflow and shall raise questions at the mailinglist debian-j...@lists.debian.org Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#706499: marked as done (Ethernet with Realtek R8169 only working with IPV6)
Op 2013-05-06 om 12:51 schreef Debian Bug Tracking System: the Debian Bug report #706499, regarding Ethernet with Realtek R8169 only working with IPV6 to be marked as done. snip/ From: Ben Hutchings b...@decadent.org.uk To: 706499-d...@bugs.debian.org Subject: Re: Bug#706499: Ethernet with Realtek R8169 only working with IPV6 Message-ID: 1367844634.4131.62.ca...@deadeye.wl.decadent.org.uk X-Mailer: Evolution 3.4.4-2 On Mon, 2013-05-06 at 09:56 +0200, Karsten Malcher wrote: [...] Afterwards the R8169 card works without problem. Good. [...] The problem has come like a ghost and gone like a ghost. It's hard to say for me but - the bug can be closed. This problem is really not reproducible. Now i must master my routing problem - maybe the problem will come up again ... I think this was likely some kind of configuration problem all along (though I don't know what). FWIW: The 192.168.1.3 and 192.168.1.4 are on the _SAME_ IP-network. That is odd for one single computer with two interfaces. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#706666: please remove Conglomerate also from testing -- RoM
Hello FTP-masters, Bug #70, this bugreport, is/was about removal of package Conglomerate from unstable. Please remove Conglomerate also from testing. - Forwarded message from Debian testing watch nore...@release.debian.org - Date: Sun, 05 May 2013 16:39:20 + From: Debian testing watch nore...@release.debian.org To: conglomer...@packages.debian.org Subject: conglomerate 0.9.1-3.3 MIGRATED to testing Message-Id: e1uz1y4-0006w3...@franck.debian.org FYI: The status of the conglomerate source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0.9.1-3.3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. - End forwarded message - Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706666: RM: conglomerate -- RoM; no longer maintaint upstream
Package: ftp.debian.org Severity: normal Hello FTP masters, Packages conglomerate and conglomerate-common are no longer maintaint upstream. Please remove them from unstable. This request is to make sure that Conglomerate does not go into Wheezy. A request to remove from the upcoming release is granted in #706638 - Forwarded message from Adam D. Barratt - Date: Fri, 03 May 2013 06:18:54 +0100 From: Adam D. Barratt To: Geert Stappers stapp...@debian.org Cc: 706638-d...@bugs.debian.org Subject: Re: Bug#706638: RM: conglomerate/0.9.1-3.2 Message-ID: 1367558334.9105.16.ca...@jacala.jungle.funky-badger.org On Fri, 2013-05-03 at 07:07 +0200, Geert Stappers wrote: Op 2013-05-02 om 21:06 schreef Adam D. Barratt: On Thu, 2013-05-02 at 21:54 +0200, Geert Stappers wrote: XML editor Conglomerate got it last upstream release in 2006. We should consider it death upstream. Please remove it from the archive. Do you mean the archive, or wheezy? Wheezy Okay; removal hint added. It would be worth considering asking ftp-master to remove it from unstable... Regards, Adam - End forwarded message - Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#706638: RM: conglomerate/0.9.1-3.2
Op 2013-05-03 om 06:18 schreef Adam D. Barratt: On Fri, 2013-05-03 at 07:07 +0200, Geert Stappers wrote: Op 2013-05-02 om 21:06 schreef Adam D. Barratt: On Thu, 2013-05-02 at 21:54 +0200, Geert Stappers wrote: XML editor Conglomerate got it last upstream release in 2006. Please remove it from the archive. Do you mean the archive, or wheezy? Wheezy Okay; removal hint added. Thanks It would be worth considering asking ftp-master to remove it from unstable... Done. It be came bug #70 Groeten Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#569668: libhtmlcleaner-java for davmail
Hello Alexandre, Here an e-mail from the person who wants to sponsor uploading the davmail package into Debian. What you think about this ITP, Intend To Package proposal?: * Package name : libhtmlcleaner-java Version : 2.2 Upstream Author : Vladimir Nikic vni...@users.sourceforge.net * URL : http://htmlcleaner.sourceforge.net/ * License : BSD Programming Lang : Java Description : Java HTML Parser library HtmlCleaner can be used in java code, as command line tool or as Ant task. It is designed to be small, independent (no runtime dependencies except JRE 1.5+), fast and flexible (its behavior is configurable through number of parameters). Although the main motive was to prepare ordinary HTML for XML processing with XPath, XQuery and XSLT, structured data produced by HtmlCleaner may be consumed and handled in many other ways. Groeten Geert Stappers Who couldn't find an existing ITP for libhtmlcleaner-java at http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=wnpp signature.asc Description: Digital signature
Bug#706638: RM: conglomerate/0.9.1-3.2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hello FTP masters, XML editor Conglomerate got it last upstream release in 2006. We should consider it death upstream. Please remove it from the archive. During Squeeze took Conglomerate resources like translating and library fixes. That should be avoided during Wheezy. My apology for the late request. It was hard for me to write this request. Conglomerate was the package that got me Debian Developer. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#569668: progress update
Progress report
Did a `git clone` of davmail. Encountered the build dependency
on HTML cleaner
done
git clone git://anonscm.debian.org/pkg-java/libhtmlcleaner-java
With `dpkg-buildpackage -uc -us` there I got this error:
dpkg-source: error: can't build with source format '3.0 (quilt)': no upstream
tarball found at ../libhtmlcleaner-java_2.2.orig.tar.{bz2,gz,lzma,xz}
Continueing with `fakeroot debian/rules binary` got me a libhtmcleaner-java.deb
Installed the HTML cleaner package.
With `dpkg-buildpackage -uc -us` there was an error,
with `fakeroot debian/rules binary` I got a davmail Debian package.
So far this report.
To be continued
Groeten
Geert Stappers
--
And is there a policy on top-posting vs. bottom-posting?
Yes.
signature.asc
Description: Digital signature
Bug#706638: RM: conglomerate/0.9.1-3.2
Hello Release Team, Op 2013-05-02 om 21:06 schreef Adam D. Barratt: On Thu, 2013-05-02 at 21:54 +0200, Geert Stappers wrote: The Release Team are not the FTP masters. XML editor Conglomerate got it last upstream release in 2006. We should consider it death upstream. Please remove it from the archive. Do you mean the archive, or wheezy? Wheezy Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#703195: Cant get BCM43228 to work
On Sat, Mar 16, 2013 at 06:50:24PM +0100, Mathieu Malaterre wrote: Is there a way for me to track what could possibly be going on wrong with setup of wireless driver ? do lspci -s 03:00.0 -n and check that VendorID and ProductID matches what you found with modinfo alias: pci:v14E4d0576sv*sd*bc*sc*i* alias: pci:v14E4d4727sv*sd*bc*sc*i* alias: pci:v14E4d4353sv*sd*bc*sc*i* alias: pci:v14E4d4357sv*sd*bc*sc*i* Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678029: the i386 binary does mipsel on amd64
For what it's worth: the i386 binary does mipsel on amd64 In other words: when a i386 binary of qemu-mipsel is used on an amd64 host, it is possible to have a mipsel enviroment without segfaults. It is not a solution to this bug, but it gives a working qemu-mipsel-static on amd64 Commands to get the i386 binaries with minimal effect on the amd64 wget http://ftp.nl.debian.org/debian/pool/main/q/qemu/qemu-user-static_1.1.2%2Bdfsg-3_i386.deb mkdir unpacked dpkg -x qemu-user-static_1.1.2+dfsg-3_i386.deb unpacked find unpacked | grep /bin/ cp unpacked/usr/bin/qemu-mipsel-static oa/usr/bin/qemu-mipsel-static chroot oa where 'oa' is created with the file from posting http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678029#25 Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678029: some kind of backtrace
Hello, Here the progress that I made. * Was able to build an unstripped binary and installed it * Got a fresh core after setting limit -c to unlimited * Made a backtrace with gdb. root@rosa:/usr/src/bts678029# root@rosa:/usr/src/bts678029# dpkg -i ../qemu-user-static_1.1.2+dfsg-3.1_amd64.deb (Database inlezen ... 66165 files and directories currently installed.) Voorbereiden om qemu-user-static 1.1.2+dfsg-3.1 te vervangen (door .../qemu-user-static_1.1.2+dfsg-3.1_amd64.deb) ... Uitpakken van vervangende qemu-user-static ... Instellen van qemu-user-static (1.1.2+dfsg-3.1) ... Processing triggers for man-db ... root@rosa:/usr/src/bts678029# cp -p /usr/bin/qemu-mips-static oa/usr/bin root@rosa:/usr/src/bts678029# chroot oa qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentatiefout root@rosa:/usr/src/bts678029# ls -l oa/core -rw--- 1 root root 97800192 dec 16 23:40 oa/core root@rosa:/usr/src/bts678029# ulimit -c 0 root@rosa:/usr/src/bts678029# ulimit -c unlimited root@rosa:/usr/src/bts678029# chroot oa Segmentatiefout (geheugendump gemaakt) root@rosa:/usr/src/bts678029# ls -l oa/core -rw--- 1 root root 97800192 dec 18 18:04 oa/core root@rosa:/usr/src/bts678029# gdb /usr/bin/qemu-mips-static oa/core GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/qemu-mips-static...done. warning: core file may not match specified executable file. [New LWP 3250] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Core was generated by `/usr/bin/qemu-mips-static /bin/bash -i'. Program terminated with signal 11, Segmentation fault. #0 0x600d8bd7 in kill () (gdb) bt #0 0x600d8bd7 in kill () #1 0x60042a48 in force_sig (target_sig=target_sig@entry=11) at /usr/src/qemu/linux-user/signal.c:405 #2 0x600416be in queue_signal (env=env@entry=0x634f3190, sig=sig@entry=11, info=info@entry=0x7fff9bc06980) at /usr/src/qemu/linux-user/signal.c:443 #3 0x6002e9e2 in cpu_loop (env=env@entry=0x634f3190) at /usr/src/qemu/linux-user/main.c:2293 #4 0x6002f6dc in main (argc=1666129488, argv=optimized out, envp=optimized out) at /usr/src/qemu/linux-user/main.c:3857 (gdb) quit root@rosa:/usr/src/bts678029# ls oa/*core* oa/core oa/qemu_bash_20121218-170427_3250.core oa/qemu_bash_20121216-224051_7558.core root@rosa:/usr/src/bts678029# root@rosa:/usr/src/bts678029# gdb /usr/bin/qemu-mips-static oa/qemu_bash_20121218-170427_3250.core GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/qemu-mips-static...done. warning: core file may not match specified executable file. warning: Selected architecture i386:x86-64 is not compatible with reported target architecture i386 warning: Architecture rejected target-supplied description warning: Couldn't find general-purpose registers in core file. [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. warning: Couldn't find general-purpose registers in core file. #0 unavailable in ?? () (gdb) quit root@rosa:/usr/src/bts678029# root@rosa:/usr/src/bts678029# exit -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678029: also in 1.1.2
Over here with version 1.1.2 I also get a qemu: uncaught target signal 11 (Segmentation fault) - core dumped But I can't find the dumped core with sudo find . -name *core* Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678029: found the dumped core
On Sun, Dec 16, 2012 at 02:50:10PM +0400, Michael Tokarev wrote: On 16.12.2012 14:23, Geert Stappers wrote: [ bug reproducable, got core dumped message ] But I can't find the dumped core with sudo find . -name *core* Does it chdir to some other place perhaps? Got meanwhile the dumped core. I had 'ulimit -c 0'. After doing ulimit -c unlimited and triggering the bug, I got two files with core in the name: |inertia:/usr/src/rtrbrd |# ls -lh oa/*core |-rw--- 1 root root 94M dec 16 16:23 oa/core |-rw-r--r-- 1 root root 1,4K dec 16 16:23 oa/qemu_bash_20121216-152313_27693.core |inertia:/usr/src/rtrbrd |# file oa/*core |oa/core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/qemu-mips-static /bin/bash -i' |oa/qemu_bash_20121216-152313_27693.core: ELF 32-bit MSB core file, MIPS, MIPS-I version 1 (SYSV), SVR4-style |inertia:/usr/src/rtrbrd |# But anyway. Please tell us something about your environment, what you're trying to run, I want to run MIPS executables on an AMD64. It is based upon the packages qemu-user-static and binfmt-support Several months ago I had that working. maybe some minimal reproducer, - create a mips chroot tree with multistrap, I have it named 'oa' - cp /usr/bin/qemu-mips-static oa/usr/bin - chroot oa - beng, the segfault I'll provide files for easy reproduction. and whenever it happens with non-static variant too. I don't known how to do that. (and the static used to work. ) Cheers Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678029: reproduce files
On Sun, Dec 16, 2012 at 06:54:08PM +0100, Geert Stappers wrote:
On Sun, Dec 16, 2012 at 02:50:10PM +0400, Michael Tokarev wrote:
maybe some minimal reproducer,
- create a mips chroot tree with multistrap, I have it named 'oa'
- cp /usr/bin/qemu-mips-static oa/usr/bin
- chroot oa
- beng, the segfault
I'll provide files for easy reproduction.
This script is in the attached tar among other files.
#!/bin/bash
#
# to reproduce 678029
#
# depends on the Debian package multistrap
#
# root privileges required
#
ARCH=sparc
ARCH=armel
ARCH=mips
#
# wipe a possibly previous version
rm -rf oa
#
# setup a chroot tree in other architure directory
/usr/sbin/multistrap --arch ${ARCH} -f ./multistrap.conf
# now there is directory 'oa'
#
#
BINFMTEMUL=/usr/bin/qemu-${ARCH}-static
if [ -x ${BINFMTEMUL} ] ; then
cp -p ${BINFMTEMUL} oa/usr/bin
else
echo E:No binfmt emulator ${BINFMTEMUL}
exit 7
fi
## mkdir -p oa/proc
mkdir -p oa/sysfs
# l l
Cheers
Geert Stappers
bts678029.tar
Description: Unix tar archive
Bug#678029: it should work ;-)
On Sun, Dec 16, 2012 at 10:31:34PM +0400, Michael Tokarev wrote: gandalf:/tmp/bts678029# sh ./trigger mounting done triggering bug 678029 mips unmounting back to normal So it looks like the mips emulation works fine, I don't see any crashes or core dumps. Thanks for checking. Now I know for sure that it should work, that it makes sense to chasse this bug :-/ I'll build an unstripped qemu-mips-static to make an usefull gdb backtrace [] mkdir -p oa/sysfs Btw, is it really sysfs and not sys? Oops. I'll change it Thanks, Thank you! /mjt Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692522: packages matching running kernel 3.2.0-3-amd64 in archive
On Sat, Nov 10, 2012 at 01:36:50PM +, Brian Potkin wrote: On Sat 10 Nov 2012 at 14:11:31 +0100, Geert Stappers wrote: Summary: version mismatch in archive Hello Debian-boot, The kernel from http://ftp.nl.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux is a 3.2.0-3-amd64 The file debian/dists/wheezy/main/debian-installer/binary-amd64/Packages.gz from http://ftp.nl.debian.org/ has 3.2.0-4-amd64 modules. In syslog of the wanna be installation computer is the line Nov 10 12:41:12 anna[2071]: WARNING **: no packages matching running kernel 3.2.0-3-amd64 in archive In the d-i user screen ( tty1 ) is a dutch version of Template: anna/no_kernel_modules _Description: Continue the install without loading kernel modules? No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. . If you're installing from a mirror, you can work around this problem by choosing to install a different version of Debian. The install will probably fail to work if you continue without kernel modules. How to fix the version mismatch in the Debian archive? Please see bug #692522. That is is reopen by me to tell that current beta1 d-i netboot images do not match with beta3 archive. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550534: long lines
long, non-wrapped, lines of posting from Bart-Jan Vrielink [598216.014608] iwl4965 :03:00.0: Microcode SW error detected. Restarting 0x8200. [598216.014612] iwl4965 :03:00.0: Loaded firmware version: 228.61.2.24 [598216.014628] iwl4965 :03:00.0: Start IWL Error Log Dump: [598216.014630] iwl4965 :03:00.0: Status: 0x000213E4, count: 5 [598216.014777] iwl4965 :03:00.0: Desc Time data1 data2 line [598216.014780] iwl4965 :03:00.0: FH_ERROR (0x000C) 3967722153 0x0008 0x0313 208 [598216.014783] iwl4965 :03:00.0: pc blink1 blink2 ilink1 ilink2 hcmd [598216.014786] iwl4965 :03:00.0: 0x0046C 0x05CB2 0x004C2 0x006DE 0x018B8 0x285001C [598216.014788] iwl4965 :03:00.0: FH register values: [598216.014802] iwl4965 :03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X09373900 [598216.014816] iwl4965 :03:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00646f00 [598216.014830] iwl4965 :03:00.0: FH_RSCSR_CHNL0_WPTR: 0X0068 [598216.014843] iwl4965 :03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00819000 [598216.014857] iwl4965 :03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X003c [598216.014870] iwl4965 :03:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X0313 [598216.014884] iwl4965 :03:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [598216.014897] iwl4965 :03:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0002 [598216.014911] iwl4965 :03:00.0: FH_TSSR_TX_ERROR_REG: 0X [598216.015157] ieee80211 phy1: Hardware restart was requested HTH -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625020: version HEAD no FTBFS
For the people at chan-capi-users(a)lists.melware.net, you find context at http://bugs.debian.org/625020 On Thu, Oct 18, 2012 at 01:11:13PM +0200, Geert Stappers wrote: On Thu, Oct 18, 2012 at 07:24:16AM +0200, Joerg Dorchain wrote: I would not mind a packages from ftp://ftp.chan-capi.org/chan-capi/chan_capi-HEAD.tgz , which works with the current asterisk in testing. Based upon that information, I did remove the won't fix tag The FTBFS is indeed gone in upstream's HEAD version. I got a clean debianbuild with the october 19th version of chan-capi. The most clean solution to fix this Fails To Build From Source Bug would be getting an version number greater as 1.1.5 from upstream. (They are now in the loop) Another solution would be create version something like 1.1.5+VCS20121019 Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#625020: wontfix versus fixed upstream
tags 625020 - wontfix thanks On Thu, Oct 18, 2012 at 07:24:16AM +0200, Joerg Dorchain wrote: On Thu, Oct 18, 2012 at 12:36:18PM +1100, Mark Purcell wrote: If upstream don't intend to release then I would argue the viability of the package in Debian is questionable. I would not mind a packages from ftp://ftp.chan-capi.org/chan-capi/chan_capi-HEAD.tgz , which works with the current asterisk in testing. Based upon that information, I did remove the won't fix tag Best regards, Joerg Hi Joerg, You bring back the good memories of the Oldenburg m68k meetings. :-) Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685540: getting the asterisk module loadable
On Sat, Oct 13, 2012 at 09:02:56PM +0200, Jonas Smedegaard wrote: On 12-10-13 at 04:08pm, Geert Stappers wrote: Here a message from the Utrecht BSP 2012. ( http://wiki.debian.org/BSP/2012/10/nl/Utrecht ) Bugreport 685540 is release critical according http://bugs.debian.org/release-critical/other/testing.html so I spend some time on it and go it fixed. When compiling with asterisk installed, I get a loadable app_flite.so In other words: A build-depend on asterisk solves this issue. I believe your reasoning is flawed: Compiling _without_ adding a build-dependency on asterisk _also_ makes app_flite.so loadable. That does makes sense, at least it matches my observation: module was loadable after a recompile I gonna do a non-maintainer upload to the 10 days delay queue. Thanks for the attempt - but please cancel that misleading upload unless you can provide additional info contraditing what I wrote above. There was a `dput --delayed 10` down and after that a `dcut`. In ten day we know for sure that cancel was succesfull. If my `dcut` was unsuccesfull, we get a binNMU :-/ The specific issue needs only a simple binNMU, That information is now in this bugreport. which the release team has judged is wrong to do. Having the reason in this BR would be nice. The underlying issue is that asterisk fails to provide proper shlibs hinting, so that packages building against asterisk do not get versioned binary dependencies that can reveal leed for binNMU later on. That ? binary dependencies that can reveal need for binNMU later on. That underlying issue needs to be reported against asterisk and fixed there. The Debian maintainers of asterisk are in the Cc. Reporting the issue in a BR is now, wheezy release freeze, not done. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625020: Update
Information from the IRC channel #debian-voip * how to get the source * what to do to get it fixed 12:29 stappers Hi 12:30 stappers http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625020 is RC bug about asterisk-chan-capi 12:30 stappers It is a FTBFS, but where to get src:asterisk-chan-capi ??? 13:06 pabs stappers: dget http://http.debian.net/debian/pool/main/a/asterisk-chan-capi/asterisk-chan-capi_1.1.5-1.dsc 13:07 pabs stappers: too late to fix that for wheezy though 13:51 tzafrir_laptop stappers, th fix is to get a newr chan_capi from SVN 13:52 tzafrir_laptop It seems that thy don't intend to release anything. But thir branch 1.1.5 is old. Hope this helps Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685540: Is marked release critical, fix available
Hello, Here a message from the Utrecht BSP 2012. ( http://wiki.debian.org/BSP/2012/10/nl/Utrecht ) Bugreport 685540 is release critical according http://bugs.debian.org/release-critical/other/testing.html so I spend some time on it and go it fixed. When compiling with asterisk installed, I get a loadable app_flite.so In other words: A build-depend on asterisk solves this issue. I gonna do a non-maintainer upload to the 10 days delay queue. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#645540: to close bug#685540
From: Geert Stappers stapp...@stappers.nl --- debian/changelog |7 +++ debian/control |1 + 2 files changed, 8 insertions(+) diff --git a/debian/changelog b/debian/changelog index 9fed194..fb8f7ac 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +asterisk-flite (2.1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Build-depend on asterisk. Closes: bug#643703 + + -- Geert Stappers stapp...@debian.org Sat, 13 Oct 2012 15:21:10 +0200 + asterisk-flite (2.1-1) unstable; urgency=low * New upstream release. diff --git a/debian/control b/debian/control index 876ff4d..1d9c12b 100644 --- a/debian/control +++ b/debian/control @@ -5,6 +5,7 @@ Maintainer: Jonas Smedegaard d...@jones.dk Build-Depends: cdbs, debhelper, dh-buildinfo, + asterisk, asterisk-dev, flite-dev Standards-Version: 3.9.3 -- 1.7.10.4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685540: to close bug#685540
From: Geert Stappers stapp...@stappers.nl --- debian/changelog |7 +++ debian/control |1 + 2 files changed, 8 insertions(+) diff --git a/debian/changelog b/debian/changelog index 9fed194..fb8f7ac 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +asterisk-flite (2.1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Build-depend on asterisk. Closes: bug#643703 + + -- Geert Stappers stapp...@debian.org Sat, 13 Oct 2012 15:21:10 +0200 + asterisk-flite (2.1-1) unstable; urgency=low * New upstream release. diff --git a/debian/control b/debian/control index 876ff4d..1d9c12b 100644 --- a/debian/control +++ b/debian/control @@ -5,6 +5,7 @@ Maintainer: Jonas Smedegaard d...@jones.dk Build-Depends: cdbs, debhelper, dh-buildinfo, + asterisk, asterisk-dev, flite-dev Standards-Version: 3.9.3 -- 1.7.10.4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645540: sorry
My excuses for the noise. Mainwhile is 685...@bugs.debian.org updated with the correct information. Sorry Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686096: Reviewed
severity: normal thanks Therefore, I believe the wrong value was cached somewhere within partman Or some thing else that is wrong. But the severity is not critical. The bugreporter can reproduce the bug. It would a bug (without quotes) when it is reproduceable with two disks. Currently is the bug only seen when creating two physical volume on on one single disk. I don't known partman well enough how it counts or measures disk size, but I can imagine that it is misleaded when multiple physical volume are on the same physical disk. Frankly, I think this bugreport is about a non real use case and it should be closed. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686096: Reviewed
severity 686096 normal thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569668: davmail ITP status update (Re: ITP: davmail)
On Mon, Oct 01, 2012 at 03:15:42PM +0200, Alexandre Rossi wrote: I'll be seeking sponsorship when wheezy is realeased, I want to be that sponsor. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685864: linux-image-3.2.0-3-amd64: Commande halt or halt -p and shutdown = reboot system. Cm :gigabyte z77x-ud5h
[Please reply to all, including the address 685...@bugs.debian.org] vrom: novice gavo...@panthere-noire.com Date: Tue, 28 Aug 2012 03:06:46 +0200 1. Uninstall the nvidia driver (or somehow stop it from loading) yes . I also tested modprobe -r nvidia `modprobe -r nvidia` removes the nvidia kernel module from memory. It is the undo of `modprobe nvidia`, which loads it in memory. BUT: modprode is MORE then just load and unload, there is also programcode from the kernel module executed. During load there is initialization done. The request is uninstall the nvidia module. To remove it from disk. With the effect to stop it from loading and executing init code. 2. Reboot reboot . That reboot is to clear initialiastion the nvidia driver could have done. 3. Run 'shutdown' Ben. use: shutdown -h nows result reboot. That is the reason for this ticket :-/ thank you for your patience This E-mail is / was about telling that uninstall is more then `modprobe -r modulename` Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685864: linux-image-3.2.0-3-amd64: Commande halt or halt -p and shutdown = reboot system. Cm :gigabyte z77x-ud5h
Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 04) 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI]) 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04) 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4) (prog-if 00 [Normal decode]) 00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4) (prog-if 00 [Normal decode]) 00:1c.5 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev c4) (prog-if 01 [Subtractive decode]) 00:1c.6 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 [8086:1e1c] (rev c4) (prog-if 00 [Normal decode]) 00:1c.7 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 [8086:1e1e] (rev c4) (prog-if 00 [Normal decode]) 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) (prog-if 20 [EHCI]) 00:1f.0 ISA bridge [0601]: Intel Corporation Z77 Express Chipset LPC Controller [8086:1e44] (rev 04) 00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04) (prog-if 01 [AHCI 1.0]) 00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04) Subsystem: Giga-byte Technology Device [1458:5001] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin C routed to IRQ 18 Region 0: Memory at f653a000 (64-bit, non-prefetchable) [size=256] Region 4: I/O ports at f020 [size=32] 02:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller [1b4b:9172] (rev 11) (prog-if 01 [AHCI 1.0]) 03:00.0 PCI bridge [0604]: Integrated Technology Express, Inc. Device [1283:8892] (rev 30) (prog-if 01 [Subtractive decode]) 04:01.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev c0) (prog-if 10 [OHCI]) 05:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet [1969:1083] (rev c0) 06:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller [1b4b:9172] (rev 11) (prog-if 01 [AHCI 1.0]) 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller]) Kernel driver in use: nvidia As far as I known is there nouveau the open source driver voor Nvidia. 07:00.1 Audio device [0403]: NVIDIA Corporation GF104 High Definition Audio Controller [10de:0beb] (rev a1) ** USB devices: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 2109:0810 According my web search an USB 3 device Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 2109:0810 Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 003 Device 004: ID 2109:0810 Bus 003 Device 005: ID 2109:0810 Bus 003 Device 006: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 003 Device 007: ID 046d:c223 Logitech, Inc. G11/G15 Keyboard / USB Hub Bus 003 Device 008: ID 046d:c068 Logitech, Inc. G500 Laser Mouse Bus 003 Device 009: ID 05e3:0605 Genesys Logic, Inc. USB 2.0 Hub [ednet] Bus 003 Device 010: ID 046d:c226 Logitech, Inc. G15 Refresh Keyboard Bus 003 Device 011: ID 046d:c227 Logitech, Inc. G15 Refresh Keyboard Bus 003 Device 012: ID 03f0:6104 Hewlett-Packard DeskJet 5650c Bus 003 Device 013: ID 046d:0a0b Logitech, Inc. ClearChat Pro USB My two cents Cheers Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684516: bluetooth.ko unlikely in initrd
On Sat, Aug 25, 2012 at 09:07:30PM +0200, asronche...@libero.it wrote: Da: stapp...@stappers.nl Data: 25-ago-2012 19.59 Remove the bluetooth module from /lib/modules and the initial ramdisk, so that the computer hasn't any more the module. btw, what do you mean with 'ramdisk' ? is that 'initramfs' ? Yes. if i remove that file, will the system be still bootable? Do NOT remove files like /boot/initrd.img-* After removing bluetooth.ko from /lib/module/ update the Init R.D. with the command update-initramfs (sorry, i still am not an expert about the linux boot stuff) My expertise level also can use some more learning. Where I/we want so that the computer hasn't any more the module. I told Remove the bluetooth module from /lib/modules and should have left out and the initial ramdisk, on second thought it is unlikely that the bluetooth module is in initrd. In the initial ramdisk are modules which are needed to mount root f.s. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#684516: bluetooth loaded for UNKNOWN reason
On Sun, Aug 19, 2012 at 07:41:50PM +0200, asronche...@libero.it wrote: Da: Johantan Niederman jrnie...@gmail.com Data: 19-ago-2012 19.27 (Though I have no idea whether they trigger autoloading of the bluetooth module or if it's udev's responsibility.) Thanks for the advice. I checked via aptitude but i have already removed the bluez package. Ben Hutchings @ Sun, 19 Aug 2012 17:56:35 +0100 Not a bug; please stop pursuing this irrelevant detail. How can you think that it's not a bug? The challenge is to be constructive. 1) I dont have bluetooth devices attached to this notebook. 2) I followed your advice and i removed the bluetooth package 3) today i had a kernel panic and the error message appeared on the the screen showed a list of loaded modulse. The first module of that list was indeed the bluetooth module. My advice is to research what causes the bluetooth module be loaded. I would start with checking udev rules. Thing I would NOT do, is yelling: Nobody listens to me! Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683080: bacula-fd: build with libcap-dev, don't enable it by default
Op 20120807 om 22:18 schreef Elrond: On Fri, Aug 03, 2012 at 16:12:58 +0200, Luca Capello wrote: [...] I would go even further: if I read it correctly, this should improves security, so I was wondering if it would be better to have it by default... Please don't. Avoid stiffeling the restore. This is quite attractive, I can understand that. Really I would love to see this. BUT ... ... it will stop nice restores. s/nice restore/plain restore/ You have to restore to /tmp and all the restored files will be owned by nobody and not the original owner. I don't know if people are ready for this. I'm a smart part of people, I expect that a restore goes the same way as backup, no so detour trough /tmp with chown. In a first step, I would suggest to add the capability support, so that users can play with this feature and learn. In a second step, I would suggest making it easy for users to enable this feature (maybe commented version in /etc/default/bacula-fd?) Or maybe add a debconf knob directly? So that people can enable it easily while installing bacula-fd on all of their client machines? I do understand the good intention to add a new feature, but I think that default read only capability feature for bacula-fd is wrong. Just my personal thoughts. Yes, this E-mail is also sharing my thoughts (and worries). joke consider=some what sick To prevent bacula-fd default started with -k option, I will not contribute any code. /joke Cheers Elrond Groeten Geert Stappers Agreeing on the build with libcap-dev, not on enabling it by default -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643319: No added value in optional queue name
Hello, FWIW I don't seen added value in changing -d queue_id into -d queue_id [queue_name] I have been exprimenting with adding queue name and I consider it harmfull. |cazio:/etc |# postsuper -d C8C8DF9D0 2555DF9CC deferred |postsuper: fatal: invalid directory name: 2555DF9CC |cazio:/etc |# postsuper -d C8C8DF9D0 2555DF9CC |postsuper: fatal: invalid directory name: 2555DF9CC |cazio:/etc |# postsuper -d 2555DF9CC active |cazio:/etc |# postsuper -d 2555DF9CC deferred |postsuper: 2555DF9CC: removed |postsuper: Deleted: 1 message |cazio:/etc |# postsuper -d C8C8DF9D0 |postsuper: C8C8DF9D0: removed |postsuper: Deleted: 1 message |cazio:/etc |# postsuper -d C8C8DF9D0 |cazio:/etc |# Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682246: postfix: postsuper man pages needs update on -d example
Package: postfix
Version: 2.9.3-2+b1
Severity: minor
Dear Maintainer,
The manual page of postfix's postsuper needs an update.
Currently it is not possible to copy and paste the provide example.
tail +2 has to be tail -n +2
because tail requires nowerdays the -n option to state number of lines
And quote character should just be the single quote character,
nothing special. So
awk ´BEGIN
becomes
awk 'BEGIN
and the closing quote also ´ to '
As unified diff:
--- man/man1/postsuper.1_from_2.9.3 2012-01-25 01:45:14.0 +0100
+++ man/man1/postsuper.12012-07-20 19:10:24.084079236 +0200
@@ -43,11 +43,11 @@
with exactly one recipient \fbu...@example.com\fR:
.sp
.nf
-mailq | tail +2 | grep -v '^ *(' | awk \'BEGIN { RS = }
+mailq | tail -n +2 | grep -v '^ *(' | awk 'BEGIN { RS = }
# $7=sender, $8=recipient1, $9=recipient2
{ if ($8 == u...@example.com $9 == )
print $1 }
-\' | tr -d '*!' | postsuper -d -
+ ' | tr -d '*!' | postsuper -d -
.fi
.sp
Specify \fB-d ALL\fR to remove all messages; for example, specify
I hope this Debian bugreport goes upstream.
Cheers
Geert Stappers
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#655124: possible [patch] netinst for wheezy missing r8169 driver on lemote fuloong
tag 655124 patch stop Hello debian-installer team, Please have a look at this possible patch that came along on the debian-mips mailinglist - Forwarded message from Arnaud Patard arnaud.pat...@rtp-net.org - Date: Mon, 09 Jul 2012 16:59:44 +0200 From: Arnaud Patard arnaud.pat...@rtp-net.org To: Michael Stevens mstev...@etla.org Cc: debian-m...@lists.debian.org Subject: Re: What is the status of Debian on Lemote Fuloong? Organization: RtpNet Message-ID: 87r4slgeu7@lebrac.rtp-net.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) Michael Stevens mstev...@etla.org writes: On Mon, Jul 09, 2012 at 02:30:07PM +, Code Blue wrote: On Sun, Jul 08, 2012 at 10:55:25AM +0200, Andreas Barth wrote: * Code Blue (codeb...@inbox.lv) [120708 10:32]: Can anybody point me to a source that describes exactly how to get this running? I have no idea how to install Debian on the Fuloong since I haven't found a bootable USB installer. see http://www.debian.org/releases/stable/installmanual and http://www.debian.org/releases/stable/mipsel/index.html.en for generic information. I usually use the images from http://d-i.debian.org/daily-images/mipsel/daily/loongson-2f/netboot/ and do netboot (please be aware that you either need to go back to the menu early to set question level to low, or you end up installing testing). If you have questions on that, please don't hesitate to ask here. Thank you, this helps a lot. It boots but it can't find the kernel module for the network adapter. I am surprised because if this is for loongson there is only one choice here, and it is not on the list. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655124 I'm guessing it's this debian-installer bug I reported some time ago? if you need the r8169 during installation, I guess that a patch like in the kernel like the following one may help (not tested at all). Index: debian/installer/mipsel/modules/mipsel-loongson-2f/nic-modules === --- debian/installer/mipsel/modules/mipsel-loongson-2f/nic-modules (revision 19204) +++ debian/installer/mipsel/modules/mipsel-loongson-2f/nic-modules (working copy) @@ -1 +1,2 @@ 8139too +r8169 Regards, Arnaud -- To UNSUBSCRIBE, email to debian-mips-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r4slgeu7@lebrac.rtp-net.org - End forwarded message - stappers@fulong:~ $ lsmod | grep ^r r8169 41527 0 rtc_cmos8329 0 stappers@fulong:~ $ uname -a Linux fulong 2.6.35-trunk-loongson-2f #1 Tue Aug 17 21:45:32 UTC 2010 mips64 GNU/Linux stappers@fulong:~ $ cat /proc/version Linux version 2.6.35-trunk-loongson-2f (Debian 2.6.35-1~experimental.2) (m...@debian.org) (gcc version 4.4.5 20100728 (prerelease) (Debian 4.4.4-8) ) #1 Tue Aug 17 21:45:32 UTC 2010 stappers@fulong:~ $ Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679711: URL to reproduce
In IRC channel #debian-nl was I told that Rhythmbox segfaults when starting the NME m3u stream at http://www.nmeradio.com/audio/stream.m3u Hopefully has #679711 now a URL to reproduce an crash. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679711: upstream bug report
In https://bugzilla.gnome.org/show_bug.cgi?id=679584 is a gdb backtrace about this bug. Man in the Middle between OFTC #debian-nl and Debian's BTS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#406114: having a tool like ping
reassign 406114 busybox-udeb stop On Fri, Jul 06, 2012 at 02:44:25PM +0200, Cyril Brulebois wrote: Philipp Kern pk...@debian.org (06/07/2012): On Fri, Jul 06, 2012 at 01:50:24PM +0400, Michael Tokarev wrote: it is really trivial to enable ping applet in busybox and close this bugreport for good. [???] Maybe it's a good idea to reassign it to busybox-udeb and fix it there finally, for good? I think that would be great. Seconded. Done. Thanks! Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549681: bug#549681: mkvmlinuz: use xz to compress vmlinuz-boxed initrd
On Sun, Jul 01, 2012 at 03:13:57PM -0400, Milan Kupcevic wrote: +if grep -q CONFIG_RD_XZ=y /boot/config-$release ; then + is_xz_supported=Yes +fi Have a look at this test statement +if test $is_xz_supported; then + XZ=xz --check=crc32 -8 +else + XZ=false +fi And have a look at these test statements: +test -z $verbose || echo === Creating compressed initrd image - if test `od -A n -c -N 2 $initrd` = 037 213; then + if test `xxd -p -l2 $initrd` = 1f8b; then + test -z $verbose || echo === $initrd is already gzip compressed + if test -n $is_xz_supported test $arch != prep; then + test -z $verbose || echo === recompressing to xz + elif test `xxd -p -l6 $initrd` = fd377a585a00; then + test -z $verbose || echo === $initrd is already xz compressed + test -z $verbose || echo === assuming $initrd was not compressed Notices that those tests are either test string = otherstring or are test --option $variable They here again a test --option $variable and a strange looking single test $variable @@ -317,7 +334,11 @@ WRAPPER=$objdir/wrapper vmlinuz=$work/vmlinuz.$arch if test -n $initrd; then -INITRD=-i $work/initrd.gz +if test $is_xz_supported; then + INITRD=-i $work/initrd.xz +else + INITRD=-i $work/initrd.gz +fi fi $WRAPPER -c -o $vmlinuz -p $arch $INITRD -D $objdir -W $work $kernel else Please use the more readable test -n $is_xz_supported Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#677177: Upstream has Fix building with --as-needed
Package: syslinux Severity: minor For your information: Upstream has Debian patch '008-as-needed' included. - Forwarded message from syslinux-bot for Micah Gersten mic...@ubuntu.com - Date: Mon, 11 Jun 2012 15:42:06 -0700 From: syslinux-bot for Micah Gersten mic...@ubuntu.com To: Syslinux commits mailing list syslinux-comm...@zytor.com Cc: t...@night-shade.org.uk, mic...@ubuntu.com, h...@linux.intel.com Subject: [syslinux:master] isohybrid: Fix building with --as-needed Message-ID: syslinux-5ccd0a7a5acc75a7f6c286875e1f0c149b8fc...@git.syslinux.org X-Mailer: Syslinux-git-log-daemon Reply-To: sysli...@zytor.com, mic...@ubuntu.com, t...@night-shade.org.uk, h...@linux.intel.com Commit-ID: 5ccd0a7a5acc75a7f6c286875e1f0c149b8fcdb5 Gitweb: http://www.syslinux.org/commit/5ccd0a7a5acc75a7f6c286875e1f0c149b8fcdb5 Author: Micah Gersten mic...@ubuntu.com AuthorDate: Mon, 11 Jun 2012 15:38:20 -0700 Committer: H. Peter Anvin h...@linux.intel.com CommitDate: Mon, 11 Jun 2012 15:38:20 -0700 isohybrid: Fix building with --as-needed The library link order was wrong. This patch was picked from Ubuntu. Reported-and-tested-by: Tim Fletcher t...@night-shade.org.uk Signed-off-by: H. Peter Anvin h...@linux.intel.com --- utils/Makefile |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/utils/Makefile b/utils/Makefile index 44cb54f..be73993 100644 --- a/utils/Makefile +++ b/utils/Makefile @@ -51,7 +51,7 @@ isohdpfx.c: $(ISOHDPFX) isohdpfxarray.pl $(PERL) isohdpfxarray.pl $(ISOHDPFX) $@ isohybrid: isohybrid.o isohdpfx.o - $(CC) $(LDFLAGS) -luuid -o $@ $^ + $(CC) $(LDFLAGS) -o $@ $^ -luuid gethostip: gethostip.o $(CC) $(LDFLAGS) -o $@ $^ ___ Syslinux-commits mailing list syslinux-comm...@zytor.com http://www.zytor.com/mailman/listinfo/syslinux-commits - End forwarded message - -- Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#648401: Harmfull with debconf
Hello ISC DHCP maintainers, Bug 648401, isc-dhcp-relay: dhcrelay(8) doesn't mention need for -i on server facing interface, is harmfull in combination with current debconf text. The text in +--| DHCP Relay |-+ | | | Please specify which network interface(s) the DHCP relay should | | attempt to configure. Multiple interface names should be entered| | as a space-separated list. | | | | Leave this field blank to allow for automatic detection and | | configuration of network interfaces by the DHCP relay, in which | | case only broadcast interfaces will be used (if possible). | | | | Interfaces the DHCP relay should listen on: | | | | __| | | | Ok | | | +-+ did trick me to enter only the interface I thought it should listen on. It took me several hours to find that it is actual asking: Enumerate all involved interfaces, so that remaining interfaces can be excluded. Leaving the interface list empty, did get my (two interface) DHCP relay working in the end. Having the patch --- dhcrelay.8.orig 2011-11-11 16:41:22.0 +1100 +++ dhcrelay.8 2011-11-11 16:43:01.0 +1100 @@ -178,7 +178,10 @@ interfaces may be specified by using more than one \fB-i\fR option. If no interfaces are specified on the command line, dhcrelay will identify all network interfaces, eliminating non-broadcast interfaces if possible, -and attempt to listen on all of them. +and attempt to listen on all of them. If you use -i, you should ensure you +include an -i option for the interface that is used to communicate with the +DHCP server. Otherwise reply packets from the DHCP server are likely to be +dropped. .TP -m \fIappend\fR|\fIreplace\fR|\fIforward\fR|\fIdiscard\fR Control the handling of incoming DHCPv4 packets which already contain in the manual page would have me saved some time and will surely save time for others. Thanks Cheers Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661369: marked as done (live-build: cannot change hostname)
On Sun, Feb 26, 2012 at 06:33:07PM +, Debian Bug Tracking System wrote: Your message dated Sun, 26 Feb 2012 19:22:30 +0100 with message-id 4f4a7866.3030...@progress-technologies.net and subject line Re: Bug#661369: live-build: cannot change hostname Package: live-build Version: 3.0~a45-1 Severity: normal Dear Maintainer, I cannot change the hostname. I have tried to change manually in config/binary: # $LB_HOSTNAME: set hostname # (Default: debian) LB_HOSTNAME=live but it doesn't work, the hostname is still debian. greetings Piotr has caused the Debian Bug report #661369, regarding live-build: cannot change hostname to be marked as done. This means that you claim that the problem has been dealt with. I wonder how. If the bugreport was invalid, please say so. If the bug was there, please tell how it was fixed. Regards Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653860: reprepro: missing Release in debian-installer directory
Package: reprepro
Version: 4.8.2-1
Severity: normaal
Hello reprepro maintainers,
When creating an udeb only aptable archive,
there is no Release file created in the debian-installer directory.
The Packages file is created. The regular aptable archive does
get a Release file and an empty Packages file.
It could be my ignorance, but to me it is strange behaviour of reprepro.
Creating a empty Package file, an unwanted / unneeded Release file
and neglecting to create the wanted / expected Release.
It is reproducable with the attached script.
Part of it output is:
aptablearchive/pool/main/a/anna/anna_1.33_mipsel.udeb
aptablearchive/dists/demo/Release
aptablearchive/dists/demo/main/binary-mipsel/Packages.gz
aptablearchive/dists/demo/main/binary-mipsel/Release
aptablearchive/dists/demo/main/binary-mipsel/Packages
aptablearchive/dists/demo/main/debian-installer/binary-mipsel/Packages.gz
aptablearchive/dists/demo/main/debian-installer/binary-mipsel/Packages
What is needed for a Release file in the debian-installer directory?
Cheers
Geert Stappers
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages reprepro depends on:
ii libarchive1 2.8.5-5 Multi-format archive and compressi
ii libbz2-1.0 1.0.6-1 high-quality block-sorting file co
ii libc6 2.13-24 Embedded GNU C Library: Shared lib
ii libdb5.15.1.29-1 Berkeley v5.1 Database Libraries [
ii libgpg-error0 1.10-1 library for common error values an
ii libgpgme11 1.2.0-1.4GPGME - GnuPG Made Easy
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
Versions of packages reprepro recommends:
ii apt 0.8.15.9 Advanced front-end for dpkg
Versions of packages reprepro suggests:
pn gnupg-agent none (no description available)
pn inoticoming none (no description available)
pn lzip none (no description available)
ii lzma 4.43-14Compression method of 7z format in
ii xz-utils 5.0.0-2XZ-format compression utilities
-- no debconf information
- End forwarded message -
--
Groeten
Geert Stappers
--
And is there a policy on top-posting vs. bottom-posting?
Yes.
#!/bin/bash
#
rm -rf demo # fresh start
mkdir demo # new directory
cd demo
mkdir conf aptablearchive
#
cat HERE conf/distributions
#
Origin: demo
Label: demo
Suite: stable
Codename: demo
Version: 3.14159
Architectures: mipsel
Components: main
UDebComponents: main
Description: Just for Demonstrating purpose
# SignWith: nope
DebOverride: override
UDebOverride: override
#
# l l
HERE
echo '# logically empty' conf/override
# get an udeb
U=anna_1.33_mipsel.udeb
wget -q http://ftp.nl.debian.org/debian/pool/main/a/anna/${U}
# now reproduce a repository
reprepro --basedir ./ \
--outdir ./aptablearchive/ \
--component main \
includeudeb demo ${U}
echo All files:
find aptablearchive -type f
echo Releases:
find aptablearchive -name Release
echo 'Packages (plus size):'
find aptablearchive -name Packages -ls
#
echo '# suggested clean up: rm -rf demo'
#
# l l
Bug#653774: reprepro: minor typo in manual page
Package: reprepro Version: 4.8.2-1 Severity: minor Hello reprepro maintainers, Thanks for providing the neat tool 'reprepro'. The nice program is a reason for report this minor typo. At the bottom of the manual page is an 'e' slipped in. The line (e.g. by using reportbug reperepro under Debian) should be in my humble opinion (e.g. by using reportbug reprepro under Debian) If I understand correct, then is the manual page hand build ( as in not generate from another file ). So this what I mean in as an unified diff --- a/docs/reprepro.1 +++ b/docs/reprepro.1 @@ -2469,7 +2469,7 @@ for interruption. .SH REPORTING BUGS Report bugs or wishlist requests to the Debian BTS .br -(e.g. by using \fBreportbug reperepro\fP under Debian) +(e.g. by using \fBreportbug reprepro\fP under Debian) .br or directly to .MTO brl...@debian.org Cheers Geert Stappers -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages reprepro depends on: ii libarchive1 2.8.5-5 Multi-format archive and compressi ii libbz2-1.0 1.0.6-1 high-quality block-sorting file co ii libc6 2.13-24 Embedded GNU C Library: Shared lib ii libdb5.15.1.29-1 Berkeley v5.1 Database Libraries [ ii libgpg-error0 1.10-1 library for common error values an ii libgpgme11 1.2.0-1.4GPGME - GnuPG Made Easy ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages reprepro recommends: ii apt 0.8.15.9 Advanced front-end for dpkg Versions of packages reprepro suggests: pn gnupg-agent none (no description available) pn inoticoming none (no description available) pn lzip none (no description available) ii lzma 4.43-14Compression method of 7z format in ii xz-utils 5.0.0-2XZ-format compression utilities -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639616: iceweasel 6: Couldn't load XPCOM
Package: iceweasel Version: 6.0-4 Severity: important When starting iceweasel, I get: Couln't load XPCOM $ iceweasel Couldn't load XPCOM. $ iceweasel -safe-mode Couldn't load XPCOM. $ MOZILLA_DISABLE_PLUGINS=1 iceweasel -safe-mode Couldn't load XPCOM. -- Package-specific info: -- Addons package information -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 3.0.0-1-powerpc Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages iceweasel depends on: ii debianutils 4.0.2 Miscellaneous utilities specific t ii fontconfig2.8.0-3generic font configuration library ii libc6 2.13-10Embedded GNU C Library: Shared lib ii libgcc1 1:4.6.1-4 GCC support library ii libgdk-pixbuf2.0-02.23.5-3 GDK Pixbuf library ii libglib2.0-0 2.28.6-1 The GLib library of C routines ii libgtk2.0-0 2.24.5-4 GTK+ graphical user interface libr ii libnspr4-0d 4.8.9-1NetScape Portable Runtime Library ii libstdc++64.6.1-4GNU Standard C++ Library v3 ii procps1:3.2.8-11 /proc file system utilities ii xulrunner-6.0 6.0-4 XUL + XPCOM application runner iceweasel recommends no packages. Versions of packages iceweasel suggests: ii libgssapi-krb5-21.9.1+dfsg-2 MIT Kerberos runtime libraries - k ii libkrb531.9.1+dfsg-2 transitional package for MIT Kerbe pn mozplugger none (no description available) pn ttf-lyx | latex-xft-fonts none (no description available) pn ttf-mathematica4.1 none (no description available) pn xfonts-mathml none (no description available) Versions of packages xulrunner-6.0 depends on: ii libasound2 1.0.24.1-3 shared library for ALSA applicatio ii libatk1.0-0 2.0.1-2 ATK accessibility toolkit ii libbz2-1.0 1.0.5-6 high-quality block-sorting file co ii libc6 2.13-10 Embedded GNU C Library: Shared lib ii libcairo2 1.10.2-6.1 The Cairo 2D vector graphics libra ii libdbus-1-3 1.4.14-1 simple interprocess messaging syst ii libevent-1.4-2 1.4.14b-stable-1 asynchronous event notification li ii libfontconfig1 2.8.0-3 generic font configuration library ii libfreetype62.4.6-2 FreeType 2 font engine, shared lib ii libgcc1 1:4.6.1-4GCC support library ii libgdk-pixbuf2.0-0 2.23.5-3 GDK Pixbuf library ii libglib2.0-02.28.6-1 The GLib library of C routines ii libgtk2.0-0 2.24.5-4 GTK+ graphical user interface libr ii libhunspell-1.2-0 1.2.14-4 spell checker and morphological an ii libjpeg88c-2 Independent JPEG Group's JPEG runt ii libmozjs6d 6.0-4Mozilla SpiderMonkey JavaScript li ii libnspr4-0d 4.8.9-1 NetScape Portable Runtime Library ii libnss3-1d 3.12.11-1Network Security Service libraries ii libpango1.0-0 1.28.4-3 Layout and rendering of internatio ii libpixman-1-0 0.22.2-1 pixel-manipulation library for X a ii libreadline66.2-4GNU readline and history libraries ii libsqlite3-03.7.7-2 SQLite 3 shared library ii libstartup-notification 0.12-1 library for program launch feedbac ii libstdc++6 4.6.1-4 GNU Standard C++ Library v3 ii libvpx0 0.9.7.p1-1 VP8 video codec (shared library) ii libx11-62:1.4.4-1X11 client-side library ii libxext62:1.3.0-3X11 miscellaneous extension librar ii libxrender1 1:0.9.6-2X Rendering Extension client libra ii libxt6 1:1.1.1-2X11 toolkit intrinsics library ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages xulrunner-6.0 suggests: ii libcanberra0 0.28-1 a simple abstract interface for pl ii libdbus-glib-1-2 0.94-4 simple interprocess messaging syst ii libgconf2-4 2.32.4-1 GNOME configuration database syste ii libgnomeui-0 2.24.5-1 GNOME user interface library - run ii libgnomevfs2-01:2.24.4-1 GNOME Virtual File System (runtime ii libnotify40.7.3-2sends desktop notifications to a n -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble?
Bug#635612: Beyond tests
retitle 635612 fakeroot: `fakeroot debian/rules binary` fails test severity 635612 minor thanks On Fri, Jul 29, 2011 at 05:13:25PM +, Clint Adams wrote: On Wed, Jul 27, 2011 at 06:33:08PM +0200, Geert Stappers wrote: - fakeroot debian/rules binary So the problem here is that fakeroot cannot be run within fakeroot (see bug#409856). In the interim, you can build with pbuilder/cowbuilder, dpkg-buildpackage, debuild, or debian/rules build fakeroot debian/rules binary doing dpkg-buildpackage -rfakeroot -uc -us did get me beyond the test. The key is to run the build target outside of fakeroot so that the tests run in a cleaner environment, and then only run the binary target specifically under your system fakeroot. We should probably test for this condition and emit some relevant warning. Fine for me. Bugreport is triaged. Feel free to close. Cheers Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632192: [PATCH] add QEMU_LD_PREFIX environment variable
On Thu, Jul 28, 2011 at 01:24:47PM +0200, Johannes Schauer wrote:
@Geert Stappers:
you are patching bsd-user/main.c and darwin-user/main.c as well. I take
it that you did test your changes on those platforms? does it work there
as well? I have no clue of darwin but is it really useful there?
They only check I did,
was checking if BSD and Darwing have getenv(), they do.
I consider the
+/* read interp_prefix from environment variable */
+if (getenv(QEMU_LD_PREFIX) != NULL) {
+interp_prefix = getenv(QEMU_LD_PREFIX);
to Darwin and BSD as harmless. In fact only reason for those additional
lines were to bring attention to those operating systems.
With the idea^Whope of better acception from upstream.
Cheers
Geert Stappers
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635612: FTBFS: fakeroot: not passing tests
Package: fakeroot Version: 1.16-1 Severity: important Hello, While building fakeroot, I did get this output make[3]: `defs' is up to date. make[3]: Leaving directory `/usr/src/fakeroot-1.16/obj-sysv/test' /usr/bin/make check-TESTS make[3]: Entering directory `/usr/src/fakeroot-1.16/obj-sysv/test' FAIL: t.chmod_dev FAIL: t.echoarg PASS: t.falsereturn FAIL: t.mknod FAIL: t.no_ld_preload FAIL: t.no_ld_preload_link FAIL: t.option FAIL: t.tar FAIL: t.touchinstall FAIL: t.truereturn = 9 of 10 tests failed Please report to cl...@debian.org = make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/usr/src/fakeroot-1.16/obj-sysv/test' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/usr/src/fakeroot-1.16/obj-sysv/test' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/usr/src/fakeroot-1.16/obj-sysv' make: *** [build-stamp] Error 2 $ and NO Debian package. For me is this a Fails To Build From Source -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages fakeroot depends on: ii libc6 2.13-11Embedded GNU C Library: Shared lib fakeroot recommends no packages. fakeroot suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635612: Reproducing
To reproduce: - have an up-to-date amd64 unstable - apt-get source fakeroot - cd fakeroot-1.16 - fakeroot debian/rules binary hth Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635625: fakechroot: FTBFS[adm64]: fatal error: sys/cdefs.h not found
Package: fakechroot Version: 2.14-1 Severity: important Hello, On an amd64 I get from `fakeroot debian/rules binary` this fatal output Making all in src make[4]: Entering directory `/usr/src/fakechroot-2.14/build-tree-lib-biarch/src' /bin/sh ../libtool --tag=CC --mode=compile gcc -m32 -DHAVE_CONFIG_H -I. -I../../src -I..-g -Wall -Wno-deprecated-declarations -g -O2 -c -o access.lo ../../src/access.c libtool: compile: gcc -m32 -DHAVE_CONFIG_H -I. -I../../src -I.. -g -Wall -Wno-deprecated-declarations -g -O2 -c ../../src/access.c -fPIC -DPIC -o .libs/access.o In file included from /usr/include/errno.h:29:0, from ../../src/libfakechroot.h:21, from ../../src/access.c:23: /usr/include/features.h:356:25: fatal error: sys/cdefs.h: No such file or directory compilation terminated. make[4]: *** [access.lo] Error 1 make[4]: Leaving directory `/usr/src/fakechroot-2.14/build-tree-lib-biarch/src' make[3]: *** [all-recursive] Error 1 It is a Fails To Build From Source ... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages fakechroot depends on: ii libc6 2.13-11Embedded GNU C Library: Shared lib fakechroot recommends no packages. Versions of packages fakechroot suggests: ii libc6-i3862.13-11Embedded GNU C Library: 32-bit sha -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635625: swapping 32 64
tags +patch thanks Hello, The debian/rules file has these lines ( note the 32-bit stuff for the 64-bit CPU ) ifeq ($(DEB_HOST_ARCH),amd64) BIARCH_LIBDIR:= /usr/lib32 BIARCH_HOST_GNU_TYPE := i486-linux-gnu BIARCH_CC:= $(CC) -m32 endif ifeq ($(DEB_HOST_ARCH),i386) BIARCH_LIBDIR:= /usr/lib64 BIARCH_HOST_GNU_TYPE := x86_64-linux-gnu BIARCH_CC:= $(CC) -m64 endif Here a (inline) patch to swap it === modified file 'debian/rules' --- debian/rules2010-12-18 01:19:11 + +++ debian/rules2011-07-27 19:49:38 + @@ -8,15 +8,15 @@ ifneq (,$(findstring :$(DEB_HOST_ARCH):,:amd64:i386:ppc64:s390:sparc:kfreebsd-amd64:)) ifeq ($(DEB_HOST_ARCH),amd64) +BIARCH_LIBDIR:= /usr/lib64 +BIARCH_HOST_GNU_TYPE := x86_64-linux-gnu +BIARCH_CC:= $(CC) -m64 +endif +ifeq ($(DEB_HOST_ARCH),i386) BIARCH_LIBDIR:= /usr/lib32 BIARCH_HOST_GNU_TYPE := i486-linux-gnu BIARCH_CC:= $(CC) -m32 endif -ifeq ($(DEB_HOST_ARCH),i386) -BIARCH_LIBDIR:= /usr/lib64 -BIARCH_HOST_GNU_TYPE := x86_64-linux-gnu -BIARCH_CC:= $(CC) -m64 -endif ifeq ($(DEB_HOST_ARCH),ppc64) BIARCH_LIBDIR:= /usr/lib32 BIARCH_HOST_GNU_TYPE := powerpc-linux-gnu Find the same patch attached Cheers Geert Stappers === modified file 'debian/rules' --- debian/rules 2010-12-18 01:19:11 + +++ debian/rules 2011-07-27 19:49:38 + @@ -8,15 +8,15 @@ ifneq (,$(findstring :$(DEB_HOST_ARCH):,:amd64:i386:ppc64:s390:sparc:kfreebsd-amd64:)) ifeq ($(DEB_HOST_ARCH),amd64) +BIARCH_LIBDIR:= /usr/lib64 +BIARCH_HOST_GNU_TYPE := x86_64-linux-gnu +BIARCH_CC:= $(CC) -m64 +endif +ifeq ($(DEB_HOST_ARCH),i386) BIARCH_LIBDIR:= /usr/lib32 BIARCH_HOST_GNU_TYPE := i486-linux-gnu BIARCH_CC:= $(CC) -m32 endif -ifeq ($(DEB_HOST_ARCH),i386) -BIARCH_LIBDIR:= /usr/lib64 -BIARCH_HOST_GNU_TYPE := x86_64-linux-gnu -BIARCH_CC:= $(CC) -m64 -endif ifeq ($(DEB_HOST_ARCH),ppc64) BIARCH_LIBDIR:= /usr/lib32 BIARCH_HOST_GNU_TYPE := powerpc-linux-gnu
Bug#632954: Crossreference to Bug#635625
This E-mail is to make a rossreference to Bug#635625 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635625 ) which is about a FTBFS of fakechroot -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632192: [PATCH 2/2] add QEMU_LD_PREFIX environment variable for BSD and Darwin
---
bsd-user/main.c|5 +
darwin-user/main.c |5 +
2 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/bsd-user/main.c b/bsd-user/main.c
index 6018a41..ed639de 100644
--- a/bsd-user/main.c
+++ b/bsd-user/main.c
@@ -763,6 +763,11 @@ int main(int argc, char **argv)
cpudef_setup(); /* parse cpu definitions in target config file (TBD) */
#endif
+/* read interp_prefix from environment variable */
+if (getenv(QEMU_LD_PREFIX) != NULL) {
+interp_prefix = getenv(QEMU_LD_PREFIX);
+}
+
optind = 1;
for(;;) {
if (optind = argc)
diff --git a/darwin-user/main.c b/darwin-user/main.c
index 35196a1..f808521 100644
--- a/darwin-user/main.c
+++ b/darwin-user/main.c
@@ -751,6 +751,11 @@ int main(int argc, char **argv)
if (argc = 1)
usage();
+/* read interp_prefix from environment variable */
+if (getenv(QEMU_LD_PREFIX) != NULL) {
+interp_prefix = getenv(QEMU_LD_PREFIX);
+}
+
optind = 1;
for(;;) {
if (optind = argc)
--
1.7.5.4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632192: [PATCH 0/3] Reworked patches for #632192
Hello, This E-mail introduces three E-mails with patches. They are against the pkg-qemu git repository branch debian-unstable The first patch should be from: Johannes Schauer jo...@pyneo.org the others are based upon it. Cheers Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632192: [PATCH 3/3] debian/qemu-user.1: QEMU_LD_PREFIX environment documented
--- debian/qemu-user.1 | 14 -- 1 files changed, 12 insertions(+), 2 deletions(-) diff --git a/debian/qemu-user.1 b/debian/qemu-user.1 index 84c07aa..8a7ea50 100644 --- a/debian/qemu-user.1 +++ b/debian/qemu-user.1 @@ -1,5 +1,5 @@ -.\ $Id: qemu-user.1 234 2007-02-07 22:57:18Z guillem $ -.TH qemu\-user 1 2007-02-08 0.9.0 Debian +.\ nroff file, manually crafted (not generated from another source) +.TH qemu\-user 1 2011-07-26 0.14.1 Debian .SH NAME qemu\-user \- QEMU User Emulator .SH SYNOPSIS @@ -31,6 +31,16 @@ Activate log (logfile=\fI/tmp/qemu.log\fP) .TP .BR \-p \fIpagesize\fP Set the host page size to 'pagesize'. +.RE +.SH ENVIRONMENT +.PP +\fBQEMU_LD_PREFIX\fR +.RS 4 +If $QEMU_LD_PREFIX is set, it's value is used as prefix to \ + the ELF interpreter. \ +This is doing the same as the option \fB\-L\fR, \ +but the command line option takes precedence. +.RE .SH SEE ALSO .BR qemu (1), .BR qemu\-img (1). -- 1.7.5.4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632192: [PATCH 1/3] add QEMU_LD_PREFIX environment variable
From: Johannes Schauer jo...@pyneo.org
---
linux-user/main.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/linux-user/main.c b/linux-user/main.c
index 0d627d6..c802175 100644
--- a/linux-user/main.c
+++ b/linux-user/main.c
@@ -2758,6 +2758,11 @@ int main(int argc, char **argv, char **envp)
cpudef_setup(); /* parse cpu definitions in target config file (TBD) */
#endif
+/* read interp_prefix from environment variable */
+if (getenv(QEMU_LD_PREFIX) != NULL) {
+interp_prefix = getenv(QEMU_LD_PREFIX);
+}
+
optind = 1;
for(;;) {
if (optind = argc)
--
1.7.5.4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632192: [PATCH 2/3] add QEMU_LD_PREFIX environment variable for BSD and Darwin
---
bsd-user/main.c|5 +
darwin-user/main.c |5 +
2 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/bsd-user/main.c b/bsd-user/main.c
index 6b12f8b..cb98fa6 100644
--- a/bsd-user/main.c
+++ b/bsd-user/main.c
@@ -763,6 +763,11 @@ int main(int argc, char **argv)
cpudef_setup(); /* parse cpu definitions in target config file (TBD) */
#endif
+/* read interp_prefix from environment variable */
+if (getenv(QEMU_LD_PREFIX) != NULL) {
+interp_prefix = getenv(QEMU_LD_PREFIX);
+}
+
optind = 1;
for(;;) {
if (optind = argc)
diff --git a/darwin-user/main.c b/darwin-user/main.c
index 175e12f..5a67164 100644
--- a/darwin-user/main.c
+++ b/darwin-user/main.c
@@ -752,6 +752,11 @@ int main(int argc, char **argv)
/* init debug */
cpu_set_log_filename(DEBUG_LOGFILE);
+/* read interp_prefix from environment variable */
+if (getenv(QEMU_LD_PREFIX) != NULL) {
+interp_prefix = getenv(QEMU_LD_PREFIX);
+}
+
optind = 1;
for(;;) {
if (optind = argc)
--
1.7.5.4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632954: background information
More background information about multiarch is at http://lists.debian.org/debian-devel-announce/2011/06/msg2.html And some background information about me, I'm considering to NMU Looking forward for a response Groeten Geert Stappers signature.asc Description: Digital signature
Bug#632954: make fakechroot multiarch
On Thu, Jul 07, 2011 at 05:51:11PM +0200, Johannes Schauer wrote: On Thu, Jul 07, 2011 at 02:28:04PM +0200, Geert Stappers wrote: bigsnip/ At least is it hard to see what the actual multiarch enabling is. The enabling is in increasing the compatibility level to 9, build depending on debhelper (= 8.1.3), and setting Multi-Arch: same for the shared library. Now I do understand why the patch did look so intrusive. Thanks for elaborating. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632954: make fakechroot multiarch
On Thu, Jul 07, 2011 at 12:50:54PM +0200, Johannes Schauer wrote: Hi, I prepared a patch that enables multiarch for fakechroot. Please have a look at it and see that everything is okay. To me does look this NMU as a complete rewrite of the debian directory. At least is it hard to see what the actual multiarch enabling is. Cheers Stappers who could resist to remove the patch tag +++ fakechroot-2.14/debian/control2011-07-07 12:39:27.0 +0200 -Standards-Version: 3.9.1 +Standards-Version: 3.9.2 Build-Depends: - libc6-dev-i386 [amd64], - libc6-dev-amd64 [i386], - libc6-dev-powerpc [ppc64], - libc6-dev-s390x [s390], - libc6-dev-sparc64 [sparc], - libc0.1-dev-i386 [kfreebsd-amd64], - gcc-multilib [amd64 i386 powerpc s390 sparc kfreebsd-amd64], - debhelper (= 7.0.50~) + autotools-dev, + debhelper (= 8.1.3) Homepage: http://fakechroot.alioth.debian.org/ -Vcs-Browser: http://bazaar.launchpad.net/~dexter/fakechroot/sid/files -Vcs-Bzr: lp:fakechroot +Vcs-Browser: https://github.com/fakechroot/fakechroot +Vcs-Git: git://github.com/fakechroot/fakechroot.git snip/ diff -Nru fakechroot-2.14/debian/rules fakechroot-2.14/debian/rules --- fakechroot-2.14/debian/rules 2010-12-18 02:12:23.0 +0100 +++ fakechroot-2.14/debian/rules 2011-07-07 12:09:15.0 +0200 @@ -1,97 +1,4 @@ ninety-seven lines deleted, four lines inserted. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632192: FWIW debian/qemu-user-static.README.Debian
For What it's Worth: In the file debian/qemu-user-static.README.Debian is this text * Configuring qemu-user-static to use in a foreign chroot When used with binfmt, qemu-user-ARCH-static can be configured to run a foreign chroot. The qemu-user-ARCH-static binary should be copied (or better hard linked) into the chroot in /usr/bin. Then the chroot can be entered and used like a normal chroot. I haven't played with it, but it seems to help for polystrap Cheers Geert Stappers signature.asc Description: Digital signature
Bug#632192: FWIW debian/qemu-user-static.README.Debian
On Thu, Jun 30, 2011 at 11:33:27PM +0200, Marcus Osdoba wrote: Am 30.06.2011 23:15, schrieb Geert Stappers: When used with binfmt, qemu-user-ARCH-static can be configured to run a foreign chroot. The qemu-user-ARCH-static binary should be copied (or better hard linked) into the chroot in /usr/bin. Then the chroot can be entered and used like a normal chroot. Am I missing something? That was already done in polystrap: 36073d0c9a389048a7f6a4cd4e9cd28ed1bc32a9 # copy qemu usermode binary if [ $ARCH != `dpkg --print-architecture` ]; then case $ARCH in alpha|arm|armeb|i386|m68k|mips|mipsel|ppc64|sh4|sh4eb|sparc|sparc64) cp `which qemu-$ARCH-static` $ROOTDIR/usr/bin;; amd64) cp `which qemu-x86_64-static` $ROOTDIR/usr/bin;; armel) cp `which qemu-arm-static` $ROOTDIR/usr/bin;; lpia) cp `which qemu-i386-static` $ROOTDIR/usr/bin;; powerpc) cp `which qemu-ppc-static` $ROOTDIR/usr/bin;; *) echo unknown architecture: $ARCH; exit 1;; esac fi /36073d0c9a389048a7f6a4cd4e9cd28ed1bc32a9 You are right, that copying is already done in polystrap. Stappers who found meanwhile the variable 'interp_prefix' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627837: [b...@decadent.org.uk: Uploading linux-2.6 (2.6.39-2)]
This bugreport, #627837, is allready tagged 'pending'. The idea behind this forward is to add some further information. I think it helps, at least Hopes this helps Geert Stappers - Forwarded message from Ben Hutchings b...@decadent.org.uk - Date: Sun, 05 Jun 2011 05:01:48 +0100 From: Ben Hutchings b...@decadent.org.uk To: Debian kernel maintainers debian-ker...@lists.debian.org Cc: debian-rele...@lists.debian.org Subject: Uploading linux-2.6 (2.6.39-2) X-Mailer: Evolution 2.32.3 I intend to upload linux-2.6 to unstable early this week. This will include stable update 2.6.39.1 and restoration of aufs support for use in Debian Live. Stable update 2.6.39.1 includes an ABI change, so we will probably have to change the binary package names. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. - End forwarded message - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627837: linux-2.6: Aufs apparently silently dropped, breaking debian-live
On Sun, May 29, 2011 at 10:16:40PM +0200, Daniel Baumann wrote: On 05/29/2011 10:04 PM, Daniel Baumann wrote: On 05/29/2011 09:53 PM, Julien Cristau wrote: Maybe it was ready in your mind, but it wasn't in debian-kernel svn or mailing list (and as far as I can tell the kernel maintainers even checked aufs git before the .39 upload, and didn't find any recent changes there). So yeah, that's exactly the problem. no; aufs.git was up2date. in time. way before. oh.. and before you ask.. 'way before' means 'at least 2011-04-18, but possibly even earlier' (yes, that really is a month before .39 was released). And what is the URL for aufs.git? And where is that information shared before? And frankly, I don't have time to check the stated facts. What I do like to see, is that this bug report is about solving an issue, NOT about who should have done what and when. So far my attempt to stop the fight. Now going forward to a solution. The previous provide URLs got some how line wrapped. In this resend they should without the line break. http://vcs.progress-linux.org/?p=packages/linux-2.6.git;a=commitdiff;h=26a2fd380e516f1df527c0357334eb5e10cdccb3 http://vcs.progress-linux.org/?p=packages/linux-2.6.git;a=commitdiff;h=973422c91686a621ecd81db1813ed3e77a837b2c HTH Stappers signature.asc Description: Digital signature
Bug#625507: acer-wmi developer says the module doesn't do anything on the aspire one
Did the driver work on this hardware in earlier kernel versions? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619827: linux-source-2.6.38: [linux-dvb] cx88-blackbird broken (since 2.6.37)
On Sat, Apr 02, 2011 at 08:01:15PM +0200, Andreas Huber wrote: please review this simple fix! Please let us know when a complete fix has been accepted upstream. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#583689: USB and RTC for loongson-2f
Hello, Attached is a patch against Debian Kernel SVN repository. It makes USB keyboard possible and setting the RTC on the loongson-2f Groeten Geert Stappers Index: debian/config/mipsel/config.loongson-2f === --- debian/config/mipsel/config.loongson-2f (revision 16146) +++ debian/config/mipsel/config.loongson-2f (working copy) @@ -14,6 +14,9 @@ ## CONFIG_LEMOTE_MACH2F=y CONFIG_CS5536_MFGPT=y +CONFIG_LOONGSON_UART_BASE=y +CONFIG_LOONGSON_MC146818=y +CONFIG_RWSEM_GENERIC_SPINLOCK=y ## ## file: arch/mips/kernel/cpufreq/Kconfig @@ -71,6 +74,21 @@ CONFIG_USB=m ## +## file: drivers/usb/host/Kconfig +## +CONFIG_USB_EHCI_HCD=m +# CONFIG_USB_EHCI_ROOT_HUB_TT is not set +CONFIG_USB_ISP116X_HCD=m +CONFIG_USB_OHCI_HCD=m +CONFIG_USB_UHCI_HCD=m +CONFIG_USB_SL811_HCD=m + +## +## file: drivers/usb/mon/Kconfig +## +CONFIG_USB_MON=y + +## ## file: drivers/video/Kconfig ## CONFIG_VIDEO_OUTPUT_CONTROL=y signature.asc Description: Digital signature
Bug#583689: Not yet support for loongson-2f
found 583689 2.6.34-1~experimental.2 thanks Hello Debian Kernel people, Version 2.6.34-1~experimental.2 says [ 0.764000] /build/buildd-linux-2.6_2.6.34-1~exprimental.2-mipsel-ZShPn4/linux-2.6-2.6.34/debian/build/source_mipsel_none/drivers/rtc/hctosys.c: unable open rtc device (rtc0) And also [ 0.912000] ata1.00: ATA-8: WDC WD1600BEVT-22ZCT0, 11.01A11, max UDMA/133 [ 0.916000] ata1.00: 312581808 sectors, mult 16: LBA48 [ 0.932000] ata1.00: configured for UDMA/100 [ 0.936000] scsi 0:0:0:0 Direct-Access ATA WDC WD1600BEVT-2 11.0 PQ: 0 ANSI: 5 [ 0.94] VFS: Cannot open root device hda1 or unknown-block(0,0) So it is too early to close bugreport 583689 Groeten Geert Stappers signature.asc Description: Digital signature
Bug#583689: FYI: 2.6.35-rc5-loongson-2f does see disk
For you information, on version 2.6.35-rc5-loongson-2f there is still the RTC error, but the harddisk is seen. (version 2.6.34 doesn't see a disk) dmesg output [0.732000] /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [0.736000] Initalizing network drop monitor service [0.916000] ata1.00: ATA-8: WDC WD1600BEVT-22ZCT0, 11.01A11, max UDMA/133 [0.92] ata1.00: 312581808 sectors, multi 16: LBA48 [0.932000] ata1.00: configured for UDMA/100 [0.936000] scsi 0:0:0:0: Direct-Access ATA WDC WD1600 BEVT-2 11.0 PQ: 0 ANSI: 5 [0.94] ata2: port disabled. ignoring. [0.94] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks : (160 GB/149 GiB) [0.944000] sd 0:0:0:0: [sda] Write Protect is off [0.948000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [0.948000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [0.952000] sda: sda1 sda2 sda3 sda4 [0.968000] sd 0:0:0:0: [sda] Attached SCSI disk [0.976000] EXT3-fs: barriers not enabled [0.984000] kjournald starting. Commit interval 5 seconds [0.988000] EXT3-fs (sda1): mounted filesystem with ordered data mode [0.992000] VFS: Mounted root (ext3 filesystem) readonly on device 8:1. hth gst -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583689: loongson-2f is missing USB Host Controller
Hello Debian Kernel People, On both 2.6.34 and 2.6.35 for the MIPSEL flavour loonson-2f is a USB Host controller missing. Missing as is in Not compiled in the kernel, not even as a module. This is what went during build in the .config file: | # | # USB Host Controller Drivers | # | CONFIG_USB_C67X00_HCD=m | CONFIG_USB_XHCI_HCD=m | # CONFIG_USB_XHCI_HCD_DEBUGGING is not set | # CONFIG_USB_EHCI_HCD is not set | # CONFIG_USB_OXU210HP_HCD is not set | CONFIG_USB_ISP116X_HCD=m | # CONFIG_USB_ISP1760_HCD is not set | # CONFIG_USB_ISP1362_HCD is not set | # CONFIG_USB_OHCI_HCD is not set | # CONFIG_USB_UHCI_HCD is not set | CONFIG_USB_U132_HCD=m | # CONFIG_USB_SL811_HCD is not set | CONFIG_USB_R8A66597_HCD=m | CONFIG_USB_WHCI_HCD=m | CONFIG_USB_HWA_HCD=m This is what aba requested in http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=config.2.6.34-1~experimental.1;att=3;bug=583689 | # | # USB Host Controller Drivers | # | # CONFIG_USB_C67X00_HCD is not set | # CONFIG_USB_XHCI_HCD is not set | CONFIG_USB_EHCI_HCD=y | CONFIG_USB_EHCI_ROOT_HUB_TT=y | # CONFIG_USB_EHCI_TT_NEWSCHED is not set | # CONFIG_USB_OXU210HP_HCD is not set | # CONFIG_USB_ISP116X_HCD is not set | # CONFIG_USB_ISP1760_HCD is not set | # CONFIG_USB_ISP1362_HCD is not set | CONFIG_USB_OHCI_HCD=y | # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set | # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set | CONFIG_USB_OHCI_LITTLE_ENDIAN=y | CONFIG_USB_UHCI_HCD=m | # CONFIG_USB_SL811_HCD is not set | # CONFIG_USB_R8A66597_HCD is not set | CONFIG_USB_WHCI_HCD=m | CONFIG_USB_HWA_HCD=m | # CONFIG_USB_GADGET_MUSB_HDRC is not set It is at least 'CONFIG_USB_OHCI_HCD=y' that should come back in the .config file. Groeten Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583689: Not yet support for loongson-2f
# Op 20100723 om 20:06 schreef Martin Michlmayr: # * Bastian Blank wa...@debian.org [2010-07-23 20:24]: # [ 0.94] VFS: Cannot open root device hda1 or unknown-block(0,0) # # You have to supply a correct initramfs. # # No, it should be built in (mips/mipsel don't use initramfs). # found 583689 2.6.34-1~experimental.2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589397: debmirror: allow creating group writeable directories
Package: debmirror
Version: 1:2.4.4
Severity: normal
Hallo Frans,
My debmirror is also updated by another unix user
as the unix user that does `debmirror`.
To allow both operating system user to update the archive,
I have put them in the same unix group and SGID the dir.
However the debmirror does 'mkdir' hardcoded with mode 755
and blocks so the user on updates in the same directory.
My workaround is now
--- debmirror.upstream 2010-03-25 19:13:29.0 +0100
+++ debmirror 2010-07-17 12:42:17.0 +0200
@@ -2253,7 +2253,7 @@
$current.=$part/;
if (! $seen{$current}) {
if (! -d $current) {
- mkdir ($current, 0755) or die mkdir failed: $!;
+ mkdir ($current, 0775) or die mkdir failed: $!;
debug(Created directory: $current);
}
$seen{$current}=1;
An cleaner solution would be
--- debmirror.upstream 2010-03-25 19:13:29.0 +0100
+++ debmirror UNTESTED
@@ -2253,7 +2253,7 @@
$current.=$part/;
if (! $seen{$current}) {
if (! -d $current) {
- mkdir ($current, 0755) or die mkdir failed: $!;
+ mkdir ($current, (0777 and not(umask))) or die mkdir failed: $!;
debug(Created directory: $current);
}
$seen{$current}=1;
The '0777 and not(umask)' will create group writeable directory when
the umask is 002. With default umask, 022, becomes the directory
only owner writeable.
Groeten
Geert Stappers
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589410: apt-cacher-ng: allow creating group writeable directories
Package: apt-cacher-ng
Version: 0.4.7-1
Severity: normal
Hello Eduard,
My apt cache is also updated by another unix user
as the unix user 'apt-cacher-ng'.
To allow both operating system user to update the archive,
I have put them in the same unix group and SGID the dir.
However apt-cacher-ng does 'mkdir' hardcoded with mode 755
and blocks so the user on updating in the same directory.
My workaround is now
--- source/meta.cc.pristine
+++ source/meta.cc
@@ -35,7 +35,7 @@
for(UINT pos=0; pospath.size(); pos=path.find(/, pos+1))
{
if(pos0)
-mkdir(path.substr(0,pos).c_str(), 00755);
+mkdir(path.substr(0,pos).c_str(), 00775);
}
}
/*
A cleaner solution would be
--- source/meta.cc.pristine
+++ source/meta.cc. UNTESTED
@@ -35,7 +35,7 @@
for(UINT pos=0; pospath.size(); pos=path.find(/, pos+1))
{
if(pos0)
-mkdir(path.substr(0,pos).c_str(), 00755);
+mkdir(path.substr(0,pos).c_str(), (00777 !umask));
}
}
/*
The '0777 and not(umask)' will create group writeable directory when
the umask is 002. With default umask, 022, becomes the directory
only owner writeable.
Groeten
Geert Stappers
signature.asc
Description: Digital signature
Bug#320666: closed by Sandro Tosi mo...@debian.org (apt-proxy removed from Debian unstable)
Op 20100714 om 19:46 schreef Helge Kreutzmann: Hello Sandro, I use apt-proxy extensively. What is the replacement and upgrade path? I'm happy with the next generation of apt-cacher. Do aptitude show apt-cacher-ng to see more information Sandro: Thank you for the clean up, the removal of apt-proxy Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576573: live-helper: config: bogus architecture checking
Package: live-helper Version: 2.0~a9-1 Hello, Live-helper config does bogus checking on architecture. To me it seems it only checks during create of the config tree Please check architecture also during update Demostration: |stapp...@inertia:/tmp |$ mkdir qed |stapp...@inertia:/tmp |$ cd qed |stapp...@inertia:/tmp/qed |$ sudo lh config --architecture i486 |P: Considering defaults defined in /etc/default/live-helper |E: Architecture i486 not yet supported (FIXME) |stapp...@inertia:/tmp/qed |$ ls |stapp...@inertia:/tmp/qed |$ sudo lh config --architecture i386 |P: Considering defaults defined in /etc/default/live-helper |P: Creating config tree |stapp...@inertia:/tmp/qed |$ ls |auto config |stapp...@inertia:/tmp/qed |$ grep -ri architecture * |config/bootstrap:# $LH_ARCHITECTURE: select chroot architecture |config/bootstrap:LH_ARCHITECTURE=i386 |stapp...@inertia:/tmp/qed |$ sudo lh config --architecture i486 |P: Considering defaults defined in /etc/default/live-helper |P: Updating config tree |stapp...@inertia:/tmp/qed |$ grep -ri architecture * |config/bootstrap:# $LH_ARCHITECTURE: select chroot architecture |config/bootstrap:LH_ARCHITECTURE=i486 |stapp...@inertia:/tmp/qed |$ Regards Geert Stappers signature.asc Description: Digital signature
Bug#576583: live-helper: config: --binary usb-hdd --linux-flavours 486 conflict
Package: live-helper Version: 2.0~a9-1 Hello, This bug(report) may be caused because it was not clear what a linux flavour is. Anyway: `lh config --binary usb-hdd --linux-flavours 486` triggers a warning about a bootloader ... |$ sudo lh config --binary usb-hdd --linux-flavours 486 |P: Considering defaults defined in /etc/default/live-helper |W: You have selected values of LH_BOOTLOADER and LH_BINARY_FILESYSTEM |which are incompatible - syslinux only supports FAT filesystems. |P: Creating config tree Regards Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576583: live-helper: config: --binary usb-hdd --linux-flavours 486 conflict
Op 20100405 om 22:01 schreef Geert Stappers: Anyway: `lh config --binary usb-hdd --linux-flavours 486` triggers a warning about a bootloader ... |$ sudo lh config --binary usb-hdd --linux-flavours 486 |P: Considering defaults defined in /etc/default/live-helper |W: You have selected values of LH_BOOTLOADER and LH_BINARY_FILESYSTEM |which are incompatible - syslinux only supports FAT filesystems. |P: Creating config tree Gone with `lh config --binary-image usb-hdd --linux-flavours 486` It seems that '--binary' becomes '--binary-filesystem' I think '--binary' should yield an error. Only '--binary-image' and '--binary-filesystem' are valid. Cheers Geert Stappers signature.asc Description: Digital signature
Bug#569204: dpkg --compare-versions is your friend
Op 20100210 om 19:57 schreef Philipp Kern: live-magic/i386 unsatisfiable Depends: live-helper (= 2.0) Indeed live-helper has a version of 2.0~a6-1 which is less than 2.0. $ dpkg --compare-versions 1.0 lt 2.0 ; echo $? 0 $ dpkg --compare-versions 3.0 lt 2.0 ; echo $? 1 $ dpkg --compare-versions 2.0~a6-1 lt 2.0 ; echo $? 0 $ dpkg --compare-versions 2.0+a6-1 lt 2.0 ; echo $? 1 $ dpkg --compare-versions 1.9pre2.0~a6-1 lt 2.0 ; echo $? 0 HtH Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539102: ML for Dutch speaking users
Hello Listmasters, Here another I want to see a Dutch User list to take-off message. So consider this E-mail as extra trust to get the ML flying. Cheers Geert Stappers signature.asc Description: Digital signature
