Bug reports for out of date packages?

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



Hi,

Arch's packages usually (almost always) get updated pretty fast and the system "don't create a bug report, just flag the package out of date to get dev's/TU's attention" works fine. But sometimes there exist packages both in community and in extra (I'm not sure about core but maybe even there) that don't get updated even after a significant time from the upstream's release (e. g. swt, amarok, jre or jdk from the nearest past). Shouldn't there be a time limit (two weeks? a month?) after which it would be OK to create a bug report? That way there could be a discussion about why that package hasn't/couldn't be updated and everyone would know where to look for the reasons without having to go through mailing list archives, bbs and so on.

Just a thought though.

Ondřej


--
Cheers,
Ondřej Kučera


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux