Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40379 - add test to release testing

Attached to Project: Arch Linux
Opened by Andreas Boerner (aboerner) - Thursday, 15 May 2014, 16:09 GMT
Last edited by Allan McRae (Allan) - Thursday, 15 May 2014, 22:36 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

This bug is related to bug  FS#40377  (gcc 4.9 breaks gcov). A breakage like that should not happen.

This bug is about adding a test into a release test suite to catch future breakage of that kind before they are released to the public.

Additional info:
* gcc version 4.9 breaks interworking with gcov (compiler flags that generate profiling info)

This task depends upon

Closed by  Allan McRae (Allan)
Thursday, 15 May 2014, 22:36 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Thursday, 15 May 2014, 16:15 GMT
> This bug is about adding a test into a release test suite to catch future breakage of that kind before they are released to the public.
Isn't this a job for upstream? We already run their test suite in the PKGBUILD
Comment by Andreas Boerner (aboerner) - Thursday, 15 May 2014, 18:09 GMT
Well, maybe they have tested with an updated gcov (and/or glibc++ etc.); one that hasn't made its way into the arch repository yet...?

I just assumed (maybe I'm wrong) that the arch maintainers run a suite of tests before they make a new package available to the public
; to prevent breakages like this, where a new package (gcc) is added into the arch repository and depends on another package (gcov) also being updated.

???

Comment by Dave Reisner (falconindy) - Thursday, 15 May 2014, 18:12 GMT
> Well, maybe they have tested with an updated gcov (and/or glibc++ etc.); one that hasn't made its way into the arch repository yet...?
Then their testsuite would be inherently flawed, but you're correct that there's no guarantee they build with the same options/toolchain that Arch does. That's why we run the test suite, as well, during packaging.

> I just assumed (maybe I'm wrong) that the arch maintainers run a suite of tests before they make a new package available to the public
Yes, again, it's the upstream test suite.

I don't really see any packaging bug to be fixed here. If there's bugs in software (yes, this really does happen), then work with upstream to fix it.

Loading...