** Description changed:
+ Rationale for FFe:
+
+ Zentyal is an open source small business server that provides a
+ graphical configuration interface for many Ubuntu services (squid,
+ dansguardian, firewall, qos, openvpn, dhcp, dns, samba, cups, etc.) and
+ integration between them.
+
+ These pa
I took a run through the revised packages this morning:
zbuildtools: OK
zentyal-ca: OK
zentyal-common: OK
zentyal-core: OK
zentyal-dhcp: OK
zentyal-dns: OK
zentyal-firewall: OK
zentyal-network: OK
zentyal-ntp: OK
zentyal-objects: OK
zentyal-openvpn: OK
zentyal-printers: OK
zentyal-samba: OK
zentya
Stephane, I'm not sure I agree with dropping this from the sponsorship
queue. What is the sponsorship queue for except reviewing items that
users feel are ready for upload?
Its certainly very *large* as a sponsorship item, but its a very
important contribution and should be reviewed in chunks by e
Some further conversation about native/non-native packaging on #ubuntu-
devel:
http://irclogs.ubuntu.com/2012/03/12/%23ubuntu-devel.txt
16:39 onwards
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I'm unsubscribing the sponsor team for now as reading through the backlog it's
not clear there's something ready for sponsorship just yet.
I also think this should be reviewed by the release team and a FFe granted
before considering an upload.
Please subscribe sponsors again once the packages ar
I've uploaded new versions of all the packages fixing the problems
reported by Cristophe and James. Please let us know if we have to do
anything else. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
I assume you release upstream tarballs? In that case, 3.0 (quilt) is
more appropriate for the distro packaging. You can use whatever you
want for upstream packaging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Hi Micah,
Zentyal is Ubuntu specific, we not only we develop for Ubuntu, but we
depend on specific Ubuntu components like upstart, the versions of the
packages in the Ubuntu archive, etc.
Eventually Zentyal could be ported to different distros but this would
be a new feature that will require cha
Not really, they are an upstream developing for Ubuntu, not something
specific to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Precise will ship totally broken ebox packages
Micah, Zentyal is Ubuntu specific.. so it makes sense as a native
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Precise will ship totally broken ebox packages
To manage notif
None of these packages should be native. Native packages are
distribution specific with no upstream tarball or VCS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Precise will ship tot
** Changed in: ebox (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Precise will ship totally broken ebox packages
To manage notifications abou
zentyal-firewall: no specific comments about this package; builds OK and
lintian clean.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Precise will ship totally broken ebox packages
To
General feedback:
Quite a few packages have upstart configurations prefixed with ebox:
./zentyal-users/debian/ebox.slapd.upstart
./zentyal-users/debian/ebox.ad-pwdsync.upstart
./zentyal-users/debian/ebox.slapd-frontend.upstart
./zentyal-users/debian/ebox.slapd-replica.upstart
./zentyal-users/debi
zentyal-dns: no specific comments about this package; builds OK and
lintian clean.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Precise will ship totally broken ebox packages
To mana
zentyal-network: no specific comments about this package; builds OK and
lintian clean.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Precise will ship totally broken ebox packages
To
zentyal-ca: no specific comments about this package; builds OK and
lintian clean.
zentyal-dhcp: no specific comments about this package; builds OK and
lintian clean.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
zbuildtools:
This package lacks Homepage and Vcs-* fields in debian/control
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Precise will ship totally broken ebox packages
To manage not
General comments:
It would be nice if all debian/copyright files conformed to:
http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
but that is optional.
All packages are defaulting to source format 1.0; its a minor change to
upgrade each to soure format 3.0 (native) and it makes i
zbuildtools:
Source package throws the following lintian warnings:
W: zbuildtools source: package-uses-deprecated-debhelper-compat-version 4
E: zbuildtools source: package-uses-debhelper-but-lacks-build-depends
W: zbuildtools source: ancient-standards-version 3.7.3 (current is 3.9.3)
I would sug
bzr branches for all of the packages in PPA can be found here:
https://code.launchpad.net/zentyal
Thanks Daviey!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Precise will ship totall
These are the comments from Christophe (huats), we are already working
on them:
zbuildtools
- The upstream source missed the COPYING file
- licensing is not OK: the GPL file pointed is /usr/share/common-licenses/GPL
(which is v3) while it should be v2 (according to the licence in the sourc
** Tags added: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Precise will ship totally broken ebox packages
To manage notifications about this bug go to:
https://bugs.l
Good idea Client, I've already filled in
https://wiki.ubuntu.com/JorgeSalamero/PerPackageDeveloperApplication so
as soon as they go thru the NEW queue we can upload further versions.
Thanks for your collaboration!
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Hi Clint,
Thanks for the reply. We understand the nature of the process and we
appreaciate your suggestion. Applying for Per-Package-Upload rights
seems the perfect solution, and we'll do it for sure.
Anyway, I suppose this is for the future, and we will still need your
help to upload the current
Hi everybody! Just an update on the status of this.
I've been talking with Christophe (huats) and he has agreed to help
shoulder the load on the review. I'll take a second look once he has
gone over things.
We cannot gloss over the NEW process, as it is in place to prevent us
from redistributing
Hi all,
In addition to the fixes we already did regarding the things you raised,
we have also make sure these new packages are 100% lintian clean.
We would really appreciate if anybody could have a look at them, again
in the same place: https://launchpad.net/~jacalvo/+archive/zentyal-
precise/.
A leaf package (or set of leaf packages) can easily get an FFe. But for
NEW packages we also need an archive admin to volunteer to review them
before we'll grant the FFe. The archive admins only guarantee NEW review
before FF.
--
You received this bug notification because you are a member of Ubun
Jorge,
We can request a Feature Freeze Exception if need be, and for packages in
universe...it's a much less intense process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Precise wil
Hi Clint and Micah,
what do you think about the approach I suggested? Sorry for pushing, but
we have only a few days to go.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928501
Title:
Prec
No need to say I agree with all points exposed by Jorge.
I've published new -1 versions of all the packages with the changes
suggested by Clint (thanks!).
Changes are: added the Breaks fields, the Vcs-Browser modification and
update the Standard-versions after checking the policy compliance.
I'v
IMHO we have to consider some variables in this situation:
* current ebox packages are broken and in an unusable state, proposed zentyal
packages at least work
* feature freeze is in 8 days and uploading new packages after that will be
more complicated
* Zentyal project is Ubuntu specific, would
Unless the archive admin accepting them is in the mood to do the full packaging
review, they might be rejected without a second review documented. Given the
situation with the current packages, my guess is that this would warrant a
feature freeze exception, but IANA release team member.
As for
Micah, good point, perhaps its better to make those X- fields. Though I
do believe the Zentyal team intendes to maintain the distro packages
themselves eventually, even then I think we'd want the packages
maintained in launchpad bzr so that other ubuntu developers can
collaborate on them.
And they
While having a reference to the upstream packaging branch is nice, Vcs-
Browser is meant to point to the distro packaging branch. Also, unless
the Debian dir content is the same except for a few name substitutions
or packaging upgrades, these packages should really have 2 people
reviewing them befo
For zentyal-common:
You have a Replaces: libebox (<< 2.0.100), which is good. However, I
suspect you'd like for libebox to be removed upon upgrade. If so, then
you will want to also have
Breaks: libebox (<< 2.0.100).
This will signal to apt that it should just remove libebox before
installing an
Jorge, this is a *massive* amount of review work. I hope you'll be
patient with us as we get through each item.
Is there any reason zentyal is broken up into so many source packages?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
37 matches
Mail list logo