Preferred form of modification for binary data used in unit testing?

[Philipp Hahn]

Hi,

if a *previous* version of a software generated a *buggy* binary
database, that bug got fixed in a *newer* version and also some
*recovery* mechanism was added to allow reading that broken format
*once*, but there is no code the write the *broken* file again. For
*unit testing* the upstream developers added an *example* of such a
broken database to their test data.
What's the preferred form of modification for that data set?

* Should I include a copy of the *broken code* to generate that data?
* Declare that there in no preferred form for modification, as a
"open-save"-cycle with the current code will not re-create the bit
idencial file again.
* Remove the test data because it is not DFSG conformant and hope the
Debian build will never break the recovery code.
* Include instructions on how to re-build the broken version and give
instructions on how to maybe rebuild a similar broken file.

Philipp

PS: This question is motivated while working on a private build of
> E: keepassxc source: source-is-missing tests/data/keepassxc.opvault/default

Re: Source only upload

[Holger Levsen]

On Wed, Jul 15, 2020 at 02:37:26AM +, Paul Wise wrote:
> On Tue, Jul 14, 2020 at 4:06 PM Thomas Goirand wrote:
> > Better: we must mandate binary uploads, rebuild them, and make sure they
> > are reproducible. Then get the buildd upload the binary they build (or
> > the one from the uploader, since that's the same thing...).
> >
> > When the package isn't reproducible: reject the package and provide a
> > link to diffoscope. :)
> That would be nice, but I wonder if build-dep version skew will make
> it infeasible.

debrebuild from src:devscripts can create an sbuild commandline to install
exactly the build depends which were installed in the build which is about
to be rebuild, using the data from the .buildinfo file.


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Re: Source only upload

[Paul Wise]

On Wed, Jul 15, 2020 at 11:22 AM Holger Levsen wrote:

> debrebuild from src:devscripts can create an sbuild commandline to install
> exactly the build depends which were installed in the build which is about
> to be rebuild, using the data from the .buildinfo file.

So we have the buildds installing packages from snapshot.d.o based on
what the maintainer built the package with?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Re: Source only upload

[Holger Levsen]

On Wed, Jul 15, 2020 at 12:41:00PM +, Paul Wise wrote:
> So we have the buildds installing packages from snapshot.d.o based on
> what the maintainer built the package with?

no(t yet?)

also: s#what the maintainer built the package with#what the packages was built 
with#


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Re: Source only upload

[Paul Wise]

On Wed, Jul 15, 2020 at 12:45 PM Holger Levsen wrote:
> On Wed, Jul 15, 2020 at 12:41:00PM +, Paul Wise wrote:
> > So we have the buildds installing packages from snapshot.d.o based on
> > what the maintainer built the package with?
>
> no(t yet?)
>
> also: s#what the maintainer built the package with#what the packages was 
> built with#

I'm confused, Thomas proposed that packages are rejected unless the
buildd binaries are identical to the maintainer binaries. So the
buildds would need to run debrebuild and install build-deps from
snapshot.debian.org instead of from the main archive, in order to
avoid build-dep version skew between maintainer and buildd binaries.
Correct?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Re: Source only upload

[Holger Levsen]

On Wed, Jul 15, 2020 at 01:33:10PM +, Paul Wise wrote:
> > > So we have the buildds installing packages from snapshot.d.o based on
> > > what the maintainer built the package with?
> > no(t yet?)
> I'm confused, Thomas proposed that packages are rejected unless the
> buildd binaries are identical to the maintainer binaries. So the
> buildds would need to run debrebuild and install build-deps from
> snapshot.debian.org instead of from the main archive, in order to
> avoid build-dep version skew between maintainer and buildd binaries.
> Correct?

yes. (It's a proposal indeed. The above quote to me sounded like you were
trying to describe reality.)


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#965065: ITP: golang-github-mmcloughlin-avo -- Generate x86 Assembly with Go

[Roger Shimizu]

Package: wnpp
Severity: wishlist
Owner: Roger Shimizu 

* Package name: golang-github-mmcloughlin-avo
  Version : 0.0~git20200523.4439b6b-1
  Upstream Author : Michael McLoughlin
* URL : https://github.com/mmcloughlin/avo
* License : BSD-3-clause
  Programming Lang: Go
  Description : Generate x86 Assembly with Go

 avo makes high-performance Go assembly easier to write, review and
 maintain. The avo package presents a familiar assembly-like interface
 that simplifies development without sacrificing performance:
 - Use Go control structures for assembly generation; avo programs
   are Go programs
 - Register allocation: write functions with virtual registers and avo
   assigns physical registers for you
 - Automatically load arguments and store return values: ensure memory
   offsets are correct for complex structures
 - Generation of stub files to interface with your Go package

