Your message dated Mon, 23 Aug 2021 13:48:42 +0000
with message-id <[email protected]>
and subject line Bug#795552: fixed in fritzing 0.9.6+dfsg-1
has caused the Debian Bug report #795552,
regarding fritzing: please reconsider packaging strategy
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.)


-- 
795552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795552
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: fritzing
Version: 0.9.2b-1
Severity: wishlist

The current packaging strategy is very awkward one for fritzing
(fritzing-app) and fritzing-parts.  There are rooms for improvement to
address few issues.
 * Ease of cherry-picking patch from the upstream by moving to git
   ==> Please consider migrating to git (in alioth)
 * Ease of building from the latest upstream VCS source.
   ==> Current build script is not friendly for this.
 * Build all from one source.
   ==> This ensures package version matching betweeen fritzing and 
       fritzing-parts under the restrictive upload policy during 
       the pre-release freeze.
 * Reduce code duplication of source packages.
   ==> One source to build all binaries!

The available upstream sources:
 * fritzing-app-0.9.2b.tar.gz : fritzing source without submodule
      From https://github.com/fritzing/fritzing-app/releases
 * fritzing-parts-0.9.2b.tar.gz : submodule for parts
      From https://github.com/fritzing/fritzing-parts/releases
 * fritzing-0.9.2b.linux.i386.tar.bz2 : Compiled source with binary
      Contain both fritzing-app and fritzing-parts
      From http://fritzing.org/download/?donation=0
 * Source managed in git using submodule
      Source tree build from both fritzing-app and fritzing-parts repos.
      See https://github.com/fritzing/fritzing-app/wiki/1.3-Linux-notes

The current Debian packaging is done by odd combination:
   fritzing       from fritzing-app-0.9.2b.tar.gz
   fritzing-parts from fritzing-0.9.2b.linux.i386.tar.bz2

Proposed solution:
Although multi upstream source tarballs may be an elegant solution, that
may cause some extra work.  Let me propose a lazy solution.

|  Package all fritzing fritzing-data and fritzing-parts binary packages
|  from the DFSG processed fritzing-0.9.2b.linux.i386.tar.bz2 after
|  removing compiled binary and jar files.

This kind of packaging allows me to build the latest upstream VCS
version with minimal efforts from VCS.

FYI: I have folked upstream VCS and added Debian package history.
         https://github.com/osamuaoki/fritzing-app/branches
         (I have most my changes in local only for now.)
     I can not promise but I should be updating build script etc. soon.

-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: fritzing
Source-Version: 0.9.6+dfsg-1
Done: Georges Khaznadar <[email protected]>

