This bug was fixed in the package mercurial - 6.7.2-1ubuntu2.2
---
mercurial (6.7.2-1ubuntu2.2) noble; urgency=medium
* Fix FTBFS with email.utils.getaddresses change introduced in Python
3.12.6 (LP: #2081117)
mercurial (6.7.2-1ubuntu2.1) noble; urgency=medium
* Cherry-pick
Release of this update is blocked on someone doing the QA for bug
2076152, with which this fix is bundled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070443
Title:
SRU: Fix critical regression i
Hello, we had the same issue when updating our Mercurial server from Ubuntu
22.04 to 24.04 LTS.
This leaded to repository corruption that was difficult to fix, so it's really
critical.
I confirm that applying the proposed update fixed the issue.
Do you know when the proposed update will be availa
Any updates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070443
Title:
SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4
To manage notifications about this bug go to:
https://bugs.launchpa
Looks good enough to me, thank you!
I've replicated the verification here just for completeness sake, but
hopefully this should be good enough for SRU team to approve during the
next review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
If my check not enough please revert my tag change
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070443
Title:
SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4
To manage notifications about
Test locally on Kubuntu 24.04.1 with test plan above
Version berofe 6.7.2-1ubuntu2
hg verify before commit - all right
hg verify after commit - 3 errors
Enable proposed in software-properties-gtk
sudo apt update
sudo apt install mercurial/noble-proposed
Installed 6.7.2-1ubuntu2.2 over 6.7.2-1ubu
So this failed to build. I know Dave is working on it, but just a note
that the call for testing above is invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070443
Title:
SRU: Fix critical regr
Hello Gleb, or anyone else affected,
Accepted mercurial into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/mercurial/6.7.2-1ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Following on from the xz-utils code injection, it's clearly critical to
validate binary blobs, so I tried to do that and am recording what I
found here.
https://lists.mercurial-scm.org/pipermail/mercurial-
packaging/2024-August/000737.html is the best validation I could find
for mercurial-6.8.1.ta
** Changed in: mercurial (Ubuntu Noble)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070443
Title:
SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4
T
Urgh ... one of the required patches includes a binary for the test
suite. So, that's going to be fun to include. However, I don't see any
(simple) way around it given current versions of mercurial apparently
don't even produce the type of changelog necessary to demonstrate the
corruption.
** Desc
I'll take a look, and see if I can put a minimal patchset together.
** Changed in: mercurial (Ubuntu Noble)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I am not working on this. Sorry, I don't see the time efforts worth the benefit.
If somebody is fixing this, please also fix LP: #2076152, or we will have two
competing SRUs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Ok thanks for the clarification
Sent from my iPhone
> On 5 Sep 2024, at 18:41, Robie Basak <2070...@bugs.launchpad.net> wrote:
>
> Sorry, I think you misunderstand. My comments were aimed at the Ubuntu
> developer who prepared an update that was not acceptable for the reasons
> I gave. My invol
Sorry, I think you misunderstand. My comments were aimed at the Ubuntu
developer who prepared an update that was not acceptable for the reasons
I gave. My involvement was as a reviewer to uphold quality standards
within Ubuntu which apply to any change we make in stable Ubuntu
releases. This is nec
>>> "RB" == Robie Basak <2070...@bugs.launchpad.net> writes:
> We can bump Mercurial up to 6.7.4 in Ubuntu 24.04. However, this
> requires someone to take one of the following three paths. See
> https://canonical-sru-docs.readthedocs-
> hosted.com/en/latest/reference/requirements/#new-upstream-mic
We can bump Mercurial up to 6.7.4 in Ubuntu 24.04. However, this
requires someone to take one of the following three paths. See
https://canonical-sru-docs.readthedocs-
hosted.com/en/latest/reference/requirements/#new-upstream-microreleases
1. If all changes being made are acceptable under normal S
** Summary changed:
- Critical regression in Mercurial 6.7.x < 6.7.4
+ SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4
** Description changed:
From mailing list mercurial-packag...@mercurial-scm.org:
Hello all,
Monday evening we got a report from a user about a critical bug t
19 matches
Mail list logo
