Hi!
AFAICT midgard2-core is the only package of the two having an open RC
bug affecting testing (namely, #677795). So keeping it while removing
php5-midgard2 from testing would not help us (from a release PoV).
Note that php5-midgard2 is only being removed because it
(Build-)Depnds on
Hi!
for the record, the discussion on #677795 lead to a release team
member write As it is, I am inclined to agree with OdyX's
observations, so I am tagging the bug as will-remove for now.
I don't feel I have the right hat to close these two unblock requests
(#688966 and #692358)
Hi!
After 300 days the easiest solution seems to be will-remove for now
but there hasn't been any single explanation why one package migrated
while the other not?
It didn't migrate because of #678531 still being considered as open by
the BTS until Niels fixed the bug state up in November
Only (and only) if midgard2-core[0] and php5-midgard2[1] are
distributed together.
Why?
Because php5-midgard2 provides language bindings to midgard2 content repository.
Unfortunately there's no php-gir bindings. Testing distribution has
midgard2-core 10.05.7 and php5-midgard2 10.05.6. Both
Hi!
So, php5-midgard2 would need just a rebuild to pick up the new library
name, together with uploading of midgard2-core. The mentors link of
php5-midgard2 has expired, but if I recall correctly Piotr had only
indeed put it there with a changelog entry like rebuild, so there are
no actual
Exactly. There are no changes made to php5-midgard2 package, so it
only requires rebuild against fixed[0] midgard2-core package.
OK, this confirms #692358 and #688966 are totally unrelated, then.
Only (and only) if midgard2-core[0] and php5-midgard2[1] are
distributed together.
In any other
-midgard2-10.05.7/debian/changelog 2012-06-16 00:06:45.0 +0200
@@ -1,6 +1,13 @@
+php5-midgard2 (10.05.7-1) unstable; urgency=low
+
+ * New upstream
+ * Use php5en(dis)mod in prerm and postinst. Closes: #667785
+
+ -- Piotr Pokora piotrek.pok...@gmail.com Wed, 13 Jun 2012 21:34:29 +0200
+
php5
Hi!
Wheezy has php5-midgard2 version 10.05.6-1.
If you want an unblock for version 10.05.7-1, you need to look at the
freeze
I am not sure due to #688966.
If midgard2-core is accepted to stable, then php5-midgard2 might break.
Also, you should include the debdiff between both versions in
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Please review php5-midgard2 for inclusion in wheezy.
This package has no single bug submitted.
It provides PHP extension for Midgard2 Content Repository.
PHP is currently the most popular language used with
Hi!
Please review midgard2-core for inclusion in squeeze.
I'm assuming you mean wheezy?
Of course wheezy :)
Package contains only one RC bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677795
and hopefully fixes one RC bug :-)
It's worth mentioning that lintian (-i -I -E
Hi!
this is a quick update on what's going on with your package in NEW.
We're holding it due to a library transition which would affect some
reverse
dependencies. As Wheezy is frozen, Release Team asked us to refrain from
processing packages which introduce unplanned transitions, as this
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Please review midgard2-core for inclusion in squeeze.
Package contains only one RC bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677795
New source package which fixes the bug (with renamed packages)
Hi!
Confirmed and reproduced. It'll be fixed ASAP.
I wonder though, why this doesn't happen on travis (for example),
where tests (and library loading) are run frequently.
Piotras
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Hi!
I expect new release in two or three weeks, so then, I'll update
debian packages.
Another 3 weeks have passed.
Yes, I know. Sorry for being quiet.
Did the upstream release happen in the mean
time?
We have some issue with postgresql provider. At least tests started to
fail with it
Hi!
Since it is May now, I wanted to kindly ask what the current state is.
Any progress since we last talked? Any blockers getting midgard2-core
updated?
Upstream is updated and tested against libgda 5.0.
I expect new release in two or three weeks, so then, I'll update
debian packages.
Hi Piotr,
Hi!
did you have time to look into this?
The plan is to depend on 5.0 since May 2012.
https://github.com/midgardproject/midgard-core/issues/135
http://mail.gnome.org/archives/gnome-db-list/2012-January/msg7.html
Piotras
--
To UNSUBSCRIBE, email to
Given that wheezy is planned to be frozen around June/July, seeing the
switch happen sooner rather then later would imho be good as it would
give more time for testing.
Yes, you are right. But currently we have enough problems with libgda
4.0 and 4.2 available here or there. Depending on 5.0
Hi!
This issue is fixed in upstream.
The new version is expected to be released in mid February.
Piotras
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi!
| The following packages have unmet dependencies:
| python-midgard2 : Depends: python ( 2.7) but 2.7.2-9 is to be installed
| E: Broken packages
This package could be removed. No more upstream development since Python
and GIR does the job great.
Piotras
--
To UNSUBSCRIBE, email
W dniu 06.04.2011 11:57, Emilio Pozuelo Monfort pisze:
On 04/04/11 12:08, Emilio Pozuelo Monfort wrote:
Just to clarify, we mean dropping gir1.0 packages from unstable, not gir1.2
packages from experimental. This is temporary until libgda4 builds gir1.2
packages in unstable, of course. libgda
Note that this is the last bit for the gir1.2 transition. If you don't drop
the
gir1.0-midgard2 package from unstable, midgard2-core may be removed from
testing.
I doubt there's anything I can do.
There is: you can build midgard2-core with --disable-introspection and remove
the
Hi!
According to Emilio Pozuelo Monfort from the gnome team, midgard2-core
should temporarily drop its gir bindings so we can go ahead with the
gir1.2 transition.
Can you keep midgard2-core and libgda4 in experimental?
IMO, it doesn't make sense to move it and disable/enable gir here and
Hi!
IMO, it doesn't make sense to move it and disable/enable gir here and
there. Just keep going with gir 1.2 transition and ignore midgard2-core
and libgda4 packages.
Not sure what you mean here.
I understood that either packages are uploaded to sid without gir ones
or they are removed
On 25.10.2010 20:36, Adam D. Barratt wrote:
Which of the fixes mentioned in upstream's changelog does the above
refer to?
* libgda/gda-debug-macros.h, libgda/gda-transaction-status.c: Removed
internal debug macros
Both of those changes are to code which is in #ifdef GDA_DEBUG blocks.
On 23.10.2010 19:44, Adam D. Barratt wrote:
Without this release, any derived application or library breaks to build
with GObject Introspection enabled.
Which of the fixes mentioned in upstream's changelog does the above
refer to?
* libgda/gda-debug-macros.h, libgda/gda-transaction-status.c:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please consider freeze exception for libgda4 package.
Recent, maintenance release fixes critical GObject Introspection issue.
Without this release, any derived application or
Here's GDA 4.0.11 upstream changelog:
http://ftp.acc.umu.se/pub/GNOME/sources/libgda/4.0/libgda-4.0.11.changes
4.0.10 is not available as mentioned in changes.
Piotras
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: wnpp
Severity: wishlist
Package name: midgard2-core
Version: 10.05.1.1
Author: Midgard Project
URL: http://www.midgard-project.org
License: LGPL
Description: Midgard Content Repository - Runtime Library
Midgard2 is an Open Source Content Repository. It provides an
object-oriented
Package: wnpp
Severity: wishlist
Package name: python-midgard2
Version: 10.05.1.1
Author: Midgard Project
URL: http://www.midgard-project.org
License: LGPL
Description: Python bindings for Midgard Content Repository
Midgard2 is an Open Source Content Repository. It provides an
object-oriented
Package: wnpp
Severity: wishlist
Package name: php5-midgard2
Version: 10.05.1
Author: Midgard Project
URL: http://www.midgard-project.org
License: LGPL
Description: Midgard2 Content Repository - PHP5 language bindings
Midgard2 is an Open Source Content Repository. It provides an
Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org
-Uploaders: @GNOME_TEAM@
+Uploaders: @GNOME_TEAM@, Piotr Pokora piotrek.pok...@gmail.com
Vcs-Browser: http://svn.debian.org/viewsvn/pkg-gnome/packages/unstable/libgda4/
Vcs-Svn: svn://svn.debian.org/pkg-gnome/packages
Emilio Pozuelo Monfort pisze:
On 28/01/10 21:30, Piotr Pokora wrote:
and removes uploader section.
Why?
I thought it was supposed to be not NMU, which means maintainer is an
uploader.
Piotras
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
Package: wnpp
Severity: wishlist
Package name: midgard
Version: 9.09.2
Author: Midgard Project
URL: http://www.midgard-project.org
License: LGPL
Description:
Midgard2 is an Open Source Content Repository. It provides an
object-oriented and replicated environment for building data-intensive
]
* Explicitly disable java.
- -- Emilio Pozuelo Monfort po...@debian.org Sun, 13 Sep 2009 17:43:33 +0200
+ [ Piotr Pokora ]
+ * New upstream release
+ * Removed duplicated libsqlite3-dev build dependency
+ -- Piotr Pokora piotrek.pok...@gmail.com Thu, 28 Jan 2010 11:31:29 +0100
+
libgda4
release
+ * Removed duplicated libsqlite3-dev dependency from source package.
+ * Added nmu to debian version. Fixes: source-nmu-has-incorrect-version-number
+
+ -- Piotr Pokora piotrek.pok...@gmail.com Wed, 28 Jan 2010 15:24:46 +0200
+
libgda4 (4.0.4-2) UNRELEASED; urgency=low
[ Emilio
Emilio Pozuelo Monfort pisze:
Hi Piotr,
Hi!
-Build-Depends: cdbs (= 0.4.41),
+Build-Depends: cdbs (= 0.4.65),
- libglib2.0-dev (= 2.16),
+ libglib2.0-dev (= 2.22),
- libxml2-dev (= 2.4.22),
+ libxml2-dev (= 2.7.3),
You didn't mention why you bumped these build dependencies in your
Josselin Mouette pisze:
- libxml2-dev (= 2.4.22),
+ libxml2-dev (= 2.7.3),
Same here. Why bump this dependency?
Because libxml2-dev can not be less than 2.7.3 in debian unstable. The
same applies to cdbs and libglib2.0-dev. It's absolutely safe from
upstream
37 matches
Mail list logo