This is the new dependency of latest golang-github-cloudflare-circl:
- https://tracker.debian.org/pkg/golang-github-cloudflare-circl
- https://github.com/cloudflare/circl

Re: Bug#965044: RFP: gnome-podcasts — A podcast client for GNOME

[Andrei POPESCU]

Control: reassign -1 wnpp

On Ma, 14 iul 20, 23:22:20, Graweeld - (grwd) wrote:
> Package: gnome-podcasts
> 
> RFP
> Severity: wishlist
> 
> A simple, and responsive podcast feed player for the GNOME desktop.
> 
> License: GPL
> 
> Source: https://gitlab.gnome.org/World/podcasts#contributing
> 
> P.S. A package for the aarch64 would be also very neat. Much thanks!
> 
> Marek Ľach, Bc.

-- 
Looking after bugs filled against unknown packages


signature.asc
Description: PGP signature

Bug#965078: ITP: golang-github-adrianmo-go-nmea -- Go library for the NMEA 0183 protocol

[Francisco Vilmar Cardoso Ruviaro]

Package: wnpp
Severity: wishlist
Owner: Francisco Vilmar Cardoso Ruviaro 
X-Debbugs-Cc: debian-devel@lists.debian.org, francisco.ruvi...@riseup.net

* Package name: golang-github-adrianmo-go-nmea
  Version : 1.2.0
  Upstream Author : Adrián Moreno 
* URL : https://github.com/adrianmo/go-nmea
* License : Expat
  Programming Lang: Go
  Description : Go library for the NMEA 0183 protocol

Go library for the National Marine Electronics Association 0183 protocol.
.
NMEA 0183 is a combined electrical and data specification for communication
between marine electronics such as echo sounder, sonars, anemometer,
gyrocompass, autopilot, GPS receivers and many other types of instruments.
.
Features include:
 * Parse individual NMEA 0183 sentences.
 * Register custom parser for unsupported sentence types.
.
Supported sentences:
 * Sentence type | Description
- RMC| Recommended Minimum Specific GPS/Transit data.
- PMTK   | Messages for setting and reading commands for MediaTek
   gps modules.
- GGA| GPS Positioning System Fix Data.
- GSA| GPS DOP and active satellites.
- GSV| GPS Satellites in view.
- GLL| Geographic Position, Latitude / Longitude and time.
- VTG| Track Made Good and Ground Speed.
- ZDA| Date & time data.
- HDT| Actual vessel heading in degrees True.
- GNS| Combined GPS fix for GPS, Glonass, Galileo, and BeiDou.
- PGRME  | Estimated Position Error (Garmin proprietary sentence).
- THS| Actual vessel heading in degrees True and status.
- VDM/VDO| Encapsulated binary payload.
- WPL| Waypoint location.
- RTE| Route.
- VHW| Water Speed and Heading.
- DPT| Depth of Water.
- DBS| Depth Below Surface.
- DBT| Depth below transducer.

Bug#965084: ITP: golang-github-malfunkt-iprange -- IPv4 address parser for the nmap format

[Francisco Vilmar Cardoso Ruviaro]

Package: wnpp
Severity: wishlist
Owner: Francisco Vilmar Cardoso Ruviaro 
X-Debbugs-Cc: debian-devel@lists.debian.org, francisco.ruvi...@riseup.net

* Package name: golang-github-malfunkt-iprange
  Version : 0.9.0
  Upstream Author : José Nieto 
Arturo Vergara 
* URL : https://github.com/malfunkt/iprange
* License : Expat
  Programming Lang: Go
  Description : IPv4 address parser for the nmap format

IPrange is a library can use to parse IPv4 addresses from a string
in the nmap format.
.
IPrange takes a string, and returns a list of Min-Max pairs, which
can then be expanded and normalized automatically by the package.
.
Supported Formats:
 - 10.0.0.1
 - 10.0.0.0/24
 - 10.0.0.*
 - 10.0.0.1-10
 - 10.0.0.1, 10.0.0.5-10, 192.168.1.*, 192.168.10.0/24

Re: Pimp your shell - Debian developer tips?

[Samuel Henrique]

Sorry for being late to the discussion, but I'd like to share my
dotfiles and setup script that I use for my Debian Testing machines.

https://salsa.debian.org/samueloph/dotfiles

I just updated the README.md to explain the high level of it.

In summary, this is what I use to setup vim, atom, i3, bashrc,
powerline and my packaging tools.

Regards,

--
Samuel Henrique