Bug#818190: /usr/bin/borg VS /usr/bin/borgbackup

2016-03-14 Thread Technicien Informatique
Package: borgbackup Version: 1.0.0-2~bpo8+1 Hi, Is there a reason the borgbackup package installs borg in two different places (/usr/bin/borg & /usr/bin/borgbackup) ? I have to say this is a little bit confusing. The documentation says you should call "borg", but your package is named "borgbacku

Bug#785052: Roadmap for OC8 packaging

2015-05-11 Thread Technicien Informatique
Package: owncloud HI! I just wanted to know if you had a roadmap for the packaging of OC 8. It's been out for a few weeks now and I wondered if you thought packaging it before fall was reasonable. OC 8 fixes a lot of annoying bugs and I would like to use the summer to migrate from OC 7 to it...

Bug#768495: Upgrade from 2.20.1-5.11 to 2.25.2-2 breaks pam-mount

2014-12-12 Thread Technicien Informatique
or my company... You would do me a big favor by pushing the newest release to sid :D -- Louis-Philippe VĂ©ronneau 2014-11-07 15:29 GMT-05:00 Phillip Susi : > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > reassign 768495 libpam-mount > thanks > > On 11/7/2014 2:5

Bug#768495: Upgrade from 2.20.1-5.11 to 2.25.2-2 breaks pam-mount

2014-11-07 Thread Technicien Informatique
Package: mount Version: 2.25.2-2 I am using mount with pam-mount and davfs2 to mount Owncloud WebDAV shares on user accounts. The actual mounting is done by pushing a custom /etc/security/pam_mount.conf.xml file to the clients where the right davfs2 configuration is written. It looks like this:

Bug#332392: iptables: module iprange doesn't work

2005-10-06 Thread Technicien
Package: iptables Version: 1.3.3-2 Severity: normal Hello when trying to use the iprange module : located in /lib/iptables/libipt_iprange.so with a command like iptables -A INPUT -m iprange --src-range 192.168.1.0-192.168.1.255 -j ACCEPT -v I get this message with an error : ACCEPT all opt -- i