Control: tag -1 pending
On Wed, Jan 22, 2014 at 16:51:10 +0100, Ondřej Surý wrote:
> Uploaded, thanks.
>
Telling the bug.
Cheers,
Julien
signature.asc
Description: Digital signature
Control: tag -1 confirmed
On Sun, Oct 27, 2013 at 13:56:34 +0100, Ondřej Surý wrote:
> And could we talk about the schedule of this transition? Seems like this
> will be last Berkeley DB transition ever :).
>
I guess if you want to switch db-defaults to 5.3 and are confident it
won't break too m
Hi,
could you please rename the transition tracker from db6.0 to db5.3?
The db5.1 to db6.0 transition won't happen due to the relicensing to
AGPLv3 that happened in db 6.0.x (and finally applied to the upstream
package in 6.0.20).
And could we talk about the schedule of this transition? Seems li
The git version was 8 commits behind, I did push the remaining changes few
hours ago.
Ondřej Surý
> On 15. 6. 2013, at 13:33, "Bernhard R. Link" wrote:
>
> * Ondřej Surý [130611 08:27]:
>> the information from Matthias was correct, and Berkeley DB 6.0 has been
>> released today, + packaged an
* Ondřej Surý [130611 08:27]:
> the information from Matthias was correct, and Berkeley DB 6.0 has been
> released today, + packaged and uploaded to unstable.
>
> db-defaults has been updated to 6.0 dependencies and uploaded to
> experimental.
Are those package also available somewhere while it i
Hi release team and Matthias,
the information from Matthias was correct, and Berkeley DB 6.0 has been
released today, + packaged and uploaded to unstable.
db-defaults has been updated to 6.0 dependencies and uploaded to
experimental.
I don't expect bigger problems with the transition since I thi
Am 06.05.2013 08:25, schrieb Ondřej Surý:
> On Mon, May 6, 2013 at 3:37 AM, Matthias Klose wrote:
>> Am 05.05.2013 23:22, schrieb Ondřej Surý:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian@packages.debian.org
>>> Usertags: transition
>>>
>>> Hi,
>>>
>>> it's tha
If the information is true then I don't mind waiting couple of months for BDB
6. I just wish Berkeley DB was acquired by some more open company :-/.
The new major version number is also often a culprit for breakages, although I
think I have fixed most if not all of them in 4->5 transition.
Ondř
Am 06.05.2013 08:25, schrieb Ondřej Surý:
> BTW do you have any information on db 6.x? I haven't seen any nor I
> have been able to find any information about it.
see http://bugs.python.org/issue17477
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsu
On Mon, May 6, 2013 at 3:37 AM, Matthias Klose wrote:
> Am 05.05.2013 23:22, schrieb Ondřej Surý:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: transition
>>
>> Hi,
>>
>> it's that time again we should prepare to switch to new Berke
Am 05.05.2013 23:22, schrieb Ondřej Surý:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> Hi,
>
> it's that time again we should prepare to switch to new Berkeley DB
> upstream version.
>
> This time it's the 5.1 to 5.3 t
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi,
it's that time again we should prepare to switch to new Berkeley DB
upstream version.
This time it's the 5.1 to 5.3 transition. I expect that there might
be another upstream releas
12 matches
Mail list logo