Bug#930343: libgcr410 FTCBFS: uses the wrong compiler
Go ahead. Peter. On 2019-06-11 06:13:16 (+0200), Helmut Grohne wrote: > Source: libgcr410 > Version: 2.4.0-9.2 > Tags: patch > User: debian-cr...@lists.debian.org > Usertags: ftcbfs > > libgcr410 fails to cross build from source, because it does not pass > cross tools to make. The easiest way of doing so - using dh_auto_build - > makes libgcr410 cross buildable. Please consider applying the attached > patch. > > Helmut > diff -u libgcr410-2.4.0/debian/changelog libgcr410-2.4.0/debian/changelog > --- libgcr410-2.4.0/debian/changelog > +++ libgcr410-2.4.0/debian/changelog > @@ -1,3 +1,10 @@ > +libgcr410 (2.4.0-9.3) UNRELEASED; urgency=medium > + > + * Non-maintainer upload. > + * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1) > + > + -- Helmut Grohne Tue, 11 Jun 2019 06:10:48 +0200 > + > libgcr410 (2.4.0-9.2) unstable; urgency=low > >* Non-maintainer upload. > diff -u libgcr410-2.4.0/debian/rules libgcr410-2.4.0/debian/rules > --- libgcr410-2.4.0/debian/rules > +++ libgcr410-2.4.0/debian/rules > @@ -3,7 +3,7 @@ > build: build-stamp > build-stamp: > dh_testdir > - $(MAKE) > + dh_auto_build > touch build-stamp > > clean:
Bug#902795: systemd fills kmsg and console with rubbish
On 2018-07-01 20:48:01 (+0200), Michael Biebl wrote: > Am 01.07.2018 um 01:49 schrieb Peter De Schrijver: > > Package: systemd > > Version: 239-3 > > Severity: important > > > > > > systemd fills kmsg and console with: > > > > [ 102.676667] systemd-journald[360]: Sent WATCHDOG=1 notification. > > [ 102.683373] systemd-journald[360]: Journal effective settings seal=no > > compress=yes compress_threshold_bytes=512B > > This is a debug log message [1]. Please check if you have debug logging > enabled. > Most likely you have added "debug" to the kernel command line. > > If you turn off debug logging, those log messages should go away. > However, this doesn't mean systemd should spam the console log to the point where it becomes unusable for any other purpose. There should be flags to limit the amount of console output, even when in debug mode. Peter.
Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot
On 2017-12-15 20:28:28 (+0100), Michael Biebl wrote: > Am 15.12.2017 um 20:26 schrieb Peter 'p2' De Schrijver: > > On 2017-12-15 20:23:11 (+0100), Michael Biebl wrote: > > >> Could it be a problem that > >> > >> [[0;32m OK [0m] Stopped LSB: Open vSwitch switch. > >> > >> is stopped before the NFS mounts are unmounted? Not familiar how ovs > >> works. Is the network down at this point? > >> > > > > Maybe? I don't know the ovs internals either TBH > > So, since the ordering from the systemd POV is apparently correct, the > best we can do is to either reassign this to ifupdown or ovs. I think > the latter is probably the best action as apparently neither you nor me > knows how OVS works. > Yes, I will try to do that.. Peter.
Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot
On 2017-12-15 20:23:11 (+0100), Michael Biebl wrote: > Am 15.12.2017 um 20:19 schrieb Peter 'p2' De Schrijver: > > On 2017-12-14 00:58:33 (+0100), Michael Biebl wrote: > >> Am 14.12.2017 um 00:09 schrieb Michael Biebl: > >>> Am 13.12.2017 um 22:04 schrieb Peter 'p2' De Schrijver: > >>>> On 2017-12-13 21:53:10 (+0100), Michael Biebl wrote: > >>>>> Control: tags -1 + moreinfo > >> > >>>> NFS mount is just done manually: > >>>> > >>>> mount freenas:/mnt/storage /nfs/ > >>>> mount freenas:/mnt/storage/p2_home/ /nfs/p2_home/ > >>> > >>> What's the systemctl status and systemctl show output for these mount > >>> points? > >> > >> We will need a systemd-analyze dump output and a verbose debug log from > >> shutdown. > >> See /usr/share/doc/systemd/README.Debian.gz on how to generate a debug > >> log on shutdown. > >> > > > > Debug log attached. It's from serial console because the script doesn't get > > run. > > Could it be a problem that > > [[0;32m OK [0m] Stopped LSB: Open vSwitch switch. > > is stopped before the NFS mounts are unmounted? Not familiar how ovs > works. Is the network down at this point? > Maybe? I don't know the ovs internals either TBH Peter.
Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot
On 2017-12-14 00:58:33 (+0100), Michael Biebl wrote: > Am 14.12.2017 um 00:09 schrieb Michael Biebl: > > Am 13.12.2017 um 22:04 schrieb Peter 'p2' De Schrijver: > >> On 2017-12-13 21:53:10 (+0100), Michael Biebl wrote: > >>> Control: tags -1 + moreinfo > > >> NFS mount is just done manually: > >> > >> mount freenas:/mnt/storage /nfs/ > >> mount freenas:/mnt/storage/p2_home/ /nfs/p2_home/ > > > > What's the systemctl status and systemctl show output for these mount > > points? > > We will need a systemd-analyze dump output and a verbose debug log from > shutdown. > See /usr/share/doc/systemd/README.Debian.gz on how to generate a debug > log on shutdown. > Debug log attached. It's from serial console because the script doesn't get run. Peter. [ 220.842975] FS-Cache: Loaded [ 220.843050] systemd[1]: systemd-udevd.service: Got notification message from PID 407 (WATCHDOG=1) [ 220.843087] systemd-udevd[407]: Validate module index [ 220.843100] systemd-udevd[407]: Check if link configuration needs reloading. [ 220.843745] systemd-udevd[2729]: passed device to netlink monitor 0x562227d56940 [ 220.843813] systemd-udevd[2729]: Unload module index [ 220.843841] systemd-udevd[2729]: Unloaded link configuration context. [ 220.886948] systemd-udevd[2730]: passed device to netlink monitor 0x562227d56940 [ 220.894409] systemd-udevd[2730]: Unload module index [ 220.894927] systemd-udevd[2731]: passed device to netlink monitor 0x562227d1af60 [ 220.894969] systemd-udevd[2731]: Unload module index [ 220.894987] systemd-udevd[2731]: Unloaded link configuration context. [ 220.918539] FS-Cache: Netfs 'nfs' registered for caching [ 220.925686] Key type dns_resolver registered [ 220.935134] NFS: Registering the id_resolver key type [ 220.940187] Key type id_resolver registered [ 220.944369] Key type id_legacy registered [ 221.031665] systemd[1]: Accepted new private connection. [ 221.038279] systemd[1]: rpc-statd.service: Trying to enqueue job rpc-statd.service/start/replace [ 221.047104] systemd[1]: nss-lookup.target: Installed new job nss-lookup.target/start as 992 [ 221.055468] systemd[1]: nfs-config.service: Installed new job nfs-config.service/start as 994 [ 221.063990] systemd[1]: rpc-statd.service: Installed new job rpc-statd.service/start as 987 [ 221.072355] systemd[1]: rpc-statd-notify.service: Installed new job rpc-statd-notify.service/start as 995 [ 221.081927] systemd[1]: rpc-statd.service: Enqueued job rpc-statd.service/start as 987 [ 221.090153] systemd[1]: nfs-config.service: Passing 0 fds to service [ 221.096514] systemd[1]: nfs-config.service: About to execute: /usr/lib/systemd/scripts/nfs-utils_env.sh [ 221.106455] systemd-logind[642]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=609 reply_cookie=0 error-name=n/a error-message=n/a [ 221.106508] systemd-journald[366]: Successfully sent stream file descriptor to service manager. [ 221.106640] systemd[2743]: nfs-config.service: Executing: /usr/lib/systemd/scripts/nfs-utils_env.sh [ 221.109327] systemd-journald[366]: Successfully sent stream file descriptor to service manager. [ 221.109406] systemd[2745]: rpc-statd.service: Executing: /sbin/rpc.statd --no-notify [ 221.109800] systemd-journald[366]: Successfully sent stream file descriptor to service manager. [ 221.110029] systemd[2746]: rpc-statd-notify.service: Executing: /sbin/sm-notify [ 221.177840] systemd-logind[642]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/nss_2dlookup_2etarget interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=610 reply_cookie=0 error-name=n/a error-message=n/a [ 221.201798] systemd-logind[642]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/nfs_2dconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=611 reply_cookie=0 error-name=n/a error-message=n/a [ 221.225827] systemd-logind[642]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/nfs_2dconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=612 reply_cookie=0 error-name=n/a error-message=n/a [ 221.249897] systemd-logind[642]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/job/994 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=613 reply_cookie=0 error-name=n/a error-message=n/a [ 221.272214] systemd-logind[642]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=614 reply_cookie=0 error-name=n/a error-message=n/a [ 221.29
Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot
On 2017-12-14 00:09:23 (+0100), Michael Biebl wrote: > Am 13.12.2017 um 22:04 schrieb Peter 'p2' De Schrijver: > > On 2017-12-13 21:53:10 (+0100), Michael Biebl wrote: > >> Control: tags -1 + moreinfo > >> > >> > >> Am 13.12.2017 um 21:32 schrieb Peter De Schrijver: > >>> Package: systemd > >>> Version: 235-2 > >>> Severity: important > >> Please include more information about your network setup. > >> What tools do you use (NM, ifupdown, networkd), what configuration > > > > ifupdown > > > > >> (ethernet, wifi, dhcp, static), how does your nfs mount configuration > > > > Ethernet and OVS > > > >> look like (your fstab contains no information in that regard) > >> > > > > NFS mount is just done manually: > > > > mount freenas:/mnt/storage /nfs/ > > mount freenas:/mnt/storage/p2_home/ /nfs/p2_home/ > > What's the systemctl status and systemctl show output for these mount > points? > > HOME\p2@sunshine:~$ sudo systemctl status /nfs/ /nfs/p2_home/ â nfs.mount - /nfs Loaded: loaded (/proc/self/mountinfo) Active: active (mounted) since Fri 2017-12-15 20:23:23 EET; 14s ago Where: /nfs What: freenas:/mnt/storage Dec 15 20:23:23 sunshine systemd[1]: nfs.mount: Changed dead -> mounted â nfs-p2_home.mount - /nfs/p2_home Loaded: loaded (/proc/self/mountinfo) Active: active (mounted) since Fri 2017-12-15 20:23:25 EET; 11s ago Where: /nfs/p2_home What: freenas:/mnt/storage/p2_home/ Dec 15 20:23:25 sunshine systemd[1]: nfs-p2_home.mount: Changed dead -> mounted see attached file for systemctl show output Peter. Restart=no NotifyAccess=none RestartUSec=100ms TimeoutStartUSec=1min 30s TimeoutStopUSec=1min 30s RuntimeMaxUSec=infinity WatchdogUSec=0 WatchdogTimestampMonotonic=0 FailureAction=none PermissionsStartOnly=no RootDirectoryStartOnly=no RemainAfterExit=no GuessMainPID=yes MainPID=0 ControlPID=0 FileDescriptorStoreMax=0 NFileDescriptorStore=0 StatusErrno=0 Result=success UID=[not set] GID=[not set] NRestarts=0 ExecMainStartTimestampMonotonic=0 ExecMainExitTimestampMonotonic=0 ExecMainPID=0 ExecMainCode=0 ExecMainStatus=0 MemoryCurrent=[not set] CPUUsageNSec=[not set] TasksCurrent=[not set] IPIngressBytes=18446744073709551615 IPIngressPackets=18446744073709551615 IPEgressBytes=18446744073709551615 IPEgressPackets=18446744073709551615 Delegate=no CPUAccounting=no CPUWeight=[not set] StartupCPUWeight=[not set] CPUShares=[not set] StartupCPUShares=[not set] CPUQuotaPerSecUSec=infinity IOAccounting=no IOWeight=[not set] StartupIOWeight=[not set] BlockIOAccounting=no BlockIOWeight=[not set] StartupBlockIOWeight=[not set] MemoryAccounting=no MemoryLow=0 MemoryHigh=infinity MemoryMax=infinity MemorySwapMax=infinity MemoryLimit=infinity DevicePolicy=auto TasksAccounting=yes TasksMax=4915 IPAccounting=no UMask=0022 LimitCPU=infinity LimitCPUSoft=infinity LimitFSIZE=infinity LimitFSIZESoft=infinity LimitDATA=infinity LimitDATASoft=infinity LimitSTACK=infinity LimitSTACKSoft=8388608 LimitCORE=infinity LimitCORESoft=0 LimitRSS=infinity LimitRSSSoft=infinity LimitNOFILE=1048576 LimitNOFILESoft=1048576 LimitAS=infinity LimitASSoft=infinity LimitNPROC=256526 LimitNPROCSoft=256526 LimitMEMLOCK=16777216 LimitMEMLOCKSoft=16777216 LimitLOCKS=infinity LimitLOCKSSoft=infinity LimitSIGPENDING=256526 LimitSIGPENDINGSoft=256526 LimitMSGQUEUE=819200 LimitMSGQUEUESoft=819200 LimitNICE=0 LimitNICESoft=0 LimitRTPRIO=0 LimitRTPRIOSoft=0 LimitRTTIME=infinity LimitRTTIMESoft=infinity OOMScoreAdjust=0 Nice=0 IOSchedulingClass=0 IOSchedulingPriority=0 CPUSchedulingPolicy=0 CPUSchedulingPriority=0 TimerSlackNSec=5 CPUSchedulingResetOnFork=no NonBlocking=no StandardInput=null StandardOutput=inherit StandardError=inherit TTYReset=no TTYVHangup=no TTYVTDisallocate=no SyslogPriority=30 SyslogLevelPrefix=yes SyslogLevel=6 SyslogFacility=3 SecureBits=0 CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend AmbientCapabilities= DynamicUser=no RemoveIPC=no MountFlags= PrivateTmp=no PrivateDevices=no ProtectKernelTunables=no ProtectKernelModules=no ProtectControlGroups=no PrivateNetwork=no PrivateUsers=no ProtectHome=no ProtectSystem=no SameProcessGroup=no UtmpMode=init IgnoreSIGPIPE=yes NoNewPrivileges=no SystemCallErrorNumber=0 LockPersonality=no RuntimeDirectoryPreserve=no
Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot
OVS setup is: HOME\p2@sunshine:~$ sudo ovs-vsctl show [sudo] password for HOME\p2: 6a4c96dd-80aa-4954-a2f8-22bc7fb56898 Bridge sunshine-net Port sunshine Interface sunshine type: internal Port sunshine-net Interface sunshine-net type: internal Port "eth0" Interface "eth0" ovs_version: "2.6.2" see attachement for interfaces file Peter. # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback allow-hotplug sunshine auto sunshine iface sunshine inet dhcp auto eth0 iface eth0 inet manual # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback allow-hotplug sunshine auto sunshine iface sunshine inet dhcp auto eth0 iface eth0 inet manual
Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot
On 2017-12-13 21:53:10 (+0100), Michael Biebl wrote: > Control: tags -1 + moreinfo > > > Am 13.12.2017 um 21:32 schrieb Peter De Schrijver: > > Package: systemd > > Version: 235-2 > > Severity: important > Please include more information about your network setup. > What tools do you use (NM, ifupdown, networkd), what configuration ifupdown > (ethernet, wifi, dhcp, static), how does your nfs mount configuration Ethernet and OVS > look like (your fstab contains no information in that regard) > NFS mount is just done manually: mount freenas:/mnt/storage /nfs/ mount freenas:/mnt/storage/p2_home/ /nfs/p2_home/ freenas is a freenas instance on the local network. Peter.
Bug#686949: place and route
I had a quick look at the tools. They convert a floorplan description into a bitstream and back. However for a complete workflow the following bits are missing: * VHDL/verilog compiler to netlist * place and route tool to turn the netlist into a floorplan Is this correct? Thanks, Peter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#569945: hercules: produces a disconcerting whinek
> | MAINSIZE64 64MB main memory is a bit too small for modern debian I'm afraid. Could you try again following : http://www.josefsipek.net/docs/s390-linux/hercules-s390.html Thanks, Peter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#569913: hercules: please shorten package description
Hi, > Package: hercules > Version: 3.06-1.3 > Severity: wishlist > > Hi Peter, > > fjp pointed me to the hercules package --- looks to be just what I > needed, thank you for maintaining it. The extended package description > is a little overwhelming. I???m quoting it here for reference with > comments. > > | Hercules is an open source software implementation of the mainframe > System/370 > | and ESA/390 architectures, in addition to the new 64-bit z/Architecture. > > Nitpick: I would just say: > > Hercules is a software implementation of the mainframe System/370... > > because isn???t inclusion in Debian enough to imply it is open source? Yes. This part of the description is most likely derived from the hercules website (http://www.hercules-390.org/). Hercules also runs on other host platforms besides Linux where open source might be less obvious. > > | This means that your PC can emulate an IBM mainframe processor. > [...] > | You will have to use a free software > | operating system such as Linux, write the operating system or standalone > program > | yourself, obtain a license from IBM to run one of their operating systems on > | your PC, or use IBM programs and operating systems which have been placed > in the > | public domain. > > Neat. > > | Virtual networking can be accomplished using the TUN/TAP driver in 2.2 and > 2.4 > | kernels. For older kernels, try the vmnet package. > > This information sounds outdated (2.4.x kernels?). But anyway, this > means that getting networking set up requires root access on the host > machine, right? I am not sure what the easiest way to convey this is; > maybe > > Virtual networking can be accomplished using the TUN/TAP > driver in the host (non-emulated) system???s Linux kernel. > TUN/TAP is still used with 2.6 kernels. But yes, 2.2 and 2.4 can be removed :) > | Hercules was created by Roger Bowler and is maintained by Jay Maynard. Jan > | Jaeger designed and implemented many of the advanced features of Hercules. > > I think this information does not belong in the package description, > because it would not help someone decide whether to install Hercules, > and the description is already long. > The copyright file has all this info indeed. So this can be removed. Cheers, Peter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#564779: mlpost_0.7.4-1(mips/unstable):
On 2010-01-12 15:28:30 (+0100), St?phane Glondu wrote: > tags 564779 + unreproducible > severity 564779 normal > thanks > > Peter De Schrijver a écrit : > > Package: mlpost > > Version: 0.7.4-1 > > [...] > > There was an error while trying to autobuild your package: > > [...] > >> + mkdir -p img/ && cd img/ && ../customdoc/img_doc.byte >> /dev/null && cd > >> .. > >> fatal: exec failed: No such file or directoryfatal: Command failed: etex > >> --parse-first-line --interaction=nonstopmode mp146481.tex; see mpxerr.log > >> Command exited with code 1. > >> make[1]: *** [doc] Error 10 > >> make[1]: Leaving directory `/build/buildd/mlpost-0.7.4' > >> make: *** [debian/stamp-makefile-build] Error 2 > >> dpkg-buildpackage: error: debian/rules build gave error exit status 2 > > [...] > > I've successfully built mlpost on a (qemu) mips box, so I'm pretty sure > the buildd is broken. As I said, texlive-binaries doesn't seem to be > installed in the provided build log. > > My build log is available at (I used cowbuilder): > > http://debian.glondu.net/debian/pending/mlpost_0.7.4-1_mips.build > > mlpost is 17 days old now and cannot migrate to testing because of this > stupid error. Is it OK that I upload my home-built mips binary packages? The texlive-binaries are installed. But the etex symlink is not there for some reason. I guess there is a wrong Replaces clause somewhere. Cheers, Peter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#530573: remctl_2.14-1(mips/unstable): FTBFS on mips - regression test failure
> > A retry of this on mips produced the same problem, but remctl is > building fine on all other hosts. At this point, I'm suspecting that > there's something different about this particular buildd that's causing > accept() to fail. I see that both of the failed builds are on mayr, and > the last successful build was on ball. > > Unfortunately, mahler appears not to have schroot or any development > packages installed, so I can't easily try doing a mips build and be sure > there isn't something else wrong. > > Could you try the above or point me in the right direction to get more > details about what could be going wrong? (I'm not sure if I should be > mailing debian-mips or m...@buildd instead.) See test output in attachment. It seems at least ipv6 is not enabled in this kernel. Could that be a problem ? Cheers, Peter. 1..87 ok 1 - IPv4 server test ok 2 - ...socket accept ok 3 - ...socket read ok 4 # skip IPv6 not supported ok 5 # skip IPv6 not supported ok 6 # skip IPv6 not supported # cannot listen to socket: Bad file descriptor not ok 7 - IPv6 server test not ok 8 - IPv6 server test not ok 9 - IPv6 server test ok 10 # skip IPv6 not configured ok 11 # skip IPv6 not configured ok 12 # skip IPv6 not configured ok 13 # skip IPv6 not configured ok 14 # skip IPv6 not configured ok 15 # skip IPv6 not configured ok 16 - IPv4 network client ok 17 - ...socket accept ok 18 - ...socket read ok 19 - IPv4 server test ok 20 - ...socket accept ok 21 - ...socket read ok 22 # skip IPv6 not supported ok 23 # skip IPv6 not supported ok 24 # skip IPv6 not supported # cannot listen to socket: Bad file descriptor not ok 25 - IPv6 server test not ok 26 - IPv6 server test not ok 27 - IPv6 server test ok 28 # skip IPv6 not configured ok 29 # skip IPv6 not configured ok 30 # skip IPv6 not configured ok 31 # skip IPv6 not configured ok 32 # skip IPv6 not configured ok 33 # skip IPv6 not configured ok 34 - IPv4 network client ok 35 - ...socket accept ok 36 - ...socket read ok 37 - sprint of 127.0.0.1 ok 38 - ...with right results ok 39 - sockaddr_port ok 40 - sockaddr_equal ok 41 - sockaddr_equal of unequal addresses ok 42 - ...and the other way around ok 43 - sprint of IPv6 address ok 44 - ...with right results ok 45 - sockaddr_port IPv6 ok 46 - sockaddr_equal IPv6 ok 47 - ...and not equal to IPv4 ok 48 - ...other way around ok 49 - sprint of IPv4-mapped address ok 50 - ...with right IPv4 result ok 51 - sockaddr_equal of IPv4-mapped address ok 52 - ...and other way around ok 53 - ...but not some other address ok 54 - ...and the other way around ok 55 - equal not equal with address mismatches ok 56 - port meaningless for AF_UNIX ok 57 - compare 127.0.0.1 127.0.0.1 (null) ok 58 - compare 127.0.0.1 127.0.0.2 (null) ok 59 - compare 127.0.0.1 127.0.0.0 31 ok 60 - compare 127.0.0.1 127.0.0.0 32 ok 61 - compare 127.0.0.1 127.0.0.0 255.255.255.255 ok 62 - compare 127.0.0.1 127.0.0.0 255.255.255.254 ok 63 - compare 10.10.4.5 10.10.4.255 24 ok 64 - compare 10.10.4.5 10.10.4.255 25 ok 65 - compare 10.10.4.5 10.10.4.255 255.255.255.0 ok 66 - compare 10.10.4.5 10.10.4.255 255.255.255.128 ok 67 - compare 129.0.0.0 1.0.0.0 1 ok 68 - compare 129.0.0.0 1.0.0.0 0 ok 69 - compare 129.0.0.0 1.0.0.0 0.0.0.0 ok 70 - compare FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 (null) ok 71 - compare FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 128 ok 72 - compare FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 60 ok 73 - compare ::127 0:0::127 128 ok 74 - compare ::127 0:0::128 120 ok 75 - compare ::127 0:0::128 128 ok 76 - compare ::7fff 0:0::8000 113 ok 77 - compare ::7fff 0:0::8000 112 ok 78 - compare ::3: ::2: 120 ok 79 - compare ::3: ::2: 119 ok 80 - compare ::1 7fff::1 1 ok 81 - compare ::1 7fff::1 0 ok 82 - compare fffg::1 fffg::1 (null) ok 83 - compare ::1 7fff::1 -1 ok 84 - compare ::1 ::1 -1 ok 85 - compare ::1 ::1 129 ok 86 - compare fred fred (null) ok 87 - compare (null) ok 88 - compare 0 ok 89 - compare 127.0.0.1 127.0.0.1 pete ok 90 - compare 127.0.0.1 127.0.0.1 1p ok 91 - compare 127.0.0.1 127.0.0.1 1p ok 92 - compare 127.0.0.1 127.0.0.1 -1 ok 93 - compare 127.0.0.1 127.0.0.1 33
Bug#524584: lastfm_1:1.5.1.31879.dfsg-2(mips/unstable): FTBFS on mips
On 2009-04-18 09:36:37 (-0700), John Stamp wrote: > There are only a few minor changes between -1 and -2, and mips > successfully completed a bin-NMU of -1+b2 on March 11. > > Here's the relevant snippet from the build of -1+b2: > > > /usr/bin/uic-qt4 confirmdialog.ui -o ../../build/ui_confirmdialog.h > > g++ -c -pipe -g -O2 -g -Wall -O2 -w -D_REENTRANT -fPIC -DNBREAKPAD > > -DLINUX -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB > > -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. > > -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtCore > > -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtNetwork > > -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtGui -I/usr/include/qt4 > > -I. -I../libUnicorn -I../../src -I../../build > > -I../../build/Moose/release -I../../build > > -o ../../build/Moose/release/confirmdialog.o confirmdialog.cpp > > And the same section just before the errors that you cited for -2: > > > /usr/bin/uic-qt4 confirmdialog.ui -o ../../../../ui_confirmdialog.h > > g++ -c -pipe -g -O2 -g -Wall -O2 -w -D_REENTRANT -fPIC -DNBREAKPAD > > -DLINUX -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB > > -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. > > -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtCore > > -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtNetwork > > -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtGui -I/usr/include/qt4 > > -I/src/libMoose -I/src/libUnicorn -I/src -I/build > > -I../../../../Moose/release -I/build > > -o ../../../../Moose/release/confirmdialog.o confirmdialog.cpp > > As you can see, a number of include and destination paths are broken. > e.g.: > -I/src/libMoose -I/src/libUnicorn -I/src -I/build > > I suspect the problem is related to lastfm's definitions.pro.inc, where > it defines: > > ROOT_DIR = $$system( pwd ) > > and proceeds from there: > > BIN_DIR = $$ROOT_DIR/bin > DESTDIR = $$BIN_DIR > [...] > INCLUDEPATH += $$ROOT_DIR/src/libMoose $$ROOT_DIR/src/libUnicorn > [...] > > Any idea why this now a problem? No. We did find out there is an incompatibility between glibc and the kernel installed on the mips buildds. I'm not sure this is related, but I want to wait to look into this until we fixed this issue. Cheers, Peter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#524593: collectd_4.6.2-1(mips/unstable): FTBFS on mips. libnetlink not compiled correctly ?
On 2009-04-18 17:44:45 (+0200), Sebastian Harl wrote: > Hi, > > On Sat, Apr 18, 2009 at 06:28:36PM +0300, Peter 'p2' De Schrijver wrote: > > On 2009-04-18 17:19:10 (+0200), Sebastian Harl wrote: > > > That looks like mips behaves like most other architectures and does not > > > allow to link static object compiled without -fPIC into shared objects. > > > Is that true? I wonder why it has had been working so far then. > > > > That's true yes. > > Do you happen to know if that's true for mipsel as well? So far, > collectd has not been built there yet, so I cannot tell from the build > logs ;-) It's true for mipsel as well. Cheers, Peter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#524593: collectd_4.6.2-1(mips/unstable): FTBFS on mips. libnetlink not compiled correctly ?
On 2009-04-18 17:19:10 (+0200), Sebastian Harl wrote: > Hi, > > Thanks for reporting this. > > On Sat, Apr 18, 2009 at 01:15:32PM +0300, Peter De Schrijver wrote: > > > /bin/sh ../libtool --tag=CC --mode=link mips-linux-gnu-gcc -Wall > > > -Werror -Wall -g -O2 -module -avoid-version -o netlink.la -rpath > > > /usr/lib/collectd netlink_la-netlink.lo -lnetlink > > > mips-linux-gnu-gcc -shared .libs/netlink_la-netlink.o -lnetlink > > > -Wl,-soname -Wl,netlink.so -o .libs/netlink.so > > > /usr/bin/ld: > > > /usr/lib/gcc/mips-linux-gnu/4.3.3/../../../../lib/libnetlink.a(libnetlink.o): > > > relocation R_MIPS_HI16 against `__gnu_local_gp' can not be used when > > > making a shared object; recompile with -fPIC > > > /usr/lib/gcc/mips-linux-gnu/4.3.3/../../../../lib/libnetlink.a: could not > > > read symbols: Bad value > > > collect2: ld returned 1 exit status > > That looks like mips behaves like most other architectures and does not > allow to link static object compiled without -fPIC into shared objects. > Is that true? I wonder why it has had been working so far then. > That's true yes. I have no idea why it has been working up till now then. > If that's the case, the only way to fix this is by disabling the netlink > plugin on mips as well. > Ok. Cheers, Peter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#516962: blender_2.46+dfsg-6+b1(mips/unstable): FTBFS on mips - missing include file(s) ?
Hi, > Peter De Schrijver (24/02/2009): > > Package: blender > > Version: 2.46+dfsg-6+b1 > > Severity: serious > > Hello, > > > > source/blender/blenkernel/intern/writeffmpeg.c:874: error: 'outfile' > > > undeclared (first use in this function) > > > source/blender/blenkernel/intern/writeffmpeg.c:875: warning: implicit > > > declaration of function 'av_write_trailer' > > > source/blender/blenkernel/intern/writeffmpeg.c:880: error: 'video_stream' > > > undeclared (first use in this function) > > > source/blender/blenkernel/intern/writeffmpeg.c:881: warning: implicit > > > declaration of function 'avcodec_close' > > > source/blender/blenkernel/intern/writeffmpeg.c:890: warning: implicit > > > declaration of function 'av_freep' > > > source/blender/blenkernel/intern/writeffmpeg.c:895: error: > > > 'current_frame' undeclared (first use in this function) > > > source/blender/blenkernel/intern/writeffmpeg.c:896: warning: implicit > > > declaration of function 'delete_picture' > > > source/blender/blenkernel/intern/writeffmpeg.c:900: error: 'AVFMT_NOFILE' > > > undeclared (first use in this function) > > > source/blender/blenkernel/intern/writeffmpeg.c:901: warning: implicit > > > declaration of function 'url_fclose' > > > source/blender/blenkernel/intern/writeffmpeg.c:905: warning: implicit > > > declaration of function 'av_free' > > > source/blender/blenkernel/intern/writeffmpeg.c:922: warning: implicit > > > declaration of function 'sws_freeContext' > > > scons: *** [build/linux2/source/blender/blenkernel/intern/writeffmpeg.o] > > > Error 1 > > > scons: building terminated because of errors. > > > make: *** [build-stamp] Error 2 > > > dpkg-buildpackage: failure: debian/rules build gave error exit status 2 > > the ???funny??? bits being that it previously built successfully. I guess > I'll have to dig some ffmpeg/libavcodec changes??? Yeah. It looks like ffmpeg is somehow broken :( Sorry for the noise. I guess I will close this again. Cheers, Peter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514795: [Pkg-openmpi-maintainers] Bug#514795: FTBFS on mips
Hi Manuel, > Hi Peter! > > Am Dienstag, den 10.02.2009, 22:26 + schrieb Peter De Schrijver: > > Problem with atomic-asm.S doesn't seem to be solved yet. See attached > > log file. > > Thanks for your report! I'm aware of the issue and hope to find some > time soon to debug it on a porter box. > > I'm currently triaging the Open MPI bug but most of them are rather > complex. A short-term solution would be to downgrade the bug (and merge > it with #489173) and don't build Open MPI on MIPS until the remaining > issues are fixed. Does this seem acceptable to you? > Yes. I think we can live with that. > Also, if you have any insights how high the demand for the MIPS support > is, please let me know. It would help me to prioritize the remaining > (build) issues. I don't really know to be honest. I don't think there is a high demand on the current debian/mips supported hardware. Cheers, Peter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513819: Package FTBFS on mips
On 2009-02-01 19:28:45 (-0500), Tim Abbott wrote: > Okay, so the actual problem is that sqrtl is not defined on mips, because > mips has the whole no long doubles thing: > > gcc -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g > -O2 -g -Wall -O2 -fPIC -I/build/buildd/sagemath-3.0.5dfsg/local//include > -I/build/buildd/sagemath-3.0.5dfsg/local//include/csage > -I/build/buildd/sagemath-3.0.5dfsg/devel//sage/sage/ext -I/usr/include > -I/usr/include/numpy -I/usr/include/FLINT -I/usr/include/givaro > -I/usr/include/gsl -I/usr/include/fplll -I/usr/include/eclib > -I/usr/include/gmp++ -I/usr/include/linbox -I/usr/include/NTL > -I/usr/include/pari -I/usr/include/qd -I/usr/include/singular > -I/usr/include/singular/singular -I/usr/include/symmetrica > -I/usr/include/polybori -I/usr/include/cudd -I/usr/include/polybori/groebner > -I/usr/include/zn_poly -I/usr/include/python2.5 -c > sage/combinat/partitions_c.cc -o > build/temp.linux-mips-2.5/sage/combinat/partitions_c.o -w -w > cc1plus: warning: command line option "-Wstrict-prototypes" is valid for > Ada/C/ObjC but not for C++ > sage/combinat/partitions_c.cc: In function 'void > initialize_constants(unsigned int, unsigned int)': > sage/combinat/partitions_c.cc:788: error: 'sqrtl' was not declared in this > scope > error: command 'gcc' failed with exit status 1 > sage: There was an error installing modified sage library code. > > sage/combinat/partitions_c.cc seems to be the only file affected, so this > should be relatively simple. Is there a standard fix for this problem? > I think it's best to use some form of conditional compilation based on either an autoconf test or the architecture. You could look at #451049 or #495465. Cheers, Peter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#494493: Autodetection is broken
The module probably works if you force the model as mentioned in #473671, but autodetection is broken. The patch fixes this. Tested on Medion MD97600. Cheers, Peter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#489785: please add sample config file for cortex M3 target
Package: openocd Version: 0.0+r655-1 Severity: wishlist Tags: patch See sample config in attachement. Tested on a LM3S8962 development board. Thanks. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24.2 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages openocd depends on: ii libc62.7-6 GNU C Library: Shared libraries ii libftdi1 0.12-1 Library to control and program the ii libusb-0.1-4 2:0.1.12-11 userspace USB programming library openocd recommends no packages. -- no debconf information #daemon configuration telnet_port gdb_port gdb_detach reset gdb_memory_map enable gdb_flash_program enable #interface interface ft2232 ft2232_device_desc "Stellaris Evaluation Board" ft2232_layout evb_lm3s811 ft2232_vid_pid 0x0403 0xbcd9 jtag_speed 6 #LM3S811 Evaluation Board has only srst reset_config srst_only separate #jtag scan chain #format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE) jtag_device 4 0x1 0xf 0xe #target configuration daemon_startup reset #target #target arm7tdmi target cortex_m3 little run_and_halt 0 # 4k working area at base of ram working_area 0 0x2000 0x1000 nobackup #target_script 0 reset ../doc/scripts/evb_lm3s811_test.script #flash configuration flash bank stellaris 0 262144 0 0 0
Bug#480473: openocd coredumps on AMD64
Package: openocd Version: 0.0+r423-1+b1 Severity: important Openocd coredumps on AMD64 at startup. Latest svn version fixes this. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24.2 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages openocd depends on: ii libc62.7-6 GNU C Library: Shared libraries ii libftdi1 0.11-1 Library to control and program the ii libusb-0.1-4 2:0.1.12-11 userspace USB programming library openocd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#472574: jack support should be enabled for AMD64
Package: portaudio19 Severity: normal The memory barrier instructions for i386 (mfence, lfence and sfence) also work on amd64. So there is no reason to prohibit the use of jack. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24.2 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414519: closed by Peter 'p2' De Schrijver <[EMAIL PROTECTED]> (fixed in some previous version)
On 2008-03-19 23:58:40 (+0100), Aurelien Jarno <[EMAIL PROTECTED]> wrote: > reopen 414519 > thanks > > Debian Bug Tracking System a écrit : > > This is an automatic notification regarding your Bug report > > which was filed against the hercules package: > > > > #414519: hercules: FTBFS on GNU/kFreeBSD > > > > It has been closed by Peter 'p2' De Schrijver <[EMAIL PROTECTED]>. > > > > Their explanation is attached below along with your original report. > > If this explanation is unsatisfactory and you have not received a > > better one in a separate message then please contact Peter 'p2' De > > Schrijver <[EMAIL PROTECTED]> by > > replying to this email. > > > > > > > > > > > > > > Sujet: > > fixed in some previous version > > That is wrong. One part has been fixed, but as explain in the last > message (see the bug log), the config.guess and config.sub files needs > to be updated to a more recent version. > New version ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414519: closed by Peter 'p2' De Schrijver <[EMAIL PROTECTED]> (fixed in some previous version)
On 2008-03-19 23:58:40 (+0100), Aurelien Jarno <[EMAIL PROTECTED]> wrote: > reopen 414519 > thanks > > Debian Bug Tracking System a écrit : > > This is an automatic notification regarding your Bug report > > which was filed against the hercules package: > > > > #414519: hercules: FTBFS on GNU/kFreeBSD > > > > It has been closed by Peter 'p2' De Schrijver <[EMAIL PROTECTED]>. > > > > Their explanation is attached below along with your original report. > > If this explanation is unsatisfactory and you have not received a > > better one in a separate message then please contact Peter 'p2' De > > Schrijver <[EMAIL PROTECTED]> by > > replying to this email. > > > > > > > > > > > > > > Sujet: > > fixed in some previous version > > That is wrong. One part has been fixed, but as explain in the last > message (see the bug log), the config.guess and config.sub files needs > to be updated to a more recent version. > There is no newer version then 3.05 of this package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420046: marked as done (libgcr410: FTBFS: ./ifdhandler.h:115: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'IFDHCreateChannel')
> The libgcr410_2.4.0-8.diff.gz does not agree with that. It's also a > well know feature that it doesn't do that. Your own log even shows the > warning. > The warning is a problem of dpkg-source. The diff was generated by hand, and deletes the file perfectly here. > The attached simple patch fixes it. Please apply it. > This is an unacceptable hack which will not be applied. Cheers, Peter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420046: marked as done (libgcr410: FTBFS: ./ifdhandler.h:115: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'IFDHCreateChannel')
On 2008-01-31 21:05:39 (+0100), Kurt Roeckx <[EMAIL PROTECTED]> wrote: > reopen 420046 > thanks > > > Subject: works fine > > See buildlog (on amd64) > > [...] > dpkg-source: warning: ignoring deletion of file ifdhandler.h > [...] > > Peter, > > You seem to be the only one that is able to actually build this. > Various people have shown that it doesn't work. I've already suggest > that you should try and use the sources as they were uploaded, and that > you're probably using different sources than the rest of us. > > Looking at the difference between 2.4.0-7 and 2.4.0-8, the only thing > mentioning ifdhandler.h is the changelog entry about it. The other > 2 changes I see in the diff are the other 2 things mentioned in the > changelog. > > Looking at your build log, it's also obvious that you deleted it. But > the .diff generated does not reflect that. You can't delete files in > the .diff. You will need to do that in the rules file. > My .diff deletes the file fine. So there must be something wrong with your build process. Cheers, Peter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#463190: k3b does not handle 24bit sampled flac files
Package: k3b Version: 1.0.4-3 Severity: normal When trying to burn an audio CD based on 24bit sampled flac files, k3b complains about 'Unable to handle the following files due to an unsupported format' without mentioning the problem is the sample size, not the flac format itself. See http://www.aavepyora.net/musa/bizarroworld.html for some example files. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.24-rc6 (SMP w/2 CPU cores; PREEMPT) 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 k3b depends on: ii cdparanoia 3.10+debian~pre0-5 audio extraction tool for sampling ii cdrdao 1:1.2.2-10 records CDs in Disk-At-Once (DAO) ii genisoimage 9:1.1.6-1 Creates ISO-9660 CD-ROM filesystem ii kdebase-bin 4:3.5.8.dfsg.1-5core binaries for the KDE base mod ii kdelibs-data 4:3.5.8.dfsg.1-5core shared data for all KDE appli ii kdelibs4c2a 4:3.5.8.dfsg.1-5core libraries and binaries for al ii libacl1 2.2.45-1Access control list shared library ii libart-2.0-2 2.3.19-3Library of functions for 2D graphi ii libattr1 1:2.4.39-1 Extended attribute shared library ii libaudio21.9-3 Network Audio System - shared libr ii libc62.7-3 GNU C Library: Shared libraries ii libdbus-1-3 1.1.1-3 simple interprocess messaging syst ii libdbus-qt-1-1c2 0.62.git.20060814-2 simple interprocess messaging syst ii libdvdread3 0.9.7-5 library for reading DVDs ii libexpat11.95.8-4XML parsing C library - runtime li ii libfam0 2.7.0-13Client library to control the FAM ii libfontconfig1 2.4.2-1.3 generic font configuration library ii libfreetype6 2.3.5-1+b1 FreeType 2 font engine, shared lib ii libgcc1 1:4.2.2-4 GCC support library ii libhal1 0.5.10-4Hardware Abstraction Layer - share ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libidn11 1.1-1 GNU libidn library, implementation ii libjpeg626b-14 The Independent JPEG Group's JPEG ii libk3b3 1.0.4-3 The KDE cd burning application lib ii libmusicbrainz4c2a 2.1.5-1 Second generation incarnation of t ii libpng12-0 1.2.15~beta5-3 PNG library - runtime ii libqt3-mt3:3.3.7-9 Qt GUI Library (Threaded runtime v ii libsm6 2:1.0.3-1+b1X11 Session Management library ii libstdc++6 4.2.2-4 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-7 X11 client-side library ii libxcursor1 1:1.1.9-1 X cursor management library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxft2 2.1.12-2FreeType-based font drawing librar ii libxi6 2:1.1.3-1 X11 Input extension library ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library ii libxrandr2 2:1.2.2-1 X11 RandR extension library ii libxrender1 1:0.9.4-1 X Rendering Extension client libra ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii wodim9:1.1.6-1 command line CD/DVD writing tool ii zlib1g 1:1.2.3.3.dfsg-7compression library - runtime Versions of packages k3b recommends: pn dvd+rw-tools (no description available) pn kcontrol (no description available) pn kdebase-kio-plugins(no description available) pn vcdimager (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420046: Still not fixed...
On 2008-01-14 17:39:21 (+), Marco Rodrigues <[EMAIL PROTECTED]> wrote: > I still got the same error with the version 2.4.0-8. > I tried again here. I can't reproduce your problem. Cheers, Peter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354906: ITP: libftdi -- programming interface for FTDI FT2232C, FT232BM and FT245BM USB interface chips.
Package: wnpp Severity: wishlist Owner: "Peter 'p2' De Schrijver" <[EMAIL PROTECTED]> * Package name: libftdi Version : 0.7 Upstream Author : Intra2net AG <[EMAIL PROTECTED]> * URL : http://www.intra2net.com/de/produkte/opensource/ftdi/ * License : LGPL Description : programming interface for FTDI FT2232C, FT232BM and FT245BM USB interface chips. libftdi is a library which provides a programming interface for the advanced features of the FTDI FT2232C, FT232BM and FT245BM chips. These chips can act as a USB interface to GPIO lines, a multiprotocol synchronous serial engine or a 8051 style bus in addition to a standard USB to asynchronous serial convertor. This library provides access to the additional functions. More information on the FTDI chips can be found on http://www.ftdichip.com. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.13.4 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354893: abcde: seperate directories for different codecs
Package: abcde Version: 2.3.99-1 Severity: wishlist It would be useful to be able to specify a seperate directory for each encoder format. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.13.4 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8) Versions of packages abcde depends on: ii cd-discid 0.9-1 CDDB DiscID utility ii cdda2wav 4:2.01+01a01-2 Creates WAV files from audio CDs ii cdparanoia3a9.8-11 An audio extraction tool for sampl ii flac 1.1.2-3Free Lossless Audio Codec - comman ii lame 3.96-1 LAME Ain't an MP3 Encoder ii vorbis-tools 1.0.1-1.1 Several Ogg Vorbis Tools ii wget 1.10.2-1 retrieves files from the web -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354892: abcde: Add support for uploading cddb data
Package: abcde Version: 2.3.99-1 Severity: wishlist It would be useful to be able to upload a modified cddb entry to a cddb server. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.13.4 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8) Versions of packages abcde depends on: ii cd-discid 0.9-1 CDDB DiscID utility ii cdda2wav 4:2.01+01a01-2 Creates WAV files from audio CDs ii cdparanoia3a9.8-11 An audio extraction tool for sampl ii flac 1.1.2-3Free Lossless Audio Codec - comman ii lame 3.96-1 LAME Ain't an MP3 Encoder ii vorbis-tools 1.0.1-1.1 Several Ogg Vorbis Tools ii wget 1.10.2-1 retrieves files from the web -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#340234: subversion: prompt user in case of http redirect
Package: subversion Version: 1.0.6-2 Severity: wishlist It would be nice if svn would prompt the user to connect to a redirected URL instead of just dumping the somewhat cryptic error message as shown in the following example : [EMAIL PROTECTED]:~/abcde$ svn co http://svn.hispalinux.es:8080/svn/abcde/trunk svn: PROPFIND request failed on '/svn/abcde/trunk' svn: PROPFIND of '/svn/abcde/trunk': 302 Found (http://svn.hispalinux.es:8080) -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.13.4 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages subversion depends on: ii db4.2-util 4.2.52-18 Berkeley v4.2 Database Utilities ii libapr0 2.0.53-4the Apache Portable Runtime ii libc62.3.5-6 GNU C Library: Shared libraries an ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [ ii libexpat11.95.8-1XML parsing C library - runtime li ii libldap2 2.1.30-3OpenLDAP libraries ii libneon240.24.7.dfsg-0.2 An HTTP and WebDAV client library ii libssl0.9.7 0.9.7e-3SSL shared libraries ii libsvn0 1.0.6-2 Shared libraries used by Subversio ii libxml2 2.6.22-1GNOME XML library ii patch2.5.9-2 Apply a diff file to an original ii zlib1g 1:1.2.2-4 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323733: patch
Hi, Attached you will find a patch which makes gnubg compile with gcc 4.0. Cheers, Peter (p2). diff -urN gnubg-0.12/gtkprefs.c fixed/gnubg-0.12/gtkprefs.c --- gnubg-0.12/gtkprefs.c 2001-10-31 16:57:40.0 +0100 +++ fixed/gnubg-0.12/gtkprefs.c 2005-08-27 22:01:21.0 +0200 @@ -42,10 +42,12 @@ gtk_color_selection_set_opacity #endif +GtkWidget *pwBoard; + static GtkAdjustment *apadj[ 2 ], *paAzimuth, *paElevation, *apadjCoefficient[ 2 ], *apadjExponent[ 2 ], *apadjPoint[ 2 ], *padjBoard, *padjSpeed; -static GtkWidget *apwColour[ 2 ], *apwPoint[ 2 ], *pwBoard, *pwTranslucent, +static GtkWidget *apwColour[ 2 ], *apwPoint[ 2 ], *pwTranslucent, *pwLabels, *pwUseDiceIcon, *pwPermitIllegal, *pwBeepIllegal, *pwHigherDieFirst, *pwAnimateNone, *pwAnimateBlink, *pwAnimateSlide, *pwSpeed; diff -urN gnubg-0.12/sgf.c fixed/gnubg-0.12/sgf.c --- gnubg-0.12/sgf.c2001-11-01 16:47:56.0 +0100 +++ fixed/gnubg-0.12/sgf.c 2005-08-27 21:57:10.0 +0200 @@ -279,6 +279,7 @@ break; default: + break; /* ignore */ } signature.asc Description: Digital signature
Bug#323292: fix
Hi, The attached patch fixes the build problem on 64bit architectures. I tested it on alpha, but it should work on the other 64bit architectures as well. Cheers, Peter (p2). diff -urN libmetakit2.4.9.3-2.4.9.3/python/PyRowRef.cpp fixed/libmetakit2.4.9.3-2.4.9.3/python/PyRowRef.cpp --- libmetakit2.4.9.3-2.4.9.3/python/PyRowRef.cpp 2004-01-21 02:46:06.0 +0100 +++ fixed/libmetakit2.4.9.3-2.4.9.3/python/PyRowRef.cpp 2005-08-27 17:01:25.0 +0200 @@ -24,12 +24,12 @@ } static int PyRowRef_print(PyRowRef *o, FILE *f, int) { - fprintf(f, "", (int)o); + fprintf(f, "", o); return 0; } static int PyRORowRef_print(PyRowRef *o, FILE *f, int) { - fprintf(f, "", (int)o); + fprintf(f, "", o); return 0; } diff -urN libmetakit2.4.9.3-2.4.9.3/python/PyView.cpp fixed/libmetakit2.4.9.3-2.4.9.3/python/PyView.cpp --- libmetakit2.4.9.3-2.4.9.3/python/PyView.cpp 2004-01-21 02:46:06.0 +0100 +++ fixed/libmetakit2.4.9.3-2.4.9.3/python/PyView.cpp 2005-08-27 17:40:27.0 +0200 @@ -971,15 +971,15 @@ } static int PyView_print(PyView *o, FILE *f, int) { - fprintf(f, "", (int)o); + fprintf(f, "", o); return 0; } static int PyViewer_print(PyView *o, FILE *f, int) { - fprintf(f, "", (int)o); + fprintf(f, "", o); return 0; } static int PyROViewer_print(PyView *o, FILE *f, int) { - fprintf(f, "", (int)o); + fprintf(f, "", o); return 0; } signature.asc Description: Digital signature
Bug#270801: netaboot with 'small' images
Hi, Could you give me a complete log of the bootstrap (ie. starting from the boot command entered at the SRM prompt) ? It would be useful to know if there is any message printed by aboot itself. Normally aboot prints a banner including version quite early during boot. Thanks, Peter (p2). signature.asc Description: Digital signature
Bug#322300: openhackware: should not try to build on !powerpc environments
Hi, > No, it's code that can be used by emulators like qemu, that's why > it's an all package, there's existing practice for this, and the No. The emulator is still a ppc processor (albeit a software implementation of it). The Architecture: field specifies the cpu architecture(s) for which binaries have to be generated, which is only powerpc in this case. Otherwise we could just as well have no Architecture: field. Afterall qemu can also emulate an i386 processor, so you can always run the i386 binary, no matter what architecture you're using. > problem comes from a deficiency in the source format, that does > not allow to specify that an all package needs a specific building > environment (or arch). > No. The problem is that cross compiling is not covered by debian yet. The solution is to make debian cross compiler aware, not to hack around the problem by declaring every package Architecture: all. > The only thing I can do is fail gracefully with a message if the > environment, be it native or a cross toolchain, is not the > apropropriate. That defeats the purpose of build dependencies. The whole idea of having build dependencies is that the buildds know what's required to build a package instead of just trying and see what happens. Cheers, Peter (p2). signature.asc Description: Digital signature
Bug#318791: patch
Hi, Please find attached a patch which should solve the problem. It's untested on a 64bit machine however. Feel free to test and report the result. Thanks, Peter (p2). diff -ruN orig/opencv-0.9.6/tests/cv/src/apyramids.cpp opencv-0.9.6/tests/cv/src/apyramids.cpp --- orig/opencv-0.9.6/tests/cv/src/apyramids.cpp2005-08-11 00:27:36.0 +0100 +++ opencv-0.9.6/tests/cv/src/apyramids.cpp 2005-08-10 23:54:45.0 +0100 @@ -186,7 +186,7 @@ const int r = 2; int code = TRS_OK; -int param = (int)arg; +int param = ((int *)arg)[0]; int depth = param/2 != 0 ? IPL_DEPTH_32F : IPL_DEPTH_8U; int channels = param % 2 == 1 ? 3 : 1; @@ -318,7 +318,7 @@ const int r = 2; int code = TRS_OK; -int param = (int)arg; +int param = ((int *)arg)[0]; int depth = param/2 != 0 ? IPL_DEPTH_32F : IPL_DEPTH_8U; int channels = param % 2 == 1 ? 3 : 1; @@ -448,10 +448,10 @@ } } -#define _8U_C10 -#define _8U_C31 -#define _32F_C1 2 -#define _32F_C3 3 +#define _8U_C1(int []) { 0 } +#define _8U_C3(int []) { 1 } +#define _32F_C1 (int []) { 2 } +#define _32F_C3 (int []) { 3 } void InitAPyramids( void ) { signature.asc Description: Digital signature
Bug#322300: wrong Architecture line in control file
This package only works on ppc as it contains ppc assembler code. The architecture field in debian/control should therefor be Architecture: powerpc Cheers, Peter (p2). signature.asc Description: Digital signature
Bug#315592: RFH aboot (Alpha bootloader): Looking for co-maintainers
Hi Helge, > > Great. Since I am not a DD, I will inform Steve Langasek, who did the > uploads and helped me a great deal with all the packaging details. > > The first thing you can do is to check out our CVS from alioth > (pkg-aboot). I'll ask Steve to add you to the group and get a little > aqauinted with the source layout. Please ask if something is unclear, > ... I cannot tell you the nitty gritty source details, but the overall > layout and the purpose of the various tools/directories etc. I know. > > Out of the bugs, I'd consider #270801 the most anyoing. Unfortunately, > netabootwrap is not in the upstream source, hence we are "on our own". Ok. Do I get it right that aboot doesn't display any messages at all ? (not even 'aboot: Linux/Alpha SRM bootloader version ') ? > For #153176 and #222904 I tried to collect as much info as possible, > and also talked to upstream, but there is no solution yet. Please see > the logs. > Ok. I will look into this. > If you know how to add other FS, then #153666 might be fun for you. > Upstream is a little reluctant, though, to add more and more file > systems. Since a patch is available, the next thing would be to test, > if possible, and add it in the next upload which could deal with the > new policy version as well (haven't looked yet, what this would > require). > I have done (am doing this) for other bootloaders. Should be doable for aboot as well. > Suggestions for #271180 are welocme as well. > I think it might be good to interpret booted_osflags the same way for netboot then for disk/cd boot. Ie as the aboot.conf entry to use for booting. This would require a small aboot.conf to be included in the netboot image. > A very important thing is, though, to keep aboot buildable (by > having machines to build and test on). > Yep. Although SRM seems to be a reasonably well behaved firmware in my experience. > And finally, I have the upstream e-mail adresses and can try to get > them working on it again. And documentation fixes I can submit both > for Debian as upstream (sourceforge) as well. > Ok. Cheers, Peter (p2). signature.asc Description: Digital signature
Bug#271180: Bug#305117: installation report
On Mon, Apr 18, 2005 at 02:53:32AM -0700, Steve Langasek wrote: > On Mon, Apr 18, 2005 at 11:49:04AM +0200, Peter 'p2' De Schrijver wrote: > > On Sun, Apr 17, 2005 at 06:28:01PM -0700, Steve Langasek wrote: > > > On Mon, Apr 18, 2005 at 03:09:53AM +0200, Peter De Schrijver wrote: > > > > Debian-installer-version: 2005/04/17 rc3 netboot image > > > > uname -a: Linux pisco 2.4.27-2-generic #1 Sat Apr 9 19:43:25 UTC 2005 > > > > alpha GNU/Linux > > > > Date: Mon Apr 18 02:59:19 CEST 2005 > > > > Method: netboot from local server. installation from ftp.belnet.be > > > > > 1) Initial boot only worked after I changed the ramdisk size by giving > > > > the ramdisk_size parameter. The image could be configured to give this > > > > parameter automagically. > > > > What was the boot commandline that failed, and what did you set > > > ramdisk_size > > > to in order to get it booting? > > > Ok. I found the problem. The XP1000 SRM by default passes -fl a to the > > boot command which causes aboot to replace the kernel flags by the > > letter 'a'. This is overwrites the default commandline in the netboot > > image :( Workaround is to set boot_osflags to "" before doing a bootp. > > Yep, well-known bug #271180. > It's more subtle then that. aboot treats the contents of booted_osflags differently depending on how it was loaded. When netbooting the contents is passed as kernel parameter, except if it is a single 'i', which causes it to ask for the kernel commandline on the console. When booting from disk or cdrom, the contents is used by aboot to select the aboot.conf entry to boot. (it's somewhat more complicated then what I describe here, look at get_aboot_options in disk.c for full details). A good solution might be to make netboot behaviour similar to disk boot behaviour by including a single entry aboot.conf in the netboot image. Cheers, Peter (p2). signature.asc Description: Digital signature
Bug#305117: installation report
On Sun, Apr 17, 2005 at 06:28:01PM -0700, Steve Langasek wrote: > On Mon, Apr 18, 2005 at 03:09:53AM +0200, Peter De Schrijver wrote: > > Debian-installer-version: 2005/04/17 rc3 netboot image > > uname -a: Linux pisco 2.4.27-2-generic #1 Sat Apr 9 19:43:25 UTC 2005 alpha > > GNU/Linux > > Date: Mon Apr 18 02:59:19 CEST 2005 > > Method: netboot from local server. installation from ftp.belnet.be > > > 1) Initial boot only worked after I changed the ramdisk size by giving > > the ramdisk_size parameter. The image could be configured to give this > > parameter automagically. > > What was the boot commandline that failed, and what did you set ramdisk_size > to in order to get it booting? > Ok. I found the problem. The XP1000 SRM by default passes -fl a to the boot command which causes aboot to replace the kernel flags by the letter 'a'. This is overwrites the default commandline in the netboot image :( Workaround is to set boot_osflags to "" before doing a bootp. Cheers, Peter (p2). signature.asc Description: Digital signature
Bug#304071: Boot fails on IBM RS/6000 Model 43P-140 (PreP)
On Mon, Apr 11, 2005 at 11:32:39PM +0200, maximilian attems wrote: > tags 304071 moreinfo > thanks > > On Sun, 10 Apr 2005, Peter De Schrijver wrote: > > > Package: kernel-image-2.6.8-powerpc > > Version: 2.6.8-12 > > Severity: important > > > > > > The kernel image fails to boot on IBM RS/6000 Model 43P-140, which is a PreP > > machine. The kernel doesn't post any message on the console. A > > self-compiled > > 2.6.11.6 works fine. Note that I use serial console as the IBM graphics > > board > > is not supported by Linux. > > > can you test 2.6.10 or 2.6.11 from the unstable debian archive? Neither of them work. They fail the same way kernel-image-2.6.8-powerpc does. > there should also be a 2.6.9 in snapshot.debian.net. > would be nice sine when it works, if debian builds don't break it.. I couldn't find the 2.6.9 image in snapshot.debian.net. Do you know the exact URL of it ? Cheers, Peter (p2). signature.asc Description: Digital signature
Bug#304248: install report - alpha 500au - first soft-reboot fails
On Mon, Apr 11, 2005 at 11:17:39PM -0700, Steve Langasek wrote: > On Tue, Apr 12, 2005 at 06:55:59AM +0200, Christian Perrier wrote: > > (Steve, in case you missed that one) > > > Quoting Peter Vandenabeele ([EMAIL PROTECTED]): > > > > * soft reboot fails. A consecutive power cycle worked fine. > > > (see below for more details). > > > Well, given that a consecutive "hard" reboot worked, I don't know if > > this can be easily reproduced and/or investigated. Steve, you're > > tagged as "alpha wizard", among many other thingsany thoughts? > > Eh, s/alpha wizard/guy who does alpha stuff/. I saw this, but don't have > any idea; cc:ed to debian-alpha, in case someone there has a better idea > what would cause this, but it sounds like hardware-specific wackiness to me. > It looks to me as if the soft reboot didn't properly shutdown PCI. Looking at the cia init code (arch/alpha/kernel/core_cia.c, verify_tb_operation) it looks as if the 5th PCI TLB test somehow crashed the machine. Cheers, Peter (p2). signature.asc Description: Digital signature
Bug#302272: more info
On Thu, Mar 31, 2005 at 07:15:29PM +0200, Geert Stappers wrote: > On Thu, Mar 31, 2005 at 12:44:12PM +0200, Peter 'p2' De Schrijver wrote: > > FYI: the install attempt was done using serial console. The machine does > > not have a linux supported graphics board. > > | > | Console output : > | > | 0 > boot /pci/ethernet:, console=ttyS0 > | LOAD: Waiting 60 seconds for Spanning Tree > | BOOTP R = 1 BOOTP S = 1 > | FILE: /tftpboot/vmlinuz-prep.initrd > | Load Addr=0x100 Max Size=0x700 > | FINAL Packet Count = 10778 Final File Size = 5517847 bytes. > | > > mm > > Where I'm not aware about the default baudrate > I would force it to 9600 > By default the kernel takes the bitrate as configured in the UART so it should be ok as it works with other kernels without this parameter. The firmware uses 9600 bps. > 0 > boot /pci/ethernet:, console=ttyS0,9600 > > > > And another "more then skipping to the next message" : > > Are bootstrap serial port and Linux ttyS0 the same device? > Yes, they are. 2 possible reasons for this problem I see : + http://www.solinno.co.uk/7043-140/files/2.6.9-rc2/*.diff are not applied + support for 8250 serial and console is missing. I wouldn't expect that as all other prep platforms I know of use a 8250 compatible UART. A self-compiled 2.6.11.6 fai kernel works fine. Cheers, Peter (p2). signature.asc Description: Digital signature
Bug#302272: more info
FYI: the install attempt was done using serial console. The machine does not have a linux supported graphics board. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293292: ITP: btexmms -- XMMS plugin to use some (Sony) Ericsson phones as a remote control
On Wed, Feb 02, 2005 at 04:41:15PM +, Paul Brossier wrote: > On Wed, 2005-02-02 at 10:41 +0100, Peter 'p2' De Schrijver wrote: > > * Package name: btexmms > > xmms plugins would be better named xmms- (btexmms for the > source should be fine though) > So xmms-btexmms would be better ? > > Version : x.y.z > > Upstream Author : Name <[EMAIL PROTECTED]> > > * URL : http://www.example.org/ > > * License : (GPL, LGPL, BSD, MIT/X, etc.) > > mmh, looks like it lacks a few info here... > It seems I missed some bits of the template yes. Version : 0.5 Upstream Author : Nikolay Igotti ([EMAIL PROTECTED]) URL : http://www.lyola.com/bte/ License : GPL > > Description : XMMS plugin to use some (Sony) Ericsson phones as a > > remote control > > what is the name of the feature provided by 'some (Sony) Ericsson' ? > imo, it would looks better with that name instead. > It uses the accessory menu feature to display messages and mobile equipment event reporting to read the keys. > > This plugin allows using some Ericsson and Sony Ericsson phones as a remote > > control for XMMS. Phones which are known to work are the SE T68i and the > > SE T610. The plugin uses the accessory commands documented in the > > Ericsson R320 manual. > > any chance this documentation can be shipped with the package itself ? No. The documentation used to be available on the ericsson website (http://mobileinternet.ericsson.se/emi_manuals/R320s/ATCommand/R320AT_R1A.pdf) but the link is dead now. The document says (c) Ericsson Mobile Communications. There are a few sites which still have it, but I'm not convinced that this is legal. Cheers, Peter (p2). signature.asc Description: Digital signature
Bug#293292: ITP: btexmms -- XMMS plugin to use some (Sony) Ericsson phones as a remote control
Package: wnpp Severity: wishlist * Package name: btexmms Version : x.y.z Upstream Author : Name <[EMAIL PROTECTED]> * URL : http://www.example.org/ * License : (GPL, LGPL, BSD, MIT/X, etc.) Description : XMMS plugin to use some (Sony) Ericsson phones as a remote control This plugin allows using some Ericsson and Sony Ericsson phones as a remote control for XMMS. Phones which are known to work are the SE T68i and the SE T610. The plugin uses the accessory commands documented in the Ericsson R320 manual. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#289867: coriander: version 1.0.1 is out
On Tue, Jan 11, 2005 at 02:36:32PM +0100, Laurent Bonnaud wrote: > Package: coriander > Version: 1.0.0-r-1 > Severity: wishlist > > > Hi, > > coriander 1.0.1 is out with a lot of fixes: > Unfortunately this version relies on an unreleased CVS version of libdc1394. I would rather avoid packaging unreleased software. I will ask the author when he plans to release the new libdc1394. Cheers, Peter (p2). signature.asc Description: Digital signature