Bug#728121:
Hi all,
The following CMakeLists.txt fails, cause gdcm targets are defined twice.
Adding gdcm into the dependency would solve this blocking issue!
Thanks
Arnaud
---
project( foo )
cmake_minimum_required( VERSION 2.6 )
find_package( GDCM REQUIRED )
include( ${GDCM_USE_FILE} )
find_package( ITK 4.0 REQUIRED )
include( ${ITK_USE_FILE} )
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736482: libcgal-dev: compilation error with jet_smooth_point
Subject: libcgal-dev: compilation error with jet_smooth_point
Package: libcgal-dev
Version: 4.2-5+b2
Severity: important
Dear Maintainer,
A bug has been reported on the mailing list here with the correction to be made
in the source (see attached files):
https://sympa.inria.fr/sympa/arc/cgal-discuss/2014-01/msg00097.html
Without this fix, the following won't compile:
#include CGAL/jet_smooth_point_set.h
void main() {}
Thanks for applying the fix.
Best,
Arnaud
-- System Information:
Debian Release: 7.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (200,
'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libcgal-dev depends on:
ii libboost-dev 1.54.0.1
ii libboost-program-options-dev 1.54.0.1
ii libboost-system-dev 1.54.0.1
ii libboost-thread-dev 1.54.0.1
ii libcgal10 4.2-5+b2
ii libgmp-dev [libgmp10-dev] 2:5.1.3+dfsg-1
ii libmpfr-dev 3.1.2-1
ii zlib1g-dev1:1.2.8.dfsg-1
libcgal-dev recommends no packages.
libcgal-dev suggests no packages.
-- no debconf information
jet_estimate_normals.h
Description: Binary data
jet_smooth_point_set.h
Description: Binary data
Bug#706934: firmware-linux-nonfree: Can't get network to work
Package: firmware-linux-nonfree Version: 0.36+wheezy.1 Severity: important *** Please type your report below this line *** Without internet connection, I have downloaded and installed the corresponding package manually; but I could not manage to make it work as expected... Thanks in advance for your help $ lspci | grep Bro 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10) $ sudo lspci -s 05:00.0 -vvx 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10) Subsystem: Dell Device 0293 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 68 Region 0: Memory at f3de (64-bit, non-prefetchable) [size=64K] Region 2: Memory at f3df (64-bit, non-prefetchable) [size=64K] Capabilities: [48] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME- Capabilities: [40] Vital Product Data Product Name: Broadcom NetXtreme Gigabit Ethernet Controller Read-only fields: [PN] Part number: BCM95761 [EC] Engineering changes: 106679-15 [SN] Serial number: 0123456789 [MN] Manufacture ID: 31 34 65 34 [RV] Reserved: checksum good, 28 byte(s) reserved Read/write fields: [YA] Asset tag: XYZ01234567 [RW] Read-write area: 107 byte(s) free End Capabilities: [60] Vendor Specific Information: Len=6c ? Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: 4099 Capabilities: [cc] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s 4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 4096 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 1us, L1 64us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr+ BadTLP+ BadDLLP+ Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [13c v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [160 v1] Device Serial Number b8-ac-6f-ff-fe-87-0d-7b Capabilities: [16c v1] Power Budgeting ? Kernel driver in use: tg3 00: e4 14 81 16 06 04 10 00 10 00 00 02 10 00 00 00 10: 04 00 de f3 00 00 00 00 04 00 df f3 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 28 10 93 02 30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 01 00 00 $ sudo lshw -class network *-network description: Ethernet interface product: NetXtreme BCM5761 Gigabit Ethernet PCIe vendor: Broadcom Corporation physical id: 0 bus info: pci@:05:00.0 logical name: eth0 version: 10 serial: b8:ac:6f:87:0d:7b size: 100Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.121 duplex=full
Bug#706934:
$ sudo modinfo tg3 | grep -i 14e4 | grep 1681 alias: pci:v14E4d1681sv*bc*sc*i* Let me know if there is any additional information you would need or would be relevant Thank you very much in advance for your help!!
Bug#649580: j and jumpstat are not present once autojump is installed
Package: autojump Version: 17-1 Severity: important When using autojump, you are supposed to use j to switch directories, and jumpstat to get the statistics. Even according to the man page. If these commands have been renamed, please provide the new names; however that would not be consistent with the upstream version. Else j and jumpstat are not installed; which most likely seems to be the case here... -- System Information: Debian Release: 6.0.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages autojump depends on: ii python3 3.2.2~rc1-2 interactive high-level object-orie autojump recommends no packages. autojump 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#649580: j and jumpstat are not present once autojump is installed
Hi Tanguy, I have been using autojump on other machines (Mac, and other linux boxes with various distributions). Part of the standard installation of autojump (see install.sh) is to add the right lines into user's bashrc? Shouldn't it be the same when installing autojump on debian? Thanks, Arnaud On Nov 22, 2011, at 11:41 AM, Tanguy Ortolo wrote: Arnaud Gelas, 2011-11-22 04:26 UTC-0500: When using autojump, you are supposed to use j to switch directories, and jumpstat to get the statistics. Even according to the man page. Yes, but only after you loaded autojump's shell code, since they are shell functions defined by autojump. Else j and jumpstat are not installed; which most likely seems to be the case here... So, did you load autojump? I suggest that you add it to your shell's startup code, for instance in your bashrc: . /usr/share/autojump/autojump.sh -- ,--. : /` ) Tanguy Ortolo xmpp:tan...@ortolo.eu irc://irc.oftc.net/Elessar | `-'Debian Maintainer \_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649580: j and jumpstat are not present once autojump is installed
I can understand why bash* files should not get altered when installing autojump. But when installing autojump, users (like me) would expect the same behavior as manual installation. I think it cold also be reported upstream, check if they don't have an alternative solution. Else some documentation is missing. Not sure where it should be located though (may be in the information of the package?), but it would avoid some problems. Opinion? On Nov 22, 2011, at 12:07 PM, Tanguy Ortolo wrote: Arnaud Gelas, 2011-11-22 11:52 UTC+0100: I have been using autojump on other machines (Mac, and other linux boxes with various distributions). Part of the standard installation of autojump (see install.sh) is to add the right lines into user's bashrc? Shouldn't it be the same when installing autojump on debian? No, I am sorry but it cannot. Adding it to the users' shell configuration is not an option, and changing the global shell configuration is not acceptable either, since it would not be sane to dynamically patch another package's configuration file. When I had to make that decision I checked the policy and took some advice from other Debian contributors; I do not remember exactly the arguments that made me choose not to configure the shell but to document how to do that, but I do remember that I had very good reason to do so. :-) If you need I can check the Debian Policy again, but I do not think I can change that. If you have arguments to the opposite option, or possible solutions, I would be glad to hear them, otherwise this bug report should be closed or perhaps tagged as wontfix. -- ,--. : /` ) Tanguy Ortolo xmpp:tan...@ortolo.eu irc://irc.oftc.net/Elessar | `-'Debian Maintainer \_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649580: j and jumpstat are not present once autojump is installed
On 11/22/2011 07:34 AM, Tanguy Ortolo wrote: Arnaud Gelas, 2011-11-22 12:15 UTC+0100: I can understand why bash* files should not get altered when installing autojump. Well, when it comes to Debian packages, my understanding is that installing them makes the corresponding software available. I do not think it means that, when they require something to be enabled, they should be enabled for the users. Also remember that Debian is a universal operating system and not an operating system focused on Desktop usage; its goal thus includes multi-users environment… Take bootchart, for instance, which provides a way to analyze the boot process of a system. By installing it you make bootchart available, but it does not enable it for each boot which would be an error; to use it you need to explicitely ask for it at boot time. I was not arguing, here I repeat: I can understand why bash* files should not get altered when installing autojump. But when installing autojump, users (like me) would expect the same behavior as manual installation. I must disagree. The Debian package is bound to the packaging practices and Debian Policy, as it is meant for a more generic goal than the manual autojump installer. As long as it is documented and known that is not the default behavior, it is fine with me! I think it cold also be reported upstream, check if they don't have an alternative solution. Yes, I shall contact the upstream developper and ask him to add a note to the REDME.rst which is displayed on the home page of the project. Excellent! I have cc'ed Joel. Else some documentation is missing. Not sure where it should be located though (may be in the information of the package?), but it would avoid some problems. I agree that documentation is needed, however it is not missing. You will find it at the place where it is expected to be: /usr/share/doc/autojump/README.Debian. Thanks for the pointer, that's what I was looking for!! Also, it seems that jumpapplet is not part of the package!? Thank you very much for your help and quick replies, Best, Arnaud -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649580: j and jumpstat are not present once autojump is installed
Agree! Thanks Joel for taking care of it so quickly!!! Arnaud On 11/22/2011 08:20 AM, Joel Schaerer wrote: I have updated the documentation as requested by Tanguy. It's a shame that simply installing the package is not enough, but I think it really has to be that way. I would certainly not want apt to modify my personal bash resource files. joel Arnaud Gelas wrote: On 11/22/2011 07:34 AM, Tanguy Ortolo wrote: Arnaud Gelas, 2011-11-22 12:15 UTC+0100: I can understand why bash* files should not get altered when installing autojump. Well, when it comes to Debian packages, my understanding is that installing them makes the corresponding software available. I do not think it means that, when they require something to be enabled, they should be enabled for the users. Also remember that Debian is a universal operating system and not an operating system focused on Desktop usage; its goal thus includes multi-users environment… Take bootchart, for instance, which provides a way to analyze the boot process of a system. By installing it you make bootchart available, but it does not enable it for each boot which would be an error; to use it you need to explicitely ask for it at boot time. I was not arguing, here I repeat: I can understand why bash* files should not get altered when installing autojump. But when installing autojump, users (like me) would expect the same behavior as manual installation. I must disagree. The Debian package is bound to the packaging practices and Debian Policy, as it is meant for a more generic goal than the manual autojump installer. As long as it is documented and known that is not the default behavior, it is fine with me! I think it cold also be reported upstream, check if they don't have an alternative solution. Yes, I shall contact the upstream developper and ask him to add a note to the REDME.rst which is displayed on the home page of the project. Excellent! I have cc'ed Joel. Else some documentation is missing. Not sure where it should be located though (may be in the information of the package?), but it would avoid some problems. I agree that documentation is needed, however it is not missing. You will find it at the place where it is expected to be: /usr/share/doc/autojump/README.Debian. Thanks for the pointer, that's what I was looking for!! Also, it seems that jumpapplet is not part of the package!? Thank you very much for your help and quick replies, Best, Arnaud -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635371: linux-image-2.6.32-5-amd64: screen freezes when doing make -j12
Hi Jonathan, On 07/25/2011 04:44 PM, Jonathan Nieder wrote: severity 635371 wishlist tags 635371 + upstream moreinfo quit Hi Arnaud, Arnaud Gelas wrote: When compiling some libraries with gcc with all possible threads, the screen freezed and even killing processes is difficult How much memory was used? Did it go into swap? Is swap on a slow disk? Is this behavior different from previous versions of the kernel? Other notable details? $ free -m total used free sharedbuffers cached Mem: 12041 11723317 0368 7170 -/+ buffers/cache: 4184 7856 Swap:19322301 19021 The swap is located a recent and decent disk. I have just switched from another distribution (Fedora) where I never had this problem before. So I can't tell about previous kernel on debian. (Note: it may have been fixed in more recent version of the kernel?) The memory management subsystem or perhaps the I/O scheduler (?) is known to not cope very well with low-memory situations when memory being actively used needs to be reclaimed by swapping things out. In an ideal world, we would want the system to remain responsive enough to kill something, but in practice it is hard to figure out how to do that and figure out what to keep in memory. If some details inspire a method of chiseling away at the problem, I can help direct you to an appropriate person upstream to discuss it and point out patches to test. Otherwise, I will probably close the bug, since it would not be clear how to use this knowledge to improve the kernel. I can test patches if anyone could see a solution. Thanks for reporting. Regards, Jonathan Thanks, Arnaud -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635371: linux-image-2.6.32-5-amd64: screen freezes when doing make -j12
Package: linux-2.6 Version: 2.6.32-35 Severity: important When compiling some libraries with gcc with all possible threads, the screen freezed and even killing processes is difficult -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:42:28 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=57c8b4a5-e20f-4b9e-9826-d64f14db774f ro quiet ** Not tainted ** Kernel log: [634280.081014] [drm] nouveau :02:00.0: plugged DVI-I-1 [634280.097500] [drm] nouveau :02:00.0: unplugged DVI-I-1 [634280.346850] [drm] nouveau :02:00.0: plugged DVI-I-1 [636412.946015] [drm] nouveau :02:00.0: unplugged DVI-I-1 [636413.195349] [drm] nouveau :02:00.0: plugged DVI-I-1 [636413.205692] [drm] nouveau :02:00.0: unplugged DVI-I-1 [636413.455160] [drm] nouveau :02:00.0: plugged DVI-I-1 [636413.471645] [drm] nouveau :02:00.0: unplugged DVI-I-1 [636413.720964] [drm] nouveau :02:00.0: plugged DVI-I-1 [646858.287596] [drm] nouveau :02:00.0: unplugged DVI-I-1 [646858.536932] [drm] nouveau :02:00.0: plugged DVI-I-1 [646858.547286] [drm] nouveau :02:00.0: unplugged DVI-I-1 [646858.796741] [drm] nouveau :02:00.0: plugged DVI-I-1 [646858.813228] [drm] nouveau :02:00.0: unplugged DVI-I-1 [646859.062544] [drm] nouveau :02:00.0: plugged DVI-I-1 [651926.509154] ITKImageGridTes[25101]: segfault at 8032864b0 ip 005bd5a7 sp 7fffe78343c0 error 4 in ITKImageGridTestDriver[40+89f000] [656378.662330] [drm] nouveau :02:00.0: unplugged DVI-I-1 [656378.911637] [drm] nouveau :02:00.0: plugged DVI-I-1 [656378.921964] [drm] nouveau :02:00.0: unplugged DVI-I-1 [656379.171443] [drm] nouveau :02:00.0: plugged DVI-I-1 [656379.187912] [drm] nouveau :02:00.0: unplugged DVI-I-1 [656379.437235] [drm] nouveau :02:00.0: plugged DVI-I-1 [663350.630204] [drm] nouveau :02:00.0: unplugged DVI-I-1 [663350.879522] [drm] nouveau :02:00.0: plugged DVI-I-1 [663350.889867] [drm] nouveau :02:00.0: unplugged DVI-I-1 [663351.139337] [drm] nouveau :02:00.0: plugged DVI-I-1 [663351.155837] [drm] nouveau :02:00.0: unplugged DVI-I-1 [663351.405177] [drm] nouveau :02:00.0: plugged DVI-I-1 [673891.744876] [drm] nouveau :02:00.0: unplugged DVI-I-1 [673891.994213] [drm] nouveau :02:00.0: plugged DVI-I-1 [673892.004558] [drm] nouveau :02:00.0: unplugged DVI-I-1 [673892.254022] [drm] nouveau :02:00.0: plugged DVI-I-1 [673892.270505] [drm] nouveau :02:00.0: unplugged DVI-I-1 [673892.519820] [drm] nouveau :02:00.0: plugged DVI-I-1 [678061.951508] [drm] nouveau :02:00.0: unplugged DVI-I-1 [678062.200759] [drm] nouveau :02:00.0: plugged DVI-I-1 [678062.211159] [drm] nouveau :02:00.0: unplugged DVI-I-1 [678062.460627] [drm] nouveau :02:00.0: plugged DVI-I-1 [678062.477094] [drm] nouveau :02:00.0: unplugged DVI-I-1 [678062.726415] [drm] nouveau :02:00.0: plugged DVI-I-1 [682679.738403] INFO: task firefox-bin:11874 blocked for more than 120 seconds. [682679.738406] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [682679.738408] firefox-bin D 88000c4cfa20 0 11874 1 0x [682679.738412] 88031e4ec6a0 0082 8802f5fefe34 [682679.738415] 8800cfc1a188 8802f5fefe18 f9e0 8802f5feffd8 [682679.738418] 00015780 00015780 880311eb2a60 880311eb2d58 [682679.738421] Call Trace: [682679.738428] [810b4c0c] ? wait_on_page_writeback_range+0xce/0x11b [682679.738442] [a011df74] ? log_wait_commit+0xbf/0x112 [jbd] [682679.738446] [81064f1a] ? autoremove_wake_function+0x0/0x2e [682679.738451] [a012e3f8] ? ext3_sync_file+0x94/0xc8 [ext3] [682679.738456] [8110bce8] ? vfs_fsync_range+0x73/0x9e [682679.738458] [8110bd92] ? do_fsync+0x28/0x39 [682679.738460] [8110bdb1] ? sys_fdatasync+0xe/0x13 [682679.738464] [81010b42] ? system_call_fastpath+0x16/0x1b [682799.653529] INFO: task firefox-bin:11874 blocked for more than 120 seconds. [682799.653532] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [682799.653533] firefox-bin D 88000c4cfa20 0 11874 1 0x [682799.653536] 88031e4ec6a0 0082 8802f5fefe34 [682799.653538] 8800cfc1a188 8802f5fefe18 f9e0 8802f5feffd8 [682799.653540] 00015780 00015780 880311eb2a60 880311eb2d58 [682799.653542] Call Trace: [682799.653549] [810b4c0c] ? wait_on_page_writeback_range+0xce/0x11b [682799.653560] [a011df74] ? log_wait_commit+0xbf/0x112 [jbd] [682799.653563] [81064f1a] ? autoremove_wake_function+0x0/0x2e [682799.653567] [a012e3f8] ? ext3_sync_file+0x94/0xc8 [ext3] [682799.653571] [8110bce8] ?
Bug#634921: gofigure2: missing dependency to mysql server (service)
Package: gofigure2 Severity: important In the dependency list, right now the package, which provides mysql as a service for the system, is missing. Although gofigure2 compiles and gets installed normally, after you can't really use it since mysql service is not running. -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634921: [Debian-med-packaging] Bug#634921: gofigure2: missing dependency to mysql server (service)
Hi! On 07/20/2011 06:23 PM, Nelson A. de Oliveira wrote: Hi! On Wed, Jul 20, 2011 at 7:00 PM, Arnaud Gelas arnaud_ge...@hms.harvard.edu wrote: In the dependency list, right now the package, which provides mysql as a service for the system, is missing. Although gofigure2 compiles and gets installed normally, after you can't really use it since mysql service is not running. It doesn't have a dependency on mysql since you can use a database from another server/machine (File menu → Use Database → ServerName:). The missing depends on the server isn't wrong then: you can both install a database server locally (mysql-server) or use from another machine. Maybe we should add mysql-server in Suggests (and/or a an explanation in README.Debian). Best regards, Nelson I would definitively agree with you. As of now, we have not been working on the case with remote database. It has not been our primary focus until now. It may work (?), but I am not too confident. Note: if you tried and it works, please let me know!!! Anyway, this feature will be part and fully supported in a future release. Arnaud -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
