[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1042960: marked as done (FTBFS: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 3 package 'gcc-doc')



Your message dated Fri, 18 Aug 2023 15:27:10 +0000
with message-id <E1qX1NW-00BUGK-96@fasolo.debian.org>
and subject line Bug#1042960: fixed in gcc-doc-defaults 5:27
has caused the Debian Bug report #1042960,
regarding FTBFS: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 3 package 'gcc-doc'
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 owner@bugs.debian.org
immediately.)


-- 
1042960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042960
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-doc-base
Version: 12.2.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

gcc-doc-base currently fails to build from source on amd64. From my build log:

| dh_gencontrol -pgcc-doc-base -- -v12.2.0-1
| dh_gencontrol -i --remaining-packages
| dh_gencontrol: warning: No packages to build. Possible architecture mismatch: amd64, want: all alpha amd64 arm64 armel armhf i386 ia64 mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el powerpc ppc64 ppc64el s390 s390x sparc sparc64 x32 any
| make[1]: Leaving directory '/<<PKGBUILDDIR>>'
|    dh_md5sums
|    dh_builddeb
| dpkg-deb: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 3 package 'gcc-doc':
|  'Version' field value '5:': nothing after colon in version number
| dpkg-deb: error: parsing file 'debian/cpp-doc/DEBIAN/control' near line 3 package 'cpp-doc':
|  'Version' field value '5:': nothing after colon in version number
| dpkg-deb: error: parsing file 'debian/gfortran-doc/DEBIAN/control' near line 3 package 'gfortran-doc':
|  'Version' field value '5:': nothing after colon in version number
| dh_builddeb: error: dpkg-deb --build debian/gcc-doc .. returned exit code 2
| dh_builddeb: error: dpkg-deb --build debian/cpp-doc .. returned exit code 2
| dh_builddeb: error: dpkg-deb --build debian/gfortran-doc .. returned exit code 2
| dpkg-deb: building package 'gnat-doc' in '../gnat-doc_12.2.0-1_amd64.deb'.
| dpkg-deb: error: parsing file 'debian/gccgo-doc/DEBIAN/control' near line 3 package 'gccgo-doc':
|  'Version' field value '5:': nothing after colon in version number
| dpkg-deb: building package 'gcc-doc-base' in '../gcc-doc-base_12.2.0-1_all.deb'.
| dh_builddeb: error: dpkg-deb --build debian/gccgo-doc .. returned exit code 2
| dh_builddeb: error: Aborting due to earlier error
| make: *** [debian/rules:117: binary] Error 25
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2
| --------------------------------------------------------------------------------
| Build finished at 2023-08-03T10:53:37Z

Regards
Aurelien

--- End Message ---
--- Begin Message ---
Source: gcc-doc-defaults
Source-Version: 5:27
Done: Dmitry Baryshkov <dbaryshkov@gmail.com>

We believe that the bug you reported is fixed in the latest version of
gcc-doc-defaults, 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 1042960@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Baryshkov <dbaryshkov@gmail.com> (supplier of updated gcc-doc-defaults 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 04 Aug 2023 13:56:04 +0300
Source: gcc-doc-defaults
Architecture: source
Version: 5:27
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers <debian-gcc@lists.debian.org>
Changed-By: Dmitry Baryshkov <dbaryshkov@gmail.com>
Closes: 1042960
Changes:
 gcc-doc-defaults (5:27) unstable; urgency=medium
 .
   * d/control: remove -guest from Salsa URLs
   * d/rules: add riscv64 to go_archs to sync with gcc-defaults
   * d/rules: Build using GCC 13 (Closes: #1042960)
   * d/control: regen using GCC 13
Checksums-Sha1:
 4d5c2a170d28297f5319dcfe09e38c53306fcc13 2081 gcc-doc-defaults_27.dsc
 c24ec2fa96af1c8d7ff8d07cfc3ff87ec3cfd3c8 31708 gcc-doc-defaults_27.tar.xz
 7c52b0d6370792a873a7e6aa6f36d00cb7740090 6601 gcc-doc-defaults_27_source.buildinfo
Checksums-Sha256:
 92f46038945b8a4dc9d9fb74d55f11dfc75c8c2b19f8560bacb77f62029de839 2081 gcc-doc-defaults_27.dsc
 cde1c083594064b68ef669444ce1585f40e15d85507a7a62116861330dc08599 31708 gcc-doc-defaults_27.tar.xz
 3da9a396131fc49f7c67cbf3abe1b30c5cf1fbbc094bb5eec49b51df64a94980 6601 gcc-doc-defaults_27_source.buildinfo
Files:
 637e2f6e7d05c84182c8663a92559ae7 2081 contrib/doc optional gcc-doc-defaults_27.dsc
 de8b783fd2b95959a04244f73f6378af 31708 contrib/doc optional gcc-doc-defaults_27.tar.xz
 6a999cb86fe921d0212c491f6832a2f5 6601 contrib/doc optional gcc-doc-defaults_27_source.buildinfo

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

iQFJBAEBCgAzFiEETHCElVyyY1bwuJV/izyKPgIpKNUFAmTM7SEVHGRiYXJ5c2hr
b3ZAZ21haWwuY29tAAoJEIs8ij4CKSjV8mEIAJJwd/6M5sF0zteIOeEeRQIS4Eb3
8pMMOFpEou2cqyZwLUkfXPRuaZJ3znVJB9I4BbYKdSQKBLcMet1v4yFh/Gg8uvG5
g130MkreN7ZU9NtwFSLQiXx6WHNbDFVPWDAPyCXPKvxc447Uagvqy4v9eBhwb9Bd
6g/9/w0+bm4pelTLY6GLiVD5I+1ajcMtrlkyJW7icmgTAoi2chFPL6KcVJH8OCM8
EIbD6vFhchtyK103puvcDvaKXCTRUW9l5a/DRlvDfNAGV5g/XeGMupasSM/pI7C+
wBlDASOot+vHCJNJAZb/nShtGJPgtJoYci52wgQLoDDf+rFMLfDTYYSPdPg=
=54ur
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: