Bug#692984: Expected upload of sogo-connector

2014-07-22 Thread Luca Capello
forcemerge 692984 659291
reassign 705488 wnpp
forcemerge 692984 705488
user cont...@itopie.ch
usertags 692984 + itopie.ch-installation
user i...@codha.ch
usertags 692984 + codha.ch-installation
thanks

Hi there!

Merging all relevant/duplicate bugs and Cc:ing all the interested
people.

On Wed, 30 Apr 2014 13:46:26 +0200, Carsten Schoenert wrote:
 Am 30.04.2014 12:41, schrieb Boris Barbour:
  I'm interested in obtaining the sogo-connector, as this seems to be the 
  only way to sync contacts with owncloud. I'd prefer to get it through 
  the debian repositories. The messages above suggest that it could be (or 
  has been) uploaded, which is good news. When might we expect it to appear?
 
 thanks for your interests!
 I don't know then the FTP Team will allow the upload of the package, so
 sorry, I can't say something promising right now.

The package is still in the NEW queue, please remember to close this bug
when the package will enter Debian, since the current debian/changelog
does not automatically close any bug:

  https://ftp-master.debian.org/new/sogo-connector_24.0.5-1.html

 You can rebuild the package by yourself using the current repository
 which will be found on
 
   https://github.com/tijuca/sogo-connector

Any reason why this is not on Alioth?

 You will probably need a sid chroot to build the package, right know I
 always used git-pbuilder and doesn't have cared about backports or so.
 But that should not be a big problem to created a wheezy-backport
 package too.

Actually, using a *plain* wheezy chroot is not enough:
=
[...]
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
The following NEW packages will be installed:
  bsdmainutils{a} debhelper{a} file{a} gettext{a} gettext-base{a}
  groff-base{a} html2text{a} intltool-debian{a} libasprintf0c2{a}
  libcroco3{a} libffi5{a} libgettextpo0{a} libglib2.0-0{a} libmagic1{a}
  libpcre3{a} libpipeline1{a} libunistring0{a} libxml2{a} man-db{a}
  po-debconf{a}
0 packages upgraded, 20 newly installed, 0 to remove and 0 not upgraded.
Need to get 9191 kB/9656 kB of archives. After unpacking 25.6 MB will be used.
The following packages have unmet dependencies:
 pbuilder-satisfydepends-dummy : Depends: icedove-dev (= 24~) but it is not 
going to be installed.
 Depends: mozilla-devscripts (= 0.32~) but it 
is not going to be installed.
 Depends: python-ply but it is not going to be 
installed.
Unable to resolve dependencies!  Giving up...
[...]
Abort.
E: pbuilder-satisfydepends failed.
=

Here is the reason:
=
$ rmadison icedove-dev | grep wheezy
 icedove-dev | 10.0.12-1  | wheezy| amd64, armel, armhf, 
i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, 
sparc
 icedove-dev | 17.0.10-1~deb7u1   | wheezy-security   | ia64, kfreebsd-amd64, 
kfreebsd-i386, mips, mipsel
 icedove-dev | 24.5.0-1~deb7u1| wheezy-security   | s390, sparc
 icedove-dev | 24.6.0-1~deb7u1| wheezy-security   | amd64, armel, armhf, 
i386, powerpc, s390x
$ 
=

I confirm that adding the wheezy-security repository is enought to build
a wheezy-backports without changing anything in the current Debian
sources on GitHub.

Since we currently use this extension, I am interested in a
wheezy-backports and I could maintain it by myself, but only once it
reaches testing and anyway not before the next 3 months.

Thx, bye,
Gismo / Luca


signature.asc
Description: Digital signature


Bug#692984: Expected upload of sogo-connector

2014-07-22 Thread Carsten Schoenert
Hello Luca,

Am 22.07.2014 13:59, schrieb Luca Capello:
 Any reason why this is not on Alioth?

there is no special reason, I just started last year the packaging and
wanted the repo putting in some official place to let other see the
current state. But I wanted be able to rebase and push my work without
any take care for on person depended on a repository in a more public
place like Alioth.

Once the package is accepted it will move to Alioth.

 Actually, using a *plain* wheezy chroot is not enough:
...
 Here is the reason:
 =
 $ rmadison icedove-dev | grep wheezy
  icedove-dev | 10.0.12-1  | wheezy| amd64, armel, armhf, 
 i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, 
 s390x, sparc
  icedove-dev | 17.0.10-1~deb7u1   | wheezy-security   | ia64, kfreebsd-amd64, 
 kfreebsd-i386, mips, mipsel
  icedove-dev | 24.5.0-1~deb7u1| wheezy-security   | s390, sparc
  icedove-dev | 24.6.0-1~deb7u1| wheezy-security   | amd64, armel, armhf, 
 i386, powerpc, s390x
 $ 
 =
 
 I confirm that adding the wheezy-security repository is enought to build
 a wheezy-backports without changing anything in the current Debian
 sources on GitHub.

I know this circumstance, but thanks for hinting.

 Since we currently use this extension, I am interested in a
 wheezy-backports and I could maintain it by myself, but only once it
 reaches testing and anyway not before the next 3 months.

A backport is heavily depending on entering the testing release, so I
still don't care much about it in the current state. But as you wrote
it's more a question of the chroot to build a backport package. Right
know I would be happy to get the connector into testing before the freeze.

-- 
Regards
Carsten


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#692984: Expected upload of sogo-connector

2014-04-30 Thread Boris Barbour
I'm interested in obtaining the sogo-connector, as this seems to be the 
only way to sync contacts with owncloud. I'd prefer to get it through 
the debian repositories. The messages above suggest that it could be (or 
has been) uploaded, which is good news. When might we expect it to appear?



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#692984: Expected upload of sogo-connector

2014-04-30 Thread Carsten Schoenert
Hello Boris,

Am 30.04.2014 12:41, schrieb Boris Barbour:
 I'm interested in obtaining the sogo-connector, as this seems to be the 
 only way to sync contacts with owncloud. I'd prefer to get it through 
 the debian repositories. The messages above suggest that it could be (or 
 has been) uploaded, which is good news. When might we expect it to appear?

thanks for your interests!
I don't know then the FTP Team will allow the upload of the package, so
sorry, I can't say something promising right now.

You can rebuild the package by yourself using the current repository
which will be found on

  https://github.com/tijuca/sogo-connector

You will probably need a sid chroot to build the package, right know I
always used git-pbuilder and doesn't have cared about backports or so.
But that should not be a big problem to created a wheezy-backport
package too.

-- 
Regards
Carsten


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org