Bug#957230: Bug#966370: bsdmainutils: 12.1.3 removal of lorder breaks rdeps
> > I'm surprised it is actually used as it was pointed out to me that
> > the script
> > has been non-functional for quite a while.
>
> I do recall having an issue with it at one point a few years back and
> meaning to submit a patch to bsdmainutils to fix it, but resolved it
> one way or another without that, though can't find any evidence of
> that
> nor can I remember what the problem was. But regardless, it was
> working
> well enough for the freebsd-* packages to build fine.
My guess would be that its functionality is not needed at all.
> > Anyway, it cannot easily be "restored"
> > because the old bsdmainutils package does not exist anymore. All
> > tools except
> > ncal and calendar, which are now in their own package, are now
> > build out of
> > util-linux. Would it be possible to include lorder.sh in one of the
> > affected
> > freebsd packages?
>
> Yeah, it's possible, and that's no doubt what I'll end up doing. But
> I
I'm glad you agree, I will therefore close this bug.
> really don't appreciate all the breakage that's come about from
> bsdmainutils in the past few months. The util-linux handover was
Pas few months is a slight exaggeration but whatever.
> poorly-handled causing all kinds of problems across the archives
It is well documented that the changes caused more issues than
expected, but all packages received the necessary fixes as quickly as
possible. Having to go through NEW certainly caused some delay, too,
but again stuff like this happens, it's called unstable for a reason.
> (release and ports), and this removal of something, and thus
> *deliberately breaking* the package's "API", should have been done
> more
> carefully by checking whether anyone is actually using it (archive-
> wide
> rebuilds like is done for the new GCC versions is the
> easy-but-computationally-expensive way to do it). As it stands, I got
Come again please? Is this a joke or are you really suggesting we
should rebuild the whole archive to figure out if any package still
uses a non-functional tool in its build process?
> hit with a surprise set of RC bugs from the first archive-wide
> rebuild
> after this change landed, and I therefore have to react in a
> time-pressured way to fix it lest packages be removed from testing
> (though, arguably, testing doesn't matter so much for these given
> kfreebsd-* aren't release architectures). This really should have
So why do you bring up this point then?
> been
> found out first, with Severity: important bugs filed a month or more
> in
> advance of making the change, that can then be upgraded to be
> release-critical further down the line. So, please, never do a
> transition like this again.
Just for the record, I do not consider removing lorder.sh a transition
of any kind. Nor do I think removing a faulty tool that apparently had
no real functionality anymore warrants the kind of lecture you're
giving me.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De
Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Reply to: