Bug#969576: nextcloud-desktop: Main window not visible/constructable
On Wed, 2020-09-09 at 15:58 +0200, Stefano Zacchiroli wrote > > After installing the following packages, I can see the main window > > again(although it still disappears on me sometimes): > > * qml-module-qtquick-layouts* qml-module-qtquick-controls2* qml- > > module-qtgraphicaleffects* qml-module-qtqml-models2* qml-module- > > qtqml > > Thanks for this. After "apt install"-ing the above packages the > issuewas fixed for me too. For what is worth, the packages that > were*actually* missing on my system prior to the installation were > just: > qml-module-qtquick-controls2 qml-module-qtquick-templates2 I have to reaffirm that I used an iterative approach to install each of these to get rid of all warnings and have the main interface appear. I'm afraid that all dependencies listed above seem necessary, maybe you had the others for other reasons already? What is weird to me, though, is that qml-module-qtquick-controls (so version 1) does depend on most of these, whereas qml-module-qtquick- controls2 does not. Kind regards, Paul van Tilburg -- Debian developer| E-mail: paulvt@debian.orghttps://www.debian.org | GnuPG: 0xC7DE073EDA9EEC4D>>> Using the Power of Debian GNU/Linux | Matrix: @paul:luon.net
Bug#969576: nextcloud-desktop: Main window not visible/constructable
Package: nextcloud-desktop Version: 3.0.1-1 Severity: important Dear Maintainer, The upgrade to 3.0 of the Nextcloud client led to the main window not being visible anymore. It seems that the QT QML modules are missing to make it work. Consider the warnings in the logs: ``` 2020-09-05 11:48:57:445 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml: module "QtQuick" is not installed 2020-09-05 11:48:57:445 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:7:1: module "QtGraphicalEffects" is not installed 2020-09-05 11:48:57:445 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:6:1: module "QtQuick.Layouts" is not installed 2020-09-05 11:48:57:445 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:5:1: module "QtQuick.Controls" is not installed 2020-09-05 11:48:57:445 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:4:1: module "QtQuick.Window" is not installed 2020-09-05 11:48:57:445 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:3:1: module "QtQuick" is not installed 2020-09-05 11:48:57:445 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:2:1: module "QtQml.Models" is not installed 2020-09-05 11:48:57:445 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:1:1: module "QtQml" is not installed ``` After installing the following packages, I can see the main window again (although it still disappears on me sometimes): * qml-module-qtquick-layouts * qml-module-qtquick-controls2 * qml-module-qtgraphicaleffects * qml-module-qtqml-models2 * qml-module-qtqml Also, when using GNOME there is no way to reach the main window because it has become a tray-only application, unfortunately. However, this might warrant another bug report alltogether. Kind regards, Paul van Tilburg -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nextcloud-desktop depends on: ii libc6 2.31-3 ii libcloudproviders00.3.0-3 ii libgcc-s1 10.2.0-6 ii libglib2.0-0 2.64.4-1 ii libnextcloudsync0 3.0.1-1 ii libqt5core5a 5.14.2+dfsg-6 ii libqt5dbus5 5.14.2+dfsg-6 ii libqt5gui55.14.2+dfsg-6 ii libqt5keychain1 0.10.0-1 ii libqt5network55.14.2+dfsg-6 ii libqt5qml55.14.2+dfsg-3 ii libqt5quick5 5.14.2+dfsg-3 ii libqt5quickcontrols2-55.14.2+dfsg-2 ii libqt5sql5-sqlite 5.14.2+dfsg-6 ii libqt5svg55.14.2-2 ii libqt5webenginecore5 5.14.2+dfsg1-4 ii libqt5webenginewidgets5 5.14.2+dfsg1-4 ii libqt5webkit5 5.212.0~alpha4-5 ii libqt5widgets55.14.2+dfsg-6 ii libstdc++610.2.0-6 ii nextcloud-desktop-common 2.6.4-1 ii nextcloud-desktop-l10n3.0.1-1 Versions of packages nextcloud-desktop recommends: ii nextcloud-desktop-doc 3.0.1-1 nextcloud-desktop suggests no packages. -- no debconf information
Bug#954189: Backport to buster?
Hi! This bug report was originally about buster and in my opinion a backport is necessary (stretch also had one). I reckon mostly servers use Let's Encrypt, and they mostly run Debian buster/stable. Given that upstream doesn't seem to change to that much, is that a possibility? I didn't reopen this bug report and will leave that to the maintainer's discretion, however, I did want to mention this. Kind regards, Paul -- Web: http://paul.luon.net/ | E-mail: p...@luon.net Matrix: @paul:luon.net | GnuPG: 0xC6DE073EDA9EEC4D
Bug#949220: RM: ffrenzy -- ROM; Dead upstream
Package: ftp.debian.org Severity: normal Dear ftp-masters, Both as co-author and as maintainer I can say that this project has dead upstream. As a result it will never be ported to Python 3 and newer XML libraries. Please remove it from the archive. Kind regards, Paul van Tilburg -- Web: http://paul.luon.net/ | E-mail: p...@luon.net XMPP: p...@luon.net | GnuPG: 0xC6DE073EDA9EEC4D
Bug#929985: ftp.debian.org: Not maintained for years; low popcon
Package: ftp.debian.org Severity: normal Dear FTP masters, Please remove the mcrl2 from unstable (and thereby Buster). It has not been maintained in Debian for years and the popcon is very low. It might return later if upstream packaging work is pushed towards Debian again? Kind regards, Paul
Bug#916036: gnome-software: Bump the Suggest on fwupd to a Recommend?
Package: gnome-software Version: 3.30.5-1 Severity: wishlist Dear GNOME team, Now that LVFS has matured over the last year (both programming as well as support wise), I wonder if it is possible or time to bump the Suggest on fwupd to a Recommend? Are there any points in favour of against this? Or is this never likely to happen? Over the year, I have had to explain to people to install this manually when they wondered how I got this nice BIOS software updates and integration in the GNOME desktop. Another point in favour would be that people will have not forget their important security updates fixed in their laptops. Kind regards, Paul -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-software depends on: ii appstream0.12.3-1 ii apt-config-icons 0.12.3-1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-1 ii gnome-software-common3.30.5-1 ii gsettings-desktop-schemas3.28.1-1 ii libappstream-glib8 0.7.12-1 ii libatk1.0-0 2.30.0-1 ii libc62.27-8 ii libcairo21.16.0-1 ii libfwupd21.1.4-1 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-6 ii libglib2.0-0 2.58.1-2 ii libgnome-desktop-3-173.30.2-1 ii libgspell-1-11.6.1-1 ii libgtk-3-0 3.24.1-2 ii libgtk3-perl 0.034-2 ii libgudev-1.0-0 232-2 ii libjson-glib-1.0-0 1.4.4-1 ii libpackagekit-glib2-18 1.1.11-1 ii libpolkit-gobject-1-00.105-22 ii libsecret-1-00.18.6-3 ii libsoup2.4-1 2.64.1-3 ii packagekit 1.1.11-1 ii software-properties-gtk 0.96.20.2-1 gnome-software recommends no packages. Versions of packages gnome-software suggests: pn apt-config-icons-hidpi ii fwupd 1.1.4-1 ii gnome-software-plugin-flatpak 3.30.5-1 pn gnome-software-plugin-snap -- no debconf information
Bug#911831: linux: Serial port of dw-abp-uart missing due to serial dev bus activation
Source: linux
Version: 4.18.10-2
Severity: normal
Dear Maintainer,
Since the upgrade of our system from Debian 9 (Stretch) to 10 (Buster), but
also from Ubuntu 16.04 LTS (Xenial) to 18.04 LTS (Bionic), the serial port
of our Atom E3950-based board can no longer be used.
I have traced the cause to the enabling of CONFIG_SERIAL_DEV_BUS=y and
CONFIG_SERIAL_DEV_CTRL_TTYPORT=y in the kernel config of versions
4.17.0-3 (Debian) and 4.15.0.36.38 (Ubuntu).
In a working system the dw-abp-uart driver exposes two tty devices:
# dmesg | grep tty
[2.437836] dw-apb-uart.2: ttyS0 at MMIO 0x8121c000 (irq = 4, base_baud =
115200) is a 16550A
[2.439193] dw-apb-uart.3: ttyS1 at MMIO 0x8121a000 (irq = 6, base_baud =
115200) is a 16550A
of which we always use ttyS1. (I do not know why ttyS0 does nothing,
supposedly this system has only one UART?) The corresponding udev info is:
looking at device '/devices/pci:00/:00:18.0/dw-apb-uart.2/tty/ttyS0':
KERNEL=="ttyS0"
SUBSYSTEM=="tty"
DRIVER==""
looking at parent device '/devices/pci:00/:00:18.0/dw-apb-uart.2':
KERNELS=="dw-apb-uart.2"
SUBSYSTEMS=="platform"
DRIVERS=="dw-apb-uart"
ATTRS{driver_override}=="(null)"
looking at parent device '/devices/pci:00/:00:18.0':
KERNELS==":00:18.0"
SUBSYSTEMS=="pci"
DRIVERS=="intel-lpss"
ATTRS{ari_enabled}=="0"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x118000"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{d3cold_allowed}=="1"
ATTRS{device}=="0x5abc"
ATTRS{dma_mask_bits}=="32"
ATTRS{driver_override}=="(null)"
ATTRS{enable}=="1"
ATTRS{index}=="9"
ATTRS{irq}=="4"
ATTRS{label}=="Onboard - Other"
ATTRS{local_cpulist}=="0-3"
ATTRS{local_cpus}=="f"
ATTRS{msi_bus}=="1"
ATTRS{numa_node}=="-1"
ATTRS{revision}=="0x0b"
ATTRS{subsystem_device}=="0x7270"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{vendor}=="0x8086"
looking at device '/devices/pci:00/:00:18.2/dw-apb-uart.3/tty/ttyS1':
KERNEL=="ttyS1"
SUBSYSTEM=="tty"
DRIVER==""
looking at parent device '/devices/pci:00/:00:18.2/dw-apb-uart.3':
KERNELS=="dw-apb-uart.3"
SUBSYSTEMS=="platform"
DRIVERS=="dw-apb-uart"
ATTRS{driver_override}=="(null)"
looking at parent device '/devices/pci:00/:00:18.2':
KERNELS==":00:18.2"
SUBSYSTEMS=="pci"
DRIVERS=="intel-lpss"
ATTRS{ari_enabled}=="0"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x118000"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{d3cold_allowed}=="1"
ATTRS{device}=="0x5ac0"
ATTRS{dma_mask_bits}=="32"
ATTRS{driver_override}=="(null)"
ATTRS{enable}=="1"
ATTRS{index}=="10"
ATTRS{irq}=="6"
ATTRS{label}=="Onboard - Other"
ATTRS{local_cpulist}=="0-3"
ATTRS{local_cpus}=="f"
ATTRS{msi_bus}=="1"
ATTRS{numa_node}=="-1"
ATTRS{revision}=="0x0b"
ATTRS{subsystem_device}=="0x7270"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{vendor}=="0x8086"
looking at parent device '/devices/pci:00':
KERNELS=="pci:00"
SUBSYSTEMS==""
DRIVERS==""
However, when the serial device bus with the serial TTY control port is
enabled, ttyS1 disappears:
# dmesg | grep tty
[2.499748] dw-apb-uart.2: ttyS0 at MMIO 0x8121c000 (irq = 4, base_baud =
115200) is a 16550A
[2.500852] dw-apb-uart.3: ttyS1 at MMIO 0x8121a000 (irq = 6, base_baud =
115200) is a 16550A
[2.500996] serial serial0: tty port ttyS1 registered
The difference in the udev info is:
looking at device
'/devices/pci:00/:00:18.2/dw-apb-uart.3/serial0/serial0-0':
KERNEL=="serial0-0"
SUBSYSTEM=="serial"
DRIVER==""
looking at parent device
'/devices/pci:00/:00:18.2/dw-apb-uart.3/serial0':
KERNELS=="serial0"
SUBSYSTEMS=="serial"
DRIVERS==""
and there is no longer tty under
/sys/devices/pci:00/:00:18.2/dw-apb-uart.3.
Attached is the full dmesg output for the broken tty port instance. Let me know
if more information is required.
I must also note that I am not very knowledgeable about the serial
interface internals, so feel free to point me to any further reading to
understand what is going on under the hood.
Kind regards,
Paul van Til
Bug#885737: Cannot upgrade
Hello, Unfortunately the liquidsoap from unstable requires libc6 (>= 2.27) which is not installable on Stretch. So I could not test this. It also seems the packaging has been reorganized. Maybe if it works on Buster, it could be backported to Stretch? Kind regards, Paul -- Debian developer| E-mail: pau...@debian.org https://www.debian.org | GnuPG: 0xC6DE073EDA9EEC4D Using the Power of Debian GNU/Linux | XMPP: p...@luon.net
Bug#891287: Works with xserver-xorg 2:1.20.0-2
Hey, Also note that if you to test this, that it seems that they have renamed the extension from "Composite" to "COMPOSITE". (I have no idea why anyone would do this, without mentioning it in the changelog even, but that is besides the issue here). So my test config for the 1.20 Xorg server is now: # Test the X server without compositing support Section "Extensions" Option "COMPOSITE" "Disable" EndSection Cheers, Paul -- Debian developer| E-mail: pau...@debian.org https://www.debian.org | GnuPG: 0xC6DE073EDA9EEC4D >>> Using the Power of Debian GNU/Linux | XMPP: p...@luon.net
Bug#891287: Works with xserver-xorg 2:1.20.0-2
Hi! I performed a test and upgraded xserver-xorg to unstable, which currently is on version2 :1.20.0-2. The problem has disappeared for me again. Can you confirm this before I tag stuff on this bug report? This would mean that there are some upstream commits have fixed the issues introduced by the commits you mentioned, and thus could maybe be applied as patches. Paul -- Debian developer| E-mail: pau...@debian.org https://www.debian.org | GnuPG: 0xC6DE073EDA9EEC4D >>> Using the Power of Debian GNU/Linux | XMPP: p...@luon.net
Bug#879184: Update QCA6174/hw3,0/firmware-6.bin
Hi! This can be solved by replacing firmware-6.bin by the newest one from the official repository: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 It was added about a month ago. See also this commit: https://github.com/kvalo/ath10k-firmware/commit/7eb330e1e0f21f325f4f50a98922b3be04d43722 (which mentions a WPA-related issue). I did this temporarily until the firmware-atheros package is updated. After boot/module reload, the journal should report the new version (≥ 4.4.1-0079): > sudo journalctl --boot | grep WLAN.RM Jan 16 10:22:38 quantum kernel: ath10k_pci :3a:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb For more details, see also this Arch forum post: https://bbs.archlinux.org/viewtopic.php?pid=1737681#p1737681 Kind regards, Paul -- Web: http://paul.luon.net/ | E-mail: p...@luon.net XMPP: p...@luon.net | GnuPG: 0xC6DE073EDA9EEC4D
Bug#885737: liquidsoap: Terminated by SIGILL after upgrade to Stretch
Package: liquidsoap Version: 1.1.1-7.2 Severity: normal Dear Maintainer, I recently upgraded my server Debian Stretch and since then Liquidsoap doesn't work anymore. (Although it seems to be basically the same release as in Jessie.) $ liquidsoap /etc/liquidsoap/luon-radio.liq fish: “liquidsoap /…” terminated by signal SIGILL (Illegal instruction) I also couldn't find a way to GDB this. Downgrading all liquidsoap* packages to the version from Debian Jessie, i.e. 1.1.1-7+b1, immediately fixed the problem. It is not exactly trivial on this production server to keep switching versions for debugging purposes, but let me know how to get more information out of the error above. Kind regards, Paul van Tilburg -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#885706: RM: mooproxy -- ROM; Upstream dead; not used
Package: ftp.debian.org Severity: normal Dear FTP masters, This package has dead upstream and 3 installations in popcon. Please remove the package from the archive. Kind regards, Paul van Tilburg
Bug#879770: RM: gnoemoe -- ROM; Dead upstream; Uses libraries that are removed
Package: ftp.debian.org Severity: normal Dear FTP masters, Please remove this package from the repository. It's upstream has been long dead and nobody is stepped up to port this program, that is also little used, to more modern libraries. This RM is also as per request by Emilio Pozuele Monfort to get rid of packages that depend on old GNOME libraries such as libgnome/libgnomeui/etc. besides the already open bugreports of gnoemoe depending on the old gnome-vfs and libvte. For more information, see: https://lists.debian.org/debian-devel/2017/10/msg00299.html Kind regards, Paul van TIlburg
Bug#858143: Gets killed by logind kills user processes
Version: 0.9.1-9 Dear all, I would like to report a problem with the fix in 0.9.1-9 and I hope you would consider reopening this bug report. The first issue is that it seems that when a user logs in now, the xrdp-sesman main process is moved to scope of the first session! (This did not used to happen before.) $ systemctl status xrdp-sesman.service ● xrdp-sesman.service - xrdp session manager Loaded: loaded (/lib/systemd/system/xrdp-sesman.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2017-05-15 10:49:28 CEST; 1 weeks 1 days ago Docs: man:xrdp-sesman(8) man:sesman.ini(5) Main PID: 3050 (xrdp-sesman) Tasks: 0 (limit: 4915) CGroup: /system.slice/xrdp-sesman.service ‣ 3050 /usr/sbin/xrdp-sesman $ loginctl SESSIONUID USER SEAT TTY 426 1001 paul c4 1002 other.user $ systemctl status session-c4.scope ● session-c4.scope - Session c4 of user corry.kosters Loaded: loaded (/run/systemd/transient/session-c4.scope; transient; vendor preset: enabled) Transient: yes Active: active (running) since Mon 2017-05-15 10:49:43 CEST; 1 weeks 1 days ago CGroup: /user.slice/user-10016.slice/session-c4.scope ├─ 3050 /usr/sbin/xrdp-sesman … We have a deployment where we have configured systemd-logind to kill user process when there are no more sessions for said user (via both Xrdp and ssh). So, now, not only his/her session is killed but also the main xrdp-sessman process (!), after which Xrdp becomes unavailable. A workaround is to login with a user that just disconnects, but that is not exactly ideal. A secondary effect of the fix that I see is that loginctl also only reports a session for the first user that logged in. For example, see the loginctl output above. The session of my user (c5) is not visible at all. Both issues indicate that there is still an issue with properly registering the sessions. I have confirmed that going back to 0.9.1-7 fixes both issues. Kind regards, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/XMPP: p...@luon.net | GnuPG key ID: 0x50064181
Bug#862089: Can also make it work with xserver-xorg-legacy
Hey, It can also be made to work with xserver-xorg-legacy installed, but then one needs to configure the wrapper to allow anybody to use it instead of console users (e.g. via dpkg-reconfigure -plow xserver-xorg-legacy). It is interesting how this was not necessary before and it worked with "console users only". Can this be due to the recent security fixes? Kind regards, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/XMPP: p...@luon.net | GnuPG key ID: 0x50064181
Bug#840132: xrdp-sesman.service sometimes fails to start on boot
On Mon, Mar 06, 2017 at 06:06:19AM +, David Gilmour wrote: > On Tue, 28 Feb 2017 15:07:39 +0100 Paul van Tilburg <pau...@debian.org> wrote: > > I have updated the xrdp.service unit locally and that seems to fix it > > (see attached file). > > > > The changes are: > > > > --- /lib/systemd/system/xrdp.service2017-01-25 18:10:11.0 > > +0100 > > +++ /etc/systemd/system/xrdp.service2017-02-28 15:07:01.130060204 > > +0100 > > @@ -1,8 +1,7 @@ > >[Unit] > >Description=xrdp daemon > >Documentation=man:xrdp(8) man:xrdp.ini(5) > > -Requires=xrdp-sesman.service > > -After=network.target xrdp-sesman.service > > +After=network-online.target > > Paul, unfortunately it didn’t seem to work for me: > > root@pod:/home/david# systemctl status xrdp > > ● xrdp.service - xrdp daemon > >Loaded: loaded (/etc/systemd/system/xrdp.service; enabled; vendor preset: > enabled) >Active: failed (Result: resources) since Sun 2017-03-05 21:39:49 PST; 56s > ago > Docs: man:xrdp(8) >man:xrdp.ini(5) > Process: 873 ExecStart=/usr/sbin/xrdp $XRDP_OPTIONS (code=exited, status=0/ > SUCCESS) > Process: 849 ExecStartPre=/bin/sh /usr/share/xrdp/socksetup (code=exited, > status=0/SUCCESS) > > Mar 05 21:39:46 pod systemd[1]: Starting xrdp daemon... > Mar 05 21:39:46 pod systemd[1]: xrdp.service: PID file /run/xrdp/xrdp.pid not > readable (yet?) after start: No such file or directory > Mar 05 21:39:48 pod xrdp[1119]: (1119)(139942974253888)[INFO ] starting xrdp > with pid 1119 > Mar 05 21:39:49 pod xrdp[1119]: (1119)(139942974253888)[ERROR] > xrdp_listen_main_loop: listen error, possible port already in use > Mar 05 21:39:49 pod xrdp[1119]: (1119)(139942974253888)[DEBUG] Closed socket > 11 (AF_INET6 :: port 0) The above is strange. So even after the network-online target, there is still something that prevents XRDP for listening on its required port. After a few seconds it seems settled and you can start XRDP. If I search for this error online, there are many issues reported about this error message, so I'm not sure if this a different problem. Do you get the same error with the upstream systemd unit. About xrdp-sesman, it also fails because it cannot listen on a port, weird. Something is awry in the network implementation here that doesn't bother other daemons. Do you also use NetworkManager or a different network configuration stack? Kind regards, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/XMPP: p...@luon.net | GnuPG key ID: 0x50064181
Bug#840132: xrdp.service modification
Hi! I have been struggling with the same issues. Because we want to offer a GNOME desktop, NetworkManager is installed. The way it configures the network might reveal an issue in xrdp itself. I have updated the xrdp.service unit locally and that seems to fix it (see attached file). The changes are: --- /lib/systemd/system/xrdp.service2017-01-25 18:10:11.0 +0100 +++ /etc/systemd/system/xrdp.service2017-02-28 15:07:01.130060204 +0100 @@ -1,8 +1,7 @@ [Unit] Description=xrdp daemon Documentation=man:xrdp(8) man:xrdp.ini(5) -Requires=xrdp-sesman.service -After=network.target xrdp-sesman.service +After=network-online.target [Service] Type=forking The after requirement on network-online.target is not how it should be, but it seems necessary for xrdp to start. The require on xrdp-sesman is not necessary at all (given that xrdp-sesman.service binds to xrdp.service), so I dropped that. Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/XMPP: p...@luon.net | GnuPG key ID: 0x50064181 Description=xrdp (X Remote Desktop Protocol) protocol server Documentation=man:xrdp(8) man:xrdp.ini(5) After=network-online.target [Service] Type=forking PIDFile=/run/xrdp/xrdp.pid EnvironmentFile=-/etc/sysconfig/xrdp EnvironmentFile=-/etc/default/xrdp User=xrdp Group=xrdp PermissionsStartOnly=true ExecStartPre=/bin/sh /usr/share/xrdp/socksetup ExecStart=/usr/sbin/xrdp $XRDP_OPTIONS ExecStop=/usr/sbin/xrdp $XRDP_OPTIONS --kill ExecStopPost=/bin/rm -rf /var/run/xrdp/sockdir [Install] WantedBy=multi-user.target
Bug#855516: gnome-shell: Crashes when Shotwell's Adjust dialog is moved
Package: gnome-shell Version: 3.22.2-4 Severity: normal Dear Maintainer, When using Shotwell and selecting Adjust for a picture and then trying to move the Adjust Window from the top left corner, gnome-shell/mutter crashes. The journal mentions the following: Feb 19 14:23:44 quantum org.gnome.Shell.desktop[16963]: ** Feb 19 14:23:44 quantum org.gnome.Shell.desktop[16963]: mutter:ERROR:core/window.c:1389:meta_window_unmanage: assertion failed: (window->display->focus_window != window) [...exit/crashes of all session applications...] I also attached a systemd-coredump file. Note that I am running Stretch, but have intalled shotwell 0.25.4+really0.24.5-0.1 from unstable to be able to actually use it with my camera, but it the newer version probably has the same issue. Kind regards, Paul -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2 ii evolution-data-server3.22.4-1 ii gir1.2-accountsservice-1.0 0.6.43-1 ii gir1.2-atspi-2.0 2.22.0-5 ii gir1.2-caribou-1.0 0.4.21-1 ii gir1.2-freedesktop 1.50.0-1 ii gir1.2-gcr-3 3.20.0-5 ii gir1.2-gdesktopenums-3.0 3.22.0-1 ii gir1.2-gdm-1.0 3.22.1-2 ii gir1.2-glib-2.0 1.50.0-1 ii gir1.2-gnomebluetooth-1.03.20.0-1 ii gir1.2-gnomedesktop-3.0 3.22.2-1 ii gir1.2-gtk-3.0 3.22.7-2 ii gir1.2-gweather-3.0 3.20.4-1 ii gir1.2-ibus-1.0 1.5.14-2 ii gir1.2-mutter-3.03.22.2-3 ii gir1.2-networkmanager-1.01.6.0-1 ii gir1.2-nmgtk-1.0 1.4.4-1 ii gir1.2-pango-1.0 1.40.3-3 ii gir1.2-polkit-1.00.105-17 ii gir1.2-soup-2.4 2.56.0-2 ii gir1.2-telepathyglib-0.120.24.1-1.1 ii gir1.2-telepathylogger-0.2 0.8.2-2 ii gir1.2-upowerglib-1.00.99.4-4 ii gjs 1.46.0-1+b1 ii gnome-backgrounds3.22.1-1 ii gnome-settings-daemon3.22.1-1 ii gnome-shell-common 3.22.2-4 ii gsettings-desktop-schemas3.22.0-1 ii libatk-bridge2.0-0 2.22.0-1 ii libatk1.0-0 2.22.0-1 ii libc62.24-9 ii libcairo21.14.8-1 ii libcanberra-gtk3-0 0.30-3 ii libcanberra0 0.30-3 ii libcroco30.6.11-2 ii libdbus-glib-1-2 0.108-2 ii libecal-1.2-19 3.22.4-1 ii libedataserver-1.2-223.22.4-1 ii libgcr-base-3-1 3.20.0-5 ii libgdk-pixbuf2.0-0 2.36.4-1 ii libgirepository-1.0-11.50.0-1 ii libgjs0e [libgjs0-libmozjs-24-0] 1.46.0-1+b1 ii libglib2.0-0 2.50.2-2 ii libglib2.0-bin 2.50.2-2 ii libgstreamer1.0-01.10.3-1 ii libgtk-3-0 3.22.7-2 ii libical2 2.0.0-0.5+b1 ii libicu57 57.1-5 ii libjson-glib-1.0-0 1.2.2-1 ii libmozjs-24-024.2.0-5.1 ii libmutter0i 3.22.2-3 ii libnm-glib4 1.6.0-1 ii libnm-util2 1.6.0-1 ii libpango-1.0-0 1.40.3-3 ii libpangocairo-1.0-0 1.40.3-3 ii libpolkit-agent-1-0 0.105-17 ii libpolkit-gobject-1-00.105-17 ii libpulse-mainloop-glib0 10.0-1 ii libpulse010.0-1 ii libsecret-1-00.18.5-2 ii libstartup-notification0 0.12-4 ii libsystemd0 232-15 ii libtelepathy-glib0 0.24.1-1.1 ii libwayland-client0 1.12.0-1 ii libx11-6 2:1.6.4-3 ii
Bug#834716: bundler: man-pages in wrong directory
Package: bundler Version: 1.12.5-3 Severity: normal Dear Maintainer, The man-pages are installed in the Ruby library directory, as a result, they are unavailable to the user. See the following partial file listing of ruby-bundler: $ dpkg -L ruby-bundler | grep man /usr/lib/ruby/vendor_ruby/bundler/man /usr/lib/ruby/vendor_ruby/bundler/man/bundle /usr/lib/ruby/vendor_ruby/bundler/man/bundle-config /usr/lib/ruby/vendor_ruby/bundler/man/bundle-config.txt /usr/lib/ruby/vendor_ruby/bundler/man/bundle-exec /usr/lib/ruby/vendor_ruby/bundler/man/bundle-exec.txt /usr/lib/ruby/vendor_ruby/bundler/man/bundle-gem /usr/lib/ruby/vendor_ruby/bundler/man/bundle-gem.txt /usr/lib/ruby/vendor_ruby/bundler/man/bundle-install /usr/lib/ruby/vendor_ruby/bundler/man/bundle-install.txt /usr/lib/ruby/vendor_ruby/bundler/man/bundle-lock /usr/lib/ruby/vendor_ruby/bundler/man/bundle-lock.txt /usr/lib/ruby/vendor_ruby/bundler/man/bundle-package /usr/lib/ruby/vendor_ruby/bundler/man/bundle-package.txt /usr/lib/ruby/vendor_ruby/bundler/man/bundle-platform /usr/lib/ruby/vendor_ruby/bundler/man/bundle-platform.txt /usr/lib/ruby/vendor_ruby/bundler/man/bundle-update /usr/lib/ruby/vendor_ruby/bundler/man/bundle-update.txt /usr/lib/ruby/vendor_ruby/bundler/man/bundle.txt /usr/lib/ruby/vendor_ruby/bundler/man/gemfile.5 /usr/lib/ruby/vendor_ruby/bundler/man/gemfile.5.txt [...] Cheers, Paul -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bundler depends on: ii ruby-bundler 1.12.5-3 Versions of packages bundler recommends: ii build-essential 12.2 ii less 481-2.1 ii ruby-dev 1:2.3.0+4 ii sudo 1.8.17p1-2 bundler suggests no packages. -- no debconf information
Bug#832973: Acknowledgement (vile-filters: vile filter for mail broken)
Dear Maintainer, It seems that (almost) all filters are broken. All miss the _wrap symbol? Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181
Bug#832973: vile-filters: vile filter for mail broken
Package: vile-filters Version: 9.8r-1 Severity: normal Dear Maintainer, Since the recent upgrade to 9.8r-1 in Sid, I'm unable to edit e-mails due to vile's mail filter being broken. Vile drops me into the HighlightFilter buffer everytime I try to edit an e-mail. If I run the highligh/unhighlight macros, vile reports: [Error: can't load shared object vile-mail-filt.so (/usr/lib/vile/vile-mail-filt.so: undefined symbol: mail_wrap)] Probably something is wrong with the build? Kind regards, Paul -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vile-filters depends on: ii libc62.23-4 ii vile-common 9.8r-1 vile-filters recommends no packages. vile-filters suggests no packages. -- no debconf information
Bug#815641: Release 0.11.0
Hi! Actually, 0.11.0 has been released yesterday [1], so it would make more sense to get that into Debian now that things start rolling again. Cheers, Paul 1: https://github.com/GNOME/geary/releases -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181
Bug#469215: Still a problem
Hi all,
I ran into this bug too, while trying to deploy Xrdp as a terminal
server solution for a customer of mine. It seems that there is also now
an upstream bug report for this and that it is thus still present in the
later releases: https://sourceforge.net/p/xrdp/bugs/54/.
I have attached a patch that is a modified version of the
aforementioned 09sesman_sig_handling.dpatch. This patch not only lets
the SIGCHLD handler reap all zombie child processes, but also reconnects
this handler after the fork of xrdp-sessvc and the entire session has
happened. This is not a solution I'd recommend using in the packaging
;), as it is quick & dirty, but it does indicate where the problem
lies... the SIGCHLD signal handler gets disconnected somewhere around
the fork.
Kind regards,
Paul
--
Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org
Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181
Description: When a user logged out, he/she cannot login anymore
This is due to sesman leaving a defunct session parent, while it thinks
the session is still running and thus fails to reconnect.
This patch has been modified to also ensure that the SIGCHLD signal
handler is reconnect after forking xrdp-sessvc and the entire session.
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469215
Bug-Upstream: https://sourceforge.net/p/xrdp/bugs/54/
Author: Vincent Bernat <ber...@luffy.cx>, Paul van Tilburg <p...@mozcode.nl>
--- a/sesman/sig.c
+++ b/sesman/sig.c
@@ -121,13 +121,14 @@
if (g_getpid() != g_pid)
{
+log_message(&(g_cfg->log), LOG_LEVEL_WARNING, "g_getpid() [%d] differs from g_pid [%d]", g_getpid(), g_pid);
return;
}
- pid = g_waitchild();
- if (pid > 0)
- {
+ while ((pid = g_waitchild()) > 0) {
+LOG_DBG("g_waitchild() [%d] Child %d is dead", g_getpid(), pid);
session_kill(pid);
}
+ LOG_DBG("g_waitchild() [%d] No more children", g_getpid());
}
/**/
--- a/sesman/session.c
+++ b/sesman/session.c
@@ -562,6 +562,7 @@
}
else /* parent sesman process */
{
+g_signal_child_stop(sig_sesman_session_end); /* SIGCHLD */
temp->item->pid = pid;
temp->item->display = display;
temp->item->width = width;
Bug#771411: ganeti-instance-debootstrap: Uses deprecated losetup commands
Package: ganeti-instance-debootstrap Version: 0.14-2 Severity: important Tags: fixed-upstream Dear Maintainer, When setting up a VM using the debootstrap+default OS, the create script uses losetup commands that fail: # gnt-instance add -o debootstrap+default -s 5G vm1 Fri Nov 28 16:48:08 2014 - INFO: Resolved given name 'vm1' to 'vm1.domain.tld' Fri Nov 28 16:48:12 2014 - INFO: Selected nodes for instance vm1.domain.tld via iallocator hail: hongkong.domain.tld Fri Nov 28 16:48:15 2014 * disk 0, size 5.0G Fri Nov 28 16:48:15 2014 * creating instance disks... Fri Nov 28 16:48:16 2014 adding instance vm1.domain.tld to cluster config Fri Nov 28 16:48:16 2014 adding disks to cluster config Fri Nov 28 16:48:17 2014 - INFO: Waiting for instance vm1.domain.tld to sync disks Fri Nov 28 16:48:17 2014 - INFO: Instance vm1.domain.tld's disks are in sync Fri Nov 28 16:48:17 2014 - INFO: Waiting for instance vm1.domain.tld to sync disks Fri Nov 28 16:48:17 2014 - INFO: Instance vm1.domain.tld's disks are in sync Fri Nov 28 16:48:18 2014 * running the instance OS create scripts... Failure: command execution error: Could not add os for instance vm1.domain.tld on node vmhost.domain.tld: OS create script failed (exited with exit code 1), last lines in the log file: -O, --output cols specify columns to output for --list -n, --noheadings don't print headings for --list output --raw use raw --list output format -h, --help display this help and exit -V, --version output version information and exit Available --list columns: NAME loop device name AUTOCLEAR autoclear flag set BACK-FILE device backing file BACK-INO backing file inode number BACK-MAJ:MIN backing file major:minor device number MAJ:MIN loop device major:minor number OFFSET offset from the beginning PARTSCAN partscan flag set RO read-only device SIZELIMIT size limit of the file in bytes For more details see losetup(8). It appears this is a known issue and has already been fixed, see also: https://code.google.com/p/ganeti/issues/detail?can=2q=690colspec=ID%20Type%20Component%20Status%20Priority%20Stars%20Opened%20Modified%20Milestone%20Owner%20Summaryid=690 I patched the files and confirmed that I can now create VMs using debootstrap+default. I am new to Ganeti so I don't know if this breaks this package for all usages or just mine, so I left the priority set to important. Cheers, Paul -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ganeti-instance-debootstrap depends on: ii debootstrap 1.0.64 ii dump 0.4b44-5 ii initscripts 2.88dsf-58 ii kpartx 0.5.0-5 ganeti-instance-debootstrap recommends no packages. ganeti-instance-debootstrap 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#688832: Cannot find help/documentation
Hi, Actually both suggestions don't work for me: % man git-flow No manual entry for git-flow % git help flow No manual entry for git-flow See 'man 7 undocumented' for help when manual pages are not available. Since recent versions git flow without arguments does provide help information (same as git flow help). What I find inconsistent is that all commands support -h/--help, except for the main command: % git flow init --help usage: git flow init [-h] [-d] [-f] Setup a git repository for git flow usage. Can also be used to start a git repository. % git flow --help paul@entropy% git flow --help No manual entry for git-flow See 'man 7 undocumented' for help when manual pages are not available. Compare with: % git rebase --help [I get the manual page] Maybe the man page is just not installed/generated (correctly)? Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765520: git-flow: Uses bashisms but calls /bin/sh
Package: git-flow Version: 1.8.0-1 Severity: important Dear maintainer, In the past few days I have sometimes encountered some bashisms while using git-flow. When I changed the shebang in /usr/lib/git-core/git-flow to # !/bin/bash, git-flow worked fine again. I cannot recall all commands, but one that is reproducible is: % git flow log /usr/lib/git-core/git-flow: 70: /usr/lib/git-core/git-flow: [[: not found /usr/lib/git-core/git-flow: 70: /usr/lib/git-core/git-flow: =: not found /usr/lib/git-core/git-flow: 78: /usr/lib/git-core/git-flow: [[: not found Comparing against branch fatal: ..: '..' is outside repository Cheers, Paul -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-flow depends on: ii git [git-core] 1:2.1.1-1 git-flow recommends no packages. git-flow 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#760964: empathy: no sound from callee duwing XMPP (voice) calls
Package: empathy Version: 3.12.5-1 Severity: normal Dear maintainer, Up until (rougly) the end of July, I was able to succesfully perform audio calls with other parties, but since August I no longer get sound from the callee. (The same if the other party calls me and I am the callee.) Some extra information: * This happens in various settings: calls over the internet or both parties on a single LAN, using IPv6 and not. Using iftop we have determined that at least no audio mediastream seems to be returned. * If a video call is performed, the video _is_ streamed both ways, but still no returning audio. * Downgrades of telepathy-gabble to 0.18.2-1 and empathy to 3.12.4-1 (versions used in July) have been attempted, without success. Maybe it's related to pulseaudio or gstreamer? * It was tested between several installations (Sid/Sid, Jessie/Sid, etc.) If you need me to test some more, please let me know. Kind regards, Paul -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages empathy depends on: ii dbus-x11 1.8.6-2 ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii empathy-common 3.12.5-1 ii geoclue-2.0 2.1.8-1 ii gnome-icon-theme 3.12.0-1 ii gsettings-desktop-schemas3.12.2-1 ii gstreamer1.0-pulseaudio 1.4.1-1 ii libc62.19-10 ii libcairo21.12.16-5 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libchamplain-0.12-0 0.12.8-1 ii libchamplain-gtk-0.12-0 0.12.8-1 ii libcheese-gtk23 3.12.2-1 ii libclutter-1.0-0 1.18.4-2 ii libclutter-gst-2.0-0 2.0.12-1 ii libclutter-gtk-1.0-0 1.5.4-1 ii libcogl-path20 1.18.2-2 ii libcogl201.18.2-2 ii libdbus-glib-1-2 0.102-1 ii libenchant1c2a 1.6.0-10.1 ii libfarstream-0.2-2 0.2.3-3 ii libfolks-telepathy25 0.9.8-1 ii libfolks25 0.9.8-1 ii libgcr-base-3-1 3.12.2-1 ii libgcr-ui-3-13.12.2-1 ii libgdk-pixbuf2.0-0 2.30.8-1 ii libgee-0.8-2 0.14.0-2 ii libgeocode-glib0 3.12.2-1 ii libglib2.0-0 2.40.0-5 ii libgnutls-deb0-283.3.7-2 ii libgoa-1.0-0b3.12.4-1 ii libgstreamer-plugins-base1.0-0 1.4.1-1 ii libgstreamer1.0-01.4.1-1 ii libgtk-3-0 3.12.2-3+b1 ii libgudev-1.0-0 208-8 ii libmission-control-plugins0 1:5.16.2-1 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.7-1 ii libpulse-mainloop-glib0 5.0-6 ii libpulse05.0-6 ii libsecret-1-00.18-1 ii libsoup2.4-1 2.46.0-2 ii libtelepathy-farstream3 0.6.1-1 ii libtelepathy-glib0 0.24.0-1 ii libtelepathy-logger3 0.8.0-3 ii libwayland-server0 1.5.0-1 ii libwebkitgtk-3.0-0 2.4.5-2 ii libx11-6 2:1.6.2-3 ii libxml2 2.9.1+dfsg1-4 ii telepathy-logger 0.8.0-3 ii telepathy-mission-control-5 1:5.16.2-1 Versions of packages empathy recommends: ii gvfs-backends1.20.3-1 ii sound-theme-freedesktop 0.8-1 ii telepathy-gabble 0.18.3-1 pn telepathy-haze none ii telepathy-salut 0.8.1-4 Versions of packages empathy suggests: ii telepathy-idle 0.2.0-1 ii vino3.12.0-2 Versions of packages empathy is related to: ii telepathy-gabble [telepathy-connection-manager] 0.18.3-1 ii telepathy-idle [telepathy-connection-manager]0.2.0-1 ii telepathy-rakia [telepathy-connection-manager] 0.8.0-2 ii telepathy-salut [telepathy-connection-manager] 0.8.1-4 -- no debconf information -- To
Bug#582043: Ruby1.8 not available anymore
fixed 2.1.0-1 thanks From version 2.1.0-1 and on in Jessie/Sid, Ruby 1.8 support has been dropped (as Ruby 1.8 is also not available anymore). Hence, this bug can be considered fixed starting from version 2.1.0-1. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747581: gnome-music: doesn't start (missing TrackerSparqlConnection GIR typelib?)
Package: gnome-music Version: 3.12.1-1 Severity: normal Hi, At the moment, gnome-music doesn't start for me. It gives the following warnings: % gnome-music /usr/lib/python3/dist-packages/gi/module.py:178: Warning: cannot register existing type 'TrackerSparqlConnection' g_type = info.get_g_type() /usr/lib/python3/dist-packages/gi/module.py:178: Warning: g_once_init_leave: assertion 'result != 0' failed g_type = info.get_g_type() /usr/lib/python3/dist-packages/gi/module.py:212: Warning: g_type_get_qdata: assertion 'node != NULL' failed type_ = g_type.pytype /usr/lib/python3/dist-packages/gi/module.py:226: Warning: g_type_get_qdata: assertion 'node != NULL' failed g_type.pytype = wrapper /usr/lib/python3/dist-packages/gi/module.py:226: Warning: g_type_set_qdata: assertion 'node != NULL' failed g_type.pytype = wrapper Maybe this non-fatal (since it's a warning) but I get no UI. Note that I have purged gir1.2-tracker-0.16, but to no avail. Also note that the gir1.2-tracker-1.0 package contains no 'TrackerSparqlConnection' typelib: % dpkg -L gir1.2-tracker-1.0 | grep typelib /usr/lib/girepository-1.0/TrackerControl-1.0.typelib /usr/lib/girepository-1.0/Tracker-1.0.typelib /usr/lib/girepository-1.0/TrackerMiner-1.0.typelib Kind regards, Paul -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-music depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii gir1.2-glib-2.0 1.40.0-2 ii gir1.2-grilo-0.2 0.2.10-1 ii gir1.2-gst-plugins-base-1.0 1.2.4-1 ii gir1.2-gstreamer-1.0 1.2.4-1 ii gir1.2-gtk-3.0 3.12.1-1 ii gir1.2-notify-0.70.7.6-2 ii gir1.2-totem-plparser-1.03.10.2-1 ii gir1.2-tracker-1.0 1.0.1-2 ii gnome-settings-daemon3.12.1-3 ii grilo-plugins-0.20.2.12-2+b1 ii libatk1.0-0 2.12.0-1 ii libc62.18-5 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk-3-0 3.12.1-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii python3 3.3.4-1 ii python3-dbus 1.2.0-2+b2 ii python3-gi 3.12.1-1 ii python3-gi-cairo 3.12.1-1 pn python3:any none ii tracker 1.0.1-2 gnome-music recommends no packages. gnome-music 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#738393: Probably related to Tilt API changes
severity 738393 normal affects 738488 camping usertag 738393 +will-break-if-tilt-2.0-is-uploaded thanks Hi, I'm pretty sure (looking at the timeline) that the build issues were due to Tilt suddenly changing it's API. This was fixed by a reupload of ruby-tilt 2.0.0+really1.4.1-1 but will break Camping again once Tilt 2.0.0 is really uploaded. For now, the FTBFS is no longer reproducible. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725325: RM: moovida -- ROM; dead upstream; no longer functioning
Package: ftp.debian.org Severity: normal Hi! It has been years since Moovida development was abandoned (or: went in a completely different direction and closed-source). Bug #606819 indicates that Moovida also not longer starts up anymore. Also, finally XBMC became available in Debian as a media center alternative. I don't think that Moovida should be a part of Jessie, please remove it from the archive. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725351: RM: moovida-plugins-good -- ROM; should be removed if moovida is removed
Package: ftp.debian.org Severity: normal Hi! I filed a request for the removal of moovida from unstable (see #725325). If moovida is removed, the package containing these plugins should also be removed. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725352: RM: moovida-plugins-bad -- ROM; should be removed if moovida is removed
Package: ftp.debian.org Severity: normal Hi! I filed a request for the removal of moovida from unstable (see #725325). If moovida is removed, the package containing these plugins should also be removed. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725353: RM: moovida-plugins-ugly -- ROM; should be removed if moovida is removed
Package: ftp.debian.org Severity: normal Hi! I filed a request for the removal of moovida from unstable (see #725325). If moovida is removed, the package containing these plugins should also be removed. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724888: RM: ruby-revolution -- ROM; Ruby 1.8 only; no upstream
Package: ftp.debian.org Severity: normal Hi! I would like to request that ruby-revolution is removed from the archive. No upstream releases have been done since 2005 and it only supports Ruby 1.8, which is not going to be shipped anymore with Wheezy. Also popcon is very low. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720709: ITP: ruby-pcaprub -- Ruby bindings for LBL Packet Capture library (libpcap)
Hi Jérémy, On Sat, Aug 24, 2013 at 06:49:05PM +0200, Jérémy Bobbio wrote: Package: wnpp Severity: wishlist Owner: Jérémy Bobbio lu...@debian.org Control: block 719297 by -1 * Package name: ruby-pcaprub Version : 0.11.3-1 Upstream Author : shadowbq shado...@gmail.com * URL : https://github.com/shadowbq/pcaprub [...] I have uploaded, maintained and also neglected ruby-pcap a bit in the archive. See also: http://packages.qa.debian.org/r/ruby-pcap.html If this is different upstream, better maintained or just a new version please feel welcome to take it over. I have not used it for a while also. Kind regards, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#720709: ITP: ruby-pcaprub -- Ruby bindings for LBL Packet Capture library (libpcap)
On Sat, Aug 24, 2013 at 09:29:20PM +0200, Jérémy Bobbio wrote: Thanks for the “go ahead”. :) I didn't mean it like that! :P I think it's great someone takes it over. This is a different — active — upstream. Quoting pcaprub's README: This project was created because the currently available ruby-pcap library is poorly designed and has been unmaintained since 2000. Agreed. :) As I've written in the initial ITP, ruby-pcap should probably be removed from the archive once pcaprub gets in: it has no rdeps. Also agreed. That's what I actually wanted to suggest! Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#710814: [DRE-maint] Bug#710814: rubygems-integration: fails to override bin_path
Heya, On Sun, Jun 02, 2013 at 07:18:00PM +0200, Christian Hofstaedtler wrote: there is a problem with rubygems-integration in which it fails to properly override the binary path for gems. This is mostly seen when having bin stubs from previously installed gems in /usr/local/bin, for example: % nokogiri /usr/local/bin/nokogiri:23:in `load': cannot load such file -- /usr/share/rubygems-integration/1.9.1/gems/nokogiri-1.5.9/bin/nokogiri (LoadError) from /usr/local/bin/nokogiri:23:in `main' Explicitly calling /usr/bin/nokogiri works fine. A log of a chroot install to reproduce this for rake in Wheezy: root@entropy:/# apt-get install rake rubygems rubygems-integration Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libffi5 libreadline5 libruby1.8 libruby1.9.1 libssl1.0.0 libyaml-0-2 ruby ruby1.8 ruby1.9.1 Suggested packages: ri ruby-dev ruby1.8-examples ri1.8 ruby-switch ruby1.9.1-examples ri1.9.1 graphviz ruby1.9.1-dev bundler Recommended packages: zip ruby1.8-dev The following NEW packages will be installed: libffi5 libreadline5 libruby1.8 libruby1.9.1 libssl1.0.0 libyaml-0-2 rake ruby ruby1.8 ruby1.9.1 rubygems rubygems-integration 0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 4782 B/9142 kB of archives. After this operation, 27.5 MB of additional disk space will be used. Do you want to continue [Y/n]? y [...] root@entropy:/# rake --version rake, version 0.9.2.2 root@entropy:/# gem install rake --version 0.9.0 Fetching: rake-0.9.0.gem (100%) Successfully installed rake-0.9.0 1 gem installed [...] root@entropy:/# /usr/local/bin/rake --version /usr/local/bin/rake:23:in `load': cannot load such file -- /usr/share/rubygems-integration/1.9.1/gems/rake-0.9.2.2/bin/rake (LoadError) from /usr/local/bin/rake:23:in `main' It seems that the problem occurs if a older gem with a program is installed while already the same but newer is installed via Debian and rubygem-intergration. (That is why I explicitly install rake 0.9.0, while Debian Wheezy has 0.9.2.2.) Also involved is the binary stub generation by our patched RubyGems implementation. It seems to put the stub(s) somewhere in /usr/local/bin and to carry no version requirement so that it takes the newest one. This is fine, but in case of it finding our Debian integration-gemspec it should use /usr/bin as bin path, not /usr/share/rubygems-integration/1.9.1/gems/gem-version/bin/program IMO. (Btw, it seems to disregard version specifications as well, ie. # rake _0.9.0_ --version rake, version 0.9.2.2 but that is another issue :)) Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708698: [DRE-maint] Bug#708698: gem2deb is failing to integrate chronic with rubygems
Hi, On Sat, May 18, 2013 at 12:49:44AM +0530, Praveen A wrote: packages created with gem2deb cannot be detected by rubygems. I tried the current version in the archive 0.6.7 or chronic as well as the latest 0.9.1, in both cases deb package in missing gemspec files in /usr/share/rubygems-integration IIRC it doesn't install if tests fail or if they are disabled. Is this the case? It's another matter whether this should be the case :) Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648653: Discontinued
Hi, I would like to inquery if you have changed the packaging (wrt to what is mentioned in the original ITP) from the discontinued[1] plugin by Simon Legner to the one by Christian Metzler[2]? The latter plugin has evolved quite a lot, for example it has a decent settings dialog and is also supported via extensions.gnome.org nowadays. Also, it receives daily maintenance. Cheers, Paul 1: https://github.com/simon04/gnome-shell-extension-weather/commit/41765c9672772de9da50d7944f677899c5fd4842 2: https://github.com/Neroth/gnome-shell-extension-weather -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701074: ITP: ruby-ox -- a fast XML parser and object marshaller for Ruby
Package: wnpp Severity: wishlist Owner: Paul van Tilburg pau...@debian.org * Package name: ruby-ox Version : 1.8.8 Upstream Author : Peter Ohler pe...@ohler.com * URL : http://www.ohler.com/ox/ * License : 3-clause BSD Programming Lang: C, Ruby Description : a fast XML parser and object serializer for Ruby Optimized XML (Ox), as the name implies, was written to provide speed optimized XML handling. It was designed to be an alternative to Nokogiri and other Ruby XML parsers for generic XML parsing and as an alternative to Marshal for Object serialization. Ox handles XML documents in three ways. It is a generic XML parser and writer, a fast Object / XML marshaller, and a stream SAX parser. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691839: [Pkg-owncloud-maintainers] Bug#691839: [owncloud] New upstream version available (4.5.1)
On Mon, Nov 05, 2012 at 04:45:06PM +0100, Jean Charles Delépine wrote: For my own needs I've made my own owncloud 4.5.1a debian packages. If one want to have a look at it. http://debian-upjv.u-picardie.fr/laurent/pool/owncloud/ As always, no garanties, will make your hairs fall, ... I can make the debdiff, but am generally interested in the changes you have made. I have imported 4.5.1 into our Git repository and this can go to experimental. However, when I inspected the diff between (tags) upstream/4.0.8debian and upstream/4.5.1+debian, I got a diff of over 500,000 lines (yes, really). Most of this pertains to translation, but still quite some files are added to the 3rdparty/ folder which means we need a big update of debian/copyright again. This is going to take quite some time, unfortunately. I wanted to explain this, because I see that many people are eager to get their hands on 4.5.1, but it's just more work than import upstream, build and push. Given that Thomas and I have little time at the moment, this makes it go slower than you guys would want. Any help is appreciated though. Maybe I should upload preliminary packages again? Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691839: [Pkg-owncloud-maintainers] Bug#691839: [owncloud] New upstream version available (4.5.1)
Hi, On Wed, Oct 31, 2012 at 12:11:55PM +0100, Nik Lutz wrote: Thank you for maintaining ownCloud - looking forward to 4.5 Currently the ownCloud team members are hard pressed on time. I hope we can upload 4.5.x soon. We are aware of the release. Maybe this helps: http://software.opensuse.org/download/package?project=isv:ownCloud:communitypackage=owncloud Unfortunately not. The packaging used there is by far not useful or up-to-standards/policy for Debian. Thanks for the pointer though. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691445: unblock: camping/2.1.498-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hello release time, I would like to request package camping (version 2.1.498-4) to be unblocked. I have applied a patch that fixes support for HTTP POST, which is rather necessary in a web application framework. This upload fixes RC bug #689038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689038 I have attached a debdiff of camping with the version in testing (2.1.498-3). Plase unblock camping/2.1.498-4, Cheers, Paul -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru camping-2.1.498/debian/changelog camping-2.1.498/debian/changelog --- camping-2.1.498/debian/changelog 2012-06-24 16:23:09.0 +0200 +++ camping-2.1.498/debian/changelog 2012-10-25 19:54:18.0 +0200 @@ -1,3 +1,11 @@ +camping (2.1.498-4) unstable; urgency=low + + * debian/patches: add camping-allow-POST-through-Rack-File, +courtesy of Magnus Holm (closes: #689038) + * debian/source/local-options: unapply patches after build + + -- Paul van Tilburg pau...@debian.org Thu, 25 Oct 2012 19:54:15 +0200 + camping (2.1.498-3) unstable; urgency=low * debian/control: diff -Nru camping-2.1.498/debian/patches/allow-POST-through-Rack-File.patch camping-2.1.498/debian/patches/allow-POST-through-Rack-File.patch --- camping-2.1.498/debian/patches/allow-POST-through-Rack-File.patch 1970-01-01 01:00:00.0 +0100 +++ camping-2.1.498/debian/patches/allow-POST-through-Rack-File.patch 2012-10-25 19:42:13.0 +0200 @@ -0,0 +1,25 @@ +From fe791e787f5665efdc3f17b0f6122260b3a6d770 Mon Sep 17 00:00:00 2001 +From: Magnus Holm judo...@gmail.com +Date: Fri, 10 Feb 2012 17:31:12 +0100 +Subject: [PATCH] Server: Also catch 405 from Rack::File + +--- + lib/camping/server.rb |2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/lib/camping/server.rb b/lib/camping/server.rb +index 47bffa7..af2bfc8 100644 +--- a/lib/camping/server.rb b/lib/camping/server.rb +@@ -149,7 +149,7 @@ module Camping + end + + def app +- Rack::Cascade.new([Rack::File.new(public_dir), self], [404, 403]) ++ Rack::Cascade.new([Rack::File.new(public_dir), self], [405, 404, 403]) + end + + def current_app +-- +1.7.10.4 + diff -Nru camping-2.1.498/debian/patches/series camping-2.1.498/debian/patches/series --- camping-2.1.498/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ camping-2.1.498/debian/patches/series 2012-10-25 19:42:13.0 +0200 @@ -0,0 +1 @@ +allow-POST-through-Rack-File.patch
Bug#691447: RM: checkservice -- ROM; no maintainer interest, very dead upstream
Package: ftp.debian.org Severity: normal Hi! I have been (not really) maintaining checkservice for over 12 years. It is really old now, upstream development has been stopped over 11 years ago and there is no interest from me, as maintainer, to maintain it. Featurewise nagios3/icinga could be considered as a replacement (it also has an engine that runs service checks using plugins) with a lot of additional features. Therefore, I request this package to be removed. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689038: camping: Does not support HTTP POST
Hi, On Tue, Oct 23, 2012 at 07:25:37PM +0200, Salvatore Bonaccorso wrote: Niels Thykier announced[1] that this package is a candidate for removal. I'm not a user of this package, so can not judge if the patch is sufficient, but it is comitted as is already some time upstream. Do you plan to upload the package applying the patch? Please note that this should happen before of the 26th october. Yes, I am aware of it, as I filed a bug report with patch against a package of myself, hehe. But it has been busy and such. I will do it tomorrow or Thursday latest. Close call but in time. Cheers for remembering me though, Regards, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#689038: camping: Does not support HTTP POST
Package: camping Version: 2.1.498-3 Severity: grave Tags: patch upstream Justification: renders package unusable Hi, Currently, it is not possible in Debian to use the Camping framework to write/create an application that supports HTTP POST next to GET nor to use/run Camping webapps that use POST. This only holds when using Camping server and not other deployment methods. However, it is obviously a must for it to work during development. The problem is caused by the fact that the Rack::File middleware, used for serving static files, is chained before the app and this middleware logically doesn't support POST and throws a HTTP 405 error which is subsequently not handled. The patch attached ensures that HTTP 405 is ignored and the POST request is propagated to the Camping app. Cheers, Paul -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages camping depends on: ii ruby 4.9 ii ruby-rack 1.4.1-2 ii ruby1.8 [ruby-interpreter]1.8.7.358-4 ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-1 Versions of packages camping recommends: ii ruby-activerecord-2.3 2.3.14-2 ii ruby-mab 0.0.1+git20120515.30414e4-2 ii ruby-sqlite3 1.3.6-2 ii ruby-tilt 1.3.3-2 Versions of packages camping suggests: ii thin 1.3.1-3 -- no debconf information From fe791e787f5665efdc3f17b0f6122260b3a6d770 Mon Sep 17 00:00:00 2001 From: Magnus Holm judo...@gmail.com Date: Fri, 10 Feb 2012 17:31:12 +0100 Subject: [PATCH] Server: Also catch 405 from Rack::File --- lib/camping/server.rb |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/camping/server.rb b/lib/camping/server.rb index 47bffa7..af2bfc8 100644 --- a/lib/camping/server.rb +++ b/lib/camping/server.rb @@ -149,7 +149,7 @@ module Camping end def app - Rack::Cascade.new([Rack::File.new(public_dir), self], [404, 403]) + Rack::Cascade.new([Rack::File.new(public_dir), self], [405, 404, 403]) end def current_app -- 1.7.10.4
Bug#687324: [Pkg-owncloud-maintainers] Bug#687324: owncloud: Install wizard doesn't run
On Sat, Sep 22, 2012 at 09:09:32PM -0500, Karl Sackett wrote: On Sat, Sep 22, 2012 at 7:10 PM, Diederik de Haas didi.deb...@cknow.org wrote: When you then request http://server/test.php and you only see a heading with PHP Info then that means the appropriate php module isn't installed or loaded. aptitude search ~ilibapache should at least return libapache2-mod-php5 and ls -l /etc/apache2/mods-enabled/ | grep php should return ../mods- available/php5.conf and ../mods-available/php5.load. I found the problem: the owncloud package doesn't depend on libapache2-mod-php5, so it wasn't automatically installed when I installed owncloud itself. After I manually installed libapache2-mod-php5 everything started working. So adding that dependency to the owncloud package should fix the bug, I think. That is odd. owncloud depends on php5, and php5 depends on various types of setting up PHP5 support. libapache2-mod-php4 cannot be added as a depend as for example apache2-mpm-worker does not work with it and needs php5-cgi/cli instead. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685632: liquidsoap: missing versioned depend on libcamomile-ocaml-data
Package: liquidsoap Version: 1.0.0-4+b2 Severity: important Hi, I was trying to advance on the upgrade from Squeeze to Wheezy by adding a pinned version of Wheezy and upgrade liquidsoap to the Wheezy version. However, after installing, I ran into a problem: # liquidsoap Fatal error: exception Not_found Then, strace revealed it could not find/open the file /usr/share/camomile/database/age.mar which is not present in the Squeeze version of libcamomile-ocaml-data (0.7.2-2), but it is in the Wheezy version (0.8.4-2). Hence, liquidsoap should depend on libcamomile-ocaml-data (= 0.8.4). As libcamomile-ocaml-data will probably be upgraded when switching to Wheezy, this is not an RC bug. Paul -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages liquidsoap depends on: ii adduser3.112+nmu2add and remove users and groups ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libcamomile-ocaml-data 0.8.4-2 Unicode data for OCaml ii libmagic1 5.04-5+squeeze2 File type determination library us ii libpcre3 1:8.30-5 Perl 5 Compatible Regular Expressi ii perl 5.10.1-17squeeze3 Larry Wall's Practical Extraction ii sox14.3.1-1+b1 Swiss army knife of sound processi ii wget 1.12-2.1 retrieves files from the web Versions of packages liquidsoap recommends: ii liquidsoap-plugin-faad1.0.0-4+b2 audio streaming language -- FAAD p ii liquidsoap-plugin-flac1.0.0-4+b2 audio streaming language -- FLAC p ii liquidsoap-plugin-icecast 1.0.0-4+b2 audio streaming language -- Icecas ii liquidsoap-plugin-lame1.0.0-4+b2 audio streaming language -- Lame p ii liquidsoap-plugin-mad 1.0.0-4+b2 audio streaming language -- Mad pl ii liquidsoap-plugin-pulseaudio 1.0.0-4+b2 audio streaming language -- Pulsea ii liquidsoap-plugin-taglib 1.0.0-4+b2 audio streaming language -- Taglib ii liquidsoap-plugin-voaacenc1.0.0-4+b2 audio streaming language -- Voaace ii liquidsoap-plugin-vorbis 1.0.0-4+b2 audio streaming language -- Vorbis ii logrotate 3.7.8-6Log rotation utility ii mp3gain 1.5.1-4Lossless mp3 normalizer with stati ii vorbis-tools 1.4.0-1several Ogg Vorbis tools ii vorbisgain0.36-3.1 add Replay Gain volume tags to Ogg Versions of packages liquidsoap suggests: pn festival none (no description available) ii icecast2 2.3.2-6Ogg Vorbis and MP3 streaming media pn liguidsoapnone (no description available) pn liquidsoap-plugin-samplerate none (no description available) pn liquidsoap-plugin-xmlplaylist none (no description available) pn mplayer none (no description available) -- 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#679767: Backtrace with more information
Hi!
I have reproduced the problem. I have a (refined) trackback with more
information:
(gdb) bt full
#0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:32
No locals.
#1 0x2b885357 in xdr_string (xdrs=xdrs@entry=0x7fffcf90,
cpp=cpp@entry=0x7fffd0f8, maxsize=maxsize@entry=4294967295) at
xdr.c:680
sp = 0x1c52ab7fd960 Address 0x1c52ab7fd960 out of bounds
size = optimized out
nodesize = optimized out
__func__ = xdr_string
#2 0x2b159061 in xdr_gf1_cli_create_vol_rsp
(xdrs=xdrs@entry=0x7fffcf90,
objp=objp@entry=0x7fffd0f0) at cli1-xdr.c:279
No locals.
#3 0x2af44f11 in xdr_serialize_generic (outmsg=...,
res=0x7fffd0f0,
proc=0x2b159010 xdr_gf1_cli_create_vol_rsp) at rpc-common.c:36
ret = -1
xdr = {x_op = XDR_ENCODE, x_ops = 0x2bb01860, x_public = 0x0,
x_private = 0x2c2cc008 , x_base = 0x2c2cc000
\377\377\321@,
x_handy = 131064}
__FUNCTION__ = xdr_serialize_generic
#4 0x2cb6b906 in glusterd_serialize_reply
(req=req@entry=0x2cdac024,
arg=0x7fffd0f0, sfunc=0x2b15a250
gf_xdr_serialize_cli_create_vol_rsp,
outmsg=outmsg@entry=0x7fffd020) at glusterd-utils.c:402
iob = 0x55783760
retlen = -1
__FUNCTION__ = glusterd_serialize_reply
I suspect, that objp-volname (at cli1-xdr.c:279) contains uninitialized memory,
and when xdr_string tries to perform a strlen on that, it breaks, down.
Cheers,
Paul
--
| mozcode. | e-mail: p...@mozcode.nl
| (open source) software | web: http://www.mozcode.nl
| ontwikkeling consultancy | jabber/gtalk: p...@luon.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680090: RM: libgsl-ruby -- ROM; obsoleted by ruby-gsl
Package: ftp.debian.org Severity: normal Hi! Please remove libgsl-ruby source package from unstable. It is obsoleted by ruby-gsl, which provides transitional packages for all binary packaged built from it. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679784: gnome-shell: cannot pair due to exception
Package: gnome-shell Version: 3.4.1-8 Severity: normal Hi! When I try to pair my phone with my laptop (from the phone) from the phone, Gnome Shell throws an exception (found in ~/.xsession-errors) and as a result I never get a dialog to confirm/deny the pairing, nor verify the PIN. The trace: JS ERROR: !!! Exception was: TypeError: args[i++] is null JS ERROR: !!! lineNumber = '48' JS ERROR: !!! fileName = '/usr/share/gnome-shell/js/misc/format.js' JS ERROR: !!! stack = '(%ss,25,Pairing confirmation for %s)@/usr/share/gnome-shell/js/misc/format.js:48 format(null)@/usr/share/gnome-shell/js/misc/format.js:22 ([object Object],[object _private_GnomeBluetoothApplet_Applet],/org/bluez/2810/hci0/dev_40_98_4E_2E_75_AA,null,null,750375)@/usr/share/gnome-shell/js/ui/status/bluetooth.js:408 wrapper([object Object],[object _private_GnomeBluetoothApplet_Applet],/org/bluez/2810/hci0/dev_40_98_4E_2E_75_AA,null,null,750375)@/usr/share/gjs-1.0/lang.js:204 ([object Object],[object _private_GnomeBluetoothApplet_Applet],/org/bluez/2810/hci0/dev_40_98_4E_2E_75_AA,null,null,750375)@/usr/share/gjs-1.0/lang.js:145 ([object Object],[object _private_GnomeBluetoothApplet_Applet],/org/bluez/2810/hci0/dev_40_98_4E_2E_75_AA,null,null,750375)@/usr/share/gjs-1.0/lang.js:239 ([object _private_GnomeBluetoothApplet_Applet],/org/bluez/2810/hci0/dev_40_98_4E_2E_75_AA,null,null,750375)@/usr/share/gnome-shell/js/ui/status/bluetooth.js:323 wrapper([object _private_GnomeBluetoothApplet_Applet],/org/bluez/2810/hci0/dev_40_98_4E_2E_75_AA,null,null,750375)@/usr/share/gjs-1.0/lang.js:204 To reproduce, enable bluetooth and set bluetooth to visible using the Bluetooth panel icon. Then, try to pair from the phone. Cheers, Paul -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-2 ii gconf-service3.2.5-1 ii gir1.2-accountsservice-1.0 0.6.21-5 ii gir1.2-atk-1.0 2.4.0-2 ii gir1.2-caribou-1.0 0.4.2-2 ii gir1.2-clutter-1.0 1.10.8-1 ii gir1.2-cogl-1.0 1.10.2-6 ii gir1.2-coglpango-1.0 1.10.2-6 ii gir1.2-folks-0.6 0.6.9-1+b1 ii gir1.2-freedesktop 1.32.1-1 ii gir1.2-gconf-2.0 3.2.5-1 ii gir1.2-gcr-3 3.4.1-3 ii gir1.2-gdesktopenums-3.0 3.4.2-1 ii gir1.2-gdkpixbuf-2.0 2.26.1-1 ii gir1.2-gee-1.0 0.6.4-2 ii gir1.2-gkbd-3.0 3.4.0.2-1 ii gir1.2-glib-2.0 1.32.1-1 ii gir1.2-gmenu-3.0 3.4.2-3 ii gir1.2-gnomebluetooth-1.03.4.1-1 ii gir1.2-gtk-3.0 3.4.2-2 ii gir1.2-json-1.0 0.14.2-1 ii gir1.2-mutter-3.03.4.1-4 ii gir1.2-networkmanager-1.00.9.4.0-5 ii gir1.2-pango-1.0 1.30.0-1 ii gir1.2-polkit-1.00.105-1 ii gir1.2-soup-2.4 2.38.1-2 ii gir1.2-telepathyglib-0.120.18.1-2 ii gir1.2-telepathylogger-0.2 0.4.0-1 ii gir1.2-upowerglib-1.00.9.17-1 ii gjs 1.32.0-2 ii gnome-bluetooth 3.4.1-1 ii gnome-icon-theme-symbolic3.4.0-2 ii gnome-settings-daemon3.4.2-3 ii gnome-shell-common 3.4.1-8 ii gnome-themes-standard3.4.2-1 ii gsettings-desktop-schemas3.4.2-1 ii libatk1.0-0 2.4.0-2 ii libc62.13-34 ii libcairo-gobject21.12.2-2 ii libcairo21.12.2-2 ii libcanberra0 0.28-4 ii libclutter-1.0-0 1.10.8-1 ii libcogl-pango0 1.10.2-6 ii libcogl9 1.10.2-6 ii libcroco30.6.5-1 ii libdbus-1-3 1.6.2-1 ii libdbus-glib-1-2 0.100-1 ii libebook-1.2-13 3.4.3-1 ii libecal-1.2-11 3.4.3-1 ii
Bug#679028: [Pkg-owncloud-maintainers] Bug#679028: Acknowledgement (owncloud: pgsql connection not usable)
Hi, On Mon, Jun 25, 2012 at 10:57:36PM +0200, Bernd Zeimetz wrote: ... also it should not try to create existing databases ... DB Error: ERROR: permission denied to create database Offending command was: CREATE DATABASE owncloud OWNER owncloud MDB2 Error: connect failed: _doConnect: [Error message: unable to establish a connection] By own admission of upstream [1], the PostgreSQL support is not so solid/stable yet. As it will get some attention in the future, we definitely plan to support it in Debian as well, but we have decided to drop it for Wheezy. The next upload (4.0.4debian-1) will no longer have the owncloud-pgsql package. I will leave the bug report open, as it is still relevant for the upcoming releases, and of course for Wheezy+1. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678956: [Pkg-owncloud-maintainers] Bug#678956: Bug#678956: Patch tested
Hello, On Mon, Jun 25, 2012 at 02:22:07PM +0200, Thomas Müller wrote: thanks for testing the patch! We will incorporated this asap. In addition I advised upstream to release a 4.0.4 to clarify the confusion. In the meantime, 4.0.4 has been released including the cache fix. It is unfortunate that the migration script doesn't clear the fscache table, but maybe they have another workaround that I don't see, because it seems to work for me. You are welcome the test pacakges available via: deb http://pkg-owncloud.alioth.debian.org/packages ./ I will upload these packages to Wheezy on Friday (29 June) if I don't hear anything back. (Sorry for the tight schedule, but the freeze is nigh!) Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678956: The fs caching problem is a big issue!
severity 678956 grave thanks Hi, The caching problem makes ownCloud pretty much unusable as the Files application is impacted which is also the core part. It will show misleading information and might make users even delete their own data. A solution is on the way, though. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678956: [Pkg-owncloud-maintainers] Bug#678956: Bug#678956: Patch tested
Hey all, On Mon, Jun 25, 2012 at 02:22:07PM +0200, Thomas Müller wrote: thanks for testing the patch! We will incorporated this asap. Ok, but there is also this bug report: http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-1092 Which is the same bug I think. It's just that the fix is in the third release of 4.0.3 (yes, you read that right). In addition I advised upstream to release a 4.0.4 to clarify the confusion. Good idea. Could you also ask them to script somehow that the migration/setup/install for 4.0.4 flushes the fscache table. That's rather hard to do from the outside given the different types of databases that we allow (and custom table names/prefix and what not). Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678512: ruby-eventmachine: crashes when using IPv6 socket
Package: ruby-eventmachine Version: 0.12.10-3 Severity: normal Hi! I am using Rails 3 from Rubygems which uses Thin/ruby-eventmachine when serving. When I tell the server to bind to :: so that it is reachable via Ipv6, the server crashes when accessed. There seems to be an issue with the hardening/fortify stuff: $ rails server -b :: = Booting Thin = Rails 3.2.5 application starting in development on http://:::3000 = Call with -d to detach = Ctrl-C to shutdown server Thin web server (v1.3.1 codename Triple Espresso) Maximum connections set to 1024 Listening on :::3000, CTRL+C to stop *** stack smashing detected ***: /usr/bin/ruby1.9.1 terminated === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x2ab130fcff07] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x2ab130fcfed0] /usr/lib/ruby/vendor_ruby/1.9.1/x86_64-linux/rubyeventmachine.so(_ZN18AcceptorDescriptor4ReadEv+0x1b7)[0x2ab134612917] /usr/lib/ruby/vendor_ruby/1.9.1/x86_64-linux/rubyeventmachine.so(_ZN14EventMachine_t14_RunSelectOnceEv+0x2c9)[0x2ab134604669] /usr/lib/ruby/vendor_ruby/1.9.1/x86_64-linux/rubyeventmachine.so(_ZN14EventMachine_t8_RunOnceEv+0x28)[0x2ab1346054f8] /usr/lib/ruby/vendor_ruby/1.9.1/x86_64-linux/rubyeventmachine.so(_ZN14EventMachine_t3RunEv+0x5c)[0x2ab134606ddc] /usr/lib/ruby/vendor_ruby/1.9.1/x86_64-linux/rubyeventmachine.so(+0x17379)[0x2ab13460a379] /usr/lib/libruby-1.9.1.so.1.9(+0x15204a)[0x2ab13013c04a] /usr/lib/libruby-1.9.1.so.1.9(+0x147eb5)[0x2ab130131eb5] /usr/lib/libruby-1.9.1.so.1.9(+0x14d564)[0x2ab130137564] /usr/lib/libruby-1.9.1.so.1.9(rb_yield+0x17c)[0x2ab13013dc9c] /usr/lib/libruby-1.9.1.so.1.9(+0x9dd09)[0x2ab130087d09] /usr/lib/libruby-1.9.1.so.1.9(+0x15204a)[0x2ab13013c04a] /usr/lib/libruby-1.9.1.so.1.9(+0x147eb5)[0x2ab130131eb5] /usr/lib/libruby-1.9.1.so.1.9(+0x14d564)[0x2ab130137564] /usr/lib/libruby-1.9.1.so.1.9(rb_iseq_eval+0x160)[0x2ab13013ea70] /usr/lib/libruby-1.9.1.so.1.9(+0x60b10)[0x2ab13004ab10] /usr/lib/libruby-1.9.1.so.1.9(rb_require_safe+0x45c)[0x2ab13004bd7c] /usr/lib/libruby-1.9.1.so.1.9(+0x15204a)[0x2ab13013c04a] /usr/lib/libruby-1.9.1.so.1.9(+0x147eb5)[0x2ab130131eb5] /usr/lib/libruby-1.9.1.so.1.9(+0x14d564)[0x2ab130137564] /usr/lib/libruby-1.9.1.so.1.9(rb_iseq_eval_main+0xad)[0x2ab13013eb5d] /usr/lib/libruby-1.9.1.so.1.9(+0x5df7a)[0x2ab130047f7a] /usr/lib/libruby-1.9.1.so.1.9(ruby_exec_node+0x1d)[0x2ab130048a1d] /usr/lib/libruby-1.9.1.so.1.9(ruby_run_node+0x1e)[0x2ab13004a4ae] /usr/bin/ruby1.9.1[0x40091b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x2ab130f01ead] /usr/bin/ruby1.9.1[0x400949] === Memory map: 0040-00401000 r-xp fe:02 667857 /usr/bin/ruby1.9.1 0060-00601000 r--p fe:02 667857 /usr/bin/ruby1.9.1 00601000-00602000 rw-p 1000 fe:02 667857 /usr/bin/ruby1.9.1 00ba7000-02dff000 rw-p 00:00 0 [heap] 2ab12fdc8000-2ab12fde8000 r-xp fe:02 265225 /lib/x86_64-linux-gnu/ld-2.13.so 2ab12fde8000-2ab12fdea000 rw-p 00:00 0 2ab12fdea000-2ab12ff63000 r--p fe:02 660950 /usr/lib/locale/locale-archive 2ab12ffe7000-2ab12ffe8000 r--p 0001f000 fe:02 265225 /lib/x86_64-linux-gnu/ld-2.13.so 2ab12ffe8000-2ab12ffe9000 rw-p 0002 fe:02 265225 /lib/x86_64-linux-gnu/ld-2.13.so 2ab12ffe9000-2ab12ffea000 rw-p 00:00 0 2ab12ffea000-2ab1301dd000 r-xp fe:02 673775 /usr/lib/libruby-1.9.1.so.1.9.1 2ab1301dd000-2ab1303dc000 ---p 001f3000 fe:02 673775 /usr/lib/libruby-1.9.1.so.1.9.1 2ab1303dc000-2ab1303e4000 rw-p 001f2000 fe:02 673775 /usr/lib/libruby-1.9.1.so.1.9.1 2ab1303e4000-2ab13040 rw-p 00:00 0 2ab13040-2ab130417000 r-xp fe:02 264076 /lib/x86_64-linux-gnu/libpthread-2.13.so 2ab130417000-2ab130616000 ---p 00017000 fe:02 264076 /lib/x86_64-linux-gnu/libpthread-2.13.so 2ab130616000-2ab130617000 r--p 00016000 fe:02 264076 /lib/x86_64-linux-gnu/libpthread-2.13.so 2ab130617000-2ab130618000 rw-p 00017000 fe:02 264076 /lib/x86_64-linux-gnu/libpthread-2.13.so 2ab130618000-2ab13061d000 rw-p 00:00 0 2ab13061d000-2ab130624000 r-xp fe:02 265217 /lib/x86_64-linux-gnu/librt-2.13.so 2ab130624000-2ab130823000 ---p 7000 fe:02 265217 /lib/x86_64-linux-gnu/librt-2.13.so 2ab130823000-2ab130824000 r--p 6000 fe:02 265217 /lib/x86_64-linux-gnu/librt-2.13.so 2ab130824000-2ab130825000 rw-p 7000 fe:02 265217 /lib/x86_64-linux-gnu/librt-2.13.so 2ab130825000-2ab130827000 r-xp fe:02 264068 /lib/x86_64-linux-gnu/libdl-2.13.so 2ab130827000-2ab130a27000 ---p 2000 fe:02 264068
Bug#676194: [DRE-maint] Bug#676194: ruby-xmlparser: diff for NMU version 0.7.2-1.1
On Fri, Jun 22, 2012 at 04:55:14PM +0200, gregor herrmann wrote: I've prepared an NMU for ruby-xmlparser (versioned as 0.7.2-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Also thanks for this fix. It has been incorperated in the team Git repository. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#676205: [DRE-maint] Bug#676205: ruby-ldap: diff for NMU version 0.9.12-1.1
Hi! On Fri, Jun 22, 2012 at 04:41:48PM +0200, gregor herrmann wrote: I've prepared an NMU for ruby-ldap (versioned as 0.9.12-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. No, that is not necessary, it is fine. I've merged the changes in our team Git repository. Thanks! Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#677971: backupninja: [rsync] helper warning leads to fatal error
Package: backupninja Version: 1.0-1 Severity: normal Hi, In earlier reports we talked about backupninja not aborting if the rsync commandline was broken or wrong, i.e. backupninja reported success while the rsync helper failed. This was fixed, but maybe a bit too good? If rsync runs and for example files disappear while syncing (this happens often for backups of /), rsync generates a warning at the end, which backupninja then treats as a fatal error and aborts the process. Info: Syncing / on /media/Backup/tetraeder///daily.1/... [...] rsync warning: some files vanished before they could be transferred (code 24) at main.c(1526) [generator=3.0.7] Fatal: Rsync error when trying to transfer / It seems that as a result the created metadata is not written; this subsequently makes (long format) rotation fail. Cheers, Paul -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages backupninja depends on: ii bash 4.1-3 The GNU Bourne Again SHell ii bsd-mailx [mailx] 8.1.2-0.20100314cvs-1 simple mail user agent ii dialog 1.1-20100428-1Displays user-friendly dialog boxe ii gawk 1:3.1.7.dfsg-5GNU awk, a pattern scanning and pr ii mawk 1.3.3-15 a pattern scanning and text proces backupninja recommends no packages. Versions of packages backupninja suggests: ii bzip2 1.0.5-6+squeeze1 high-quality block-sorting file co pn debconf-utils none (no description available) pn duplicity none (no description available) pn genisoimage none (no description available) pn hwinfo none (no description available) ii mdadm 3.1.4-1+8efb9d1+squeeze1 tool to administer Linux MD arrays ii rdiff-backup1.2.8-6 remote incremental backup ii rsync 3.0.7-2 fast remote file copy program (lik pn subversion none (no description available) pn trickle none (no description available) pn wodim none (no description available) -- 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#677410: backupninja: more issues with the rsync helper
Package: backupninja Version: 1.0~rc1-1~bpo60+1 Severity: normal Hi! I've recently updated to 1.0~rc1-1 via backports and am unfortunately still experiencing quite some issues. First of all, a part of the log: Info: starting action /etc/backup.d/10.cube.rsync (because of --now) Debug: yes Debug: executing handler in locked section controlled by /var/lock/backupninja/_etc_backup.d_10.cube.rsync Debug: ssh -T -o PasswordAuthentication=no -p 22 -i /root/.ssh/id_rsa.ninja root@cube 'echo -n 1' Debug: Connected to cube successfully Debug: RSYNC_RSH=ssh -T -o PasswordAuthentication=no -p 22 -i /root/.ssh/id_rsa.ninja Info: Rotating /media/Backup/cube///... Warning: Warning: metadata does not exist for /media/Backup/cube///daily.1. This backup may be only partially completed. Skipping rotation. Debug: skipping rotation of /media/Backup/cube///weekly.4 because it was created 3 days ago (21 needed). Debug: skipping rotation of /media/Backup/cube///weekly.3 because it was created 3 days ago (14 needed). Debug: skipping rotation of /media/Backup/cube///weekly.2 because it was created 3 days ago (7 needed). Debug: skipping rotation of /media/Backup/cube///weekly.1 because /media/Backup/cube///weekly.2 already exists. Debug: /media/Backup/cube///monthly.1 does not exist, skipping. Debug: removing orphaned metadata monthly.1 Warning: we seem to be resuming a partially written /media/Backup/cube///daily.1 Info: Syncing / on /media/Backup/cube///daily.1/... Debug: nice -n 0 /usr/bin/rsync -avF --delete --numeric-ids --rsync-path=rsync --exclude='/*bin' --exclude='/dev' --exclude='/home/*/.cache' --exclude='/home/*/.local/share/Trash' --exclude='/home/*/.thumbnails' --exclude='/home/*/Music' --exclude='/home/*/Videos' --exclude='/lib*' --exclude='/media' --exclude='/mnt' --exclude='/proc' --exclude='/selinux' --exclude='/sys' --exclude='/tmp' --exclude='/usr' --exclude='/var/cache' --exclude='/var/run' --exclude='/var/tmp' root@cube:/// /media/Backup/cube///daily.1/ receiving incremental file list [...] I find three things to be wrong: 1. While rsync seems to finish, it always says the backup may be partially completed; rotating seems to have stopped as a result. Also, the daily.2 backup is of the day before I upgraded backupninja. 2. For some reason montly.1 is missing, but it might be return when rotating works again. 3. I've found that it syncs /proc (amongst which /proc/kcore which always gives IO errors), although it's in the excludes. When I use ps to examine the commandline, I get: /usr/bin/rsync -avF --delete --numeric-ids --rsync-path=rsync --exclude='/*bin'?--exclude='/dev'?--exclude='/home/*/.cache'?--exclude='/home/*/.local/share/Trash'?--exclude='/home/*/.thumbnails'?--exclude='/home/*/Music'?--exclude='/home/*/Videos'?--exclude='/lib*'?--exclude='/media'?--exclude='/mnt'?--exclude='/proc'?--exclude='/selinux'?--exclude='/sys'?--exclude='/tmp'?--exclude='/usr'?--exclude='/var/cache'?--exclude='/var/run'?--exclude='/var/tmp' root@cube:/// /media/Backup/cube///daily.1/ Does this newline stuff really work? This output seems weird to me. I think that (3) needs to be fixed. And maybe due to reasons (1) and (2) I wouldn't release backupninja 1.0 with support for the long rotation format. Cheers, Paul -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages backupninja depends on: ii bash 4.1-3 The GNU Bourne Again SHell ii bsd-mailx [mailx] 8.1.2-0.20100314cvs-1 simple mail user agent ii dialog 1.1-20100428-1Displays user-friendly dialog boxe ii gawk 1:3.1.7.dfsg-5GNU awk, a pattern scanning and pr ii mawk 1.3.3-15 a pattern scanning and text proces backupninja recommends no packages. Versions of packages backupninja suggests: ii bzip2 1.0.5-6+squeeze1 high-quality block-sorting file co pn debconf-utils none (no description available) pn duplicity none (no description available) pn genisoimage none (no description available) pn hwinfo none (no description available) ii mdadm 3.1.4-1+8efb9d1+squeeze1 tool to administer Linux MD arrays ii rdiff-backup1.2.8-6 remote incremental backup ii rsync 3.0.7-2 fast remote file copy program (lik pn subversion none (no description available) pn trickle none (no description available) pn wodim none (no description available) -- no
Bug#676319: [Pkg-owncloud-maintainers] Bug#676319: owncloud: installation depends on apache2 even though it depends on apache2 or httpd
Hi! On Wed, Jun 06, 2012 at 08:43:41AM +0200, Rafael Jesús Alcántara Pérez wrote: I have installed lighttpd but when I try to install owncloud, apt-get tries to install apache2 too. ownCloud for Debian supports and suggests to use Apache 2. However, we have an alternative depend on httpd. This means that other webservers, such as lighttpd, nginx, can be used but they need to be configured manually. This also means that apt-get will try to install apache2 unless you tell it not too. It is done this way by many packages such as roundcube, redmine, wordpress, etc. I do agree that there is a problem with our post-installation script, because it tries to use a2enmod and apache2ctl even if Apache2 is not installed. I will try to fix this in the new release. I hope this is a satisfying situation for you. Kind regards, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676600: [Pkg-owncloud-maintainers] Bug#676600: owncloud - lighttpd - php5-fpm: undefined method
Hi!
On Fri, Jun 08, 2012 at 07:45:49AM +0200, Thomas Renard wrote:
ACTUAL OUTCOME:
Internal server error or white page. lighttpd log shows:
error.log:2012-06-07 14:06:37: (mod_fastcgi.c.2699) FastCGI-stderr: PHP
message: PHP Fatal error: Call to undefined method OC_App::addSettingsPage()
in /usr/share/owncloud/files/appinfo/app.php on line 6
The first web page is not the expected owncloud page design but simple html.
Maybe the css-stuff is missing too. Because of the mod_fastcgi error it
may occur with php5-cgi too.
REPRODUCIBILITY:
always.
First I thought it was a migration problem from stock owncloud binaries
to the debian package but it occurs with a fully new installation too.
Do you mean by a fully new installation an installation using the released
tarball from upstream?
footnote1:
lighty configuration for owncloud (works with stock owncloud tarball):
alias.url += ( /owncloud/ = /var/lib/owncloud/ )
$HTTP[url] =~ ^/owncloud/data/ {
url.access-deny = ()
}
$HTTP[url] =~ ^/owncloud($|/) {
dir-listing.activate = disable
}
Given the .htaccess file that is shipped with ownCloud 4,
I am actually not aware whether lighttpd can read and use .htacess
files. If not, given the .htaccess file that is shipped with ownCloud
4, I am not sure that just the above three directives are enough to get
it working.
Cheers,
Paul
--
Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org
Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676319: Not a broken depedency problem
severity 676319 normal thanks Hi, I am downgrading the severity of this bug report, because there is no broken dependency problem. Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676131: owncloud: generates configuration that is user-readable
Package: owncloud Version: 4.0.1debian-1 Severity: important Hi, When you install owncloud, set up a MySQL/PostgreSQL database and then visit http://host/owncloud/, it generates the configurationf file /etc/owncloud/config.php. However, this file is readable by all users, which thereby gives them access to the database! This files should have mode 600 or 640 (given that it's owned by www-data:www-data). Cheers, Paul -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/3 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages owncloud depends on: ii apache2 2.2.22-5 ii apache2-mpm-prefork [httpd] 2.2.22-5 ii libjs-jquery 1.7.2+debian-1 ii libjs-jquery-jplayer 2.1.0-1 ii libjs-jquery-ui 1.8.ooops.20+dfsg-1 ii libphp-phpmailer 5.1-1 ii owncloud-mysql 4.0.1debian-1 ii php-crypt-blowfish 1.1.0~RC2-1 ii php-getid3 1.9.3-1 ii php-mdb2 2.5.0b3-2 ii php-mdb2-schema 0.8.5-1 ii php-pear 5.4.0-3 ii php-sabredav 1.6.2-1 ii php-xml-parser 1.3.4-4 ii php5 5.4.0-3 ii php5-curl5.4.0-3 ii php5-gd 5.4.0-3 Versions of packages owncloud recommends: ii exim4 4.77-1 ii exim4-daemon-light [mail-transport-agent] 4.77-1+b1 owncloud suggests no packages. -- Configuration Files: /etc/apache2/conf.d/owncloud.conf changed [not included] -- 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#675274: RM: libmarkaby-ruby -- ROM; unmaintained upstream, actually unlicensed
Package: ftp.debian.org Severity: normal Hi! As it turns out, Markaby actually isn't licensed by the license that is specified. In fact, not a trace of any license can be found. Also, the only reverse depend of Markaby is Camping, and that has switched to using Mab, a Markaby replacement (packaged in Debian as ruby-mab). See also this post and the discussion that follows: http://rubyforge.org/pipermail/camping-list/2011-December/001709.html Hence, Markaby should be removed! Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675083: bsfilter: should follow Debian Ruby policy draft (more)
Package: bsfilter Version: 1:1.0.17-2 Severity: important Hi! This package is part of the Debian/Ruby Extras team, but it is different in several different ways. In some ways it violates the Debian Ruby policy draft or team package practices; see also [1]. This bug report should be considered as a package review. As I am not familiar with the Japanese character sets, nor the package itself, I would like to leave the changes to you. (But do note that the freeze is near!) My remarks: * The maintainer of the package should be the team, the rest of us should be added as uploaders once we touch the package. * The Vcs-* fields are missing, please add them. * The standards version can be bumped. * If the depend is set on ruby1.8, also set XS-Ruby-Versions and XB-Ruby-Versions and ensure that the bsfilter script uses #!/usr/bin/ruby1.8. * The suggest on libchasen-ruby1.8 can never be fulfilled, I cannot find this package anywhere? * The names of the libraries in the depends, libkakasi-ruby1.8, libdb-ruby1.8, and libqdbm-ruby1.8 should be changed to ruby-kakasi, ruby-bdb, and ruby-qdbm respectively. * There seems to be a source problem for bsfilter concerning ruby-kakasi and mipsel, please refer to [2] for details. * Please convert the copyright file to the Debian copyright format version 1.0 * Please run the test suite during the build process. * It seems that debian/docs is emtpy, maybe it should contain htdocs? * The pristine-tar branch seems to be missing. Thanks in advance, Paul 1: http://wiki.debian.org/Teams/Ruby/Packaging 2: http://qa.debian.org/debcheck.php?dist=sidpackage=bsfilter -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675083: Acknowledgement (bsfilter: should follow Debian Ruby policy draft (more))
On Tue, May 29, 2012 at 07:15:11PM +, Debian Bug Tracking System wrote: Thank you for filing a new Bug report with Debian. I just saw that 1:1.0.17-2 was uploaded 3 weeks ago, but this was never pushed to the Git repository so I didn't see it. My bug report applies thus to 1:1.0.17-1, but I thinks some parts of the review still are valid for -2. Please make the changes, push the data and I'll close the bug report once this is done. Sorry for the inconvenience! Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673901: RM: libnet-tftp-ruby -- ROM; very low popcon, dead upstrean, no real maintainer
Package: ftp.debian.org Severity: normal Hi! This package has a very low popcon score (6), dead upstream (last release was about 7 years ago) and no maintainer that really cares about the package. The package should therefore be removed. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673903: RM: libbackgroundrb-ruby -- ROM; very low popcon, no real maintainer
Package: ftp.debian.org Severity: normal This package has a very low popcon score (5), it needs to be heavily revised to work with rails 3 and transitioned to the new Ruby policy, and there is no maintainer that really cares about the package. The package should therefore be removed. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673905: RM: libwww-delicous-ruby -- ROM; low popcon, no real maintainer
Package: ftp.debian.org Severity: normal This package has a very low popcon score (3) and also needs to be transition to the new Ruby policy. However, there is actually that really cares about the package. See also earlier discussion about removal of this package: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609739 The package should therefore be removed. (If necessary, it can always be repackaged with the Ruby/Extras team as ruby-delicious.) Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670829: gem doesn't contain lots of stuff
Hi! I (accidently) also started working on this, as the package is maintained with the Debian Ruby Extra team. I've just noticed this bug report. I've used gem2deb to setup a starting point, however I found out that the 1.0.0 gem only contains lib/ and ext/, which is quite meager. The 0.9.7.1 tarball used by the old rcov package containts docs, tests, and editor extensions. I'm not sure what to do. I'm mostly inclined to update 0.9.7.1 and ask for a release of 1.x with the stuff included. What do you guys think? Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609739: If not removed, than transitioned
Hello Noah, If you plan to prevent the removal of this library, I would like to ask you to transition it, please. There is not much time left until the Wheezy freeze. See also this email: https://lists.debian.org/debian-ruby/2012/04/msg00066.html If you are no longer interested, please file for removal of this library. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653359: [DRE-maint] Bug#653359: Status of mixlib-authentication tests
On Tue, May 15, 2012 at 07:11:50PM -0400, Bryan McLellan wrote: I see that the status is marked as resolved in version 0.10.12. The ticket status in JIRA is still open. The fix version was an artifact of the way it was opened, and I've removed it. We still need to find out why the test is failing. I'll try to find some time today to look at it. Ah ok. I see you have added a git-ref of some fix, but I don't know where to find it. Is it possibly to extract/get a patch? Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673166: gem2deb: installs ruby version specific .rb files in the vendor dir
Package: gem2deb Version: 0.2.13 Severity: normal Hi! When XS-Ruby-Versions is set to ruby1.8, gem2deb/dh_ruby still installs .rb files to /usr/lib/ruby/vendor_ruby. (See for example ruby-pcap 0.7.0-1.) As a result, when ruby1.9.1 is used to load the library, it can actually find it. Only when it also ships a .so file, it is out of the load path of ruby1.9.1 (namely /usr/lib/ruby/vendor_ruby/1.8/arch). gem2deb/dh_ruby should install .rb files to /usr/lib/ruby/vendor_ruby/1.8/ if XB-Ruby-Versions is set to 1.8. The symmetric case holds for ruby1.9.1. Cheers, Paul -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gem2deb depends on: ii build-essential 11.5 ii debhelper 9.20120513 ii devscripts 2.11.7 ii perl5.14.2-10 ii ruby1.8 1.8.7.358-2 ii ruby1.8-dev 1.8.7.358-2 ii ruby1.9.1 1.9.3.0-2.1 ii ruby1.9.1-dev 1.9.3.0-2.1 ii rubygems [rubygems1.8] 1.8.15-1 ii rubygems1.8 1.8.15-1 gem2deb recommends no packages. gem2deb 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#653359: Now tracked by Opscode as issue CHEF-2843
Hi! On Tue, Jan 03, 2012 at 02:12:25PM -0800, Christopher Brown wrote: http://tickets.opscode.com/browse/CHEF-2843 I see that the status is marked as resolved in version 0.10.12. However, I see on the mixlib-authentication github still just a 1.1.4 release which is two years old! I do see a lot of recent changes in the tree. Would it be possible to release a new version so it can be incorporated in Debian Wheezy (which freezes really really soon!) Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654708: backupninja: rsync handler only respects the first rsync option
On Mon, May 14, 2012 at 10:40:48AM -0300, rhatto wrote: Em Sun, May 13, 2012 at 02:38:34AM +0200, intrigeri escreveu: I have just merged half a ton of rhatto's bugfixes branches into upstream master, may someone please check if the bug is still present in the resulting Git upstream master branch? I'm also confused about this bug, as it start dealing with a specific issue (upstream https://labs.riseup.net/code/issues/3702) I can say at least, that the rsync handler I started using at some point started to respect my setting: rsync_options = -avF --delete I can see that it passes both options. The confusion is brought on by me switching to incrementally updated rsync handlers with fixes, often multiple at the same time. I am sorry. but also refers to other problems, including: - upstream https://labs.riseup.net/code/issues/3882 which is also reported at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656968 I will comment on this on the right bug report. - issues related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654192 I will also comment on this on the right bug report. Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#656968: backupninja: expands exclude paths for the remote side on the local side
On Mon, May 14, 2012 at 10:33:20AM -0300, rhatto wrote: Em Sun, May 13, 2012 at 02:43:39AM +0200, intrigeri escreveu: Paul van Tilburg wrote (23 Jan 2012 09:58:16 GMT) : which I can see when running that it is expanded to --excluded=/home/user1/Music --exclude=/home/user2/Music ... but then for users on the local side, which makes no sense. Why are these expanded and the excludes with the dot dirs not? What's the status of this bug? This bug was addressed upstream at https://labs.riseup.net/code/issues/3882 When I run backupninja -t some rsync config, I see in the debug output: Debug: Connected to host successfully sed: can't read s/^/--exclude='/g: No such file or directory Maybe I applied the patch wrong or don't have the most up-to-date rsync handler (which I am holding off due to the touch behaviour). Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#656968: backupninja: expands exclude paths for the remote side on the local side
On Mon, May 14, 2012 at 03:59:43PM -0300, rhatto wrote: Em Mon, May 14, 2012 at 05:57:03PM +0200, intrigeri escreveu: rhatto wrote (14 May 2012 15:39:06 GMT) : Does this will be correctly replaced when building backupninja? Maybe Paul didn't replaced @SED@ by sed -e but just by sed. What makes you think @SED@ should be replaced with sed -e? Maybe I confused something I always did (replacing by 'sed -e') when testing the code. :) Aargh, of course. I should actually have noticed that. Changed it throughout the handler, but now I might've falsely reported things as not fixed. This fixed the path expansion part at least: Debug: nice -n 0 /usr/bin/rsync -avF --delete --numeric-ids --rsync-path=rsync --exclude='/*bin' --exclude='/dev' --exclude='/home/*/.cache' --exclude='/home/*/.local/share/Trash' --exclude='/home/*/.thumbnails' --exclude='/home/*/Music' --exclude='/home/*/Videos' --exclude='/lib*' --exclude='/media' --exclude='/mnt' --exclude='/proc' --exclude='/selinux' --exclude='/sys' ... Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#654192: Fwd: Bug#654192: [pkg-backupninja] Bug#654192: backupninja rsync handler bugs
On Thu, May 10, 2012 at 09:50:40PM -0300, rhatto wrote: Em Thu, May 10, 2012 at 12:45:08PM +0200, intrigeri escreveu: If the rsync handler is not in a good enough state on May 20th yet, I'll release backupninja 1.0 *without* the rsync handler, and upload it to Debian sid. Seems fair and I hope we can do it. I agree. I must say that with the recent patches it seems to work for me. The other things we recently discusses are cosmetics. I actually disagree with #3929 though, now I think of it. The date of the daily/weekly/monthly dirs is valueable, otherwise there is now way to tell when the backup is made. (At least, I frequently use it to check how things are going). I just cycled over all backupninja rsync issues[1], checked their status and made the needed commits so now I think we can test a rsync handler candidate for the 1.0 release. I merged all my recent work in my rsync branch[2] which right now is merged with master. So the rsync handler can be either tested from the current code at my rsync branch[3] or use a diff from from backupinja shipped on debian squeeze. I would like to try it (and do a diff what the changes are), but the host is unforunately down (or unreachable for me). Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#654192: Fwd: Bug#654192: [pkg-backupninja] Bug#654192: backupninja rsync handler bugs
On Fri, May 11, 2012 at 09:26:10AM -0300, rhatto wrote:
Em Fri, May 11, 2012 at 09:53:41AM +0200, Paul van Tilburg escreveu:
I actually disagree with #3929 though, now I think of it. The date of
the daily/weekly/monthly dirs is valueable, otherwise there is now way
to tell when the backup is made. (At least, I frequently use it to
check how things are going).
I would like to know Intrigeri's opinion about that, but generally I think
that leaving the folder dates untouched can led to more confusion than
clarification.
True, but the touching also leads to a loss of information.
Maybe it should not remove the created metadata file. That could also
be an easy solution.
So daily.1 has a created, and daily.{2,...}, weekly.{1,...} and
monthly.{1...} has created and rotated. At the moment only daily.* seem
to retain the rotated.
On the other hand, in case of both solutions the rsync handler messes
with actual file/dir stat metadata and not just with stuff under
metadata/; this is was I actually dislike most. When I want to get
something back from a backup made on march 4, I just do ls -l in the
backup dir and know what I should use.
I would like to try it (and do a diff what the changes are), but the
host is unforunately down (or unreachable for me).
Sorry, it was an unexpected downtime. It should be reachable now.
Ok, I did a diff. I have run a version of the rsync handler without:
- the lockfile/pipefail fix,
- the debug-instead-of-echo fix,
- the weekly*/monthly*-dir-touching fix,
- the metadata-validation fix
But the basic functionality (including numerous rotation fixes) is there
and works! I'm switching to your rsync handler just yet until the
weekly.*/monthl*-dir-touching situation is resolved.
Cheers,
Paul
--
Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org
Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181
signature.asc
Description: Digital signature
Bug#654192: Fwd: Bug#654192: [pkg-backupninja] Bug#654192: backupninja rsync handler bugs
On Wed, May 09, 2012 at 07:20:25PM -0300, rhatto wrote: If I understood correctly given the info above, weekly.1/ folder dates from Feb 27 01:11 but metadata/weekly.1/rotated says it was rotated at Thu 12 Apr 2012 01:04:38 CEST. What really counts is the date from the metadata file as the folder dates varies if it was created (new increment, mkdir) or moved from an older increment (weekly.1, is the former oldest daily backup). Indeed. However, the dates of the directories seem to indicate a bit when it was last touched (roughly). This makes me feel that we should change the folder dates to something closer to the actual rotation dates (a simple touch would suffice) otherwise it can get confusing to have one date in the folder and other in the increment. For that, I'm opening upstream issue https://labs.riseup.net/code/issues/3929 Agreed. I wouldn't exclude other problems with the weekly/monthly rotations and I could not spot why your weekly.* folders are so old comparing to the daily ones (maybe you disabled your rsync action for a while?) but the rotations seems to be happening. I haven't, but rotating seems to have started to happen! # ls -l total 56 drwxr-xr-x 19 root root 4096 May 10 01:01 daily.1/ drwxr-xr-x 19 root root 4096 May 9 01:01 daily.2/ drwxr-xr-x 19 root root 4096 May 8 01:01 daily.3/ drwxr-xr-x 19 root root 4096 May 7 01:01 daily.4/ drwxr-xr-x 19 root root 4096 May 6 01:01 daily.5/ drwxr-xr-x 19 root root 4096 May 5 01:02 daily.6/ drwxr-xr-x 19 root root 4096 May 4 01:01 daily.7/ drwx-- 15 root root 4096 May 10 01:01 metadata/ drwxr-xr-x 19 root root 4096 Apr 28 01:01 weekly.1/ drwxr-xr-x 19 root root 4096 Feb 27 01:11 weekly.2/ # cat metadata/weekly.*/rotated Sat 05 May 2012 01:00:36 CEST 1336172436 Sat 05 May 2012 01:00:36 CEST 1336172436 I still need to provide an unified patch for you to test. I'm very busy with lots of stuff but I'll try to do it soon. Sure, no problem. As it seems to be going right now, I can leave it running. Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#440628: Working and broken again
Hi! I think that this bug has been fixed ages ago. At least, it has been working for me for ages. However, recently it stopped working for the unstable and experimental distributions. For example, using content search, enter bin/ls and choose paths ending with the keyword. This should obviously have results in all distributions. However, it does not give results for unstable and experimental. Maybe the index (generation) is broken? Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648674: Owncloud debian package
Hey Damien, On Tue, May 08, 2012 at 08:08:57PM +0200, Damien Raude-Morvan wrote: As user of owncloud (and DD :), I'm still interested in sponsoring / helping with owncloud packaging. Is there a current git repository that a can check ? (hint: create one on Alioth if not already done) BTW, did you fix some of glitches previously reported by me and Paul Wise [1] [2] ? Yes, we are already handling this, but there are many TODO items still open. We have actually just formed the ownCloud for Debian team [1], you are very welcome to join. We aim to package owncloud first, then the client and maybe some useful apps (and also attract other users/devs to join in). For the git repos, see [2]. 1: https://alioth.debian.org/projects/pkg-owncloud/ 2: http://anonscm.debian.org/gitweb/?p=pkg-owncloud Are you also planning to package owncloud-client part ? If so, you should check with upstream with their existing [3] packages. Plans yes, but we haven't looked at it at all yet. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#671767: [DRE-maint] Bug#671767: ruby-glib2: Ruby fail to load glib2
Hi! On Sun, May 06, 2012 at 09:30:25PM +0200, Remi Vanicat wrote: ruby fail to require glib2: [...] It seem a file as been forgotten. Commenting the require 'glib2/deprecatable' line in /usr/lib/ruby/vendor_ruby/glib2.rb make a quick and dirty fix. Yes, I am so sorry. I already fixed it this morning with a new upload. See also: http://packages.qa.debian.org/r/ruby-gnome2/news/20120506T155254Z.html Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646642: Wrong format
Hi! It seems that the format of the plugins has changed and that Ampache is behind. First of all, the .plugin file should have the header [Plugin], not [RB Plugin]. When you rename the file to ampache.plugin and make the change, Rhythmbox tries to load it. However, it also doesn't seem quite up to date with the current plugin API: % rhythmbox ImportError: No module named ampache (rhythmbox:17197): libpeas-WARNING **: Error loading plugin 'ampache' So I tried linking ampache.py to __init__.py. That also didn't help: % rhythmbox Traceback (most recent call last): File /usr/lib/rhythmbox/plugins/ampache/ampache.py, line 3, in module import rhythmdb, rb ImportError: No module named rhythmdb (rhythmbox:17281): libpeas-WARNING **: Error loading plugin 'ampache' I think this plugin is more broken than it seems. It either should be updated or removed. Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654192: Fwd: Bug#654192: [pkg-backupninja] Bug#654192: backupninja rsync handler bugs
Hello all, On Mon, Apr 09, 2012 at 02:01:45PM +0200, Paul van Tilburg wrote: I can confirm that after applying the patch, backups seem to be running again (first run with patch was Apr 7 00:36): # ls -l total 40 drwxr-xr-x 19 root root 4096 Apr 9 01:12 daily.1/ drwxr-xr-x 19 root root 4096 Apr 8 01:10 daily.2/ drwxr-xr-x 19 root root 4096 Apr 7 01:14 daily.3/ drwxr-xr-x 19 root root 4096 Apr 7 00:36 daily.4/ drwxr-xr-x 19 root root 4096 Feb 27 01:11 daily.5/ drwx-- 11 root root 4096 Apr 9 01:12 metadata/ And... I have found another problem. Sorry! The daily backups seem to run fine, but two weeks later, I still have no weekly backups: # ls -l total 52 drwxr-xr-x 19 root root 4096 Apr 24 01:01 daily.1/ drwxr-xr-x 19 root root 4096 Apr 23 01:01 daily.2/ drwxr-xr-x 19 root root 4096 Apr 22 01:01 daily.3/ drwxr-xr-x 19 root root 4096 Apr 21 01:01 daily.4/ drwxr-xr-x 19 root root 4096 Apr 20 01:01 daily.5/ drwxr-xr-x 19 root root 4096 Apr 19 01:01 daily.6/ drwxr-xr-x 19 root root 4096 Apr 18 01:01 daily.7/ drwx-- 14 root root 4096 Apr 24 01:01 metadata/ drwxr-xr-x 19 root root 4096 Feb 27 01:11 weekly.1/ drwxr-xr-x 19 root root 4096 Jan 13 01:07 weekly.2/ drwxr-xr-x 18 root root 4096 Jan 4 01:04 weekly.3/ When running backupninja in debug mode, it says that it thinks that each weekly.* is not old enough as it doesn't match the 7d/14d/21d/etc. old requirement. I think the metadata is fixed now for the daily stuff, but not the weekly stuff, concerning what I found: # cat metadata/weekly.1/rotated Thu 12 Apr 2012 01:04:38 CEST 1334185478 Obviously, weekly.1 is not rotated April 12, but February 27, the same holds for weekly.2 and weekly.3, but then with April 7. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#670196: RM: libcomplearn-ruby -- ROM; dead upstream; low popcon
Package: ftp.debian.org Severity: normal Hi! It seems that libcomplearn-ruby has dead upstream, a very low popcon (y) and there is nobody interested in maintaining it. I therefore as for removal. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670057: RM: libsvg-ruby -- ROM; dead upstream; superseeded
Package: ftp.debian.org Severity: normal Hi, The Ruby SVG library in libsvg-ruby has seen no upstream activity since 2004. Secondly, it has been superseeded by the library ruby-svg-graph (or libsvg-graph-ruby in stable) available in Debian. Therefore, I want to request removal of libsvg-ruby. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648674: Sponsoring
Hey again, On Fri, Apr 13, 2012 at 11:57:40AM +0200, Paul van Tilburg wrote: I hope you haven't lost interested in packaging ownCloud for Debian. I'm sorry you had to wait this long; these things can unfortunately take some time, so it seems. I am interested in having this package in Debian (although I am just trying out ownCloud yet) and thus have reviewed the package and have the following comments: I've gone ahead and started to update the package to 3.0.2 a bit if you don't mind. I've also found the TODO-items in debian/rules, that I overlooked previously. They need to be addressed, indeed. I also found the wget stuff in postinst, this really need to be solved! I don't think it can be uploaded until this is fixed. If really necessary we can dfsg-clean the original tarball or work out some other solution with upstream. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648674: Sponsoring
Hello Thomas, On Fri, Apr 20, 2012 at 03:27:17PM +0200, Thomas Müller wrote: I will most likly stripp off the app 'media' which is the media player. This thing needs the jplayer.swf. Well, people can install apps manually anyway, and it up to them what. As long as we do not package and redistribute problematic stuff. As you already started with the update to 3.0.2 can I assume you are also interested in co-maintaining? Well, I cannot fully commit yet, but it's looking good. I am looking to do it within the scope of my job otherwise I cannot promise having time for it yet. This means that it should be good enough for our project to use. I'd love to have a more experianced DD on my side - an least to have a backup in stressfull times. Yes, I can imagine that. The same holds for me. We need a svn or git repo - can I ask you for support on this? Yeah, we need a git repo. I already feel dirty meddling with package stuff just in some directory on my harddisk... unversioned. I suggest I set one up, you import your original 2.0.3 work, and I update it with the 3.0.2 work. As a result, you can see what I have fixed and what still needs to be done. For 4.x we need to do this again, but we might upload 3.0.2 to experimental soon. OC 4 will arrive on 22.5.2012 - maybe the candidate for Debian Wheezy? I think so. I ope we can convince them beforehand to clean the source up a bit. All these messy excutable bits and what not. Concerning your comments from your last email: - watch file: There was none due to missing upstream info on the web site. I did address this to the project head and now the info is there - let's see if it's watch file compliant. I was looking for that info, couldn't find it, so I let the watch-file be in my packages. - unapplied-patches: I still need to read the link. Already set that locally. - 3rd party stuff: I had a look and I didn't find sabre. Concerning MDB2: there is a sub-package missing - I think schema. We need to reavaluate. Ok, but I think we should either strip 3rd-party and make sure everything is in Debian separately. Or... if they made modifications to stuff in 3rd-party (which is not cool), we need to think of a better solution. I can resume work on this possibly next Sunday or Tuesday. Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654192: Fwd: Bug#654192: [pkg-backupninja] Bug#654192: backupninja rsync handler bugs
On Tue, Apr 17, 2012 at 12:56:58AM -0300, rhatto wrote: Em Sun, Apr 15, 2012 at 04:26:27PM +0200, Paul van Tilburg escreveu: I meant this differently. It just seems that if you make an error, e.g. you set: rsync_options = --non-existing-bla --syntax-error-coming up and rsync bails out, or maybe segvs or whatever, backupninja happily reports via email: SUCCES. Yes, that's another issue: https://labs.riseup.net/code/issues/3892 Ok. I know that the moreutils package in Debian has the mispipe tool[1] to return the exit code of the first program rather than the latter. Maybe this tool or its source code is useful. 1: http://packages.debian.org/source/unstable/moreutils I am reluctant to apply this... why also first $created but \$created in the second hunk? The second hunk refers to code to be executed in the remote side, so it has to be escaped to not evaluate at the local side. Maybe would be better to wait me to sort out the most important rsync handler issues and then give you a single patch to try so I don't bother you too much with my development as I already did. :/ Ok, it's no problem. I was just indicating this to mention that my results may become unreliable at some point due to this. But I keep a rsync.orig file to compare, and sometimes I patch by commenting out the old code. I think it's still good. :) Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#654708: backupninja: rsync handler only respects the first rsync option
On Fri, Apr 13, 2012 at 10:09:08AM -0300, rhatto wrote: Em Fri, Apr 13, 2012 at 09:40:09AM +0200, Paul van Tilburg escreveu: On Thu, Apr 12, 2012 at 09:34:42PM -0300, rhatto wrote: Could you try the patch below? but rsync doesn't seem to use it for some reason. I see it backing up /lib, /dev, /proc, etc. And it now hangs on /proc/kcore, so I am revering the patch. Could you try the following change (replacing @SED@ by sed)? This might add single quotes to the excludes, like --exclude='/*bin'. I am unsure if the patch is meant to be on top of the previous on, or instead of the previous one. I.e. is the adjustment to the call of $nice $rsync etc. necessary or not? Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#654708: backupninja: rsync handler only respects the first rsync option
On Sun, Apr 15, 2012 at 11:10:01AM -0300, rhatto wrote: Em Sun, Apr 15, 2012 at 04:00:02PM +0200, Paul van Tilburg escreveu: I am unsure if the patch is meant to be on top of the previous on, or instead of the previous one. It's an incremental patch, so you apply atop of the previous. I'm using a dedicated branch to handle this issue: https://git.sarava.org/?p=backupninja.git;a=shortlog;h=refs/heads/bug/3882 Ok, yes. You must understand that this is already the 6th patch applied to /usr/share/backupninja/rsync and I am starting to loose track of what I am doing. With the patch it's even worse: Info: Syncing / on /media/Backup/tetraeder.rsync///daily.1/... Debug: nice -n 0 /usr/bin/rsync -avF --delete --numeric-ids --rsync-path=rsync root@tetraeder:/// /media/Backup/tetraeder.rsync///daily.1/ Unexpected remote arg: root@tetraeder:/// rsync error: syntax or usage error (code 1) at main.c(1222) [sender=3.0.7] Info: finished action /etc/backup.d/10.tetraeder.rsync: SUCCESS Note that the whole exclude part is missing in action. Do you need my config file to be able to test it out yourself? Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#654192: Fwd: Bug#654192: [pkg-backupninja] Bug#654192: backupninja rsync handler bugs
On Thu, Apr 12, 2012 at 08:54:55PM -0300, rhatto wrote: Em Mon, Apr 09, 2012 at 02:01:45PM +0200, Paul van Tilburg escreveu: What it IMO doesn't solve, is the fact that the handler gave a syntax error and probably returned and error code, but backupninja intepreted this as backup succesful. This worries me a bit. I meant this differently. It just seems that if you make an error, e.g. you set: rsync_options = --non-existing-bla --syntax-error-coming up and rsync bails out, or maybe segvs or whatever, backupninja happily reports via email: SUCCES. I think that the only way to avoid that is to validate the metadata. The following commit tries to do it: https://git.sarava.org/?p=backupninja.git;a=commitdiff;h=e22107cf0954f29215052becf848bc28b47ffbe0 Could you test to see if it works? I am reluctant to apply this... why also first $created but \$created in the second hunk? Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#668842: RM: libmmap-ruby -- ROM; dead upstream; no reverse depends
Package: ftp.debian.org Severity: normal Hi! This package has upstream that is dead for over 7 years. There are a few bugs that cannot be solved easily. It is not ready for the future as it cannot be follow the ongoing Ruby transition nor does it support Ruby 1.9.1, the upcoming stable Ruby version. Finally, the high popcon value is due to the fact that it was a depend of libruby-extras, a package that also has been removed. Cheers, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654708: backupninja: rsync handler only respects the first rsync option
On Thu, Apr 12, 2012 at 09:34:42PM -0300, rhatto wrote: Em Mon, Apr 09, 2012 at 02:13:01PM +0200, Paul van Tilburg escreveu: This partly fixes it. Indeed, the --delete gets passed on now, but still expansion happens. But the expansion still happens (irregularly), so '/*bin' is expanded to '/bin' and '/sbin', but '/home/*/.cache' isn't, and '/home/*/Music' is!? Hi Paul, thanks again for the reportback. I opened a new upstream bug as this looks like another issue, but still related with your rsync handler experience: https://labs.riseup.net/code/issues/3882 Could you try the patch below? Applied, but it didn't help. The commandline is now: Info: Syncing / on /media/Backup/tetraeder.rsync///daily.1/... Debug: nice -n 0 /usr/bin/rsync -avF --delete --numeric-ids --rsync-path=rsync --exclude=/*bin --exclude=/dev --exclude=/home/*/.cache --exclude=/home/*/.local/share/Trash --exclude=/home/*/.thumbnails --exclude=/home/*/Music --exclude=/home/*/Videos --exclude=/lib* --exclude=/media --exclude=/mnt --exclude=/proc --exclude=/selinux --exclude=/sys --exclude=/tmp --exclude=/usr --exclude=/var/cache --exclude=/var/run --exclude=/var/tmp root@tetraeder:/// /media/Backup/tetraeder.rsync///daily.1/ but rsync doesn't seem to use it for some reason. I see it backing up /lib, /dev, /proc, etc. And it now hangs on /proc/kcore, so I am revering the patch. Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 signature.asc Description: Digital signature
Bug#655080: Fixed?
Hi! This seems to have been fixed, but I have no idea how and why, as I haven't upgraded gnome-shell recently as far as I know. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648674: Sponsoring
Hi Thomas, I hope you haven't lost interested in packaging ownCloud for Debian. I'm sorry you had to wait this long; these things can unfortunately take some time, so it seems. I am interested in having this package in Debian (although I am just trying out ownCloud yet) and thus have reviewed the package and have the following comments: * The debian/watch file is not working and needs an update. * I would add debian/source/local-options containing unapply-patches for convenience. See also: https://raphaelhertzog.com/2010/11/18/4-tips-to-maintain-a-3-0-quilt-debian-source-package-in-a-vcs/ * I see that some 3rd-party stuff is installed; should Sabre not be separately packages and is MDB2 not already in Debian? I have not checked the copyright very thorougly yet, so that is still to-do for me. Additionally, the package should probably be updated to the latest upstream version (3.0.2 I believe). Otherwise the package looks very nice and clean. I will play a bit with it now. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
