[RM] llvm-toolchain-snapshot package

Bug #1377235 reported by Matthias Klose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
llvm-toolchain-snapshot (Debian)
Fix Released
Unknown
llvm-toolchain-snapshot (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

the llvm-toolchain-snapshot package should not be part of any release. Currently this package produces binary packages which look like released versions, but they are not.

instead of clang-3.6, something like clang-snapshot-3.6 should be shipped, which changed package and binary names.

Matthias Klose (doko)
Changed in llvm-toolchain-snapshot (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Changed in llvm-toolchain-snapshot (Debian):
status: Unknown → Won't Fix
Revision history for this message
Matthias Klose (doko) wrote :

please compare this with the gcc-snapshot package. The package doesn't even include any binaries in the default PATH, so everybody using / relying on this package is aware that this really is a snapshot, not something to rely on. Different to Debian, Ubuntu does ship the gcc-snapshot package, however it doesn't interfer with any other supported package.

Revision history for this message
Simon Quigley (tsimonq2) wrote :

Bump; Gianfranco synced it and it's stuck in -proposed due to this bug. Matthias, is this still the case?

Revision history for this message
Matthias Klose (doko) wrote :

yes. why would it change?

Changed in llvm-toolchain-snapshot (Debian):
status: Won't Fix → Fix Released
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

it is time to let it go, debian unstable removed it, now only in experimental suite.

It won't be autosyncd.

summary: - the llvm-toolchain-snapshot package should not be part of any release
+ [RM] llvm-toolchain-snapshot package
Revision history for this message
Steve Langasek (vorlon) wrote :

Declining on behalf of archive admins. I understand it is deliberate that this package is present only in the devel-proposed pocket, and that's why this is a block-proposed bug. The move to experimental does not imply it should be removed from -proposed.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

it has been removed some days ago...
The reason is that the newly introduced binaries moves from snapshot to -N version and they *always* miss breaks/replaces relationships, making a pain for users to maintain.
This is why in Debian we moved snapshot to experimental only suite.

Since I'm the last snapshot maintainer, I don't want to manually have to sync it, neither to rely with incomplete/broken packages and people using them in their packages, because even if it is only on proposed pocket, nobody prevents people from using it in the archive, or in their ppa (this can't be forced, but I don't honestly care)

Revision history for this message
Sylvestre Ledru (sylvestre) wrote :

> The reason is that the newly introduced binaries moves from snapshot to -N version and they *always*
> miss breaks/replaces relationships, making a pain for users to maintain.

This has been fixed a few major versions ago.
The reason why I removed from unstable is to limit the number of versions of llvm in unstable.

As the maintainer, I don't mind if it is there or not

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.