Your message dated Tue, 31 Jul 2018 19:12:58 +0200
with message-id <[email protected]>
and subject line Re: Bug#894739: dh_octave_check tests installed package
instead of source tree when called from debian/rules
has caused the Debian Bug report #894739,
regarding dh_octave_check tests installed package instead of source tree when
called from debian/rules
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
894739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894739
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dh-octave-autopkgtest
Version: 0.3.2
On Tue, Mar 27, 2018 at 09:40:49PM +0200, Sébastien Villemot wrote:
> On Mon, Mar 26, 2018 at 07:42:09AM +0200, Rafael Laboissière wrote:
> > I messed up a little bit with the Git repo for octave-control because I did
> > my changes, uploaded version 3.1.0-1 to unstable and pushed my commits
> > without noticing that Sébastien had already done some commits. This is the
> > reason I uploaded version 3.1.0-2 also.
>
> Sorry for having left the repo in a semi-finished state.
>
> The reason is that I stumbled across a bug in dh_octave_check when updating
> the
> package, and stopped there.
>
> Essentially, dh_octave_check will check the version installed under
> /usr/share/octave/packages, if there is one, instead of the version currently
> built.
>
> You can reproduce it easily by installing octave-control 3.0.0-5 in a chroot,
> and then built octave-control 3.1.0-2 in the same chroot. You will get a build
> failure.
>
> The reason is that it does the addpath *before* doing "pkg load all" (two
> times, for the .m files, then the .cc).
>
> Swapping the order of the two seems to fix the issue. However I did not test
> that it does not break the autopkgtest functionality.
>
> Right now I don't have the time to work on a proper fix. I can open a bug
> report if you want, please let me know.
Thereby opening a bug.
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.5.4
Le vendredi 06 juillet 2018 à 14:39 +0200, Rafael Laboissière a écrit :
> > * Sébastien Villemot <[email protected]> [2018-04-03 21:21]:
>
> > Package: dh-octave-autopkgtest
> > Version: 0.3.2
> >
> > On Tue, Mar 27, 2018 at 09:40:49PM +0200, Sébastien Villemot wrote:
> > >
> > > On Mon, Mar 26, 2018 at 07:42:09AM +0200, Rafael Laboissière wrote:
> > > >
> > > > I messed up a little bit with the Git repo for octave-control because I
> > > > did
> > > > my changes, uploaded version 3.1.0-1 to unstable and pushed my commits
> > > > without noticing that Sébastien had already done some commits. This is
> > > > the
> > > > reason I uploaded version 3.1.0-2 also.
> > >
> > > Sorry for having left the repo in a semi-finished state.
> > >
> > > The reason is that I stumbled across a bug in dh_octave_check when
> > > updating the
> > > package, and stopped there.
> > >
> > > Essentially, dh_octave_check will check the version installed under
> > > /usr/share/octave/packages, if there is one, instead of the version
> > > currently
> > > built.
> > >
> > > You can reproduce it easily by installing octave-control 3.0.0-5 in a
> > > chroot,
> > > and then built octave-control 3.1.0-2 in the same chroot. You will get a
> > > build
> > > failure.
> > >
> > > The reason is that it does the addpath *before* doing "pkg load all" (two
> > > times, for the .m files, then the .cc).
> > >
> > > Swapping the order of the two seems to fix the issue. However I did not
> > > test
> > > that it does not break the autopkgtest functionality.
> > >
> > > Right now I don't have the time to work on a proper fix. I can open a bug
> > > report if you want, please let me know.
> >
> > Thereby opening a bug.
>
> Could you please check whether this bug is still present in version 0.5.4
> of the dh-octave package?
I actually don’t have the time to setup the environment to reproduce
the bug.
But given the changelog description, I think it should be fixed by now.
Hence closing.
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
signature.asc
Description: This is a digitally signed message part
--- End Message ---
