search for: bpo70

Hallo Everyone, since some days a new dovecot version is available in Debian "wheezy-backports": (1:2.2.9-1~bpo70+1) wheezy-backports As described in http://wiki2.dovecot.org/Plugins/Zlib and http://www.dovecot.org/doc/NEWS-2.2 "xz"-compression is available since Dovecot version 2.2.9. Today I tried to convert my mailboxes with the new xz compression. Therfore I changed my config as follows: /e...

...oc krb5-config libpam-krb5 Hmm, problem, libgnutls-dev doesn't exist on jessie, quick search seems to say that it has been replaced by libgnutls28-dev So tried again, still doesnt work: The following packages have unmet dependencies: libgnutls28-dev : Depends: libgnutls-deb0-28 (= 3.3.8-6~bpo70+1) but 3.3.8-6 is to be installed Depends: libgnutlsxx28 (= 3.3.8-6~bpo70+1) but it is not going to be installed Depends: nettle-dev (>= 2.5) but it is not going to be installed Depends: libtasn1-6-dev (>= 3.9) but it is not going...

Dear Samba fellows, I try to install samba on my notebook in order to get it into my samba based domain. It was a bit picky to get everything assembled on the notebook - but that last issue is hard. :-( I installed it from the sources on Debian Jessie - exactly in the same manner I used for my servers. I got sssd and kerberos working... > root at alecto:/usr/src/samba4/samba-4.2.0#

...64bit processors, 'virsh capabilities' reports the cpu differently on Debian Wheezy-amd64 and Wheezy-i386. The results given by the Wheezy-i386 version seem very wrong (since n270 is an Atom processor). Apart from architecture, the package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. /usr/share/libvirt/cpu_map.xml files are identical. Is this a known issue? Details for one server are: # cat /proc/cpuinfo| head -n 26 processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-2650L 0 @ 1.80GHz steppi...

Hi BTRFS community I have a problem using btrfs/nfs to store my vmware images. - following setup :(debian wheezy + backports) Linux sncubetest02 3.14-0.bpo.1-amd64 #1 SMP Debian 3.14.12-1~bpo70+1 (2014-07-13) x86_64 GNU/Linux > btrfs --version Btrfs v3.14.1 > btrfs fi show Label: none uuid: 8e37c8d0-e0ef-4857-ae9f-9a1be21901ed Total devices 2 FS bytes used 210.27GiB devid 1 size 500.00GiB used 107.03GiB path /dev/sdb1 devid 2 size 500.00GiB use...

I currently have the dovecot-core package from wheezy-backports pinned on one of my servers to version '2.2.9', which has been working great. I now want to upgrade that to the newest version under wheezy-backports which is: dovecot-core (1:2.2.13-11~bpo70+1) but I can't figure out how to get do it. I've tried a few different formats of the name but apt-get update then apt-get dost-upgrade doesn't pick up the new version - it ignores it when trying to do an update. This is what I've got in my apt preferences and pin files... /etc/ap...

...t;> capabilities' reports the cpu differently on Debian Wheezy-amd64 and >> Wheezy-i386. The results given by the Wheezy-i386 version seem very >> wrong (since n270 is an Atom processor). Apart from architecture, the >> package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. >> /usr/share/libvirt/cpu_map.xml files are identical. Is this a known >> issue? Details for one server are: >> >> # cat /proc/cpuinfo| head -n 26 >> processor : 0 >> vendor_id : GenuineIntel >> cpu family : 6 >> model :...

I am currently running LibVirt with Qemu on Debian Wheezy: Versions: - libvirtd (libvirt) 1.2.4 - qemu-x86_64 version 2.0.0 (Debian 2.0.0+dfsg-4~bpo70+1), Copyright (c) 2003-2008 Fabrice Bellard It's all working perfectly, including ACPI: virsh shutdown guest. However when I issue "halt" from the guest, the guest stops but libvirt thinks it is still running: (virsh list outputs state: running). virsh dominfo does the same thing:...

...s, 'virsh > capabilities' reports the cpu differently on Debian Wheezy-amd64 and > Wheezy-i386. The results given by the Wheezy-i386 version seem very > wrong (since n270 is an Atom processor). Apart from architecture, the > package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. > /usr/share/libvirt/cpu_map.xml files are identical. Is this a known > issue? Details for one server are: > > # cat /proc/cpuinfo| head -n 26 > processor : 0 > vendor_id : GenuineIntel > cpu family : 6 > model : 45 > model name : Intel(...

...reports the cpu differently on Debian Wheezy-amd64 and >>>> Wheezy-i386. The results given by the Wheezy-i386 version seem very >>>> wrong (since n270 is an Atom processor). Apart from architecture, the >>>> package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. >>>> /usr/share/libvirt/cpu_map.xml files are identical. Is this a known >>>> issue? Details for one server are: >>>> >>>> # cat /proc/cpuinfo| head -n 26 >>>> processor : 0 >>>> vendor_id : GenuineIntel >>...

...ntly on Debian Wheezy-amd64 and >>>>>> Wheezy-i386. The results given by the Wheezy-i386 version seem very >>>>>> wrong (since n270 is an Atom processor). Apart from architecture, the >>>>>> package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. >>>>>> /usr/share/libvirt/cpu_map.xml files are identical. Is this a known >>>>>> issue? Details for one server are: >>>>>> >>>>>> # cat /proc/cpuinfo| head -n 26 >>>>>> processor : 0 >>>>...

...ecture Description +++-==================================-=============================-============-============================ ii kvm 1:1.1.2+dfsg-6+deb7u8 amd64 dummy transitional package from kvm to qemu-kvm ii libvirt-bin 1.2.9-9~bpo70+1 amd64 programs for the libvirt library ii qemu-kvm 1.1.2+dfsg-6+deb7u8 amd64 Full virtualization on x86 hardware Both machines have shared storage mounted in same place. Very little info on web regarding this error. Can anyone suggest what is going...

...erkeley DB DLZ driver... not found configure: error: could not find Berkeley DB include directory root at app1:/usr/src/BUILD/bind9/bind9-9.9.5.dfsg-dlz# and gotten same at https://packages.debian.org/wheezy-backports/bind9 -> http://ftp.de.debian.org/debian/pool/main/b/bind9/bind9_9.9.5.dfsg-4~bpo70+1.dsc Check it yourself if you don?t trust - DLZ dl open support at Debian had been droped OUT. I?ll work on an debian 9.9.6 bind dlz Build project . Any vulnoteered existing patches are welcome ( by mail i.e ). -- Mit freundlichen Gr??en / Best Regards Horst Venzke ; PGP NET : 1024G/082F2E6D...

...ties' reports the cpu differently on Debian Wheezy-amd64 and > >> Wheezy-i386. The results given by the Wheezy-i386 version seem very > >> wrong (since n270 is an Atom processor). Apart from architecture, the > >> package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. > >> /usr/share/libvirt/cpu_map.xml files are identical. Is this a known > >> issue? Details for one server are: > >> > >> # cat /proc/cpuinfo| head -n 26 > >> processor : 0 > >> vendor_id : GenuineIntel > >> cpu family...

...d64 and >>>>>>>> Wheezy-i386. The results given by the Wheezy-i386 version seem very >>>>>>>> wrong (since n270 is an Atom processor). Apart from architecture, the >>>>>>>> package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. >>>>>>>> /usr/share/libvirt/cpu_map.xml files are identical. Is this a known >>>>>>>> issue? Details for one server are: >>>>>>>> >>>>>>>> # cat /proc/cpuinfo| head -n 26 >>>>>>>&...

Hi everyone, I have the exact same problem as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772154 But the Samba version is different and much newer (Debian Wheezy 2:4.1.17+dfsg-1~bpo70+1). B asically many errors appear about non existing usershares. These fake usershares are just the user name, but truncated of the last character. process_usershare_file: stat of /var/lib/samba/usershares/netlogo failed. No such file or directory There are so many messages that the serve...

...t; Rowland > If anybody is interested, this is the results of my testing, first here are the results of adding an NS record to the dns domain SOA record for the second DC on a domain using the internal dns server: root at testdc1:~# dig SOA +multiline home.lan ; <<>> DiG 9.9.5-4~bpo70+1-Debian <<>> SOA +multiline home.lan ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10153 ;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;home.lan. IN SOA ;; ANSWER SECTION...

...u differently on Debian Wheezy-amd64 and > >>>> Wheezy-i386. The results given by the Wheezy-i386 version seem very > >>>> wrong (since n270 is an Atom processor). Apart from architecture, the > >>>> package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. > >>>> /usr/share/libvirt/cpu_map.xml files are identical. Is this a known > >>>> issue? Details for one server are: > >>>> > >>>> # cat /proc/cpuinfo| head -n 26 > >>>> processor : 0 > >>>> vendor_id...

Hello all! I operate two-dc domain, based on samba 2:4.1.9+dfsg-1~bpo70+1 Forest function level: (Windows) 2003 Domain function level: (Windows) 2003 Lowest function level of a DC: (Windows) 2008 R2 AD Recycle bin not enabled (it can be enabled only on Dom.Level 2008R2) Previous week one of our administrators delete computer accounts from AD by accident, and we are...

...v > libpng12-dev > # Ricompilare pacchetti qemu da backports, purtroppo necessario per > librerie xen differenti > wget > http://ftp.de.debian.org/debian/pool/main/q/qemu/qemu_2.0.0+dfsg.orig.tar.xz > wget > http://ftp.de.debian.org/debian/pool/main/q/qemu/qemu_2.0.0+dfsg-4~bpo70+1.debian.tar.gz > tar -xpJf qemu_2.0.0+dfsg.orig.tar.xz > tar -xpzf qemu_2.0.0+dfsg-4~bpo70+1.debian.tar.gz > mv debian/ qemu-2.0.0+dfsg/ > cd qemu-2.0.0+dfsg/ > debuild -i -b -us -uc > dpkg -i qemu-system-x86*.deb qemu-system-common*.deb qemu-keymaps*.deb > qemu-utils*.deb &g...