Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Fri Jan 7 07:03:20 UTC 2011 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: rhythmbox-ampache tags 605556 + pending Bug #605556 [wnpp] ITP: rhythmbox-ampache -- GPL-2 licensed rhythmbox plugin Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 605556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129438380324297.transcr...@bugs.debian.org
Bug#502305: Temporary packages for ulogd2 : Configuration changes
Hi. Further to my previous email, I've now installed the newly built package and here are some observations. There is a lack of documentation in the built package. If the build also formatted the doc/ulogd.sgml file in the source area into txt and html files to be installed under the /usr/share/doc/ulogd/ directory, then there will be a lot more useful information on how to configure the new ulogd daemon. I made the following changes to the /etc/ulogd.conf file. Take and leave each of them as you like. I've attached the patch that makes all of these changes to the final installed configuration file. - I've made changes to produce logs in the /var/log/ulogd/ directory like the old ulogd v1.23 did. This way users upgrading from the old ulogd to the new ulogd will still find the files in the same location as before. Likewise I adjusted log file names to match what they were before (removed leading ulogd_) If the package doesn't create the /var/log/ulogd/ directory as part of its install, then it would need to be modified to do this as well. - I changed the log level to notice. I guess you can ignore this, but I've left it in the patch. - I've enabled the ULOG support. This way, people upgrading from the old ulogd daemon to the new one will still have their logging working. This will give them a chance to transition over from ULOG to NFLOG at their convenience. - There was no XML output plugin built with the package. So I've commented that plugin out to remove the error message about it not being found. I guess the other approach is to get the package to build that plugin if possible. - I added commented out plugin entries for the SQLITE3 output plugin, and the PWSNIFF filter plugin (which maybe you don't want to include). - Added a [sqlite3] section for the SQLITE3 plugin to match the example for SQLLITE3 on the old version of ulogd. Regards, -- -- Jim Barber DDI Health --- /etc/ulogd.conf.dpkg-dist 2011-01-07 14:00:16.0 +0800 +++ /etc/ulogd.conf 2011-01-07 14:54:57.0 +0800 @@ -9,10 +9,10 @@ # logfile for status messages -logfile=/var/log/ulogd.log +logfile=/var/log/ulog/ulogd.log # loglevel: debug(1), info(3), notice(5), error(7) or fatal(8) -loglevel=1 +loglevel=5 ## # PLUGIN OPTIONS @@ -26,7 +26,7 @@ plugin=/usr/lib/ulogd/ulogd_inppkt_NFLOG.so -#plugin=/usr/lib/ulogd/ulogd_inppkt_ULOG.so +plugin=/usr/lib/ulogd/ulogd_inppkt_ULOG.so plugin=/usr/lib/ulogd/ulogd_inpflow_NFCT.so plugin=/usr/lib/ulogd/ulogd_filter_IFINDEX.so plugin=/usr/lib/ulogd/ulogd_filter_IP2STR.so @@ -35,15 +35,17 @@ plugin=/usr/lib/ulogd/ulogd_filter_HWHDR.so plugin=/usr/lib/ulogd/ulogd_filter_PRINTFLOW.so #plugin=/usr/lib/ulogd/ulogd_filter_MARK.so +#plugin=/usr/lib/ulogd/ulogd_filter_PWSNIFF.so plugin=/usr/lib/ulogd/ulogd_output_LOGEMU.so plugin=/usr/lib/ulogd/ulogd_output_SYSLOG.so -plugin=/usr/lib/ulogd/ulogd_output_XML.so +#plugin=/usr/lib/ulogd/ulogd_output_XML.so #plugin=/usr/lib/ulogd/ulogd_output_OPRINT.so #plugin=/usr/lib/ulogd/ulogd_output_NACCT.so #plugin=/usr/lib/ulogd/ulogd_output_PCAP.so #plugin=/usr/lib/ulogd/ulogd_output_PGSQL.so #plugin=/usr/lib/ulogd/ulogd_output_MYSQL.so #plugin=/usr/lib/ulogd/ulogd_output_DBI.so +#plugin=/usr/lib/ulogd/ulogd_output_SQLITE3.so plugin=/usr/lib/ulogd/ulogd_raw2packet_BASE.so # this is a stack for logging packet send by system via LOGEMU @@ -53,7 +55,7 @@ #stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU # this is a stack for ULOG packet-based logging via LOGEMU -#stack=ulog1:ULOG,base1:BASE,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU +stack=ulog1:ULOG,base1:BASE,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU # this is a stack for packet-based logging via LOGEMU with filtering on MARK #stack=log2:NFLOG,mark1:MARK,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU @@ -148,15 +150,15 @@ #numeric_label=0 # optional argument [emu1] -file=/var/log/ulogd_syslogemu.log +file=/var/log/ulog/syslogemu.log sync=1 [op1] -file=/var/log/ulogd_oprint.log +file=/var/log/ulog/oprint.log sync=1 [xml1] -directory=/var/log/ +directory=/var/log/ulog/ sync=1 [pcap1] @@ -202,6 +204,11 @@ pass=changeme procedure=INSERT_OR_REPLACE_CT +[sqlite3] +table=ulog +db=/path/to/sqlite/db +buffer=200 + [dbi1] db=ulog2 dbtype=pgsql
Processed: I use it
Processing commands for cont...@bugs.debian.org: retitle 488005 ITA: wvdial -- PPP dialer with built-in intelligence Bug #488005 [wnpp] O: wvdial -- PPP dialer with built-in intelligence Bug #508379 [wnpp] O: wvdial -- PPP dialer with built-in intelligence Bug #546363 [wnpp] O: wvdial -- PPP dialer with built-in intelligence Changed Bug title to 'ITA: wvdial -- PPP dialer with built-in intelligence' from 'O: wvdial -- PPP dialer with built-in intelligence' Changed Bug title to 'ITA: wvdial -- PPP dialer with built-in intelligence' from 'O: wvdial -- PPP dialer with built-in intelligence' Changed Bug title to 'ITA: wvdial -- PPP dialer with built-in intelligence' from 'O: wvdial -- PPP dialer with built-in intelligence' owner 488005 ! Bug #488005 [wnpp] ITA: wvdial -- PPP dialer with built-in intelligence Bug #508379 [wnpp] ITA: wvdial -- PPP dialer with built-in intelligence Bug #546363 [wnpp] ITA: wvdial -- PPP dialer with built-in intelligence Owner recorded as Thierry Randrianiriana thie...@debian.org. Owner recorded as Thierry Randrianiriana thie...@debian.org. Owner recorded as Thierry Randrianiriana thie...@debian.org. thanks Stopping processing here. Please contact me if you need assistance. -- 488005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129439748213701.transcr...@bugs.debian.org
Bug#609205: ITP: libtest-file-contents-perl -- Perl module for testing the contents of files
Package: wnpp Severity: wishlist Owner: Alessandro Ghedini al3x...@gmail.com * Package name: libtest-file-contents-perl Version : 0.05 Upstream Author : Kirrily Robert s...@cpan.org * URL : http://search.cpan.org/dist/Test-File-Contents/ * License : Artistic or GPL-1+ Programming Lang: Perl Description : Perl module for testing the contents of files Test::File::Contents provides a set of routines useful to construct tests that examine the content of files. It can check for an exact match and for a regexp match against the file's contents, but also if the file's contents do not match a string or a regexp and whether a file matches or not a given md5sum. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110107112000.5908.73750.report...@pc-ale.rete
Bug#594368: Bug #594368
Vincent, please take care of gnote package, feel free to contact me if you need help. Devid On Fri, Jan 7, 2011 at 4:01 AM, Vincent Cheng vincentc1...@gmail.com wrote: Just a follow-up...I've found the upstream source for dbus-c++ (turns out I missed its git archive), and I've successfully packaged it. Note that it's NOT lintian clean at the moment. I have no idea about manpages because I don't know what the binaries in dbus-c++-dev do, and the previous maintainer didn't bother including man pages either, so I'm stuck. https://github.com/Vincent-C/dbus-cplusplus Lintian output is in the README attached to that github repo. It's packaged with a QA upload in mind. Mr. Filoni, you would also have to adopt dbus-c++ and dbus-c++-dev if you still want to adopt Gnote. If you would still like to do so, please feel free to use my work; otherwise, I would just be as willing to adopt both gnote and these dbus packages. :) - Vincent Cheng -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikd81l2gwub1p6ocutggk2c1_lgmyurn=jt-...@mail.gmail.com
Bug#609221: ITP: PyTyle2 -- PyTyle2 is an automatic and manual on-demand tiling manager
Package: wnpp Severity: wishlist Owner: Arnaud TOMEI arn...@tomei.fr * Package name: PyTyle2 Version : 2.0-dev Upstream Author : Andrew and...@pytyle.com * URL : http://code.google.com/p/pytyle * License : GPL Programming Lang: Python Description : PyTyle2 is an automatic and manual on-demand tiling manager It allow you to enable/disable tiling on a per screen per workspace basis, and continually tile your windows. Designed to work with Openbox, it support currently any EWMH compliant window manager. -- System Information: Debian Release: lenny/squeeze APT prefers stable APT policy: (990, 'stable'), (90, 'testing') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110107134033.3082.37087.report...@thor
Bug#609218: ITP: qsapecng -- a Qt-based Symbolic Analysis Program for Electric Circuits
Package: wnpp Severity: wishlist Owner: Simone Rossetto simro...@gmail.com * Package name: qsapecng Version : 1.2.1 Upstream Author : Michele Caini michele.ca...@gmail.com * URL : http://qsapecng.sourceforge.net/ * License : GPLv3 Programming Lang: C++ Description : a Qt-based Symbolic Analysis Program for Electric Circuits QSapecNG is a Qt-based program for symbolic analysis of linear analog circuits. This program consists of two indipendent parts: the SapecNG framework engine and the GUI application QSapecNG. QSapecNG is an open source, multi-platform project, continuously enhanced by students and researchers of the Department of Electronics and Telecommunications (DET) of the University of Florence (Italy). It comes as continuation of SapWin for Windows, in order to give to the project a full compatibility on other platforms. Through SapecNG/QSapecNG users can draw, solve and analyze analog circuits as well as manage them. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110107133320.4396.58182.report...@droscy.casa.local
Bug#578157: and another!
On Thu, 6 Jan 2011 17:45:57 +0100, Jonas Smedegaard d...@jones.dk wrote: On Thu, Jan 06, 2011 at 04:46:30PM +0100, Jonas Smedegaard wrote: On Thu, Jan 06, 2011 at 10:33:35AM -0500, micah anderson wrote: Do you have a repository somewhere with any work done thus far? I've tried out the cli for a while and it seems like a worthwhile package to make without the gui bits. Sorry - I thought the news was already filed here in the bugreport: The final official packaging was uploaded ultimo december, now awaiting ftpmaster approval: http://ftp-master.debian.org/new/bitcoin_0.3.19~dfsg-2.html It is also unofficially available using this APT line: deb http://debian.jones.dk/ unstable freedombox Great! I noticed that you are build-depending on libdb4.7++, I dont know that much about the bdb madness, but I do know that the bitcoin that I compiled from source was compiled against libdb4.8++ and when I try and install your packaged version, it can't read the wallet database. Is there any specific reason you went with 4.7 instead of 4.8, or was it just what your build environment had? My guess is that it would be best to switch to 4.8 right away, before this is accepted into Debian, because the transition from 4.7 to 4.8 is not going to be trivial (although, in theory... nuking the transaction logs, and removing the database environment will make it work, it will be a pain and somewhat scary for people's wallets). micah pgpUny0xu902E.pgp Description: PGP signature
Processed: retitle 597216 RFP: mozilla-httpfox -- An analyzer addon for mozilla based browsers
Processing commands for cont...@bugs.debian.org: retitle 597216 ITP: mozilla-httpfox -- An analyzer addon for mozilla based browsers Bug #597216 [wnpp] RFP: mozilla-httpfox -- An analyzer addon for mozilla based browsers Changed Bug title to 'ITP: mozilla-httpfox -- An analyzer addon for mozilla based browsers' from 'RFP: mozilla-httpfox -- An analyzer addon for mozilla based browsers' -- Stopping processing here. Please contact me if you need assistance. -- 597216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129441468324438.transcr...@bugs.debian.org
Bug#594368: Bug #594368
On Thu, Jan 06, 2011 at 07:01:23PM -0800, Vincent Cheng wrote: Just a follow-up...I've found the upstream source for dbus-c++ (turns out I missed its git archive), and I've successfully packaged it. Note that it's NOT lintian clean at the moment. I have no idea about manpages because I don't know what the binaries in dbus-c++-dev do, and the previous maintainer didn't bother including man pages either, so I'm stuck. s/packaged/updated packaging/ :) When you say you have packaged something it means you have done from scratch. https://github.com/Vincent-C/dbus-cplusplus Lintian output is in the README attached to that github repo. It's packaged with a QA upload in mind. Mr. Filoni, you would also have to adopt dbus-c++ and dbus-c++-dev if you still want to adopt Gnote. If you would still like to do so, please feel free to use my work; otherwise, I would just be as willing to adopt both gnote and these dbus packages. :) Ok, so what about the following plan: - QA uploads of tnome and dbus-c++ to update it to the latest version (as some users asked) - Then work with usptream and maintainer from other distros in getting the next version of gnote using a different D-Bus implementation. Ana -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110107155854.ga23...@pryan.ekaia.org
Bug#578157: and another!
On Fri, Jan 07, 2011 at 10:39:11AM -0500, micah anderson wrote: I noticed that you are build-depending on libdb4.7++, I dont know that much about the bdb madness, but I do know that the bitcoin that I compiled from source was compiled against libdb4.8++ and when I try and install your packaged version, it can't read the wallet database. Is there any specific reason you went with 4.7 instead of 4.8, Yes. src/build-unix.txt includes this note: You need Berkeley DB 4.7. Don't use 4.8, the database/log* files are incompatible. Helmuth Grohne, showing up on IRC just before I released the packaging, claims this might actually be a reason to run away screaming from Bitcoin, as it indicates a disastrous design flaw in relying on the network API on the internal BDB format of (little-endian!) v4.7. In other words: Bitcoin must eternally use BDB v4.7, and cannot work on e.g. PowerPC. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Processed: RFP: mozilla-httpfox -- An analyzer addon for mozilla based browsers
Processing commands for cont...@bugs.debian.org: retitle 597216 RFP: mozilla-httpfox -- An analyzer addon for mozilla based browsers Bug #597216 [wnpp] RFP: mozilla-httpfox -- An analyzer addon for mozilla based browsers Ignoring request to change the title of bug#597216 to the same title owner 597216 Mahyuddin Susanto udi...@gmail.com Bug #597216 [wnpp] RFP: mozilla-httpfox -- An analyzer addon for mozilla based browsers Owner recorded as Mahyuddin Susanto udi...@gmail.com. thanks Stopping processing here. Please contact me if you need assistance. -- 597216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129441427822820.transcr...@bugs.debian.org
Bug#597216: RFP: mozilla-httpfox -- An analyzer addon for mozilla based browsers
retitle 597216 RFP: mozilla-httpfox -- An analyzer addon for mozilla based browsers owner 597216 Mahyuddin Susanto udi...@gmail.com thanks Let me try to packaging this extennsion, i will coordinate with Mozilla Extension Packaging Team. thanks Mark! -- Mahyuddin Susanto udienz at gmail.com A0C3 AA91 1E0D B7CB F899 F67B 96FD 0511 8E7A 9CB0 signature.asc Description: Digital signature
Bug#609240: ITP: librtaudio -- A C++ library for realtime audio input/ouput
Package: wnpp Owner: Monty Taylor mord...@inaugust.com Severity: wishlist * Package name: librtaudio Version : 4.0.7 Upstream Author : Gary P. Scavone * License : MIT Programming Lang: C++ Description : A C++ library for realtime audio input/ouput RtAudio is a set of C++ classes that provides a common API (Application Programming Interface) for realtime audio input/output across Linux (native ALSA, JACK, and OSS), Macintosh OS X, SGI, and Windows (DirectSound and ASIO) operating systems. RtAudio significantly simplifies the process of interacting with computer audio hardware. It was designed with the following objectives: - object-oriented C++ design - simple, common API across all supported platforms - only one source and two header files for easy inclusion in programming projects - allow simultaneous multi-api support - support dynamic connection of devices - provide extensive audio device parameter control - allow audio device capability probing - automatic internal conversion for data format, channel number compensation, (de)interleaving, and byte-swapping RtAudio incorporates the concept of audio streams, which represent audio output (playback) and/or input (recording). Available audio devices and their capabilities can be enumerated and then specified when opening a stream. Monty Taylor -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d274ede.4000...@inaugust.com
Bug#594373: retitle ITA: jclicmoodle -- JClic module for Moodle
retitle 594373 ITA: jclicmoodle -- JClic module for Moodle -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktik8naeicry-q3s13skhr-hmg5pgazw=hba6u...@mail.gmail.com
Bug#594373: ITA: jclicmoodle -- JClic module for Moodle
retitle 594373 ITA: jclicmoodle -- JClic module for Moodle I'm interest to take this package I. De Marchi -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikr2bwta5etta4qofbkfqjql4ysvezn5o3bq...@mail.gmail.com
Bug#578157: and another!
On Fri, 7 Jan 2011 17:02:20 +0100, Jonas Smedegaard d...@jones.dk wrote: On Fri, Jan 07, 2011 at 10:39:11AM -0500, micah anderson wrote: I noticed that you are build-depending on libdb4.7++, I dont know that much about the bdb madness, but I do know that the bitcoin that I compiled from source was compiled against libdb4.8++ and when I try and install your packaged version, it can't read the wallet database. Is there any specific reason you went with 4.7 instead of 4.8, Yes. src/build-unix.txt includes this note: You need Berkeley DB 4.7. Don't use 4.8, the database/log* files are incompatible. This is interesting... I am using DB 4.8 just fine. I suspect that this build-unix.txt is out of date, or just wrong. The database/log files are just transaction logs, and while it is true that they are incompatible, this is normal for ABI differences between berkeley db versions. Helmuth Grohne, showing up on IRC just before I released the packaging, claims this might actually be a reason to run away screaming from Bitcoin, as it indicates a disastrous design flaw in relying on the network API on the internal BDB format of (little-endian!) v4.7. talking about irc gave me an idea. I stopped over to #bitcoin-dev, and asked them what the deal was: 11:46:01 hacim i noticed in src/build-unix.txt, it says to use Berkeley DB 4.7 11:46:10 hacim You need Berkeley DB 4.7. Don't use 4.8, the database/log* files are incompatible 11:46:15 hacim however, I'm using 4.8 just fine... 11:46:15 ArtForz yes, use bdb 4.7 11:46:33 ArtForz well, now your DB is auto-upgraded to 4.8 11:46:42 hacim the database/log* files are just transaction logs 11:46:51 ArtForz = 4.7 can't read it anymore 11:47:01 hacim they are of course incompatible with 4.7, this is the definition of the ABI change :) 11:47:13 gavinandresen As long as you don't reinstall a precompiled bitcoin you'll be fine. 11:47:23 ArtForz yep 11:48:03 hacim ok, so there is nothing about the 4.7 libraries, such as relying on the network API in the internal bdb format of little-endian 4.7? 11:48:10 ArtForz nope 11:48:29 ArtForz it's just that 4.8 isnt backwards compatible with 4.7 and binary builds use 4.7 11:48:31 hacim so, for new installs, why would one chose to use 4.7, when you will need to upgrade anyways? 11:48:48 hacim eventually those binary builds will need to use 4.8, and people will have to transition 11:48:54 ArtForz why? 11:49:04 hacim if the history of bdb is to be any indicator of the future... 11:49:13 ArtForz so far the binary builds are 4.7, so going to selfcompiled w/ 4.8 is a one-way street 11:49:14 hacim do you know anyone using bdb4.1? 11:49:52 ArtForz when binary build switches to 4.8, recommended version for compiling will switch to 4.8 (duh) 11:49:59 hacim why would anyone want to use 4.7 right now is beyond me 11:50:14 ArtForz no one WANTS to, everyone using a precompiled binary HAS to 11:50:20 hacim ArtForz: the 'binary build' meaning the binaries offered on the website? 11:50:56 gavinandresen hacim: you want to volunteer to organize an effort to make sure 4.8 is supported on windows mac and all the linux flavors people are using? 11:52:59 hacim gavinandresen: it works fine on three different linux flavors that I've tried this morning 11:53:07 gavinandresen hacim: or, to say it another way: bitcoin uses 4.7 because two years ago that is what Satoshi decided to use, and nobody has put in the effort needed to upgrade. It just hasn't been a priority. 11:53:32 gavinandresen hacim: great! so create a patch and recruit some people to see if it works on mac and windows. 11:53:32 hacim gavinandresen: it doesn't bother me that other people use 4.7 so it seems there is no particular reason to use 4.7, its just what their pre-compiled binary versions use, and the only reason that they dont move to 4.8 is because nobody has bothered to try it on mac and windows. As a test, I backed up my .bitcoin/ and then ran your version, with libdb4.7++ and start it up. It creates a wallet and I let it download all the current blocks. I then stop it, run a self-compiled bitcoin, linked against libdb4.8++, it converts the database to 4.8 format, and things continue to work as normal. micah pgpQhZEsQk9ol.pgp Description: PGP signature
Bug#578157: and another!
On Fri, Jan 07, 2011 at 12:06:37PM -0500, micah anderson wrote: On Fri, 7 Jan 2011 17:02:20 +0100, Jonas Smedegaard d...@jones.dk wrote: On Fri, Jan 07, 2011 at 10:39:11AM -0500, micah anderson wrote: I noticed that you are build-depending on libdb4.7++, I dont know that much about the bdb madness, but I do know that the bitcoin that I compiled from source was compiled against libdb4.8++ and when I try and install your packaged version, it can't read the wallet database. Is there any specific reason you went with 4.7 instead of 4.8, Yes. src/build-unix.txt includes this note: You need Berkeley DB 4.7. Don't use 4.8, the database/log* files are incompatible. This is interesting... I am using DB 4.8 just fine. I suspect that this build-unix.txt is out of date, or just wrong. The database/log files are just transaction logs, and while it is true that they are incompatible, this is normal for ABI differences between berkeley db versions. Helmuth Grohne, showing up on IRC just before I released the packaging, claims this might actually be a reason to run away screaming from Bitcoin, as it indicates a disastrous design flaw in relying on the network API on the internal BDB format of (little-endian!) v4.7. talking about irc gave me an idea. I stopped over to #bitcoin-dev, and asked them what the deal was: [IRC conversation snipped] so it seems there is no particular reason to use 4.7, its just what their pre-compiled binary versions use, and the only reason that they dont move to 4.8 is because nobody has bothered to try it on mac and windows. As a test, I backed up my .bitcoin/ and then ran your version, with libdb4.7++ and start it up. It creates a wallet and I let it download all the current blocks. I then stop it, run a self-compiled bitcoin, linked against libdb4.8++, it converts the database to 4.8 format, and things continue to work as normal. Thanks a lot for your investigation! So what really is the issue here is that _at_ _each_ _runtime_ _environment_ are the db files incompatible. I know that problem already from Netatalk, which also until recently did not support seemless upgrading. I'll immediately rebuild using a newer bdb, and also throw in a README based on that used in netatalk until recently - and would appreciate if you could verify if manual upgrading/downgrading works using that - to prepare for future version bumps. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#578157: and another!
On Fri, Jan 07, 2011 at 08:17:29PM +0100, Jonas Smedegaard wrote: So what really is the issue here is that _at_ _each_ _runtime_ _environment_ are the db files incompatible. I know that problem already from Netatalk, which also until recently did not support seemless upgrading. I'll immediately rebuild using a newer bdb, and also throw in a README based on that used in netatalk until recently - and would appreciate if you could verify if manual upgrading/downgrading works using that - to prepare for future version bumps. Looking some more at this upgrade issue, it seems to not be possible to use the netatalk scripts. @Micah: Could you please test if upgrading works like this: 1) Move aside your precious .bitcoin folder 2) Start the current Debian Bitcoin (or upstream binary) 3) Let Bitcoin run until its db is fully init'ed (i.e. dir is ~150MB) 3) Quit Bitcoin 4) Install packages libdb4.8-util and db4.7-util 5) run the following commands: db4.7_recover -h ~/.bitcoin db4.8_upgrade -h ~/.bitcoin wallet.dat 6) Start your locally compiled Bitcoin 7) Tell me if it worked out or not :-) I will now compile a new Bitcoin against Berkeley DB 4.8, with a README mentioning essential parts of above - blindly hoping that it works. Please be careful to test against current release, not the version I am about to release :-) - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#609278: ITP: Unity -- Interface for Ubuntu Desktop Edition
Package: wnpp Severity: wishlist Owner: Adnan Hodzic ad...@foolcontrol.org * Package name: Unity Version : 3.2.8 Upstream Author : Ubuntu Core Developers ubuntu-devel-disc...@lists.ubuntu.com * URL : https://launchpad.net/unity * License : (GPL3) Programming Lang: (C, C++, vala) Description : Interface for Ubuntu Desktop Edition Unity is a graphical interface designed for Ubuntu Desktop Edition -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110108015726.2943.68138.report...@havoc
Bug#609285: RFP: trafficserver -- Apache Traffic Server
Subject: RFP: trafficserver -- Apache Traffic Server Package: wnpp Severity: wishlist * Package name: trafficserver Version : 2.0.1 Upstream Author : Apache Foundation * URL : http://trafficsever.apache.org/ * License : Apache License 2.0 Programming Lang: C Description : Apache Traffic Server is fast, scalable and extensible HTTP/1.1 compliant caching proxy server. Formerly a commercial product, Yahoo! donated it to the Apache Foundation, and is now an Apache TLP. -- System Information: Debian Release: 5.0.7 APT prefers stable APT policy: (1000, 'stable'), (900, 'proposed-updates'), (900, 'stable') Architecture: i386 (i686) Package: Version: Severity: Tags: URL: http://devel.debian.tamay-dogan.net/ System: `uname -a` Hello Maintainer, Thanks, Greetings and nice Day/Evening Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 +49/177/935194750, rue de Soultz MSN LinuxMichi +33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
