On Sun, Apr 07, 2013 at 02:31:06PM +0200, Niels Thykier wrote:
> user release.debian@packages.debian.org
> usertags 677795 + wheezy-will-remove
> thanks
>
> On 2013-04-02 13:13, Didier Raboud wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debi
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
On 2013-04-10 10:16, Piotr Pokora wrote:
> 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 thes
On 10.04.2013 11:10, Piotr Pokora wrote:
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 Niel
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 N
On 10.04.2013 09:16, Piotr Pokora wrote:
OK, so can we keep midgard2-core 10.05.7.1-1?
It migrated to testing 300 days ago, while package which depends on
it
- php5-midgard2 - which also has been uploaded 300 days ago didn't
migrate?
After 300 days the easiest solution seems to be "will-remove
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) acc
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) accordingly, b
user release.debian@packages.debian.org
usertags 677795 + wheezy-will-remove
thanks
On 2013-04-02 13:13, Didier Raboud wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: rm
>
> Hi dear Release Team, hi dear midgard2-core and php5
Hi all,
I just stumbled upon this release-critical bug, #677795. As I read it, the
package had several packaging-related issues "summing up" to that serious bug,
filed two weeks before the freeze. Since then, in September, a package
supposedly fixing these issues has been uploaded
>> 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. Bo
Piotr Pokora wrote (04 Mar 2013 15:15:23 GMT) :
>>> 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] a
>> 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 o
Hi again,
and sorry for the flood..
Piotr Pokora wrote (04 Mar 2013 09:15:53 GMT) :
> 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.
Thank you.
intrigeri wrote (04 Mar 2013 10:16:35 GMT) :
> In any case, it looks now clear that "this needs to be unblocked else
> php5-midgard2 will be broken by midgard2-core" is no valid reason, in
> itself, to grant the unblock requested by #688966. Hopefully this will
> help the release team make a decisi
Hi Timo and Piotr,
Timo Jyrinki wrote (04 Mar 2013 07:41:40 GMT) :
> So, php5-midgard2 would need just a rebuild to pick up the new
> library name, together with uploading of midgard2-core.
Thank you for the prompt clarification!
Just to clarify even further, would a binNMU be enough? (The parag
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 ac
04.03.2013 00:54, intrigeri kirjoitti:
> "I am not sure due to #688966.
> If midgard2-core is accepted to stable, then php5-midgard2
> might break."
>
> If midgard2-core "might break" another package that's currently in
> testing, then IMHO this should be expressed in terms of binary package
Ah ok, didn't check it that much.
Thanks!
--
=Do-
N.AND
2013/2/1 Timo Jyrinki :
> Note that it's already prepared [1] and in NEW queue [2]. There's also
> the associated php5-midgard2 [3] that builds against the new package
> name. So I believe - unless it's not enough to address the rc bug - th
Note that it's already prepared [1] and in NEW queue [2]. There's also
the associated php5-midgard2 [3] that builds against the new package
name. So I believe - unless it's not enough to address the rc bug - this
is mainly about logistics, ie. the NEW queue package essentially
depending on simultan
If nobody is working on this bug, I'm offering to prepare an NMU
Nick
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Source: midgard2-core
Version: 10.05.6-1
Severity: serious
Hi,
thanks for the update to libgda5! This though made me have a look at the
midgard2-core source package, and I noticed several packaging mistakes.
- Build-Depends on gir1.2-gda-5.0. The introspection mini policy [1] says
that the cor
22 matches
Mail list logo