We believe that the bug you reported is fixed in the latest version of
fritzing, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Georges Khaznadar <[email protected]> (supplier of updated fritzing package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 22 Aug 2021 22:51:03 +0200
Source: fritzing
Architecture: source
Version: 0.9.6+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Enrique Hernández Bello <[email protected]>
Changed-By: Georges Khaznadar <[email protected]>
Closes: 795552 858192 920044 962096
Changes:
 fritzing (0.9.6+dfsg-1) unstable; urgency=medium
 .
   * new upstream version
   * refreshed debian patches, deleted some.
   * upgraded version : debhelper-compat (= 13), Standards-Version: 4.6.0
   * changed the file debian/fritzing.install to take in account the new
     desktop file.
   * exported fritzing's icon to debian/fritzing.png for the desktop file.
   * removed the special target override_dh_install-indep
   * disabled the parallel build, which is not reliable.
   * as fritzing and fritzing-parts are currently built from separate
     source repositories, and according to last e-mail about this bug,
     Closes: #795552
   * Used Paul Wise's hints to simplify do-dfsg-tarball. Closes: #962096
   * files have been renamed in previous releases, fritzing->fritzing-real,
     and Fritzing -> fritzing. Closes: #858192
   * checked that fritzing correctly opens the interface.
     Closes: #920044
   * removed an unused target from d/rules, 'update-upstream-changelog'
   * added a target override_dh_auto_clean to clean files under
     config.tests/boost
   * modified and improved d/fritzing.install, d/fritzing-data.install and
     d/fritzing.manpages to fix all the errors triggered by dh_missing
   * modified the way fritzing is launched, in order to have the application
     copied to each user's ~/.local directory
   * increased the dependency on fritzing-parts, now it must have a release
     number >= 0.9.6~0
   * removed debian/fritzing.men since a destop file is provided
   * fixed d/copyright (duplicate field in l. 59, old-fsf-address)
Checksums-Sha1:
 eafb5cf8a9790edca90117e13b55bb1db603cd71 2131 fritzing_0.9.6+dfsg-1.dsc
 0a9d56b82473f67e0324d82c876dd3740a57e59e 7397348 
fritzing_0.9.6+dfsg.orig.tar.xz
 0c9935617719005d0887fdc37ef99c4fde34a441 24836 
fritzing_0.9.6+dfsg-1.debian.tar.xz
 1ae7d8587f877e215ee89d12e869109375301b6c 11453 
fritzing_0.9.6+dfsg-1_source.buildinfo
Checksums-Sha256:
 656c654c00d8040a35150681d8db374c207bb564f289cb29949b0d55ea88faa7 2131 
fritzing_0.9.6+dfsg-1.dsc
 e7f04d90e30af88c11249628cf7428d8045c0221a1b06cd00d9341da7bb189ad 7397348 
fritzing_0.9.6+dfsg.orig.tar.xz
 a194c6e05b8f4337513de3a7a7bfd4498dc72d23dcb1f509586ab015c1a5d61a 24836 
fritzing_0.9.6+dfsg-1.debian.tar.xz
 c25c18cbfbad89e36110c8d42ada71e208e1ea5496156c555c1eb2496f148eab 11453 
fritzing_0.9.6+dfsg-1_source.buildinfo
Files:
 da9dd23898246bda009cfad212fa339c 2131 electronics optional 
fritzing_0.9.6+dfsg-1.dsc
 f689ff57b854b3e55d7f202f6242d1a9 7397348 electronics optional 
fritzing_0.9.6+dfsg.orig.tar.xz
 81ca720f9e78d205f11805d693979032 24836 electronics optional 
fritzing_0.9.6+dfsg-1.debian.tar.xz
 83953f6c7b010230327aab7dcaf0286a 11453 electronics optional 
fritzing_0.9.6+dfsg-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmEjoDYUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjnBkA//U7IblaJTsExfXJT1ZrKrIEffC1MF
5lBXv2jxypN2d7p1wz96FYdcrLe/x/Zdorf3pB+SpwlFcefQSX7uAM406YSDHK5G
+79wU9qwsQUpD1mRXO8Ueu9PB3FIUqdNwF54ioxTspbTKuDGWM6RvFAidGzgLwKh
QSU81b0sw6qUwgdcDmzjLONmb2rmO5/fffS9B7WO/Vd5jr8c+JVhgk/2yw5Bi89I
pHCvkWfsmcAapxWx4Ub49Szpu72znuqq8wxXoqe2CEGoXA4yl/JKgqNHFYV8UBc0
WtiHeJo93MfOEXxG0nqsN56CU2oah8+ps/RTeKZjfIC6oBF2lFT7uOlaoLOooZ1d
Bqih6RloUTjCkb5yIQaS5gfQ3VP8C0xQT9IoZ34dqLC7Y5WBIG5YnA5cEMPD9Be0
KAxUzwjdFNyW1LFS0u32WBTlREJc+LlWaOPOt8CFllgWnDm0CycecMjyhfETubDO
xOwWQOLKUiAFw8ulKGkIy22Lj3WWobD7IgSdz2S6YS4028Wde/4BmIKghQPk7st5
x3P04XqEN/j/XFx2hf27wurvWHVZgx1MmhkQSMxaPzoCHaI1LhGNkTH6hOqrA4u/
IyIbWE46WQ1GrUBW0EHL1lKpmYa3CwItk7UnxDP4gfbOy7FqJUoC8D4upnX6MkiB
N/oz/Tvtu+8Xhn4=
=leRM
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to