On 2021-07-27 Simon Josefsson wrote:
> Hi! I'm now resuming work on the libidn shared library transition, and
> I'm ready for the upload to experimental. I wanted to ping back here to
[...]
Hello Simon,
thank you, looks good to me.
cu Andreas
Hi! I'm now resuming work on the libidn shared library transition, and
I'm ready for the upload to experimental. I wanted to ping back here to
get more review. I'm following Andreas Metzler's outline, but included
some tweaks suggested by Simon McVittie. I decided to do some more
changes that a
On Fri, May 28, 2021 at 05:12:01PM +0100, Simon McVittie wrote:
> On Thu, 27 May 2021 at 16:53:45 +0200, David Kalnischkies wrote:
> > dpkg has the notion of "disappearing packages" (packages which have no
> > files left on a system) which could solve this cleanup compulsion, but
> > it is currentl
On Thu, 27 May 2021 at 16:53:45 +0200, David Kalnischkies wrote:
> So, here is a thing: I like transitional packages – because it means the
> package is not removed.
Right - it tells both apt and human users "this
replacement/removal/upgrade (depending how you look at it) is intentional,
according
On Thu, May 27, 2021 at 11:14:43AM -0700, Russ Allbery wrote:
> This is an incredibly useful thread that contains a lot of concrete
> recommendations for how to do library transitions smoothly. Could someone
> who has a moment collect this information into some how-to documentation
> and submit it
This is an incredibly useful thread that contains a lot of concrete
recommendations for how to do library transitions smoothly. Could someone
who has a moment collect this information into some how-to documentation
and submit it as a bug against developers-reference so that we don't lose
it?
(We
* Marvin Renich [210527 13:41]:
> packages use the same wording in the description, and searching for the
> specific word "transitional" has a non-negligible chance of a false
^
or "dummy"
...Marvin
* Andrey Rahmatullin [210527 10:38]:
> On Thu, May 27, 2021 at 10:10:15AM -0400, Marvin Renich wrote:
> > If transitional packages either had a debtag or a control file field
> > that identified them, then tools like deborphan could easily be made to
> > find and remove them
> Oh they already do (
On Thu, May 27, 2021 at 11:18:28AM +0100, Simon McVittie wrote:
> On Thu, 27 May 2021 at 08:30:11 +0200, Simon Josefsson wrote:
> > I do think it would be a wortwhile release
> > goal, at some point, to fix tooling so that dummy packages are no longer
> > necessary for package transitions.
>
> Tra
hi,
On Wed, May 26, 2021 at 11:28:24PM +0100, Simon McVittie wrote:
> piuparts only routinely tests relatively small installations - there are
> periodic QA tests done on larger systems like the union of all desktop
> tasks, but those are more expensive to run.
indeed, on jenkins.debian.net there
On Thu, May 27, 2021 at 10:10:15AM -0400, Marvin Renich wrote:
> > The one non-cosmetic reason I can think of why transitional packages
> > are potentially bad is that they aren't removed automatically, so systems
> > that have been upgraded many times can end up with a lot of transitional
> > pack
* Simon McVittie [210527 06:19]:
> The one non-cosmetic reason I can think of why transitional packages
> are potentially bad is that they aren't removed automatically, so systems
> that have been upgraded many times can end up with a lot of transitional
> packages;
If transitional packages eithe
Simon McVittie writes:
> On Wed, 26 May 2021 at 19:18:24 +0200, Simon Josefsson wrote:
>> Andreas Metzler writes:
>> > Why not use a versioned Provides *instead* of the dummy package?
>>
>> Yeah, I never understand exactly when these dummy packages are needed.
>
> My understanding is that they
On Thu, 27 May 2021 at 08:30:11 +0200, Simon Josefsson wrote:
> I do think it would be a wortwhile release
> goal, at some point, to fix tooling so that dummy packages are no longer
> necessary for package transitions.
Transitional packages have the huge advantage that they already work
(and the r
On Wed, 26 May 2021 at 19:18:24 +0200, Simon Josefsson wrote:
> Andreas Metzler writes:
> > Why not use a versioned Provides *instead* of the dummy package?
>
> Yeah, I never understand exactly when these dummy packages are needed.
My understanding is that they are usually still necessary for sm
Andreas Metzler writes:
> On 2021-05-26 Guillem Jover wrote:
>> On Tue, 2021-05-25 at 19:43:21 +0200, Andreas Metzler wrote:
> [...]
>> I'd probably instead make this a versioned Provides, so that the
>> transitional package can be removed right away from systems, it does
>> not interfere with t
On 2021-05-26 Guillem Jover wrote:
> On Tue, 2021-05-25 at 19:43:21 +0200, Andreas Metzler wrote:
[...]
> I'd probably instead make this a versioned Provides, so that the
> transitional package can be removed right away from systems, it does
> not interfere with the transition, and people can swit
On Wed, 26 May 2021 at 00:11:29 +0200, Simon Josefsson wrote:
> Andreas Metzler writes:
> > On 2021-05-24 Simon Josefsson wrote:
> >> I want to upload a new upstream libidn release into Debian, but upstream
> >> has done a shared library transition.
...
> >> Package: libidn11-dev
> >> +Section:
Andreas Metzler writes:
> On 2021-05-24 Simon Josefsson wrote:
>> Hi! This is for post-bullseye, but I appreciate guidance if anyone has
>> time. Shared library version transitions trigger uncertainty in me.
>
>> I want to upload a new upstream libidn release into Debian, but upstream
>> has d
On Tue, 2021-05-25 at 19:43:21 +0200, Andreas Metzler wrote:
> On 2021-05-24 Simon Josefsson wrote:
> > Generally, does things looks okay? Specifically, what about the
> > Breaks/Replaces/Conflicts? The d/changelog entry? Will the confusing
> > 'Replaces: libidn11-dev' for the libidn11 (!) pack
On 2021-05-24 Simon Josefsson wrote:
> Hi! This is for post-bullseye, but I appreciate guidance if anyone has
> time. Shared library version transitions trigger uncertainty in me.
> I want to upload a new upstream libidn release into Debian, but upstream
> has done a shared library transition.
mån 2021-05-24 klockan 20:45 +0200 skrev Timo Röhling:
> Hi Simon!
>
> * Simon Josefsson [2021-05-24 19:34]:
> > I want to upload a new upstream libidn release into Debian, but
> > upstream
> > has done a shared library transition.
> You should probably read the Release Team documentation [1] on
Hi! This is for post-bullseye, but I appreciate guidance if anyone has
time. Shared library version transitions trigger uncertainty in me.
I want to upload a new upstream libidn release into Debian, but upstream
has done a shared library transition. Bullseye will ship with
libidn11-dev instead
Hi Simon!
* Simon Josefsson [2021-05-24 19:34]:
I want to upload a new upstream libidn release into Debian, but upstream
has done a shared library transition.
You should probably read the Release Team documentation [1] on library
transitions if you haven't done so already.
Is the first step
24 matches
Mail list logo
