Bug#905839: [pkg-go] Bug#905839: debiman: autopkgtest fails with mdocml version 1.14.4-1
control: tag -1 + pending On Fri, Aug 10, 2018 at 2:59 PM, Michael Stapelberg wrote: > This is fixed upstream in https://github.com/Debian/debiman/commit/ > 210e94b3cf101d62b74211d0866f6308c6bee4db > > Feel free to do what is necessary to get the fix into Debian. > > On Fri, Aug 10, 2018 at 2:37 PM, Paul Gevers wrote: > >> Source: debiman >> Version: 0.0~git20180711.cb414bd-2 >> X-Debbugs-CC: debian...@lists.debian.org, mdo...@packages.debian.org >> User: debian...@lists.debian.org >> Usertags: needs-update >> Control: affects -1 src:mdocml >> >> Dear maintainers, >> >> Recently version 1.14.4-1 of mdocml was uploaded to the Debian archive. >> Your autopkgtest started to fail with the error copied below. >> >> Could you please investigate? It seems that you are comparing generated >> output with a reference. Looking at the text I can't spot obvious >> mistakes (but I may be missing details), so I think you need to update >> your reference to the new output. Please reassign this bug to mdocml if >> you think that package has this bug instead. This regression is >> currently delaying the migration of mdocml to unstable by 10 days, so >> cooperation to fix this swiftly is appreciated. >> >> Don't forget the set the appropriate Versioned (test) depends to let >> autopkgtest figure out which version is needed and maybe consider making >> your tests less sensitive to this kind of changes if they shouldn't >> delay or block other packages. If your tests aren't suitable for gating >> other packages, you can also mark them skippable and exit 77 in case of >> regressions. >> >> Paul >> >> https://ci.debian.net/data/autopkgtest/testing/amd64/d/debim >> an/796100/log.gz >> >> 2018/08/10 05:11:23 mandocd not found, falling back to fork+exec for >> each manpage >> --- FAIL: TestToHTML (0.00s) >> --- FAIL: TestToHTML/i3lock (0.01s) >> convert_test.go:92: unexpected conversion result: (diff from want >> → >> got): >> --- /tmp/debiman-314812002 2018-08-10 >> 05:11:23.148127262 + >> +++ /tmp/debiman-841037135 2018-08-10 >> 05:11:23.148127262 + >> @@ -7,65 +7,65 @@ >> >> >> >> + >> + >> NAME> href="#NAME">¶ >> i3lock - improved screen locker >> - >> + >> SYNOPSIS> href="#SYNOPSIS">¶ >> i3lock [-v] [-c color] >> - >> + >> DESCRIPTION> class="anchor" >> href="#DESCRIPTION">¶ >> i3lock is a simple screen locker like slock. After >> starting it, you will >>see a white screen (you can configure the color/an >> image). You >> can return to >>your screen by entering your password. >> - >> + >> IMPROVEMENTS> class="anchor" >> href="#IMPROVEMENTS">¶ >> >> - • >> - i3lock forks, so you can combine it >> with an >> alias to >> - suspend to RAM (run "i3lock && echo >> mem > >> - /sys/power/state" to get a locked screen after >> waking >> up your >> - computer from suspend to RAM) >> + • >> + i3lock forks, so you can combine it with an alias >> to >> suspend to RAM (run >> + "i3lock && echo mem > >> /sys/power/state" >> to get a >> + locked screen after waking up your computer from >> suspend to >> RAM) >> >> >> - • >> - You can specify either a background >> color or >> a PNG image >> - which will be displayed while your screen is >> locked. >> + • >> + You can specify either a background color or a PNG >> image >> which will be >> + displayed while your screen is locked. >> >> >> - • >> - You can specify whether i3lock >> should bell >> upon a wrong >> - password. >> + • >> + You can specify whether i3lock should bell upon a >> wrong >> password. >> >> >> - • >> - i3lock uses PAM and therefore is >> compatible >> with LDAP, etc. >> - >> - >> + • >> + i3lock uses PAM and therefore is compatible with >> LDAP, etc. >> + >> + >> >> >> OPTIONS> href="#OPTIONS">¶ >> >> - -v, --version >> - Display the version of your >> i3lock >> - >> + -v, --v
Bug#905839: [pkg-go] Bug#905839: debiman: autopkgtest fails with mdocml version 1.14.4-1
Dear Michael, On 10-08-18 14:59, Michael Stapelberg wrote: > This is fixed upstream > in > https://github.com/Debian/debiman/commit/210e94b3cf101d62b74211d0866f6308c6bee4db > > Feel free to do what is necessary to get the fix into Debian. I will not do anything to "get the fix into Debian". All I am willing to do is have the autopkgtest regression of debiman ignored to not hamper the migration of mdocml to testing. Paul signature.asc Description: OpenPGP digital signature
Bug#905839: [pkg-go] Bug#905839: debiman: autopkgtest fails with mdocml version 1.14.4-1
This is fixed upstream in https://github.com/Debian/debiman/commit/210e94b3cf101d62b74211d0866f6308c6bee4db Feel free to do what is necessary to get the fix into Debian. On Fri, Aug 10, 2018 at 2:37 PM, Paul Gevers wrote: > Source: debiman > Version: 0.0~git20180711.cb414bd-2 > X-Debbugs-CC: debian...@lists.debian.org, mdo...@packages.debian.org > User: debian...@lists.debian.org > Usertags: needs-update > Control: affects -1 src:mdocml > > Dear maintainers, > > Recently version 1.14.4-1 of mdocml was uploaded to the Debian archive. > Your autopkgtest started to fail with the error copied below. > > Could you please investigate? It seems that you are comparing generated > output with a reference. Looking at the text I can't spot obvious > mistakes (but I may be missing details), so I think you need to update > your reference to the new output. Please reassign this bug to mdocml if > you think that package has this bug instead. This regression is > currently delaying the migration of mdocml to unstable by 10 days, so > cooperation to fix this swiftly is appreciated. > > Don't forget the set the appropriate Versioned (test) depends to let > autopkgtest figure out which version is needed and maybe consider making > your tests less sensitive to this kind of changes if they shouldn't > delay or block other packages. If your tests aren't suitable for gating > other packages, you can also mark them skippable and exit 77 in case of > regressions. > > Paul > > https://ci.debian.net/data/autopkgtest/testing/amd64/d/ > debiman/796100/log.gz > > 2018/08/10 05:11:23 mandocd not found, falling back to fork+exec for > each manpage > --- FAIL: TestToHTML (0.00s) > --- FAIL: TestToHTML/i3lock (0.01s) > convert_test.go:92: unexpected conversion result: (diff from want → > got): > --- /tmp/debiman-314812002 2018-08-10 > 05:11:23.148127262 + > +++ /tmp/debiman-841037135 2018-08-10 > 05:11:23.148127262 + > @@ -7,65 +7,65 @@ > > > > + > + > NAME href="#NAME">¶ > i3lock - improved screen locker > - > + > SYNOPSIS href="#SYNOPSIS">¶ > i3lock [-v] [-c color] > - > + > DESCRIPTION class="anchor" > href="#DESCRIPTION">¶ > i3lock is a simple screen locker like slock. After > starting it, you will >see a white screen (you can configure the color/an > image). You > can return to >your screen by entering your password. > - > + > IMPROVEMENTS class="anchor" > href="#IMPROVEMENTS">¶ > > - • > - i3lock forks, so you can combine it > with an > alias to > - suspend to RAM (run "i3lock && echo mem > > > - /sys/power/state" to get a locked screen after > waking > up your > - computer from suspend to RAM) > + • > + i3lock forks, so you can combine it with an alias to > suspend to RAM (run > + "i3lock && echo mem > > /sys/power/state" > to get a > + locked screen after waking up your computer from > suspend to > RAM) > > > - • > - You can specify either a background > color or > a PNG image > - which will be displayed while your screen is > locked. > + • > + You can specify either a background color or a PNG > image > which will be > + displayed while your screen is locked. > > > - • > - You can specify whether i3lock > should bell > upon a wrong > - password. > + • > + You can specify whether i3lock should bell upon a > wrong > password. > > > - • > - i3lock uses PAM and therefore is > compatible > with LDAP, etc. > - > - > + • > + i3lock uses PAM and therefore is compatible with > LDAP, etc. > + > + > > > OPTIONS href="#OPTIONS">¶ > > - -v, --version > - Display the version of your > i3lock > - > + -v, --version > + Display the version of your i3lock > + > > > > - -c rrggbb, > --color=rrggbb > - Turn the screen into the g
